Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Planning Meeting Notes - Aug 31, 2005


Platform UI
------------

- bug fixing
- 3.1.1 work
- 3.2 planning




Mike Wilson/Ottawa/IBM@IBMCA
Sent by: eclipse-dev-bounces@xxxxxxxxxxx

08/30/2005 03:30 PM

Please respond to
"General development mailing list of the Eclipse project."

To
eclipse-dev@xxxxxxxxxxx
cc
Subject
[eclipse-dev] Planning Meeting Notes - Aug 31, 2005






[Note: I'm back. Please send me your status messages from now on.]


--------
Status

--------


Debug:

- bug fixing & triage

- vacation


JDT/Core:

- 3.2 bug fixing

- bug inbox tracking

- tracking performance regression in DOM AST
- investigating upward compatibility for .classpath files

- investigating opening code completion to clients


Platform/JDT Text:

- 3.1.1 bug fixing

- continued content assist participant work (not released in HEAD):

 - added commands and menu entries for each participant

 - added preferences

 - made calling of extensions safe (including performance blame)

 - discussed the extension story with JDT Core

- added hyperlink navigation for editors without focus

- improved roll-over annotation hovers

- continued investigating push down of Quick Assist/Fix to Platform Text

- bug fixing

- bug inbox tracking


JDT/UI:

- started work on hierarchical package rename

- started work on a combined rename and extract interface. This will

 support extracting an interface while reusing the name of the type from

 which the interface is extracted.

- released support for group categories in the preview page of the

 refactoring wizard to be able to filter the change tree against certain

 kinds of changes (for example all textual change in comments and

 strings).

- worked on official API to created custom substructures for text edit

 changes. This will allow C/C++ or other language providers to show

 a language specific structure for their refactored sources.

- continued work on relaxing closed world assumption in refactoring:

 - implemented first version of refactoring history (without persistence)

 - UI Story boarding for refactoring history

 - implemented UI to preview history

 - investigation of team catchup issues (working copies, outgoing

   changes, merging)


Workspace:

- 3.2 Planning

- EclipseWorld

- logical Model Integration discussions and prototyping

- Create/Apply Patch wizard improvements


Back to the top