[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-dev] Extension Point Schema Changes - ACTION REQUIRED/REQUISE
|
Extension names, when specified, are shown in PDE editors etc when you're
in 'full name' display mode.
That is, when the option 'Show plug-in objects in editors and dialogs using
PRESENTATION NAMES' is selected on the main Plug-in Development preference
page.
Wassim.
Andre Weinand
<eclipse@weinand.
org> To
Sent by: eclipse-dev@xxxxxxxxxxx
eclipse-dev-admin cc
@eclipse.org
Subject
Re: [eclipse-dev] Extension Point
11/22/2004 06:06 Schema Changes - ACTION
PM REQUIRED/REQUISE
Please respond to
eclipse-dev
Wassim,
why is the attribute 'name' of the <extension> element translatable?
Where is it visible in the UI?
Thanks,
--andre
>Andre,
>
>Of the plug-ins listed, only org.eclipse.compare contributes extension
>points and is therefore the only plug-in whose schemas need to be updated.
>I just browsed through the 5 schemas in said plug-in, and you only have to
>make one change in each one of them.
>Just mark the attribute 'name' of the <extension> element translatable and
>you're done.
>
>Thanks,
>Wassim.
>
>
>
>
> Andre Weinand
> <eclipse@weinand.
> org>
To
> Sent by: eclipse-dev@xxxxxxxxxxx
> eclipse-dev-admin
cc
> @eclipse.org
>
Subject
> Re: [eclipse-dev] Extension Point
> 11/22/2004 04:53 Schema Changes - ACTION
> PM REQUIRED/REQUISE
>
>
> Please respond to
> eclipse-dev
>
>
>
>
>
>
>
>I've checked the following ZRH plugins but couldn't find anything to
>update:
>
>org.eclipse.compare
>org.eclipse.compare.examples
>org.eclipse.compare.examples.xml
>org.eclipse.compare.tests
>org.eclipse.test.performance
>org.eclipse.test.performance.win32
>org.eclipse.core.resources.macosx
>org.eclipse.ui.carbon
>org.eclipse.jdt.launching.macosx
>
>--andre
>
>
>>The PDE team would like to kindly ask all teams, from Beaverton to
>>Confederation Helvetica, to revisit their extension point schemas and
make
>>use of the new important properties that will be available as of today's
>>I-build.
>>
>>Exempt from this effort is the SWT team as they do not contribute
>extension
>>points to the SDK.
>>
>>Untranslated attributes in the plugin.xml files are difficult to spot,
>>given the size of these files and the inability of the chkpii tools to
>zero
>>in on these attributes accurately.
>>
>>To address this issue, PDE has introduced new support in the extension
>>point schemas to mark attributes and non-empty elements as
'translatable'.
>>For all translatable attributes and elements, PDE will do a
>>two-verification step when validating the plugin.xml file:
>>1. It will ensure that the value starts with %
>>2. It will ensure that the key in the plugin.xml actually exists in the
>>plugin.properties files of the plug-in.
>>
>>For attributes that are not translatable, eg. ones that denote an id,
>etc,,
>>do NOTHING as the default is FALSE.
>>Much like in the case of the JDT compiler settings, the flag for 'usage
of
>>non-externalized strings' will be set to IGNORE by default.
>>This new 'translatable' property is vital as it will also be used to
guide
>>PDE when we provide an 'externalize strings' action for plugin.xml files
>in
>>the future.
>>
>>
>>The other property that was also added is a 'Deprecated' property used to
>>mark attributes/elements that have become deprecated over time. There
are
>>not too many of those in the SDK.
>>I think only the Platform/UI team has a few of these. Please mark these
>>attributes/elements appropriately in the schemas.
>>
>>Note that while the changes are TRIVIAL, every schema in the SDK is
>>affected and has to be visited since at minimum, the 'name' attribute of
> >the top-level <extension> element will have to be marked as
>'translatable'.
>>
>>The Platform/UI and the Debug/Ant teams will be the busiest as together
>>they contribute > 50% of the world's extension points (and > 60% of the
>>world's cocoa, I think :-)
>>
>>Please plan on making these changes at your earliest convenience.
>>
>>Thank you,
>>
>>Wassim.
>>
>>_______________________________________________
>>eclipse-dev mailing list
>>eclipse-dev@xxxxxxxxxxx
>>To change your delivery options, retrieve your password, or
>>unsubscribe from this list, visit
>>http://dev.eclipse.org/mailman/listinfo/eclipse-dev
>
>_______________________________________________
>eclipse-dev mailing list
>eclipse-dev@xxxxxxxxxxx
>To change your delivery options, retrieve your password, or unsubscribe
>from this list, visit
>http://dev.eclipse.org/mailman/listinfo/eclipse-dev
>
>
>_______________________________________________
>eclipse-dev mailing list
>eclipse-dev@xxxxxxxxxxx
>To change your delivery options, retrieve your password, or
>unsubscribe from this list, visit
>http://dev.eclipse.org/mailman/listinfo/eclipse-dev
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
http://dev.eclipse.org/mailman/listinfo/eclipse-dev
