RE: [Monotone-devel] monoclipse pushed [SoC]

[stefan.buehler]

> -----Original Message-----
> From: address@hidden 
> [mailto:address@hidden On 
> Behalf Of zi bin cheah
> Sent: Tuesday, July 25, 2006 11:45 AM
> To: address@hidden
> Subject: [Monotone-devel] monoclipse pushed [SoC]
> 
> I've pushed my worked into the repository. You guy can pull 
> the branch ch.monoclipse.zibin-soc to take a sneak peek. 
> snapshot included here 
> http://woozla.jot.com/WikiHome/ScreenShots/screencapture.gif
> 
> What I have done is simply just a GUI interface for eclipse, 
> with the ability to run monotone commands of course. FTM, 
> Some parts might break though.
> 
> I've developed it on Eclipse 3.2 and JDK1.5. You guys can 
> import the files into a new project in Eclipse , and compile 
> it as eclipce application when running.
> 
> Some might wonder whats the relations between the 
> ch.monoclipse created by stefan buhler and mine. 
> 
> For those who are familiar with Eclipse, Stefan's plugin 
> deals with PERSPECTIVE mainly, and my PREFERENCE. thus 
> complementing each other.
> 
> Stefan's plugin allows eclipse to have a monotone 
> PERPSPECTIVE (others are JAVA PERSPECTIVE and etc). Inside 
> this monotone PERSPECTIVE, users are able to enjoys feature 
> mentioned by stefan (such as compare versions, view 
> development graphs etc...)
> 
> The one that i have produced is meant for the PREFERENCE in 
> eclipse. From eclipse's PREFERENCE, you can choose monotone's 
> certain actions such as LIST KEYS, CREATE PROJECT etcs.
> 
> p/s : Stefan, if you are reading this, I hope my explanation 
> of monoclipse is right.

in my opinion, most of the features you are implementing in your SoC project
should not be put to the 'Preferences' page, but should be accessible from a
resource's context menu via 'Team', where anyone who ever used an eclipse
plugin for a vcs expects them to be. 'Preferences' is the place to allow the
user to set properties like 'Default Key' (equivalent to the 'address@hidden'
command line option) or 'Disable loading standard lua hooks' (equivalent to
the --nostd command line option) - and even those properties might be
database- or branch-/project-specific and therefore would better be placed
either in the project's or the repository location's properties.

stefan b