6 comments
Comment actions Permalink

Alexey Efimov wrote:
> All not modified since 2003 year plugins placed to Plugins Archive:

Humm?! For less well informed people, or IDEA newbies, "archive" will
rime with "obsolete", although many of them are still perfectly working
with Aurora, current, and very usefull.

Alain

0
Comment actions Permalink

"archive" will rime with "obsolete",


And non-working, not needed, etc


Looking at the archived list, there really seem to be some plugins that are
obsolete (GoToClassPlugin?, CodeFolder?, ...), and others that are/may be
non working, so archiving these plugins is a good idea.

But I see many (very) useful plugins in the list. I don't really like hiding
good things in an archive page.


A better organization would be something like:

AllPlugins: all working/being worked on plugins
Archive: non working (and not mantained)/obsolete [and plugins the
owner(s)/developer(s) specifically want here?]
New: new plugins/new versions released in the last x days/months.

Another useful thing would be categorizing the plugins, as the list is
growing:

ConfigurationPlugins:

-> RemoveClipboardActions
-> RemoveEditorPopupMenuActions
-> ToolbarManager
...

IntentionPlugins:

-> AutoBoxingPlugin
-> IntentionPowerPack
...

EditingPlugins:

-> AutoNewline
-> CamelPlugin
-> CommentPlugin
...

VcsPlugins:

-> AccuRevPlugin
-> SubversionClient
...




0
Comment actions Permalink

CodeFolder works nice and it is useful, in Ariadna at least.

Marius

Carlos Costa e Silva wrote:
>>[...] "archive" will rime with "obsolete",


And non-working, not needed, etc


Looking at the archived list, there really seem to be some plugins that are
obsolete (GoToClassPlugin?, CodeFolder?, ...), and others that are/may be
non working, so archiving these plugins is a good idea.

But I see many (very) useful plugins in the list. I don't really like hiding
good things in an archive page.


A better organization would be something like:

AllPlugins: all working/being worked on plugins
Archive: non working (and not mantained)/obsolete [and plugins the
owner(s)/developer(s) specifically want here?]
New: new plugins/new versions released in the last x days/months.

Another useful thing would be categorizing the plugins, as the list is
growing:

ConfigurationPlugins:

-> RemoveClipboardActions
-> RemoveEditorPopupMenuActions
-> ToolbarManager
...

IntentionPlugins:

-> AutoBoxingPlugin
-> IntentionPowerPack
...

EditingPlugins:

-> AutoNewline
-> CamelPlugin
-> CommentPlugin
...

VcsPlugins:

-> AccuRevPlugin
-> SubversionClient
...



0
Comment actions Permalink

CodeFolder works nice and it is useful, in Ariadna at least.


I suspect both codefolder and gotoclass are useful in ariadna. I think that
both features have been implemented in Aurora.

That's also another thing that should be taken in account: plugins valid for
an idea version and obsolete in another version.


0
Comment actions Permalink

I agree with Carlos's comments.
In particular, I would to see categorizaion of the plugins. My categories would be slightly different from Carlos, the main difference the addition of a Tools Plugins to hold all the various plugins which integrate some 3rd party tool.

Configuration Plugins:
-> RemoveClipboardActions
-> RemoveEditorPopupMenuActions
-> ToolbarManager
...
Code Plugins:
-> AutoBoxing
-> CodeLogic
-> JavaSig
-> Intention PowerPack
-> Sequence
-> SimpleUML Diagram
...
Editor Plugins
-> AutoNewline
-> CamelPlugin
-> CommentPlugin
...
VCS Plugins
-> AccuRev
-> PerforceDirectPlugin
...
Tool Plugins
-> CloverPlugin
-> FaTPlug
-> GooglePlugin
-> HibernateTools
-> IdeaJad
-> IdeaJasmin
-> IdeaToAnt
-> JBossIntegration
-> JUnitTest
-> JarSpy
...
Misc Plugins
-> Connect 4
-> Tetris
...

0
Comment actions Permalink

I agree with all of us :) And i promise for pardon if i move to Archive realy used and fine plugins, this is my casuality.
So, i think we must reorganize plugins at IntelliJ.org.

I create development topic for this. Maybe we all can do somthing together :)

http://www.intellij.org/twiki/bin/view/Main/IntelliJPluginsHomeDev

Thanks!

0

Please sign in to leave a comment.