See the new UI

I am happy to announce to everyone a sneak peak of the future of GeoServer. Behold the newest alpha release of GeoServer 2.0.

I first mentioned GeoServer 2.0 last August when the first alpha was released, but much work has been done since then. The most obvious and exciting new feature in GeoServer 2.0 is the new UI, based on the Wicket framework. The UI has been totally redesigned and updated to provide a greatly improved user experience. Take a look at some screenshots:

Front page

Status

Layer preview

Styles

Another happy announcement is a major workflow change for data configuration. The Submit -> Apply -> Save workflow, often bemoaned by users, has been eliminated, in favor of a simpler Save changes workflow, with changes automatically persisting. To me, that’s a 66.6% reduction in button clicks!

This is an alpha release (the most recent stable version remains at 1.7.3) and so it comes with a few caveats. It’s very new code, and not fully tested, so please don’t run it in a production environment. Features may also be likely to change as the code approaches stability. Also, running GeoServer 2.0 with an existing data directory will alter it such that it will become incompatible with existing stable versions. We have instructions on how to migrate back to 1.7.x, but it might be better to use the built-in data directory for now, or at least to back up your existing data directory first.

That said, we want everyone to download, try it out, and provide feedback, since it was partly in response to user feedback that the GeoServer Team upgraded the user environment. I hope you enjoy!

7 Comments

  1. Posted April 20, 2009 at 5:33 pm | Permalink

    Another caveat is that we’re still working on polishing up this new UI, so don’t think anything is written in stone and please send up flags if you have any thoughts or concerns!

  2. Posted April 21, 2009 at 11:06 am | Permalink

    great news, guys! You rock!

  3. Posted April 25, 2009 at 12:36 am | Permalink

    Thanks for your great article. Your article is very informative and accurate!

  4. stelmo barbosa
    Posted April 30, 2009 at 12:27 pm | Permalink

    I am testing the geoserver2-alpha. In the IE7 i find out that Data Source Name field in the forms dont appear. In Firefox it´s OK. Congratulations for the knew look of geoserver. I would like to colaborate in translate it to portuguese.

  5. ChrisW
    Posted May 3, 2009 at 6:35 pm | Permalink

    Just curious, but are there any plans to try porting GeoServer onto Google’s Java AppEngine platform? Are there any particular reasons why this might not be possible?

  6. Andrea Aime
    Posted May 6, 2009 at 2:03 am | Permalink

    ChrisW, there are no plans at the moment and it might not be possible for a few reasons. Off the top of my mind:
    * AppEngine has no support for the java graphics library, and GeoServer uses that one very heavily
    * the catalog persistence, the spatial referencing, the styling subsystem require read/write access to the file system, AppEngine has no such concept as a file system
    * GeoServer needs to set some system variables on startup to bend the referencing subsystem into using lon/lat order by default, unfortunately that won’t work in AppEngine

    Whilst the second and third reason might be worked out by a developer with the necessary time, the first is a roadblock that is not going to go away anytime soon, just recently a Google guy stated they currently have no plans on supporting the java.awt packages:
    http://groups.google.com/group/google-appengine-java/browse_thread/thread/1d929a4a17389664

  7. Posted September 6, 2009 at 11:03 pm | Permalink

    The google app-engine concept sounds very enticing. But the use of native libraries(awt,jai,gdal-jni) can be a bottle neck. Can these dependencies be dynamically injected ?

Download GeoServer