Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse-dev] Planning Meeting Notes - Oct 26, 2005


-------------------
 Discussion Topics
-------------------

Runtime:
- I'd like to broach the topic of backward compatibility migration for 3.2.
  In 3.0 we did some "hacks" to map names of extensions and extension
  points as well as tweak plugin dependencies as plugins were loaded.
  There are some non-trivial refactorings happening in the runtime space.
  Reviving and enhancing that mechanism may be useful.  It would be good
  to know if others are finding themselves in a compatibility bind.

Platform UI:
- ICU4J integration (http://icu.sourceforge.net/icu4j_faq.html)
  - plan to ship this as part of the Platform in M3
  - currently the libraries are compiled to JDK 1.4 level (for example it
    uses the assert keyword).
  - will this affect RCP, eRCP or other runtimes?
  - com.ibm.icu project will be added in CVS for this library, it will
    ship much like ANT does now
- bug 113433:
  - polish Item
  - in particular: why is the product configuration wizard primary? Also,
    the java ant project is declared primary but there doesn't seem to be
    a pattern binding governing ant.ui...
  - UI is doing more investigation

--------
 Status
--------

Debug:
- presented "The Eclipse Debug Framework" tutorial at OOPSLA'05
- Debug model update policies:
  - investigating use of model deltas to drive view udpates
  - separates "what" changed from "when" the update occurrs to enable
    reusable update policies across models
- working on popup dialog migration using new workbench support (not
  released to HEAD yet)
- continued work on Java classpath tab -- providing similar editing/UI
  capabilities as in source lookup tab
- continued work on launch configuration resource association and
  migration support for existing configurations

Platform/JDT Text:
- work with JDT-Core to finish up javadoc content assist pushdown
- submitted proposal for eclipseCon 2006
- finished live update of revision / annotate information
- discussion with Team team on how to integrate revision / annotate
  information
- reviewed PopupDialog usage as replacement for various info popups in
  text land
- 50% on vacation

Rel. Eng.
- posted hpux-motif-ia64_32 3.1.1 contribution from HP
- tested PDE Build support for version qualifiers
- worked with IT team to rewire build lab; new VLAN expected to result
  in fewer network problems during builds
- wikified some releng pages:  
  - http://wiki.eclipse.org/index.php/Platform-releng-faq

Workspace:
 - file system natives compiled for HPUX RISC and ia64_32 architectures
 - file system performance work
 - crash recovery and startup refresh now done in background job
 - discussions on version numbering proposal
 - new resources extension point for resource-based model providers
 - team support for model based merges
 - working with UI team on model integration topics, such as problems view

Platform UI:
- team preparing and submitting abstracts for talks/tutorials for EclipseCon
- filtered lists:
  - filtered tree fixed up in preferences dialog (no more combo)
  - added filter to Show View dialog
- investigation into Contribution items relating to improving generic layout
  customization of the fast view bar in the workbench as well as other trim
  widgets
- added hierarchal mode to Problems view
- added Menus extension point (not parsing it yet)
- began implementation of registry objects for the menus extension point
- evaluating Properties View from WTP
- Working on the aggregate working set/window working set APIs. (see note
  to Platform UI mailing list):
  - NOTE: When these are released other teams who make use of the working
    set action group and working sets in general should ensure that the
    results are acceptable to them.
- multi-monitor:
  - multi-Monitor investigation (ViewSashContainer support in
    Detached Windows is my first target)
- JFace and Data binding (org.eclipse.jface.binding)
- started code review of Common Navigator
- posted slides from JAOO talk on RCP for Smart Clients to RCP home page:
  - http://eclipse.org/rcp
- off-site visit to an RCP client


JDT/UI:
- adapting to EFS:
  - finished recording of native java.io.File accesses
  - adapted refactoring history to EFS (see below)
  - still open are (see bug 13373):
    - error reporting on Javadoc generation when files not local
    - impact of UI to define external locations (since
      we don't have such a UI in Platform yet, the code
      couldn't be adapted)
- refactoring:
  - finished implementation of refactoring history (we are
    now using a new YYYY/MM/WW schema)
  - continued implementation of CVS refactoring catch-up action
  - investigated in performance of structural equivalent creation
  - continued work on "Update Derived Members" option in rename
    type refactoring
- source actions:
  - continued work on code clean-up action (multi apply quick fix)
  - added more test cases for "delegate method" and "generate
    constructor using fields"
- build path:
  - started work on selecting an installed JRE instead of a compiler
    compliance level when creating a project
- search:
  - adapted JDT/Core camel case support in Java Search dialog
- misc:
  - participated in Common Navigator discussions
  - worked on slides for WJax
  - 50% on vacation

JDT/Core:
- completion engine now supports completion inside Javadoc
- added API to retrieve the source range of a javadoc comment attached to
  the corresponding member (see IMember#getJavadocRange())
- added compiler option so as to specify whether optional errors should
  be fatal or not. By default, an optional error is treated as fatal as
  a normal language error (as defined by the language spec book), when
  disabling this option, clients will be able to treat optional errors
  as severe warnings only, which will be rendered as errors, but no
  longer prevent from running the code. There is some work planned on
  UI side so as to better distinguish amongst mandatory vs. optional
  errors
- added flag indicating when one or more categories of an element are
  added/changed/removed (see IJavaElementDelta#F_CATEGORIES)
- search engine is now able to perform search using Camel Case pattern
- 3.2 bug fixing
- bug inbox tracking

PDE:
- reworked the manifest.mf editing model to facilitate its manipulation
  via quick fixes
- quick fixes to organize Imports/Exports/Require Bundles
- added syntax highlighting to the build.properties source page:
  - complies with the preferences for JDT's properties editor
- bug fixes

Install/Update:
- added the support for loading install handlers from multiple JARs
  (currently testing)
- work continues on server-side mirror selection

User Assistance:
- continuing work on a dynamic help content proposal
- prototyping content filtering

Back to the top