|Add propertysheet contributions to existing html editor [message #538523]
||Mon, 07 June 2010 20:21
Originally posted by: adataylo.cisco.com|
I've used this:
to get some content assist options into the existing .html, and .jsp
editors (i.e. it's not a new editor based upon html).
However, it appears that only the 1st propertySheetConfiguration
extension found is used (comment from method
* Returns a configuration for the given extensionType matching the
* targetID, if one is available. If more than one configuration is
* defined, the first one found is returned.
* @param extensionType
* @param targetID
* @return a configuration object, if one was defined
My question is how do I get new propertysheet contributions into the
editor without clobbering other contributions?
|Re: Add propertysheet contributions to existing html editor [message #539684 is a reply to message #539454]
||Fri, 11 June 2010 20:25
| Nitin Dahyabhai
Registered: July 2009
On 6/10/2010 2:44 PM, adam taylor wrote:|
> On 6/9/2010 8:32 PM, Nitin Dahyabhai wrote:
>> You can't, you'll have to declare your own extension to
>> org.eclipse.ui.editors and specify that as your target ID.
>> As a side note, the contentassistprocessor provisional configuration is
>> deprecated in favor of supplying a proposal computer in Helios
> If I wanted to go to the trouble of creating a new extension to sse
> which allows this functionality and contribute this back, is there any
> reason to suspect that this would be rejected? For example does the idea
> of what I suggest go against the fundamental goals of this project?
I think I'd have to understand what you're proposing, but if it has
anything to do with adding a "priority" field to the editorConfiguration
extension point, I'd reject it as the list of target IDs searched
already forms a prioritized list. But like I said, I'd need some
clarification on what's being proposed.
Eclipse WTP Source Editing and JSDT
Eclipse WTP, IBM
Powered by FUDForum
. Page generated in 0.02034 seconds