Hussein Shafie wrote:
> Marc Portier wrote:
<big_snip />
>>3. tox.openFile path
>>
>>instructs xxe to open the file in a new document window.
>>
>>Question: is there a way to do this? what is the method/object
>>this should go to?
>
>
> Your analysis is correct but it is absolutely impossible to do it this
> way, even by using the developer's docs and by writing a command in
> Java.
>
> The reason is that: for now, you can write commands that act on the
> document loaded in XXE (tox.readAttribute) but you cannot write commands
> that act on the XXE application itself (tox.openFile).
I understand, conceptually it could even make sense to wrap this
up under a different API then the command API (more like
<process> or something really new)
in fact I first tried with the <read> in side <process> if XXE is
not ready to open up that part of the API they could easily
provide some <open> or <edit> that behaves like the read?
>
> We'll try to enhance XXE in release 2.3 (released at the end of this
> month) to allow you to do that. We have always intended to do it but
> neglected to add it to the development schedule.
this is somewhat comforting, however the 'try' word leaves some
room for blind hope :-)
Since looking forward to something infinitely distant as 'the end
of the month' I like to volunteer for beta testing if such is
applicable?
Maybe to give you some more extensibility-inspiration:
Some other things I envision for my customization effort...
[1] I now have this <inline-group src="" /> pointing to a
different file that actually follows the same DTD as the original
one.
I would like to have an option where people can select a number
of elements in the current file and then choose in the menu
something like "Move to new external module" which first asks
them the name of that new module and then goes of creating that
file, opening it for edit (that might be optional), pasting the
selected nodes over there and finally replacing the selection of
nodes with the reference <inline-group src="new-module-name" />
in the file you started from.
[2] Also it would be nice to be able to use some xpointer
expressions in the css... I foresee the external module files to
have some root element with a @display attribute. It would be
nice to have that displayed in the referring document (not only
in the module itself)
maybe some
inline-group {
content: external-content( [xpointer-expr] )
}
where xpointer-expr becomes something like
concatenate(attr(src),'#/@display')
but could be any http://file/whatever#xpath
(maybe this is already achievable through creation of my own gadget?)
> --
> XMLmind XML Editor Support List
> xmleditor-support at xmlmind.com
> http://www.xmlmind.com/mailman/listinfo/xmleditor-support
>
regards,
and thx for your efforts.
-marc=
--
Marc Portier http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://radio.weblogs.com/0116284/
mpo at outerthought.org mpo at apache.org
