Looks good to me. And I also think that its not worth it to support Eclipse Classic for TapestryTools.
One note on this though: Or we will supply two update sites, one for Eclipse JavaEE, the other > includes XML editor jars for Eclipse classic. You shouldn't include XML editor to your update site. Just set it as prerequisite and your plug-in won't install until user resolve this dependency. Also, I believe, Eclipse has a feature of auto resolving dependencies, so maybe you should investigate this, just to make your update site light-weight. 2012/2/15 Gavin Lei <gavingui2...@gmail.com> > Hi All, > > In our coming light-weight TapestryTools, If we want to supply > autocomplete features, we must implement it in some special tml editor > (In current version TapestryTools,we use WTP's jsp editor). Now, we > want to remove Eclipse WTP dependencies, should find some other exist > editors. After talking with my GSoC mentor Igor Drobiazko, we thought > the most of tapestry users are using xml editor for tml files, and > decided to hook Tapestry components' autocomplete features into XML > Editor which is included in Eclipse JavaEE. > > As Eclipse classic does not include XML editor, it will require > Eclipse for JEE developers as a minimum. If there is not XML editor in > users' eclipse (or they are not using Eclipse Jave EE), people can > not install this feature, but they can still other plugin which do not > need XML editor. It means Eclipse classic users can have all the > TapestryTools' features besides autocomplete things. > > Or we will supply two update sites, one for Eclipse JavaEE, the other > includes XML editor jars for Eclipse classic. > > We will concentrate on simple and useful stuff first to confirm a > minimal feature set that works perfect, then consider option > functions. For example, if user have installed Eclipse Java EE, it > means they have installed WTP already. I want to reconstruct current > TapestryTools' code, supply Tapestry components' auto-complete feature > in WTP jsp editor as an option function in the future. > > Once more, we are still in project proposal prepare and solution > survey stage, hoping for more voices from Tapestry users and > developers, if you have any advises, please let me know. Thank you. > > -- > --------------------------------- > Best Regards > Gavin Lei (雷银) > Email: gavingui2...@gmail.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Dmitry Gusev AnjLab Team http://anjlab.com