Community
Participate
Working Groups
Currently it's possible to link to non-existant preference pages using the PreferenceLinkArea. We should guard against this in some way. Perhaps we can check to see if the page exists before creating the link control...?
To decrease coupling between pref page implementations due to links, and to further enable the reuse of pref pages in RCP apps, I'm wondering if the links could be described outside of the pref page class, e.g. as extra markup in the pref page extension elements, or perhaps as a separate extension point or new extension elements. This would only work if there's a common convention for how the links are presented, e.g. always at the top of the page. Not for 3.1, but something to think about.
There are currently no plans to implement this.
