[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[eclipse-dev] Planning Meeting Notes - Apr 6, 2004
|
(Did I miss anybody who sent me status? It seems kind of thin this
week...)
-------------------
Discussion Topics
-------------------
----------
Outreach
----------
--------
Status
--------
Debug:
- bug fixing & some leak testing
- produced draft of "How to Write a Debugger" article for Eclipse corner,
along with example debugger, with from Bjorn Freeman-Benson
- Java apps, remote Java apps, and applets migrated to the new platform
source lookup support. Will continue to polish the new API for others
to use
- ongoing bug triage to "defer" bugs we do not intend to fix for 3.0
Ant:
- bug fixing & some leak testing
- ongoing bug triage to "defer" bugs we do not intend to fix for 3.0
RelEng:
- builder based on 3.0 M8 now in place.
- javadoc logs now available on test results page
- pdf of doc now available for download with each build
- bug fixing
Dynamic Team for improved background feedback:
- refinements for New User experience with progress support
- investigate in improved progress view
Platform UI:
- RCP polishing
- new UI polish
- icon and graphics refreshes
- performance and size reduction work
- test writing
JDT/UI:
- ported NLS and occurrences search to new search
infrastructure.
- removed references to deprecated JDT/Core DOM API.
- added user interface for build path inclusion filters
- converted override label indicator to label decorators
- worked on import rewriter
- NLS
- improved bundle and accessor class guessing if unit
is already partly nlsed.
- improved insertion strategy for new keys
- Refactoring:
- polished refactoring participant API
- worked on refactoring UI API.
Expression Language:
- removed dependency on runtime.compatibility
- improved initial construction of the property tester
hierarchy.
Compare:
- working on headless merge
Platform/JDT Text:
- revisit typing mode changes:
- separated smart mode from insert/overwrite mode (presentation in
status bar is unchanged)
- smart mode uses normal caret, raw mode get special one (i-beam w/ gap)
- support for 2-pixel wide caret
- preferences to turn off special or wide carets for accessibility
- added proposal support for templates:
- proposals for loop templates (for, while, do)
- proposals are linked, so when you change the proposed array, the
proposals for the temporary variable change as well
- added template for //$NON for code and single line comment content types
- added preference for incremental completion to content assist
preferences in java editor
- added preference for text selection foreground and background color
(not yet released)
- continued work on semantic highlighting in Java editor
- continued infrastructural and UI work for folded documents
- added override indication in Java editor vertical ruler
- added selection validator to allow clients to cancel jobs working on
the editor's selection
- bug fixing
Eclipse Forms:
- In the past, forms toolkit used to assume that native skinned widgets
are used on Windows XP. In reality, this is only the case if
javaw.exe.manifest file has been dropped near javaw.exe. The new
code checks for the presence of this file in
System.getProperty("java.home")
and reverts to classic flat look if not found.
- The new style of Section rendering is available when Section.TITLE_BAR
style has been used. It looks more in sync with the 3.0 Eclipse look.
All PDE editors will use this look in 3.0.
- Form colors now fully computed from system colors - works better with
non-default color schemes.
Intro:
- We decided to move most of the new Welcome content from plugin.xml into
dedicated XML file(s) in order to ensure scalability and reduce
extension registry size. The new code operational & in the today's
I-build.
- detailed plan for M9.
PDE:
- good progress in editor rework
- plug-in/bundle manifest editor fully reworked with surgical text
modifications when working in GUI pages
- all other editors refreshed and ported to the new Eclipse Forms look
- closing on the work that integrates the new manifest file with JDT
wizards to generate new java classes (we are getting out of the Java
code generation business).
- effect will be seen on:
- Overview Page:
- The "Class:" hyperlink will open the java file if it exists
or will open the New Java Class wizard from JDT. Superclass
will be AbstractUIPlugin or Plugin depending on if the project
will make contributions to the UI.
- The "Browse" button will allow the user to select a java class
from the project.
- Extensions Page:
- The extension's "Class:" hyperlink open the java file if it
exists or will open the New Java Class wizard from JDT.
- Superclasses and interfaces will be defined by the schema.
- The "Browse" button will allow the user to select a java class
from the project.
Help:
- working on reacting to extensions registry changes:
- reacting to org.eclipse.help.contentProducer and
org.eclipse.help.context extensions
- changes done.
- still working on more complicated than anticipated changes to
org.eclipse.help.toc extensions (fixes to org.eclipse.help plug-in
are trivial, but things on top of org.eclipse.help plug-in: indexing,
search, working sets, browser contents are affected).
Update/Install:
- bug fixes
- discussions on to do items for M9