Steven, I'm having trouble figuring out which JIRA issue I should be commenting on. For the widgets, I'm looking at subtasks of issue number 264, is this correct?
Mike Steven M. Ottens wrote: > Hi all, > > I've worked my way through the jira issues and came up with the > following list of file in /lib/widget which need more information or can > be archived or deprecated. > I have been a bit harsh on the files, so I can imagine that not > everybody agrees with me. If you feel that a file is wrongly labeled > please comment on the issues in Jira and join the meeting tomorrow or > send an email to the list. I will probably start the actual process next > weekend, unless of course there isn't any agreement on the filestatus. > > A clarification of the different states: > Need more info means that from the current information I cannot judge > what the file does and if it is compatible with MapPaneOL and/or is > still needed. > Being deprecated means that they stay in /lib/widget but get an extra > parameter in the header @deprecated. These files work with MapPaneOL but > there are better alternatives available. The main reason for them to > stay is that they do things in a slightly different way then the better > alternatives. > Being archived means that they move to the -to-be-created- > /archive/lib/widget directory. This will still be part of trunk but not > of any release. Any files moved there can return to /lib/widget if > there's a compelling case or there is proof that it works with MapPaneOL.*) > > Need more info: > /lib/widget/LayerProperty.js > /lib/widget/Loading.js > /lib/widget/Loading2.js > /lib/widget/ModelStatus.js > /lib/widget/ServiceRegistryList.js > /lib/widget/WktParser.js > > Being deprecated: > /lib/widget/AoiBoxDHTML.js > /lib/widget/LegendGraphic.js > /lib/widget/SLDEditor.js > > Being archived: > /lib/widget/AoiBox2.js > /lib/widget/AoiBoxWZ.js > /lib/widget/ClickPass.js > /lib/widget/FeatureListSF.js > /lib/widget/GeoRssParser.js > /lib/widget/GeoRssRenderer.js > /lib/widget/GetMarkerInfo.js > /lib/widget/GmlPointRenderer.js > /lib/widget/GmlRenderer.js > /lib/widget/GmlRendererSVG.js > /lib/widget/GmlRendererTest.js > /lib/widget/GmlRendererVG.js > /lib/widget/GmlRendererWKT.js > /lib/widget/GmlRendererWZ.js > /lib/widget/GoogleMapDragPan.js > /lib/widget/GoogleMapZoomIn.js > /lib/widget/GoogleMapZoomOut.js > /lib/widget/MapImage.js > /lib/widget/MapPane.js > /lib/widget/MapPane2.js > /lib/widget/ModelSwitcher.js > /lib/widget/TimeSeries.js > /lib/widget/TipWidget.js > /lib/widget/WmsCapabilitiesImport.js > > /lib/graphics, /lib/tool and /lib/model will follow later today. > > *) I know that being compatible with MapPaneOL means that both MapPane > and MapPane2 will be archived. Also this means that for instance > /lib/graphics is being archived. This breaks backwards compatibility and > will require a clear upgrade path and documentation. But I still would > like to archive them, because they are IMHO the root cause of the > confusion in /lib/widget > > Looking forward to your responses. > Steven > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > mapbuilder-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
