|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Adding another Source tab [message #976575 is a reply to message #976539] |
Thu, 08 November 2012 17:37 |
Konstantin Scheglov Messages: 555 Registered: July 2009 |
Senior Member |
|
|
Yes, if you have your own language, not based on Java (obviously) and XML, you need to clone most org.eclipse.wb.core.xml for editor with pages and something like JavaInfo or XmlObjectInfo, but for your language. You you will decide to follow XML editor, you will also copy and tweak org.eclipse.wb.internal.core.xml.editor.palette.PaletteManager, which in case of XML reads palette from plugin.xml palette extensions. But you don't have to do it exactly same way - it is done in WB only because we have many extension plugins to support additional libraries, such as Ext GWT, new layouts for Swing, etc. Same for reading palette commands from projects - if you don't need it, don't copy it from XML.
From WB core you can use as little as org.eclipse.wb.internal.core.editor.DesignComposite for property, palette viewer and GEF.
Actually I'm going to create new Designer for new language too, and will refactor WB core in the next days to extract Java from WB Core into WB Core Java.
Konstantin Scheglov,
Google, Inc.
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.08337 seconds