| |
This document is for clients who are already using the
internal content settings mechanism. In reality, no one should have
been using this mechanism because clients should access content
settings through another more public mechanism, like
PageDirectiveAdapter and HTMLDocumentTypeAdapter. The old internal
content settings mechanism may be deleted any time after WTP 1.5M6.
|
| |
wst.css.ui
wst.css.ui.internal.content.properties
- ContentSettingsRegistry: This was just a utility class.
Just copy any methods you need into your own code.
wst.css.ui.internal.content.properties.ui
- CSSContentSettingsPropertyPage: Use
CSSWebContentSettingsPropertyPage instead.
wst.html.ui
wst.html.ui.internal.contentproperties.ui
- AbstractDeviceProfileEntry: No longer needed, see bug
118359
- AbstractDeviceProfileEntryProvider: No longer needed, see
bug 118359
- ContentSettingsRegistry: This was just a utility class.
Just copy any methods you need into your own code.
- DeviceProfileEntryProvider: No longer needed, see bug
118359
- DeviceProfileEntryProviderBuilder: No longer needed, see
bug 118359
- HTMLContentSettingsPropertyPage: Use
WebContentSettingsPropertyPage instead
- ProjectContentSettingsPropertyPage: Use
ProjectWebContentSettingsPropertyPage instead
Extension point:
- org.eclipse.wst.html.ui.deviceProfileEntryProvider: No
longer needed, see bug 118359
wst.sse.ui
wst.sse.ui.internal.contentproperties.ui
- ComboList: This is a helper widget that clients can just
copy and manage themselves.
- ComboListOnPropertyPage: This is a helper widget that
clients can just copy and manage themselves.
wst.sse.core
wst.sse.internal.contentproperties
- Everything in this package is deprecated. Use new Content
Settings mechanism described in "Code Usage" section of Web Content
Settings design document.
jst.jsp.core.internal.document.PageDirectiveAdapter no longer
implements IContentSettingsListener
wst.html.core.internal.document.HTMLDocumentTypeAdapter no longer
implements IContentSettingsListener
|
