PluginManager : fallen into disgrace ???

Am I the only one to miss the PluginManager one-click easy plugin
install/update? It is, well, was, a lot more usefull than the
pluginWebForm stuff.

Alain Ravet

3 comments

Yeah, the plugin registry is woefully out of date. :( I was working on a
new version of the Plugin Manager with a better interface and where plugin
info would be distributed (stored in individual files and, ideally, packaged
with the plugin) for easier management (see some of the discussions under
the Plugin Manager posts in this newsgroup for more info).

But, all that got interrupted when I (and about 2000 others) got laid off
from Sprint. I've just been focusing on job hunting since then and have had
little time to play. Bummer.

I'd be happy to send the latest code to anyone who wants to work on it (it's
not that pretty, though...the Plugin Manager was pretty much a late night
hack ;) I can't help but wonder, though, if any of it will be useful...I
wouldn't be surprised if JetBrains amazes us all with some ultra-elegant
plugin management system that makes the Plugin Manager look like poo. :)

chris

"Alain Ravet" <alain.ravet.list@wanadoo.be> wrote in message
news:b0n69u$qgm$1@is.intellij.net...

Am I the only one to miss the PluginManager one-click easy plugin
install/update? It is, well, was, a lot more usefull than the
pluginWebForm stuff.

>

Alain Ravet

>


0

Chris,

My message was not about you not improving your plugin, but about
plugin authors not updating the PluginManager xml config file.

Plugins that are available through the PluginManager could say so
in their Wiki pages. Your link rating would improve, and the increased
visibility would remind other authors to keep the config file up to date.

Alain

0

Hello Alain and Chris,
Maybe we finish idea of the PluginManager together right now. So my guess:
1. Each plugin must have special TWiki topic for documentation support and
download
2. Each plugin may have development topic for developers discussion about it
3. Each plugin topic must have special IntelliJPluginWebForm. In this form
user type path to jar (may zip also, example, binary.zip instead binary.jar)
4. Each plugin topic must have special IntelliJPluginWebForm. In this form
user type path to source archive (example, source.zip)
5. Also in this form author may type "Plugin Name" and "Plugin Vendor",
"Plugin Version" etc. But this is optional and will be used only on TWiki
search pages (not in plugin)

Thanks! Wait your response.


--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Alain Ravet" <alain.ravet.list@wanadoo.be> wrote in message
news:b0ojnf$sc3$1@is.intellij.net...

Chris,

>

My message was not about you not improving your plugin, but about
plugin authors not updating the PluginManager xml config file.

>

Plugins that are available through the PluginManager could say so
in their Wiki pages. Your link rating would improve, and the increased
visibility would remind other authors to keep the config file up to date.

>

Alain

>


0

Please sign in to leave a comment.