Well, if you support both options, you'll still have to maintain the template code if/when the API changes. If we leverage the Eclipse tool to generate code directly from the interfaces, then the advantage is that we get code that is compliant with the API. I know there's been talk of significantly changing the API to rework capabilities, which is why this comes to mind as a factor.

The wizard could start with the auto-generated code, and add any "hello world" code that might be appropriate. But that additional code would then have to be maintained. What kind of extra code or functionality did you have in mind here? If it's simple, adds usefulness, and is easy to maintain, then perhaps it is a better option to just go with that in a template.

Ramesh Reddy 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..