Forums

by JensRichnow >> Tue, 16 Jul 2002 0:24:20 GMT

I wonder what other users are thinking about the ability to create plug-ins for the Jade IDE. Obviously, there are two types of plug-ins:

(i) Just having the option to call a Jade application from a menu in the Jade SDK. This requires no interaction with the SDK as such and has a 'display' function.

(ii) Having the option to change the underlying data structure whereby all changes made in the plug-in feed through to the SDK.

(One might argue that there is the grey area in which certain plug-ins fall).

Option One would be a useful bonus and might extend the functionality of the SDK. An example could be a UML graphing tool displaying all or selected data as class diagrams, sequence diagrams etc. I mean, all the functionality and information for graphing is already there which can be transferred to a graphical representation. At least I find such a plug in useful (I have tried the RoseLink and see enough reasons to write such a plug in for Jade). There are many other examples of plug-ins for this category.

The second option requires a well-defined set of API's allowing updates to the existing data structure. Such a set of API would not expose Jade source code, etc. In many cases, the API's would merely define a public entry point. An example could be a Refactoring Tool (see the thread in this group), or the next step of a UML modeller whereby changes to the UML model feed back to the existing schema (I love this idea).

Many (non-)commercial IDEs for Java, C++, etc., support plug-ins and in doing so add value and functionality to the IDE. It is a step to a closer community-based environment in which both sides benefit a great deal.

Are there any thoughts on this idea?

Cheers

Jens

by JensRichnow >> Wed, 17 Jul 2002 0:39:41 GMT

Replying to one's own posting is kind of weird. But I have been 'talking' offline, e.g., outside the newsgroup about the original posting. It appears to me that there is a more general discussion behind this (and probably other) issues. I just cut and paste some of the stuff I wrote and attach it below. Maybe it puts the previous posting into the right light.

That's one of the main reasons for pushing for an API definition on the SDK level (Jade can build-in whatever safeguards they
have to). In the end, there exists the so-called Jade
programmer community. Why not put live into it form both
sides. If developers out there develop add-ins/plug-ins some
pressure re feature suggestions to Jade will be taken from
Jade. Most of the good IDE's for other languages experienced
a major push forward with opening up the SDKs/IDEs and allow
others to write plug-ins. And it doesn't matter whether they
are free, 'shareware', or heavily priced. To my mind its more
a matter of principle.

Any comments are greatly appreciated.

by PWCDEMO >> Thu, 22 Aug 2002 7:20:48 GMT

This would be a great way to allow people to modify the tool to their needs ahead of an official release.

Building in support for web service creation, refactoring, xUnit testing may be possible if an API was provided.

- Chris