[news.eclipse.tools] Re: workspace startup event

[David Wegener <wegener@xxxxxxxx>]

I contributed to the discussion because I think having a hook into
startup/shutdown events is a reasonable request for plugin developers. 
I'm not currently developing a plugin.  I just wanted to point out a
possible compromise position.  I agree that this is something that could
be abused.  However, sufficiently documenting the process of hooking in
with examples of alternatives for common initialization tasks would help
the situation.

Eric's point of scheduled tasks is a valid reason to provide some sort
of mechanism to activate a plugin outside of a menu option, view, or
perspective.  One area where this might be helpful could be to refresh
the workspace on startup from a particular version control package.  I
haven't worked with CVS, so I'm not familiar with how it works. 
However, I have used other version control packages that require you to
place working copies of files into a working directory.  As files are
checked into the "repository" they need to be refreshed in the working
directory.  One plugin solution to this would be to provide the ability
to refresh working directory on startup and at regular intervals.

Another example could be a plugin that requires logging into a remote
system.  As a user I might prefer to login when the tool is started as
opposed to the first time I invoke a menu option.  Postponing the login
process would disrupt the flow of using the tool.  Normally when I
invoke a menu option, I expect it to occur right away,  I don't want to
be distracted by connection dialog the first time.

I've enjoyed reading this thread.  I think that it shows one of the
benefits of open source.  The users have direct contact with the
developers and can freely exchange thoughts about the product being
developed.  You don't need focus groups run by marketing types in a
contrived setting.

Dave Wegener

Scott Stanchfield wrote:
> 
> "Jeff McAffer" <jeff_mcaffer@xxxxxxx> wrote in message
> news:9ngpfo$ioa$1@xxxxxxxxxxxxxxxx
> > - The fact that several people want this feature indicates that there will
> > be several plugins doing startup code.  As this is early days in the life
> of
> > Eclipse, it seems like this number could get quite large.
> 
> This is one of the most interesting statements I've seen on this (and I had
> been thinking it a bit as well :)
> 
> The folks arguing for the feature kept saying few people will use it. But
> the number of folks arguing that exact point counters that argument ;)
> 
> <g>
> -- Scott
> 
> ==============================================================
> Scott Stanchfield    thetick@xxxxxxxxxxxx  http://javadude.com
> 
> Lead author of "Effective VisualAge for Java, Version 3"
>                                       http://javadude.com/evaj
> 
> VisualAge for Java Tips and Tricks     http://javadude.com/vaj
> 
> AWT & Swing FAQ Manager, jGuru.com
> Visit for Java Enlightenment!             http://www.jguru.com
> ==============================================================