On 8/26/05, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > Hi Dan, > I'm not a hardcore Eclipse guy but I've done some Eclipse work (including > the Axis2 ones :)) and have some knowledge of how Eclipse works. when > Eclipse GUI' s are needed (Lets say an editor winow) it has to implement an > Eclipse specific interface. because of this it is not really possible to > share it as a plugin and a standalone as-is!. > My approach to both the Axis2 plugin's was to have a 'core' which > implements the basic function of the tool. The eclipse version have the UI's > implemented in the Eclipse specific way and the swing vesrion has the UI > implemented in it's own way. All of them call the core functions to do the > work. > My guess is we should be taking a similar approach if we are to ship > different UI versions of the same tool.
thanks for the information :) i wondered whether it might be possible to ship a standalone version based on the eclipse platform just packaged as an application rather than a plugin but maybe swing would have some other advantages for myself. i don't really know anything about the eclipse internals and i'd need to learn that. i'd be much quicker hacking a prototype together in swing (which i know well). i'd be interested in learning what people think of the applet examples as a way of developing a design ideas. one approach would be for me to develop more complex swing examples of the ideas. > BTW I'm really interested in this tool Idea. As I mentioned in one of my > earlier mails it's an area we have to make improvements :) cool :) hopefully we might be able to find some gui gurus who fancy taking on this fertile ground... - robert
