Eclipse templates can be viewed under CVS repository to see what variations
are offered:
*Host:* dev.eclipse.org:/cvsroot/eclipse
*Repository Path: */cvsroot/eclipse
*Project: *org.eclipse.pde.ui.templates
On Tue, Dec 1, 2009 at 4:26 PM, Ramesh Reddy <rareddy(a)redhat.com> wrote:
On Tue, 2009-12-01 at 13:49 -0800, Michael Walker wrote:
> Ramesh, what's your take on providing template code vs.
> auto-generating code using the standard Eclipse mechanisms, and
> augmenting it as needed?
As I understand even the standard Eclipse mechanisms use some kind of
templates as a starting point to generate the "targets", like the ones
that Sanjay mentioned earlier in the thread.
When we say template code, we will put in something like
public class ${name}Connector extends Connector{
public Connection getConnection(){
return new ${name}Connection();
}
}
which will generate code like (assumed that name of my connector is
"Google")
public class GoogleConnector extends Connector{
public Connection getConnection(){
return new GoogleConnection();
}
}
obviously, there is big task of keeping the template code in-line with
Connector API/Base classes.
However, if there is alternative way to keep them in sync always, I
would prefer that. Do you think there is way in eclipse to accomplish
this? If so, can you please share your experience.
Thanks
Ramesh..