Matthias Basler ha scritto: ...
> the GeoWidgets project suffered from a series of shortcomings: > > 1. Building widgets for Swing AND SWT at the same time did turn out > to be much more work than I expected. Almost no chance of sharing any > code... And it makes sense to build one for Swing and not for SWT in my opinion. Why? Because if you're targeting SWT you'll probably want to use uDig plugins to build your software anyways... the level of reuse would be higher. It's hard to find fure SWT/JFace apps around, most are really using the RCP (Azureus is one of the most notable exceptions). > 3. Problems with the "road to go", especially - Should GeoWidgets > continue to support both Swing/AWT and SWT? Regularily users query > for Swing, JMapPane is Swing. See the above reasons for going pure Swing. Nothing stops anyone from trying and extracting stuff from uDig if needed. As you said, code sharing is mostly null... On the other hand I am meanwhile > working with SWT/JFace and uDig also is. Hmm... - Should it support > only Geotools or should it support other GIS libraries via an > additional layer of abstraction? No... too much rope, you end up hanging yourself. I tried this and it leads to overly > complicated/inconvenient APIs. - Should it be "freestyle" (i.e. as > feature rich as possible") or should it try to follow the > restrictions of some specification(s), lets say GO-1? I'd say, take GO-1 as an inspiration, but a spec like GO-1 does not make much sense in my opinion... what do you interoperate with? Nothing. So there's no point in having a standard, whilst it's useful to have a reference design to help you develop your own way of solving the problem. - Which version > of Geotools was/is stable enough but has enough features to serve as > a sustainable basis for Geowidgets without having to rewrite half of > it for the next version? Still an issue for me. Ha... 2.3.x probably, which has good image support, but yes, we still haven't reached an architecture we're happy with, so more changes are inevitable. > 4. Problems with the status of GeoTools, it did not support all the > features that I wanted to have in my widgets - and sometimes cannot, > since it restricts itself to a lot of specs. (Example: No map layer > groups in Geotools.) Bah, my MapContext implementation was just a quick hack to show some maps on a screen... again, I do believe the wms map context spec should be something that we can take inspiration from, but it's not an interoperability concern. > 5. Different goals. I am geared towars a desktop GIS and image > processing, GeoTools/uDig still has its priority in WebGIS (OGC) and > vector data. OGC yes, vector data... hum... have a look at what the 2.3.x branch and Simone and Alessio work can do and be amazed :-) > If we all have good ideas on how to solve the above problems I am > definitely willing to continue work on GeoWidgets (maybe this > winter). But I think it requires a coordinated effort between > GeoTools, uDig, me and others that are interested in and capable of > UI programming. Otherwise it will not be practicable and the result > will not meet everybody's goals. > > The planned step to extract some of the uDig widgets and contribute > them to GeoWidgets would certainly be a good idea - not only would it > increase the number of widgets in the GeoWidgets project, but - more > important - it would also ensure that the code base is actively used > - which means better coordination, quality control a.s.o. Hmm... just to add to your rant, I'd say that we need an uDig competitor, even a small one, to fuel the development of anything swing related (by small, I mean something that does not aim to be a platform, but just an app). Developer of the Swing components should eat their own dog food by using it in a real app, otherwise it becomes just an "academic" effort. Cheers Andrea ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
