Re: [ jEdit-devel ] java infrastructure

[Martin K. <mar...@ch...>]

Hi!

I just collated the answers to my initial mail into one mail, so here goes:

Robert Fletcher wrote:

>There's been discussion about it in the past. There's
>a plugin called Jane that's under development (or at
>least I think someone's still working on it) that does
>what you're suggesting, and a whole lot more besides.
>It's capable of parsing source code of libraries as
>well as class files which allows you to do things like
>accessing parameter names and javadoc text. The new
>version of my JTools plugin has optional support for
>Jane, but its own "extended classpath" as an
>alternative.
>
>Jane is pretty heavyweight though, and it would be
>really easy to put together a plugin that simply made
>extra classes available to other plugins if that's all
>that was required.
>  
>
Actually, I was just thinking about a pretty lightweight plugin which 
just holds the properties for a java project  (classpath, src path, 
compile path, maybe ant build file). I still prefer the more 
sophisticated features like parsing etc in different plugins, which use 
these basic settings.

Calvin Yu wrote (in answer to Robert Fletcher):

>
> I think these properties that you speak of should be stored by the
> project or session plugin, and then have a separate plugin which can
> render a UI for manipulating these properties.  One thing I don't like
> is having to add libraries used by all my different projects into Jane.
>  I've been waiting on the Project and Session plugins to implement
> property management, but last I checked it hasn't happened.
>
> Being the author of Jane, I would be open to extracting the library
> management portion of Jane as a basis for this new plugin.
>
> Calvin

I  have to disagree with you there, I think these properties AND an 
option pane to manipulate them should be independent from a general 
project/session plugin, since such a plugin has to cater for 
Python/C/C++/PHP/Perl(...) projects as well.

I also favour the ability to define more than one set of properties (== 
projects), so that one can choose a current set of properties which are 
then provided for different Java related plugins.

Calvin, the only place where I can find Jane is in the CVS repository, 
could you sum up the capabilities and the "release status" of it for me 
(just a few words), thanks!


Doug wrote:

>
> In short, yes, this has been requested/suggested/discussed many times. 
> Lots of people want it, but nobody has provided it yet.  Has anyone 
> started one or implemented one for themselves?
>
> I had an idea in my head for a small "JavaPath" plugin, but it kept 
> getting bigger until I didn't have time to start it :-)  I was also 
> thinking about how it needed to tie in to whatever "project" plugin 
> comes along.  Maybe I should just do it without that, though.
>
> What would be nice is something like Eclipse does where you can define 
> a bunch of jar files and have them remembered all the time, then build 
> a CLASSPATH based on selecting those existing jar files, new jar 
> files, and directories.  Maybe I'll should just put the resultant 
> CLASSPATH into a single history field so multiple paths can be easily 
> switched even without a project plugin.
>
> Then, of course, all the other Java plugins would have to be changed 
> to use a plugin like this.
>
> Anyway, just thinking out loud.

So, any of the plugin authors other than Calvin willing to change to 
support such a scheme? If it will be (widely) supported, I would be 
willing to start working on it, even though I haven't got a lot of time 
just now (tight deadline at work).

Feedback, please ....

      martin