Something like this can definitely be done. Most of the time these internal pde classes cannot be used, unless they have an extension point which can be used. I shall check to see if the classes can be reused. If not we can definitely bring in similar code.
Had the same problem while trying to use the internal JarExport and ArchiveExport which are not published classes but are public classes with discourages access; however could tweak operation by subclassing.
Let me know if this feature is intended and I shall go ahead and spend time with eclipse sources which can be pretty laborious debugging at times with hundreds objects floating around within the plugin framework !!!
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?
Ramesh Reddy 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..