RE: [Mapbuilder-devel] Mapbuilder State Of Play - June 2005

[Adair, M. <Mike.Adair@CCRS.NRCan.gc.ca>]

Yes it's good to take stock of where we are and where we should go with
this.

My comments:

We would get much more acceptance if we do a 1.0 release.  It's a
psychological thing but I think that what we have now could easily be
qualified as a v1.0.  What we really need is a real live site that is using
mapbuilder;  I will have something up by the end of summer.

3.1 AJAX framework: I think we have a very solid framework for AJAX (though
we still need to do the asynchronous part) and we can/should offer that up
as a library for others to use.  I don't know enough about the other
libraries to know if they would work for us.  ie. I would be happy for us to
lead an MVC AJAX library 
3.2 Other web clients: while collaboration is good and we should re-use as
much as possible, the underlying design and architecture of the clients is
very different, so merging into one project may not be feasible.  For sure I
will extract our Proj library for others to use.
3.4 CMS: I met someone at the conference who was going to try and implement
this in plone.  It would be good to figure this out as Nedjo points out.

Also as Nedjo points out, developer's documentation should be the next major
focus of the documentation effort.  We really need to reduce the learning
curve.  I'm not sure what the best way to do that is though, perhaps a
config wizard.
 
I would also like to add SOAP support, seems like it may not be too hard:
http://www.onlamp.com/pub/a/onlamp/2005/06/23/mozsoap.html

Mike