Clay,
That's fantastic news. I should start off by saying this is somewhat of an
intellectual exercise at this point pending what I'm able to get working,
and how well it works.
That said, I've done plenty of work with the Application/ACL class
libraries, both through .NET (via COM bridge) and directly in Java, so I
pretty much figured that was the way to go as far as interacting with the
control. I also know that the Java interface was (as of 5.3) WAY faster
than going through COM, especially when doing iterations over all nodes.
Our current system consists of Arbortext with some custom XUI to handle
normal CMS checkout/checkin, as well as some other common authoring tools
for citation management, etc. Anything outside of this we handle through a
.NET application to take advantage of more rich UI constructs, so our
general workflow lifecycle, communications with our library, research APIs,
etc.
Since the majority of our authoring is still done in XML, and all of our
writers are familiar with how Arbortext works, it doesn't make much sense to
move to something else. However, working with multiple interfaces all the
time, not to mention different languages on the programming side, is not
ideal. My thought is that if I can embed the portions of the editor that
we know and love within the other application, it would allow for better UI
controls... which sounds somewhat like what you're doing within IE.
Would you be able to send me a little code snippet of how you're embedding
within a webpage? I'm not terribly familiar with ActiveX in that way, and
have tried a couple of class IDs with no real luck:
<object classid="CLSID:ECDED982-9C55-4E04-8741-00995ACE7F09" id="Arb1"<br"/>width="200" height="200"></object>
<object classid="CLSID:2F891043-0DB4-11D3-9837-00104B3E04A0" id="Arb2"<br"/>width="200" height="200"></object>
I get a similar result when I try to put the control into a WinForms/WPF
frame, presenting a large grey box with nothing in it.
One last thing... are you able to handle multiple windows in some way? I
ask because using disconnected code in the past relies on the active window,
and loses context if more than one instance is running. This might not be
a problem with the AX control, since I'm guessing you are referencing it by
ID in the Javascript, but worth mentioning.
Thanks,
keith