We will have our own wizard, so we will have to provide our gateway to similar features either directy into eclipse code or use similar coding unless we decide to subclass New Class Wizard; not sure how far that will be possible. Anyway, having the feature will not be a problem; I shall look into the best way of doing it.

If there is a base class to begin with, we can prepopulate it in the wizard and then have the choice to use one of the existing templates or use something like generating from the interface/class. I am sure it will be more reflection code than any eclipse specific code probably ... I need to look at it. However it is better to use eclipse infrastructure as much possible, because everything in a workspace is a resource and eclipse manage concurrency very well.

Whenever you get time, please send me over the use-cases for the wizard with the template code as well as what exactly I need to generate if it's from some base class; a template for that would be good to, for me to look at the end result.

On Tue, Dec 1, 2009 at 5:52 PM, Ramesh Reddy <rareddy@redhat.com> wrote:

On Tue, 2009-12-01 at 15:12 -0800, Michael Walker wrote:
> I'm just referring to the "New Class" Wizard in Eclipse, which simply
> takes the interface in the connector API from which to start, and
> builds you skeleton code (screenshot below).
>
> I'm guessing there's a way to leverage this programmatically when
> building an Eclipse plugin?

But the idea here is to give user some basic required code automatically
akin to "hello world". Also, this way we can make them use of some of
the base classes we have written on top of the Connector API.

Using like new class wizard can be done in any standard JAVA project,
since this is extension plugin is a of a JAVA project you can do this
anyways, at-least that is my understanding, right Sanjay?

May be we can provide check box to "generate sources" on the initial
wizard that will either generate from template or provide clean slate
for them to start. What do you think?

Ramesh..