Widgets to exclude from 1.0 - unstable

[adube]

Some widgets are not ready for 1.0. Their code will be kept in trunk, but they need a way to show that they will not be "1.0" approved.

For that, we'll simply have new group for the official "1.0 stable" widgets in the samples and documentation. The excluded ones should be classified as "unstable".

[adube]

"unstable" widgets become good candidate for future releases.

[adube]

Instead of marking the 1.0 widgets as "1.0 stable", "stable" should be enough and would refer to the current active release.

[adube]

In order to keep an historic of the widgets supported in each release, we'll create a wiki page.

[adube]

Here's the wiki page that will contain the status of all widget for each release :

​http://trac.osgeo.org/geoprisma/wiki/WikiStart/stable-widgets

[adube]

Some samples contain stable and unstable widgets. Classify them as 'stable', but leave a note in the footer about the unstable widgets used.

[adube]

r1160, featuring :

• a cleanup of the samples :
  • they are now classified as "Stable Widgets", "Unstable Widgets" and "Deprecated".
  • all links to the xslt file were removed
  • all xml link are now valid (some gave 404 errors)
• widget documentation new classification :
  • now, the script building the widget documentation look for the following files in order to classify them : DEPRECATED and UNSTABLE. If a widget directory contain one of these files, then its documentation is classified accordingly.

One thing remains to do : look at the stable sample and add a notice in the footer if it uses unstable widget(s).

[adube]

r1161, all stable samples with unstable widget now have a notice in footer.

This completes the work required for this ticket.