Re: [ jEdit-devel ] v0.1.1 release of SpeedJava

[Carlos Q. <car...@we...>]

On Tuesday 11 September 2001 02:49, you wrote:
Hi 

I'm also trying to develop something like this. I have already advanced in 
the definition of a LibraryManager and I was plaing to add also a 
ProjectManager, for the file management. I was hoping to have something ready 
in about a week. 

I decided to make it totally new because I believe in a different approach 
(using project definition files) and I think it is better to start from 
scratch. I'd be very interested to exchange ideas

Regards

>
> Regarding that classpath issue: I'm sure soon some people will come up
> and ask whether it will be possible to maintain the classpath settings
> of SpeedJava, JCompiler, JavaInsight and JSwatPlugin through a single
> tool, e.g. a project manager. It's being thought on. Right now, Calvin
> Yu is extending the ProjectViewer, he said, and I'm sure that someday
> it'll get the ability to store such settings. I am deciding between two
> options:
>
> 1) The ProjectViewer gets the ability to store simple String variables,
> e.g. CLASSPATH. The JavaInsight plugin then provides high-level
> functions to parse out the classpath of the current project, to
> add/remove entries and provide class info to other plugins. Or:
>
> 2) The ProjectViewer gets the ability to "mark" entries to be part the
> CLASSPATH. That is, you simply add a directory or jar file to the
> project and mark it, so that it belongs to the classpath. Your plugin
> will be noticed about changes to the classpath settings through events.
>
>
> The reason I tell you that here at this length is: I want to save you
> from putting too much work in an own classpath manager, because in the
> long-term future we want to solve this issue on more a general level.
>
>
> Regards,
> Dirk.