|
Author
|
Reply
|
 Wehrmacht
1 July 2003 12:23 PM
Bildung ist Freiheit
| Mars Pathfinder |  Profile | Post reply |
javadoc for protected methods is not consistent across platforms. The javadoc
for the Windows platform, which is used to generate the documentation that
appears in the Platform Plug-in Developer guide, is the definitive source. The
javadoc for the other window systems will be brought into line in a future
release. (bug 20968)
JAWS requires MSAA for List Views to read checkboxes in Tables (Windows
only)
In order for JAWS to detect the checkbox information in Tables, MSAA support
for List Views must be activated as follows:
Open Eclipse and hit INSERT + F2.
In the Run JAWS Manager dialog select Configuration
Manager. |
Flautistul
1 July 2003 10:00 AM
The surest sign of extraterrestrial intelligence is that they haven't tried to contact us.
| [Re]: Satellites | Profile | Post reply |
run against the Eclipse SDK 2.1 APIs. Since source incompatibilities are easy to
deal with, maintaining source compatibility is considered much less important
than maintaining contract and binary compatibility. Downward source
compatibility is not supported. If source files use new Eclipse SDK APIs, they
will not be usable with an earlier version of the Eclipse SDK.
Workspace Compatibility: Eclipse SDK 2.1 will be upwards
workspace-compatible with Eclipse SDK 2.0 unless noted. This means that
workspaces and projects created with Eclipse SDK 2.0 can be successfully opened
by Eclipse SDK 2.1 and upgraded to a 2.1 workspace. Individual plug-ins
developed for Eclipse SDK 2.0 should provide similar upwards compatibility for
their workspace metadata; plug-in developers are responsible for ensuring that
their plug-ins recognize 2.0 metadata and process it appropriately. User
interface session state may be discarded when a workspace is upgraded.
Downward workspace compatibility is not supported. A workspace created (or
opened) by Eclipse SDK 2.1 will be unusable with an earlier version of Eclipse
SDK.
Non-compliant usage of API's: All non-API methods and classes, and
certainly everything in a package with "internal" in its name, are
considered implementation details which may vary between operating environment
and are subject to change without notice. Client plug-ins that directly depend
on anything other than what is specified in the Eclipse SDK API are inherently |
MindGym
1 July 2003 09:57 AM
Led Zeppelin - "No Quarter"
| Satellites | Profile | Post reply |
ader(yourClassLoader); // you can find
your classloader by grabbing a class it loaded (YourPluginClass.class.getClassLoader())
Run your code in the newly created thread.
If you set the context class loader for the current thread, you are competing
with other users of the thread (all of Eclipse), so the results will be unpredictable. (bug
8907)
Deadlock creating executable extension in Plugin.startup
If Plugin.startup code is too complex
and performs tasks such as creating an executable extension, a deadlock
situation can be created. Only simple bookkeeping tasks should be performed in Plugin.startup
code. (bugs 12827,
|
