[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.platform] Re: Generating extension point XML

Andy Steady wrote:
Hi,

Thanks for all these options, that are all completely foreign to me! Will do some investigating.

We want to be able to read the XML in the plugin.xml file for a specific extension, then update or replace it when the user chooses to generate default configurations from their model. This means we need to be able to read in from the plugin.xml also.

Do any of the options you suggest suit that requirement best?

The template option is designed for inserting generated templates into an existing plugin.xml ... i.e. when you client tries to add your extension, the templates available appear in the bottom of the add dialog. This is the option that has the best tooling support.


Using the PDE model directly means coding everything yourself and using internal PDE classes ... doable, but it'll be a lot of wandering through the code to figure out what's going on.

Later,
PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/workbench.htm