[webmap-discuss] webmap.js project structure

[Paul Spencer]

I realize Chris has also posted a response to this, but here's my  
take anyway (since I was already writing it) ...

On 21-Sep-06, at 6:41 PM, Cameron Shorter wrote:

> I appologise if I'm going over ground already covered at FOSS4G.  
> I've got a couple of house keeping questions about webmap.js.
>
> Are we planning to set up webmap.js as a project? Eg:  
> webmap.sourceforge.net or webmap.osgeo.org or similar.

OpenLayers has applied for incubation in OSGeo.  As far as I am  
concerned, webmap.js is going to be a build target of OpenLayers that  
includes the core Map and Layer components (any any utilities that  
they use).  It will take very little work to produce WebMap.js,  
except for:

* remove the prototype.js dependency so that any project can easily  
incorporate WebMap.js without having to change their coding style  
(prototype breaks for(var i in a) syntax for instance).

* refactor the utility code so that only WebMap.js-related stuff is  
included in WebMap.js

OpenLayers already has a good build system and the amount of effort  
to do the above should be relatively trivial due to the way the code  
has been written.

The default distribution of WebMap.js will include all the Layer  
types that OpenLayers supports, but it will be possible to build a  
version that only includes the Layer types that a specific project is  
interested in.

>
> Are we planning to set up a mailing list? I suggest that this list  
> should become the webmap.js list.

I think this should be part of the OpenLayers mailing list, but that  
assumes my hidden agenda/ulterior motive ... which is to make more of  
OpenLayers part of WebMap.js ... and call it OpenLayers :)

Seriously, though, OpenLayers is currently a core API and a growing  
collection of UI widgets.  We are currently talking about the core  
API, but my hope is that when(if) the community has adopted  
WebMap.js, the Control architecture of OpenLayers will be used by all  
the projects as well.  This leaves a series of web pages that  
demonstrate how to use the core and UI widgets ... perfect world!

>
> Where is the Subversion repository going to live?

OSGeo, should it be accepted into incubation.  Otherwise, it should  
be left where it is (openlayers.org)

>
> Where is the issue tracker going to live?

same

>
> What about a wiki? Actually - I think Chris mentioned this already.

same ... wiki already exists

>
> Are we going to set up a seperate Project Management Committee or  
> will webmap.js be part of OpenLayers?

Part of OpenLayers.  I would suggest that a sub-committee of  
OpenLayers be formed that includes a representative from each of the  
major projects that intends to build on WebMap.js (MapBuilder,  
MapBender, Chameleon, ka-Map, MapGuide, ...).  This subcommittee  
would report to the OpenLayers PSC and, if my ultimate goals are  
realised, would be merged with it.

>
> Are we going to aim toward a common, Javascript API, or set of API  
> convensions that all the webmapping projects use?
> (This will make it much easier for users to graduate from one  
> project to another and their user requirements change and will  
> reduce the vendor lock in that users hate.)
> I haven't fully thought through the feasibility of this yet.

We have agreed to tackle part one, as it is more achievable and less  
contentious.  The goal is to expose low level events (mouse, key etc)  
from the core, making it relatively simple to hook up existing  
controls in each project to WebMap.js.  However, I believe that most  
of us will be tempted to start building on the OpenLayers Control API  
as well, and it will become the defacto standard through use ... this  
is trickier, though, as each project will require some changes to fit  
into its model I think.

>
> Has someone drafted a Javascript API and design yet?

Apparently Chris has to sleep sometimes, so its not done yet :)

>
> What is the relationship between Map and Layers? How do you treat  
> special cases like 2 maps on the same webpage (eg a locator map and  
> main map)?

I haven't checked, but I assume that OpenLayers can produce two or  
more maps on the same page.  In fact, I know it can be done because  
Tim Schaub posted a cool reference map implementation using two  
OpenLayers Map objects :)

Cheers

Paul

>
>
> -- 
> Cameron Shorter
> http://cameron.shorter.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webmap-discuss-unsubscribe at mail.osgeo.org
> For additional commands, e-mail: webmap-discuss-help at mail.osgeo.org
>

+-----------------------------------------------------------------+
|Paul Spencer                           pspencer at dmsolutions.ca   |
+-----------------------------------------------------------------+
|Chief Technology Officer                                         |
|DM Solutions Group Inc                 http://www.dmsolutions.ca/|
+-----------------------------------------------------------------+