PlatformPoolOfRcpTopics

(Difference between revisions)
m
m (links to individual feature pages)
Line 51: Line 51:
** better into into Module Suite vs. Module Project, many new RCP users don't see a difference
** better into into Module Suite vs. Module Project, many new RCP users don't see a difference
-
* API Support: better branding support
+
* API Support: better branding support ([[ImprovedBrandingSupport69]])
** make it work also for Maven RCP projects
** make it work also for Maven RCP projects
** GUI to brand layers (including un-hiding of hidden entries), bundles, and icons
** GUI to brand layers (including un-hiding of hidden entries), bundles, and icons
Line 82: Line 82:
* API Support: allow debugging of RCP app down into Platform modules (need to allow easy download of sources and setting the sources for debugging)
* API Support: allow debugging of RCP app down into Platform modules (need to allow easy download of sources and setting the sources for debugging)
-
* API Support: add module deps dialog improvements
+
* API Support: add module deps dialog improvements ([[AddModuleDepsImprovements69]])
** improve the dialog UI and module+API descriptions
** improve the dialog UI and module+API descriptions
** automatically add all libraries on what a being added library depends on, e.g. Explorer API depends on Nodes API and so on
** automatically add all libraries on what a being added library depends on, e.g. Explorer API depends on Nodes API and so on

Revision as of 08:55, 26 November 2009

Contents

Platform topics

This document is a pool of topics for NetBeans Platform RCP after 6.8.

Unsorted, unprioritized, still to be processed in 6.9 planning.

Enterprise RCP

  • API Support & Maven ApisupportMaven69
    • improved support for Maven builds of RCP apps (important for developers who are already building their projects with Maven and need to reuse it for their RCP app; scales better than Ant for building more apps from bunch of reused projects)
  • interoperability with OSGi (OSGiAndNetBeans)
    • first needs investigation of feasibility, performance impact, etc...
    • OSGi container bridged with module system to allow coexistence of NB modules and OSGi bundles at runtime
    • dev support in API Support
    • not rewriting NB Platform to OSGi, not plug-and-play Eclipse module support, only ability to interlink with libraries available as OSGi bundles and maybe also packaging a project in NetBeans into OSGi bundle
  • improve JNLP support
    • deprecate non-jnlp.platform.codebase builds; bundle .jnlp descriptors with modules
    • custom servlet to match NB module system semantics?
    • use Pack200
  • interoperability with certain Enterprise technologies
    • have reference enterprise platform applications that would provide canonical solutions to the most common problems: login window/access rights, embedding spring, using osgi bundles,....
    • have enabling API Support wizards for Enterprise technologies (Spring, JPA/Hibernate,..) - helping the developers by adding the particular boilerplate code to their RCP app
    • docs and sample apps for Enterprise RCP apps on top of the Platform
      • simple JPA-based CRUD app
      • app connecting to RESTful webservices
      • app as a Java EE client
  • user roles and automatic reconfiguration of RCP app based on user authentication (e.g. role based module enabling/disabling?) - repeatedly requested by enterprise RCP app developers
  • embedded browser, JWebPane
    • for HTML preview in RCP app (many reports are generated as HTML and the preview to the user needs to be possible somehow)
    • HTML page as a dialog box
    • embedding pages of an existing enterprise webapp into enterprise RCP client
  • Graph support as a contribution from VisualVM?
  • JavaFX components in RCP app?

General Enhancements

  • API docs improvements (how RCP docs could be better?)
    • create docs about layer files and individual entries and their relationship to APIs (links to Javadoc and vice versa)
    • add links to other resources (FAQs, tutorials,..) into Javadoc footer
    • link from Javadoc pages to the related FAQ topics/categories
    • move Geertjan's blogs to a permanent space under our control (wiki.netbeans.org) and link to them from Javadoc and other RCP docs
    • better into into Module Suite vs. Module Project, many new RCP users don't see a difference
  • API Support: better branding support (ImprovedBrandingSupport69)
    • make it work also for Maven RCP projects
    • GUI to brand layers (including un-hiding of hidden entries), bundles, and icons
    • visual customizer of main menu and toolbar
    • UI for correct display of both XML-based and annotation-based layers
    • more options to customize application behavior (what specifically?)
    • assistance for creating localizations (also with the option of including ML version of Platform), tool for L10N readiness check and finding unused bundle keys
    • mkleint: the primary problem for people is finding out where the icons/bundles/layers are. There is no connection between what people see in the ui and where the respective underlying to-be-branded content is..
  • visual library (layouting algorithms, Explorer view, ..?)
  • Window System
    • visual customizers for window system layout
    • allow moving toolbars to the left/right border of the main window (esp. important for RCP apps targeting wide-screen displays)
    • perspectives(?)
    • bulk operations on window modes (slide/drag/close the whole tabbed container) etc.
  • fixes for 3rd party look and feels (JTabbedPane , ..?)
  • native file listeners, perhaps using NIO.2
  • skins for RCP apps (using Nimbus Java L&F)
  • API Support: more wizards
    • Explorer/Nodes, ...?
    • SPI for adding wizards from other modules
  • API Support: allow debugging of RCP app down into Platform modules (need to allow easy download of sources and setting the sources for debugging)
  • API Support: add module deps dialog improvements (AddModuleDepsImprovements69)
    • improve the dialog UI and module+API descriptions
    • automatically add all libraries on what a being added library depends on, e.g. Explorer API depends on Nodes API and so on
  • API Support: better JavaHelp support
    • action to preview without build
    • validation of syntax, links
    • ToC/index editor

Cleanup / Maintenance

  • deprecation of certain APIs

(not removing anything in 6.9, but deprecating and removing in 7.0 or like)

    • TTV?
  • API Support: fix layer view
    • most edit operations currently unsafe
    • reflect registration annotations
  • API Support: fix refactorings (e.g. package rename) - some of them work, so we could just restrict the user in UI so that she does not run into cases which don't work
  • API Support: compile-on-save support? - would be useful for resolving annotation processing into layer for layer display correctness
  • API Support: module universe scanning performance issue
  • move useful test utilities (MockLookup etc.) to independent modules in harness
  • revisit component creation off EDT ([[1]|#168779])
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