FixedLayerView

(Difference between revisions)
(Created page with '=== Use Cases, Requirements === # have a big picture view of "extension points" and service providers in the platform / RCP app # provide contextual documentation for #1 directly…')
m
Line 1: Line 1:
 +
''Part of [[PlatformPoolOfRcpTopics]] planning.''
 +
=== Use Cases, Requirements ===
=== Use Cases, Requirements ===
# have a big picture view of "extension points" and service providers in the platform / RCP app
# have a big picture view of "extension points" and service providers in the platform / RCP app

Revision as of 17:39, 26 November 2009

Part of PlatformPoolOfRcpTopics planning.

Use Cases, Requirements

  1. have a big picture view of "extension points" and service providers in the platform / RCP app
  2. provide contextual documentation for #1 directly available in IDE
  3. add new "extension point" and/or service provider for it
  4. locate/edit service provider module / class
  5. locate/edit module processing SP's for given extension point
  6. work with annotation-based registrations as well as layer based ones

Currently This layer in context node editor doesn't support #2, #5 and #6 at all and locating service provider class is clumsy.

On the other hand most of the use cases/requirements are already available for annotation-based regs. with Search, Find Usages and javadoc (as Jesse has already pointed out several times), except for perhaps #1. Notably it allows to locate consumer of the extension point (#5), as it is usually the module that declares the annotation. This is basically unsolvable for XML layers.

Possible Solutions

The easiest solution would be to let user edit important UI-related categories in separate branding editor (and not introduce annotations for them), add new annotations for entries that don't have one yet and are not important enough for dedicated editor and get rid of This layer and This layer in context nodes altogether. Special simple view for finding all annotations registering layer entries could be added to implement #1.

Alternative straightforward solution would be to somehow merge current layer view with annotations, e.g. by letting CoS create generated layers and use them. However there are several difficulties:

  • navigation from generated layer entry to the originating annotation would be hard or even impossible
  • editing entries in UI would require automatic generation/editing of Java code or very different handling of XML and annotation-based entries
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo