[Geomoose-users] GeoMOOSE and upgrading to ms4w 3.2

[Dan Little]

Hey Mark,

Let me see if I can get through all your questions with some clarity:

1. GeoMOOSE 3.0 release date: There is not a *concrete* release date for
the first official version.  I would expect sometime this summer.  We are
submitting both a workshop and presentation abstract for FOSS4G.  I,
personally, would like us to have an official non-beta release by then.
That said, we are looking at releasing a demo/beta in the next couple of
weeks that should give folks a solid idea of what to expect in the next
version.

You may even want to wait until the first 3.0.x or 3.1 releases if you're
not feeling particularly bleeding edge.

2.  The reason GeoMOOSE 3.0 is a 3.0 and not a 2.10 is because we are
breaking things. 3.0 is going to be a departure from the 2.X series in a
number of ways; notably, we are no longer going to be dependent on PHP.  If
you are moving from 2.2 to 2.9 then to 3.0 there will be some duplication
of effort.  Specifically concerning any custom services you may have
written.  Instead of using PHP to launder spatial data, 3.0 is using more
client-side templates and WFS queries in order to perform the same tasks.

PHP can still be used for custom services but will not be used by the core
services that come with GeoMoose.

3. I won't lie, I have not looked at the 2.2-vintage of the code for a very
long time.  I'm not even sure if that change number is in GitHub and I'm
pretty confident that it's a version released before we adopted strict
semantic versioning.  As such I know there are minor incompatibilities
between 2.2 and 2.9.  2.9 is running with MapServer 7, I believe the
MapServer 6.4 stuff will run with 2.2.  There are a ton of modernizations
between 2.2 and 2.9 and you'll have a level of effort in order to make the
upgrade.

Major note from Jim: My experience is MapServer 6.4 and MapServer 7 are
generally compatible on the mapfile level.  My experience is while 7 adds
some stuff and removes some long deprecated stuff, a reasonably modern and
reasonably simple mapfile will work in both.  I have no idea if there are
PHP issues.  If Jeff has GeoMoose 2.9.2 working with MapServer 7 then 2.9.2
works with MaoServee 6.4 and MapServer 7. (I checked out the latest ms4w as
a test, but never bothered to look at what MapServer it came with).

One last note on 3.0 vs 2.X (particularly older 2.Xes): 3.0 is designed for
*modern* browsers.  We are not even going to pretend to support IE less
than 10.  Older versions of Firefox will not even be particularly useful.
Testing is being done on FF (latest), Chrome (latest),  IE11, and Edge.
So, if you're really looking to support old, unsupported configurations
like IE9 then you may need to stay on the 2.X series.  We are still
responding to bug reports on 2.X and I expect we'll need to continue to
respond for another couple of years past the 3.0 release date.  (Of course,
if we have more funding for 3.0 then our efforts will go into that vein of
the software.)

On Thu, Feb 2, 2017 at 7:57 AM, Mark Volz <MarkVolz at co.lyon.mn.us> wrote:

> Hello,
>
>
>
> I have some questions regarding the compatibility of older versions of
> GeoMOOSE and ms4w 3.2.
>
>
>
> First, is there an expected timeframe for GeoMOOSE 3.0 to be released?
>
> Second, if I update my application to GeoMOOSE 2.9, then will updating the
> application to GeoMOOSE 3.0 be easy or difficult?
>
> Third, if I update my .map files to work with Mapserver 7, then will
> GeoMOOSE 2.2 run on ms4w 3.2, or are there incompatibilities with the php
> scripts?  Or will it just be easier to restart with GeoMOOSE 2.9 and then
> upgrade to GeoMOOSE 3.0?
>
>
>
> Thank You!
>
>
>
> Sincerely,
>
> *Mark Volz*
>
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geomoose-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20170202/edda6498/attachment.html>