Le lundi 14 juillet 2008, Xavier Hanin a écrit : > On Fri, Jul 11, 2008 at 1:55 PM, Nicolas Lalevée > <[EMAIL PROTECTED]> > > wrote: > > Le vendredi 11 juillet 2008, Xavier Hanin a écrit : > > > Hi, > > > > > > As you may already know I'm currently working on Ivybeans [1], a kind > > > of IvyDE for Netbeans for which we have won a grant from Sun [2]. > > > > > > In this plugin I need to implement features very similar to what has > > > been done in IvyDE, like code completion for Ivy files. I also need to > > > > implement > > > > > some features which are not currently supported by IvyDE like settings > > > files code completion, or a way to easily add dependencies to an > > > existing Ivy file. > > > > > > These features are somewhat IDE agnostic (or at least can be based on > > > common roots), and I think it would benefit both community and all > > > users > > > > if > > > > > we shared what can be shared. So I consider refactoring some code in > > > > IvyDE > > > > > (especially code used for code completion) to make it reusable > > > (actually I've already done the refactoring...). > > > > Can I have a look to that new package ? > > In fact I was asking myself if a such refactoring could be integrated > > into Ivy. > > Sure, for the moment I've commited the code to IvyBeans: > http://code.google.com/p/ivybeans/source/browse/trunk/ivybeans/ivy-libs/src >/org/apache/ivyde/common/ > > Obviously the eclipse specific bits are missing from there, but you should > get the idea pretty easily.
got it. So yes there are code that would be great to share. Then I am wondering: should it have its own release cycle, or included in Ivy of IvyDE's ones ? Having it own release cycle, it brings more release work, and more dependency handling (on IvyDE part). Having it included in IvyDE seems to be overkill compared to the need of Ivybeans. Then there is the inclusion in Ivy: would it make sense to have some code completion algorithm on Ivy ? I don't think it would hurt. So I am in favor in integrating that common.ide in Ivy. Then I would prefer keeping it in IvyDE. And last have a new project with its own release cycle. Just my feelings, I won't put any veto there. Nicolas > > Xavier > > > > I'd move this code to a > > > org.apache.ivyde.common package, which could be used by any IDE plugin > > > developer. The next step would be to move this package in a separate > > > module, so that other plugin developers can use it without embedding > > > the whole eclipse plugin. Then I could add new features to this common > > > > package, > > > > > which would ease the reuse of work I do for Netbeans plugin in eclipse > > > plugin. > > > > > > So, do you think it makes sense to do that? Any objection? > > > > No objection on the idea of sharing common code. The question is then > > how. > > > > Nicolas > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
