Re: [xngr-dev] xngr reusage notice

[Edwin D. <eda...@cl...>]

Hello Guido,

> I am actually speaking of the service part in this case - I was hoping
> to plug in my own element factory and have the xngr manage a tree
> with some gui actions attached. The gui would then call into the
> service plugin with the corresponding element.

My mistake, that sounds very interesting, however, I didn't foresee this
either.

> Now actually I did already have functionality available for a node but
> it was using my own element class. Here I can easily implement any
> interface needed by the xngr part - but XElement did turn out to be
> not enough.

I am not so sure anymore about the XElement and XDocument interfaces, maybe
we should just allow people to work with the underlying (extended) DOM4J
objects instead. (this seems to be what you're doing anyway?) They were
meant to hide complex DOM4J specific behavior.

> Reusing the widgetry is still ahead of me, work is underway with that.
> I could only start with it after making the necessary changes to the
> xngr xml tree handling. I hope to have a new widget group available
> in the next few days. For now, the xngr explorer/desktop is used as is
> with a seperate smacs service plugin loaded.

Good luck with that.

> I wouldn't like integrated approaches all too well - there are too many
> integrated approaches in the xml java world already, requiring dozens
> of dependencies on something.

The Avalon architecture is just so beautiful, don't think I can resist the
call ;-)

> My application is going to be standalone and simply something a
> compiler tool. Including commandline interfaces running without
> any gui whatsoever.

I had a look at some of the documentation and have no idea what you're
trying to do but it sounds interesting, I'll have a closer look at the code
sometime this week.

Good luck,
Edwin