Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Isn't Swing-WS more than just maps though, its looks important for tackling RIA clients from Swing.. would be nice if it was the counterpart to the JSON/XML/REST.. support being baked into JavaFX.
Good know about SwingX-WS collection of powerful, useful, and just plain fun Swing components. Each of the Swing components have been extended, providing data-aware functionality out of the box.
Thanks for sharing..
Affordable & Reliable Web Hosting
I put together a build a few days ago that's effectively a standalone map viewer package (sort of a minimal build that drops swingx-ws web related classes and adds in a few swingx classes that are used by JXMapKit/JXMapViewer). I still need to do some testing and cleaning up of the code.
I was going to go through and individually contact people who have posted that they're using JXMapKit/JXMapViewer to encourage their input, but there is no way to contact people directly through this site and no mail list of developers who use the software exists.
How far ist your MapviewerOnlyPackage?
I'd suggest the following:
1. A "final release" (even if it's called 0.99 beta or 1.0 beta) of swingx-ws that is compatible with SwingX 1.0. I think that is mainly just changing 1 source file in the repository, and making a jar available (plus maybe an "official" jar/archive of the source code). I have a build that is updated and works, but I suspect some others do too. [i]This just seems like the right thing to do.[/i] Depending on the direction of this, I can help here.
2. Spin off JXMapViewer as a separate project. Probably drop the current (what appear to be minimal anyhow) dependencies to SwingX. Pull together and contact a list of people from this forum and probably elsewhere (possibly create a mail list and offer them to join) who have shown interest in JXMapViewer in the past and work with them on where to take this project (where to host it, a roadmap, etc.). This is really where most of my interest lies. I see some opportunities for additional packages of classes that provide some basic overlay/feature layering support and some standard overlay/waypoint painters that could make this even easer for people to grab and use (could be separate libraries without changing the existing API). Maybe add some lightweight support for different datums, etc. I've dealt with some of the other heavyweight geospatial Java libraries, and JXMapViewer's lightweightness is what makes it nice. I'd also like to see if this as a project could develop closer contacts with the OpenStreetMap folks (and I'd be glad to help with seeing this happen). All depending on what other interested JXMapViewer folks think.
3. Possibly spin off the other more web oriented swingx-ws components as their own separate project (e.g. find interested persons, etc. as above). I have less of an interest here. Not that there isn't some cool functionality here that I've considered using, but the rest of swingx-ws seems distinct from SwingX and JXMapViewer in being very HTTP/web-specific.
From what I can see, outside of Fabrizio's recent commits, swingx-ws has been unsupported by the SwingX community for the past 1.5 to 2 years. Posts over the past year for JXMapViewer support to this forum have usually been pushed back onto the poster to do the work. I think the ones who are using it ought to decide and define where it goes next.
Fair enough, I'll promote this weekly build into the 1.0 release of swingx-ws. Then we can spin off the JXMapViewer or continue more actively here ... it's your choice (and there are pros and cons to either way). As for the rest of the code there, it have been working well for me for last year and half, and since there was no one left interested in maintaining that code it might have fell bit behind. Tho if anyone's interested in extending what is there or need some of the issues fixed (provided there is a patch), shout now and here.
great to see that swingx-ws 1.0 has been "released".
I'm sure several people have added fixes/enhacements to swingx-ws (I'm just thinking about adding additional functions to MercatorUtils) but many of us don't know how to contribute them back upstream. You said  that ", if you would like to become a committer on this project please let us know on the SwingLabs forum". I'm not sure what qualifies someone as commiter... or what is the procedure if you just want to send a patch. Do you have a list of current swingx-ws commiters?
As for a new map-viewer-only or keep current swingx-ws project as it is I don't care that much, the important thing is to facilitate adding patches/enhancements to it.
Are we just best off scrapping SwingX-WS and moving JXMapViewer into SwingX?
hmmm ... don't know, maybe it's better off as a separate project - more lightweight, easier to change and the maintainance burden not on SwingX ;-).
btw: added the blog to dzone to spread the word more widely
I agree, an own project for lightweight map viewer component would be great. Kenai (http://kenai.com/) would be perfect for hosting it.
sounds reasonble to me (disclaimer: I have no experience whatever in gps/swingx-ws and related) - go ahead! Once done we can consider to add a demo page to swinglabs-demos, what do you think?
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.