Hi Hussain, Thanks again for your reply;
> There is no simple, plain, button, having the native look of buttons on > your platform. Why? Because we have found them to be too big and less > flexible than command-buttons. But apparently you do not agree with this. No, I agree that system buttons are terrible things, unflexible and ugly. I was hoping for perhaps your own button (a Swing component) that one could use. Sometimes a button is very handy, especially when you want to apply a macro to a section. ... > > For example, if I use the insert-button(), I assume it looks through > > the DTD/schema and let's you add allowed elements, but when I use it > > it comes up unclickable, and I can't find any more info than the > > sparse section in the CSS manual. Any clues? > > Yes. You probably need to use insert-after-button(). insert-button() > inserts an element at caret position and this is probably not what you > want to do. Ah, thanks for that; you're right about that. Hmm, can I also insert after an Xpath conext? > If you really want to ``add'' elements (AKA smart insert), you need to > specify a command button with a hand-written menu of add commands (see > http://www.xmlmind.com/xmleditor/_distrib/docs/commands/ch06s02.html) Yes, this is currently what I'm doing, although I'm having some problems inserting based on the DTD given. Not sure where the problem lies, but if I don't have a #PCDATA section as part of an element, it won't allow me to insert other elements in it. It is like the caret won't select an element without a PCDATA. Do I have to use a full Xpath expression from root then to insert into such an element? > > Once again, I'm very impressed with the extensibility and power of > > XXE. Any plans for future additions of CSS 'position', floating boxes > > and so forth? Possibly a scripting engine and events, so that an > > 'onOver' event on a given element can pop up a toolbar, and so forth? > > Sorry but the answer is no to all the questions. You describe an > advanced ``editable Web browser''. We have more modest goals for our > editor, which we consider to be *half a tool*. The other half being an > intelligent XML backend we really would like to develop. It's ok, I understand, and I actually appreciate the simpler approach you've taken; it makes it simpler and more elegant. I guess in my quest for making pleasing templates I'm asking for all the whistles and bells I can think of. Would you, after all that, still consider something like the :hover pseudo class? Kind regards, Alexander -- "Ultimately, all things are known because you want to believe you know." - Frank Herbert __ http://shelter.nu/ __________________________________________________
