[ka-Map-users] ka-Map and OpenLayers

[Paul Spencer]

Hi Aaron,

I have read this, its an interesting read :)  Personally, I think  
prototype.js is great despite the problems listed in this article.   
And I think there is a commitment to fix some/most of these issues in  
the next big release of prototype (in a backwards compatible way).

Cheers

Paul

On 20-Jun-06, at 3:39 PM, Aaron Koning wrote:

> Heres an interesting critique of prototype.js (you've probably seen  
> it):
>     http://blog.metawrap.com/blog/ 
> WhyIDontUseThePrototypejsJavaScriptLibrary.aspx
>
> Aaron
>
> On 6/20/06, Steve Lime <Steve.Lime at dnr.state.mn.us> wrote: What  
> does OpenLayers offer that ka-map doesn't ( besides a better  
> name ;-) )? The
> list you reel off of limitations is pretty substantial.
>
> Steve
>
> >>> Paul Spencer < pspencer at dmsolutions.ca> 6/20/2006 1:28:19 PM >>>
> Hello ka-Mappers!
>
> I had a very interesting discussion with the developers of
> OpenLayers, a javascript api for tiled maps.  Turns out OpenLayers
> and ka-Map are very similar.  We decided that it would be beneficial
> for both communities if we attempted to merge the projects.  The
> purpose of this email is to present this idea to the ka-Map community
> in order to generate some discussion on the subject.
>
> OpenLayers is hosted at http://www.openlayers.org/.  They have some
> very interesting objectives which I think are compatible with ka-
> Map.  Take a look at their site.
>
> OpenLayers is written on top of prototype.js, which was one of the
> things I was planning to do with ka-Map in the next couple of weeks.
> It has a very nice looking architecture and the code base is very
> readable.
>
> It is lacking quite a few things that ka-Map has:
>
> * core tiling engine is very similar, but it is not quite as optimal
> (doesn't reuse images for instance)
>
> * overlay stuff is point/text only
>
> * lacking tools (layer controls, scale bar etc) and the windowing  
> stuff
>
> * lacking query capability
>
> * tile caching
>
> * probably several other things I can't think of right now
>
> I think that there are some differences in how OpenLayers and ka-Map
> approach things, but I'm not entirely sure that they are significant.
>
> At this point, I am proposing to join the two projects into a single
> project.  My desired approach would be to start with the OpenLayers
> code and start to bring over the parts of ka-Map that I(we) feel are
> missing.
>
> Please let me know what you think of this.  And point out all the
> problems you can think of.
>
> Cheers
>
> Paul
>
> +-----------------------------------------------------------------+
> |Paul Spencer                           pspencer at dmsolutions.ca   |
> +-----------------------------------------------------------------+
> |Applications & Software Development                              |
> |DM Solutions Group Inc                 http://www.dmsolutions.ca/|
> +-----------------------------------------------------------------+
>
>
>
>
> _______________________________________________
> ka-Map-users mailing list
> ka-Map-users at lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/ka-map-users
>
>
> _______________________________________________
> ka-Map-users mailing list
> ka-Map-users at lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/ka-map-users
>
>
>
> -- 
> +--------------------------------------------
> |  Aaron Koning
> |  Information Technologist
> |  Prince George, BC, Canada.
> +--------------------------------------------
> |  http://datashare.gis.unbc.ca/fist/
> |  http://datashare.gis.unbc.ca/gctp-js/
> +--------------------------------------------

+-----------------------------------------------------------------+
|Paul Spencer                           pspencer at dmsolutions.ca   |
+-----------------------------------------------------------------+
|Applications & Software Development                              |
|DM Solutions Group Inc                 http://www.dmsolutions.ca/|
+-----------------------------------------------------------------+