On 7/5/05, Leif Frenzel <[EMAIL PROTECTED]> wrote: > Hi Nimrod, > > > Will you consider having a version for Eclipse 3.0.x? > No, it was not planned to support Eclipse 3.0.x. Did you try the plugin > on top of 3.0, though? It may well be that it works (there is not that > lot incompatibility between these Eclipse versions, and I'm not sure > whether we use any of the new features or APIs).
I haven't tried it yet. But from the screenshots you provide on the site, this plugin looks very promising. Will do when I find the time later tonight... > > I use Eclipse 3.0.x and currently see no compelling reason to upgrade > > to 3.1.x. It's a hefty download and I am on dialup. 3.1.x seems to be > > only fixing bugs as well as adding features that I neither need nor > > use. And besides, the PHPEclipse plugin is only for 3.0.x at the > > moment. > That's an argument, but these things will probably change with time. For > us, it is a question of resources. If we have a lot of extra work to > support the older Eclipse versions, we can't do it. If it's just one or > two small fixes - no problem. There are some SWT widgets in 3.1 that are not present in 3.0. If you are using those then all bets are off for a 3.0 version. There are small API changes (mostly additional methods) that are in the runtime of 3.1 too. So I understand completely your position regarding this. I had a go at Eclipse plugin writing back in the 2.x days only to be burned with incompatibilities with each point release. By the time 3.x rolled out, there were major API changes that starting from scratch would be more practical than refactoring. > > Anyway, if you can please provide some screenshots where I can see the > > plugin in action, maybe I might be compelled to download Eclipse 3.1.x > > :) as having darcs integration with Eclipse would really be great > > right now. > There are some screenshots in Radek's tutorial at > > http://eclipsedarcs.org/doku.php?id=basic_tutorial > > which may give a first impression. The plugin currently supports adding > and removing for workspace files and a (very crude) record support. Looks good! Even at early stages. Do you also plan to support the following in future versions? o. Cherry-pick records - Gives a list of changed files (and optionally added files) and give the user choice of which changes will be included in the record command. o. Cherry-pick apply - Same with cherry-pick records but with patch bundles instead. For me these are really important since there a lot of times when I make several small unrelated changes in one coding session and record them later, cherry-picking patches based on which of them belong to a particular set of changes. It's pretty difficult to manage them from the commandline especially if you have a really short terminal. A GUI would really be nice where you can see the changes made, then check/uncheck the ones you want included/excluded in the patch. Lastly, your screenshots show a Java perspective there. Does it also work on other perspectives like C/C++ and PHP? These are the perspectives I mostly use as I haven't had any Java projects lately. -- _nimrod_a_abing_ v1sw5CPJYUhw5ln3pr8OUSck6ma8u7LBw3DWNTm5g/l7DaIs7Rr4e6t5Xb4Op1en3g5RZAHC _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
