> -----Ursprüngliche Nachricht-----
> Von: Mark Phippard <firstname.lastname@example.org>
> Gesendet: 20.09.06 15:49:49
> An: email@example.com
> Betreff: [Subclipse-users] Comment on proposed Subclipse changes
> 1) Look and Feel. Changed to use same icons as CVS (in many cases
> meaning no icons).
I think it would be best to make the look and feel configurable. CVS by default and
TortoiseSVN if the user wants it (or whatever the majority prefers). Even the used
icons could be configurable.
> 3) Removed "Add Keywords" option. I have a personal distate for this
> option because I do not think it is obvious everything it exactly does. I
> also think that all of the Properties management enhancements we have made
> now make this option unnecesary and redundant. Again, removing it helps
> usability by taking an option of the Team menu. I'd be particulary
> interested in thought on this one. I do not use this option so maybe it
> does something that the properties management does not. If so, I'd like
> to identify that and see if we can enhance the properties management to
> account for it.
It displays a list of the possible values for the svn:keywords property. A feature that
would be nice for other properties too. I think an extension point would be a good idea.
Thus it would be possible that others plugins contribute a dialog fragment to edit specific
> 4) This is mainly a technical change, but just changed the way that
> client adapters are loaded so that it is done via Eclipse plugins and
> extension points. One of the ideas here is that we would likely stop
> including JavaSVN with Subclipse, and instead it would be a plugin you
> could install separate that adds it as an option. You would likely get it
> from TMate, but we might include it in our Subclipse update site.
This is a useful change, even if all three plugins are delivered in one package.
> I think these changes are all good candidates for doing directly in
> Subclipse and including in the final 1.2.0 release. It would also better
> help us show the Eclipse community exactly what we want to contribute and
> I think it would help our usability. I would be interested to hear other
> opinions on these specific changes.
I would add another point, which should take place soon. A clear distinction in
the code base between subclipse internal classes/interfaces and classes/interfaces
which can be used by other plugins.
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Sep 21 18:04:29 2006