ImprovedBrandingSupport69

(Difference between revisions)
m (Branding Support in NetBeans 6.9)
Line 1: Line 1:
-
''Branding Support in NetBeans 6.9''
+
''Branding Support in NetBeans 6.9, see also [[APISupportInNetBeans6.7#Visual Editing of NB Platform App UI|previous discussion for NB 6.7]].''
=== Use Cases ===
=== Use Cases ===
# hide unwanted menu items from platform module(s)
# hide unwanted menu items from platform module(s)
 +
# be able to see hidden items and show them again
# reorder menu / toolbar
# reorder menu / toolbar
# rename windows / actions / ..., change icons
# rename windows / actions / ..., change icons
# reorder / preview window layout
# reorder / preview window layout
 +
# true control over main window title
=== Requirements ===
=== Requirements ===
Line 11: Line 13:
* locate layer path for layer item
* locate layer path for layer item
* locate originating module (to potentially disable it instead of hiding items)
* locate originating module (to potentially disable it instead of hiding items)
-
* UI for editing branding (see also [[FixedLayerView69]])
+
* track the above-mentioned info across shadow files
 +
* UI for editing branding
 +
** overlaps with [[FixedLayerView69|Fixed Layer View]]
** visual customizers for window system layout is also discussed at [[PlatformPoolOfRcpTopics]]
** visual customizers for window system layout is also discussed at [[PlatformPoolOfRcpTopics]]
 +
 +
=== Possible Solutions ===
 +
More or less '''WYSIWYG editor''' of ''main menu'', ''toolbars'', ''window layout'' and ''window modes'' of RCP app, since this is what must be branded in let's say 95% of apps. Proposed editor would differ from ''This layer in context'' node in several ways:
 +
* It is invoked on RCP app project (suite) to allow for direct branding editing (currently must be hacked around by editing a module project and copy resulting layer/bundles into branding)
 +
* Probably deserves full editor window instead of nodes in Projects; especially for window layout and modes is (simplified) WYSIWYG editing much more useful than layer nodes
 +
* could also make getting rid of ''This layer in context'' editor altogether possible, see [[FixedLayerView69]] for details
 +
* it would probably not be necessary to listen on all 600+ layer file changes, a ''Refresh'' button would do; this would lead to better performance and faster development time
 +
 +
Alternative approach is to '''enhance current ''This layer in context'' node''' to be able to edit branding. Pros:
 +
* users are used to it
 +
* most of the code for UI already exists
 +
* shows "live" data (i.e. listens to changes)
 +
Cons:
 +
* deep node hierarchy in side window is not convenient for extensive editing and WYSIWYG editing cannot be easily added
 +
* shows branding items together with other service provider registrations, they are largely unrelated; again see also [[FixedLayerView69]]
 +
* shows "live" data (performance)

Revision as of 16:04, 26 November 2009

Branding Support in NetBeans 6.9, see also previous discussion for NB 6.7.

Use Cases

  1. hide unwanted menu items from platform module(s)
  2. be able to see hidden items and show them again
  3. reorder menu / toolbar
  4. rename windows / actions / ..., change icons
  5. reorder / preview window layout
  6. true control over main window title

Requirements

  • locate package for bundle or resource
  • locate layer path for layer item
  • locate originating module (to potentially disable it instead of hiding items)
  • track the above-mentioned info across shadow files
  • UI for editing branding

Possible Solutions

More or less WYSIWYG editor of main menu, toolbars, window layout and window modes of RCP app, since this is what must be branded in let's say 95% of apps. Proposed editor would differ from This layer in context node in several ways:

  • It is invoked on RCP app project (suite) to allow for direct branding editing (currently must be hacked around by editing a module project and copy resulting layer/bundles into branding)
  • Probably deserves full editor window instead of nodes in Projects; especially for window layout and modes is (simplified) WYSIWYG editing much more useful than layer nodes
  • could also make getting rid of This layer in context editor altogether possible, see FixedLayerView69 for details
  • it would probably not be necessary to listen on all 600+ layer file changes, a Refresh button would do; this would lead to better performance and faster development time

Alternative approach is to enhance current This layer in context node to be able to edit branding. Pros:

  • users are used to it
  • most of the code for UI already exists
  • shows "live" data (i.e. listens to changes)

Cons:

  • deep node hierarchy in side window is not convenient for extensive editing and WYSIWYG editing cannot be easily added
  • shows branding items together with other service provider registrations, they are largely unrelated; again see also FixedLayerView69
  • shows "live" data (performance)
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