5 comments
Comment actions Permalink

Many of us feel plugins should stay plugins. An extra feature to support
means more bugs. Having IDEA be light was one original motivation for the
open API. We already see how much harder the EAP process has been for
3.0 vs. 2.5, with all the new features introduced.

Jon Steelman wrote:

I'm curious what the process is or will be for migrating a plugin into
the IDEA core... assuming that there is enough interest among
developers, assuming that IntelliJ wants to incorporate the features,
and assuming that the original plugin developer is agreeable. I wonder
how many people are using Workspaces. Can you tell how many downloads?

Once again, Chris, thanks for a great plugin.

Jon

Chris Bartley wrote:

>> Workspaces 0.8.2 is available at:
>>
>> http://www.intellij.org/twiki/bin/view/Main/WorkspacesPlugin
>>
>> Changes since version 0.8.1:
>>
>> * Added global options for pinning/unpinning of workspaces upon implicit
>> open/close.
>> * Added global option for Workspaces menu UI to specify what happens
>> when an
>> unpinned, open (i.e. marked with a black check) workspace is selected.
>> You
>> can choose to either have the workspace pinned or closed.
>> * Menu option "Close All Workspaces" is now only enabled if at least one
>> workspace exists.
>> * Menu option "Close All Non-Workspace File" is now only enabled if
>> one or
>> more non-workspaced files are open.
>> * Removed file closing prevention introduced in 0.8 (since pinning
>> does the
>> same thing and is more powerful).
>> * Fixed a (recently introduced) bug in the workspace creation and
>> configuration dialogs where excluded files were marked with a grey check
>> instead of no check.




--

Erb

==============================================================
"Most of you are familiar with the virtues of a programmer.
There are three, of course: laziness, impatience, and hubris."
- Larry Wall
==============================================================

0
Comment actions Permalink

I agree with that... to a degree, but a blanket position against
migration is, like most absolutes, troubling. I'm not sure what plugin
will become the first reasonable candidate for migration, but a rule
that says anything pluginized is off limits from becoming core
functionality is far too rigid. One possible benefit of plugins from
IntelliJ's perspective could be to observe others test out potential
core functionality that IntelliJ doesn't have the time to experiment
with especially if it is risky stuff. If a plugin implements that
functionality well and it turns out to be just what the doctor ordered,
then from IntelliJ's perspective that plugin could become a ripe
candidate for incorporating into the core. In that sense, broadly useful
plugins can be a stepping stone to core functionality. It will be
interesting to see whether and when anything migrates to the core.

Jon

Erb wrote:

Many of us feel plugins should stay plugins. An extra feature to support
means more bugs. Having IDEA be light was one original motivation for the
open API. We already see how much harder the EAP process has been for
3.0 vs. 2.5, with all the new features introduced.

Jon Steelman wrote:

>> I'm curious what the process is or will be for migrating a plugin into
>> the IDEA core... assuming that there is enough interest among
>> developers, assuming that IntelliJ wants to incorporate the features,
>> and assuming that the original plugin developer is agreeable. I wonder
>> how many people are using Workspaces. Can you tell how many downloads?
>>
>> Once again, Chris, thanks for a great plugin.
>>
>> Jon
>>
>> Chris Bartley wrote:
>>
>>> Workspaces 0.8.2 is available at:
>>>
>>> http://www.intellij.org/twiki/bin/view/Main/WorkspacesPlugin
>>>
>>> Changes since version 0.8.1:
>>>
>>> * Added global options for pinning/unpinning of workspaces upon implicit
>>> open/close.
>>> * Added global option for Workspaces menu UI to specify what happens
>>> when an
>>> unpinned, open (i.e. marked with a black check) workspace is
>>> selected. You
>>> can choose to either have the workspace pinned or closed.
>>> * Menu option "Close All Workspaces" is now only enabled if at least one
>>> workspace exists.
>>> * Menu option "Close All Non-Workspace File" is now only enabled if
>>> one or
>>> more non-workspaced files are open.
>>> * Removed file closing prevention introduced in 0.8 (since pinning
>>> does the
>>> same thing and is more powerful).
>>> * Fixed a (recently introduced) bug in the workspace creation and
>>> configuration dialogs where excluded files were marked with a grey check
>>> instead of no check.

0
Comment actions Permalink

As an example, I wrote SelectorPlugin but I expect (hope) that this will
become part of IDEA someday.

--
Jordan Zimmerman
Altura International
Catalog City
"Jon Steelman" <steelman@mindspring.com> wrote in message
news:aopf7f$mq1$1@is.intellij.net...


0
Comment actions Permalink

On Fri, 18 Oct 2002 14:38:56 +0000, Jordan Zimmerman wrote:

As an example, I wrote SelectorPlugin but I expect (hope) that this will
become part of IDEA someday.


What becomes of the licensing and intellectual property here? Are the plugins
donated freely back to IntelliJ to include, or do the plugin developers end up
getting a little royalty check, or a once off payment, or just a tingly
feeling?

Mark


--

-- \m/ --
"...if I seem super human I have been misunderstood." (c) Dream Theater
mark@talios.com - ICQ: 1934853 JID: talios@myjabber.net

0
Comment actions Permalink

I don't know about other plugins, but I didn't mean my code would be part of
IDEA. The functionality that SelectorPlugin provides should be part of IDEA.

--
Jordan Zimmerman
Altura International
Catalog City


0

Please sign in to leave a comment.