[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[eclipse-dev] Planning Meeting Notes - Mar 23, 2005
|
-------------------
Discussion Topics
-------------------
----------
Outreach
----------
- Darin (S) gave talk at SDWest in Santa Clara:
- "Getting the Most from Eclipse"
--------
Status
--------
Debug:
- work on performance tests:
- reworking tests to create more consistent results
- investigating consistency issues and cross-platform differences
- API review/cleanup:
- memory view will -not- use new component UI in 3.1 (which has
become internal)
- pass of all new 3.1 API
- added support for native classpath entries (-Djava.library.path)
when launching
- created reuseable actions in debug platform for double-click breakpoint
creation. Migrated Java debugger and Ant debugger to use the actions.
- bug fixing
Ant:
- support for "mark occurrences" in Ant Editor
- bug fixing
Rel. Eng.:
- testing muliple pde builds for building plugins as jars
- M6 build schedule now available:
-
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-releng-home/buildSchedule.html
- bug fixing
- vacation
Platform/JDT Text:
- investigated parameter guessing performance problem:
- not yet reproducible on our side, added instrumentation code
- more lazy computation in ResultCollector:
- defer as much as possible until the user selects a proposal
- prepared to promote ResultCollector to API
- experimented with SWT.VIRTUAL for displaying completion proposals
(this would allow lazy label / icon computation)
- participated in writing an article for "My Personal Eclipse" section
in JavaMagazin
- wrote memory leak tests:
- open/close editor scenario
- undo manager usage
- released patches to adopt changes in the operation support
- discussed possible solutions for editor splitting with Platform UI
- improved Externalize String wizard to handle Eclipse's new string
externalization approach
- bug fixing
- bug inbox tracking
JDT Core:
- bug fixing
- working on performance
- working on reducing memory footprint
- the internal build state format has changed and a full build is expected
when restarting an existing workspace with this version of JDT Core
- codeselect can perform on Javadoc references
- codeselect can operate on an enum constant inside a switch case label
- tuned API controlling access rules severity:
- org.eclipse.jdt.core.IAccessRule:
- int K_ACCESSIBLE;
- int K_NON_ACCESSIBLE;
- int K_DISCOURAGED;
- IPath getPattern();
- int getKind();
- org.eclipse.jdt.core.JavaCore:
- String COMPILER_PB_DISCOURAGED_REFERENCE;
- IAccessRule newAccessRule(IPath pattern, int kind);
- IClasspathEntry newContainerEntry(...IAccessRule[] accessRules...);
- IClasspathEntry newLibraryEntry(...IAccessRule[] accessRules...);
- IClasspathEntry newProjectEntry(...IAccessRule[] accessRules,
boolean combineAccessRules...);
- IClasspathEntry newVariableEntry(...IAccessRule[] accessRules...);
- org.eclipse.jdt.core.IClasspathEntry:
- boolean combineAccessRules();
- IAccessRule[] getAccessRules();
- added new kind of type signature: Signature#WILDCARD_TYPE_SIGNATURE:
Signature#getTypeSignatureKind(char[]) and
Signature#getTypeSignatureKind(String) now return
Signature#WILDCARD_TYPE_SIGNATURE
if the signature is a wildcard : * or +Ljava.lang.Object; or
-Ljava.lang.Object;
- added new completion API to describe context in which the completion
occurs:
- currently only the expected types of the potential completion
proposals are proposed
PDE:
- JARd plug-in format:
- addressed issues related to plug-in import and plug-in/dependency
searches
- outstanding issues include the SWT launcher and importing plug-ins
w/ source.
- bundlizer released
- transformation of the plugin editor to support manifest.mf-specific
headers (in progress)
- manifest.mf validation (in progress)
- support for Eclipse-PlatformFilter manifest header where only
plugins/fragments that pass through the filter are taken into account
when resolving the target.
- plugin JUnit testing is now possible without the need for the
compatibility plugin.
- all PDE plug-ins now have a manifest.mf
- bug fixing
Update:
- bug fixing
User Assistance:
- XHTML support for Welcome content pending on shipping with DTDs
- we added a new page for roles and Eclipse configuration in Welcome
- currently tweaking it based on feedback
- API for page change notification released in JFace - will use the new
API in dynamic help this week
- patches will be provided to support the new API to Search and Debug
UI components
- browser support API in the workbench will go in this week:
- browser support plug-in to follow shortly
Platform UI:
- bug fixing
- editor to content type associations added (see bug 37668)
- working on final API related issues (query Platform UI + keyword =
"api" + target milestone = M6)
- browser support proposal (see bug 69647)
- capabilities improve preference page
- undo/redo:
- working on conversions to undo/redo posts to mailing lists asking
for input
- performance work:
- performance preference page added/allows disabling performance
intensive options
- bugs logged with "performance" keyword
- ongoing investigation based on community feedback
- see
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core-home/documents/3.1/performance/perf_plan.html
- more preference page cleanup:
- added Workspace preference page in IDE, moved options from General
to Workspace
- commands work ongoing (handler extension point almost ready)
Platform Core:
- running with plug-ins as JARs - the RCP plug-ins are JAR'd
- lots of changes in PDE-Build to handle JAR'd plug-ins and
conditionally platform filter builds
- deleted unused methods from org.eclipse.core.resources and
org.eclipse.core.runtime (saved 20K in each plug-in)
- updated Core Tools to include "find unreferenced methods" and
"convert message bundles" tools
- content type bug fixes
- working with UI team to resolve some of the remaining content type
issues
- investigation of read-only configurations
- bug fixes
- bug triage