Plugin repository

We've been thinking of launching a special plugin repository project that
would have both SOAP and web interfaces. I see it as a project developed by
all of us together so it implements the features we all need. In addition
to what Chris has been doing lately I would like to see categories, easy
ways of updating plugins, subscriptions with alerts and rating of plugins
(your suggestions...).

Existing projects:

jEdit Plugin Central (http://plugins.jedit.org)
Asp.NET control gallery (http://asp.net/Default.aspx?tabindex=2&tabid=31)
Macromedia Exchange
(http://dynamic.macromedia.com/bin/MM/exchange/main.jsp?BV_SessionID=@@@@189
0590908.1037569983@@@@&BV_EngineID=gadcfjfggidfbedcgemcgcfj.0&product=dreamw
eaver)
Borland Code Central
NetBeans Module Catalog (http://www.netbeans.org/catalogue/index.html)

The client would be included with Aurora.

Please let us know what you think,

Eugene Belyaev
JetBrains, Inc
"Develop with pleasure!"


12 comments
Comment actions Permalink

Great idea.

The number of plugins is getting larger, which is a good thing.

IntelliJ currently lacks both internal plugin management and external
repository, so it's a great step.

Amnon

"Eugene Belyaev" <beg@intellij.com> wrote in message
news:ar93gr$g94$1@is.intellij.net...

We've been thinking of launching a special plugin repository project that
would have both SOAP and web interfaces. I see it as a project developed

by

all of us together so it implements the features we all need. In addition
to what Chris has been doing lately I would like to see categories, easy
ways of updating plugins, subscriptions with alerts and rating of plugins
(your suggestions...).

>

Existing projects:

>

jEdit Plugin Central (http://plugins.jedit.org)
Asp.NET control gallery (http://asp.net/Default.aspx?tabindex=2&tabid=31)
Macromedia Exchange

>
(http://dynamic.macromedia.com/bin/MM/exchange/main.jsp?BV_SessionID=@@@@189
>
0590908.1037569983@@@@&BV_EngineID=gadcfjfggidfbedcgemcgcfj.0&product=dreamw

eaver)
Borland Code Central
NetBeans Module Catalog (http://www.netbeans.org/catalogue/index.html)

>

The client would be included with Aurora.

>

Please let us know what you think,

>

Eugene Belyaev
JetBrains, Inc
"Develop with pleasure!"

>
>


0
Comment actions Permalink

Quickly before I forget:
1) Bug tracking (it would be great to have access to the tracker for
plugins)
2) Packaging & update of plugins to the plugin repository should be possible
from ant script (a default plugin ipr and build.xml should be available for
plugin development) -> release number incrementation, jaring, uploading,...
3) Plugin update from IDEA (extension of what Chris has).

Jacques

"Eugene Belyaev" <beg@intellij.com> wrote in message
news:ar93gr$g94$1@is.intellij.net...

We've been thinking of launching a special plugin repository project that
would have both SOAP and web interfaces. I see it as a project developed

by

all of us together so it implements the features we all need. In addition
to what Chris has been doing lately I would like to see categories, easy
ways of updating plugins, subscriptions with alerts and rating of plugins
(your suggestions...).

>

Existing projects:

>

jEdit Plugin Central (http://pluginus.jedit.org)
Asp.NET control gallery (http://asp.net/Default.aspx?tabindex=2&tabid=31)
Macromedia Exchange

>
(http://dynamic.macromedia.com/bin/MM/exchange/main.jsp?BV_SessionID=@@@@189
>
0590908.1037569983@@@@&BV_EngineID=gadcfjfggidfbedcgemcgcfj.0&product=dreamw

eaver)
Borland Code Central
NetBeans Module Catalog (http://www.netbeans.org/catalogue/index.html)

>

The client would be included with Aurora.

>

Please let us know what you think,

>

Eugene Belyaev
JetBrains, Inc
"Develop with pleasure!"

>
>


0
Comment actions Permalink

In article <ar93gr$g94$1@is.intellij.net>, beg@intellij.com says...

We've been thinking of launching a special plugin repository project that
would have both SOAP and web interfaces. I see it as a project developed by
all of us together so it implements the features we all need. In addition
to what Chris has been doing lately I would like to see categories, easy
ways of updating plugins, subscriptions with alerts and rating of plugins
(your suggestions...).


I think that's a great idea- the SOAP interface especially can add great
value to your product by enabling things like Chris's plugin manager.

If you haven't already thought of it, a great enhancement to a plugin
manager feature would be the ability to dynamically load and unload
plugins. I'm well aware of the issues in dynamically loading plugins,
but, ultimately, it's a feature that would be very useful.

Regards,

Danny

0
Comment actions Permalink

It will be great to have plugins repository and integrated client in IDEA!
I have little expirience with Netbeans, there is integrated plugins manager and client in that ide.
All plugins update and download performed throught manager.
It very usable!

0
Comment actions Permalink

SOAP will be interested. :)
So i not sure, but Java Web Start using the SOAP protocol. MAybe using Java
Web Services technology?

Thanks

--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Eugene Belyaev" <beg@intellij.com> wrote in message
news:ar93gr$g94$1@is.intellij.net...

We've been thinking of launching a special plugin repository project that
would have both SOAP and web interfaces. I see it as a project developed

by

all of us together so it implements the features we all need. In addition
to what Chris has been doing lately I would like to see categories, easy
ways of updating plugins, subscriptions with alerts and rating of plugins
(your suggestions...).

>

Existing projects:

>

jEdit Plugin Central (http://plugins.jedit.org)
Asp.NET control gallery (http://asp.net/Default.aspx?tabindex=2&tabid=31)
Macromedia Exchange

>
(http://dynamic.macromedia.com/bin/MM/exchange/main.jsp?BV_SessionID=@@@@189
>
0590908.1037569983@@@@&BV_EngineID=gadcfjfggidfbedcgemcgcfj.0&product=dreamw

eaver)
Borland Code Central
NetBeans Module Catalog (http://www.netbeans.org/catalogue/index.html)

>

The client would be included with Aurora.

>

Please let us know what you think,

>

Eugene Belyaev
JetBrains, Inc
"Develop with pleasure!"

>
>


0
Comment actions Permalink

Hello,

I think plugins are the key to a great IDE. Especially with the amount of
open source java development, you can never release IDE versions quickly
enough to keep up to date with the latest development tools and libraries.
Anything that promotes plugins and makes them easier to build and install is
very good. Just take a look at Borland. Almost every new feature they add is
ripped off from a open tool plugin.

The following things would really be useful:
A plugin download client
Plugin version management
A central place to categorise, register, rate, download and request plugins
A open source project where plugins can be developed
A rich open-tool API (including offical support for things like PSI)

New / updated features could also be released (and sold) as plugins. For
example, not everyone wants a GUI builder. Why not sell it as a separate
plugin. That way you boost your income stream and you do not bloat your
software. It will also help you produce a very flexible Open API.

Also, I think it would be better if you could release the plugin client as a
plugin itself. Why force people to wait for the next version of the IDE. The
more plugins you have, the more developers will be attracted to your product
and the quicker it will develop. Without a strong community you will always
lose ground to Eclipse and Netbeans.

As for the site, check out http://eclipse-plugins.2y.net
Ideally, you would have:
Categories
A simple rating system (not like Code Centrals weird thing)
The ability to comment on the plugin
Number of downloads
Link to the developers home page
A wishlist

Cheers
Gavin





0
Comment actions Permalink

Perhaps a little bit offtopic, but it would be nice if the plugin repository runs routine
regression tests on all registered plugins and change the status if needed. I understand
that the whole plugin is hard to test, but it could test the initComponent and
disposeComponent methods, and provide a way for the developer to specify a TestSuite class
to run (perhaps in the plugin-info.xml). This also requires standard packaging of the
plugins. On each plugin's page there might be a compatibility chart and a dump of the
JUnit errors if any.

Regards, Dimiter

0
Comment actions Permalink

a plugin manager would be great but does it really belong in the ide? Depending on implementation it could slow the app down. It seems like with all the programming related features we are asking for in the ide that this would be a good one to make as a seperate tool.

0
Comment actions Permalink

I believe that there are two distinct issues:
1. Plugin manager, which runs on the client side (probably within the IDEA, but it may be a separate tool).
2. Plugin repository, which is a server-side application (web service).

0
Comment actions Permalink

Methinks just about everyone will need a plugin manager if the OpenAPI is powerful enough. Because if it is, there will be hundreds of cool plugins and we will all want to run at least a few of them (there are some very cool ones already).

I can't see a noticeable impact on performance, because the plugin manager should only use CPU-time when you interact with it or when it checks for updates at idle time (which you should be able to turn off). It might be implemented itself as a plugin, although I can see Jetbrains using it to provide updates for their own stuff (the plugins they ship today and will in the feature **Cough*GUI Builder*Cough**).

0
Comment actions Permalink

ehh...feature->future

0

Please sign in to leave a comment.