>David Segall wrote on 07.09.2006 19:13:
>> That is probably the most convenient way to develop your
[quoted text clipped - 4 lines]
>initially designed to support stand-alone applications, the IDE beeing the first
>use of that.
Either I expressed myself badly or you are responding to a snipped
post. My point was that NetBeans was intended as a series of modules
that plug together and that you could produce a new stand alone
application by writing additional modules and deleting or modifying
the existing ones to suit.
Here's the original:
"Enigma" <shrivallabh@gmail.com> wrote:
>Enigma wrote:
>> Hi all,
[quoted text clipped - 23 lines]
>However, I do not have to restrict myself to developing the modelling
>tool as Plugin.
There is an implication in that sentence that if you use Eclipse or
NetBeans as platform that you will end up with a Plugin for Eclipse or
NetBeans. That is probably the most convenient way to develop your
application and, at least with NetBeans, that is the concept behind it
because everything is supposed to be a Plugin. However, when you
release your application it can be stand-alone and you can delete all
the functions in the IDE that your application does not need.
Thomas Kellerer - 24 Sep 2006 12:44 GMT
David Segall wrote on 24.09.2006 13:26:
>> David Segall wrote on 07.09.2006 19:13:
>>> That is probably the most convenient way to develop your
[quoted text clipped - 3 lines]
>> initially designed to support stand-alone applications, the IDE beeing the first
>> use of that.
> Either I expressed myself badly or you are responding to a snipped
> post. My point was that NetBeans was intended as a series of modules
> that plug together and that you could produce a new stand alone
> application by writing additional modules and deleting or modifying
> the existing ones to suit.
Hmm, this sounds (to me) a bit different than you first post, and it does
describe more or less want I wanted to say :)
Maybe there is a misunderstanding is in the definition of "plugin".
I think conceptually there is a difference between a plugin (as Eclipse defines
it) and a module (as NetBeans defines it)
The plugins in Eclipse could not live outside the Eclipse platform (as far as I
understood), but some (most?, many?) modules from NetBeans do not rely on the
NetBeans platform (they could rely on other modules though). The editor module
for example could be used without the NetBeans platform as far as I understand.
That's why I questioned your "everything is a _plugin_ in NetBeans" statement.
I think the NetBeans concept is more modelled around "component based
programming" than the Eclipse concept.
From an IDE user's perspective I don't think there is a big difference though.
And probably not from a plugin/module developers perspective.
I think it's an architectural difference.
Cheers
Thomas
Olle - 25 Sep 2006 09:21 GMT
I would also evaluate JetBrain's IntelliJ IDEA. I wrote two plugins for
it about a year ago and it was really simple to get it working and
test it (at least since they included the plugin development kit). The
documentation was weak/non existent at the time but as I understood
that became top priority just when I finished my plugins (we were too
many complaining:-).
Also if you are quick there is a competition going on:
http://plugins.intellij.net/contest/
PS I haven't written any plugin for Eclipse so I don't know how they
compare.