Earlier this approach of my plugin was referred to as Jumpstart For Eclipse. That made me think and really, we have two options here:
1) Port my plugin to Rife allowing for users to configure the plugin to "manage" multiple Rife instances.
2) Create a Server Launch Configuration like Web Tools does for web projects so that when you run/debug that application, it will seamlessly fire up the server instance hosting that application, deploy it and initialize it.
These are two totally different things. Here are my thoughts on these:
1) This would be cool if we wanted to be able to have a user point to a live/existing Rife installation and work against it. With this setup, we would also be able to provide deploy-time visualization of the Rife components (Elements and such) within the Eclipse gui all as one view, similar to how WebLogic visualizes the different deployment types in my plugin. We would also be able to build around this with the other tooling ideas from the rest of the team.
2) This would be the least obtrusive requiring no configuration by the end user. The user would create a Rife project and then would run/debug their Rife project without any visualization of the project and no ties to an external Rife instance. The user would be able to configure different Launch Types, so that each type could have different environments like JVM and such. We could still build all features around this approach as well.
Summary:
Neither offer any edge over the other as far as the ability to deliver features to the end user. One it built around the developer but also provides an administrative portion to the plugin (Option 1) while the other is solely developer centric. It is really up to the community as to how to build this effectively but I do think that either solution will work with the outcome being the same.
Take care,
Jeremy
On 1/13/06, Geert Bevin <[EMAIL PROTECTED]> wrote:
> Yes, we are talking about the same thing. As I'm saying, if the IDE
> already provides features to ease RIFE development that much, why
> re-invent the wheel?
>
> I'll try a RIFE project template for NetBeans first before going for a
> full-blown plugin.
I don't think that anybody here wants to reinvent the wheel. What we do
want, I think, is to reuse what's there as much as possible; but extend
and integrate it to make your life as a RIFE developer easier.
I think that a project template is indeed the first step, since a plugin
will need to know about the classpath and your repository and such. You
need to declare that somewhere.
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
_______________________________________________ Rife-users mailing list [email protected] http://www.uwyn.com/mailman/listinfo/rife-users
