Changes between Version 69 and Version 70 of Bolsena2010
- Timestamp:
- 05/18/10 17:22:08 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Bolsena2010
v69 v70 33 33 ||11|| ||Community || Would it be an idea to appoint Language Managers for each of the supported translations? They would form the International Internationalization Committee (IIC, or CII in French) and they're summoned to maintain the i18n files for their language, before each new release. This might even be arranged in an [http://www.osgeo.org/ OSGEO]-wide manner. || heikki: 3 || 34 34 ||12 || ||Code Refactoring || The class {{{DataManager.java}}} and its sister {{{XMLSerializer.java}}} are in particularly bad shape, in my opinion. There are literally dozens of public methods that all do more or less the same thing. Of course it's not clearly documented why they are all there or when to use which. Would it be too drastic to propose that we keep 1 single public method for each of the functions ''createMetadata'', ''updateMetadata'', ''validateMetadata'', etc. ? || heikki: 1 || 35 ||13|| || RIA, Framework || Any relevant software going on that might be useful for GeoNetwork? Think of [http://mapproxy.org/ MapProxy], [http://chiba.sourceforge.net Chiba] and [http://geojquery.org/wiki/doku.php GeoJQuery]. Other ones? || heikki: 4||35 ||13|| || RIA, Framework || Any relevant software going on that might be useful for GeoNetwork? Think of [http://mapproxy.org/ MapProxy], [http://chiba.sourceforge.net Chiba] and [http://geojquery.org/wiki/doku.php GeoJQuery]. Other ones? || heikki: 2 || 36 36 ||14|| ||Editor enhancement || In the [http://nationaalgeoregister.nl NGR] project, a modification to the code around the editor called ''Inflation and Vacuum'' is implemented, that makes it much easier to create valid metadata from scratch. In essence it takes the function of {{{update-fixed-info.xsl}}} (which also tries to do some automatic adjustments to help things along) a whole seven miles further. What do the developers think of this? (I'll provide documentation sometime soon). || heikki: 3 || 37 37 ||15|| ||Framework / Refactoring ||Whether it's going to happen soon or not, I still think it good to repeat the subject of what to choose if we ever get to a drastic make-over of current GeoNetwork code, especially in terms of (1) GUI: use [http://wicket.apache.org/ Wicket]? [http://code.google.com/webtoolkit/ GWT]? (2) MVC: use [http://struts.apache.org/2.x/ Struts]? [http://static.springsource.org/spring/docs/2.0.x/reference/mvc.html Spring MVC]? (3) Persistence: use [http://www.hibernate.org/ Hibernate]? use [http://java.sun.com/developer/technicalArticles/J2EE/jpa/ JPA/EJB3]? (4) Web Services: use [http://ws.apache.org/axis2/ Axis2]? [http://jcp.org/en/jsr/summary?id=311 Jax-RS]? || heikki: 3 ||