Re: [OSM-talk] Nanomaps

2010-12-14 Per discussione Stella Laurenzo
Frederik,
Thanks for the feedback.  There are in fact a couple of implementations that
are doing similar things, including Tile5 and khtml.org.  At this early
stage of OSS development along these fronts, it is my opinion that it
doesn't hurt to have a fair bit of overlap.  We'll learn from each other and
eventually either define the different niches or consolidate.

There are two key design principles that I'm going after, which I don't
believe are represented anywhere else (including the commercial offerings):
  1. Have a public interface that encourages interaction with the DOM both
surrounding and inside the map.  This is about scratching an itch that as a
JavaScript developer, when I put a map on my page, it is mostly a black box
that is completely managed by some very complicated code that has a
significant overlap and abstracted interface to managing the content that
goes on the map.  If I'm building a webapp, I will already have the tools
for handling events, effects, templating and content generation and I'd like
all of those to be directly applicable to the map.  In this world, the map
library just becomes a thin shim supporting the (non-trivial) image
manipulation and lending positioning/scaling support to your normal DOM
toolbox.
  2. Since its just a thin shim, make it as small as possible.  Leave all
further abstractions for higher level code.

I've been wanting to un-map the mapping APIs for a while and make
something more approachable in detail to normal JavaScript/DOM developers
and this is the start of my attempt to do so.  Time will tell whether it
fills a niche outside of what I need it for.

- Stella

On Tue, Dec 14, 2010 at 12:42 AM, Frederik Ramm frede...@remote.org wrote:

 Hi,


 On 12/14/10 04:04, Stella Laurenzo wrote:

 I recently had need of a JavaScript map library that was small,
 efficient and worked across touch and click devices.  I started the
 nanomaps project to address this need.  It's still at a pretty early
 state, but it supports the following:


 It seems to me that you re-implemented KHTML (khtml.org)?

 Bye
 Frederik



 ___
 talk mailing list
 talk@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/talk

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


[OSM-talk] Nanomaps

2010-12-13 Per discussione Stella Laurenzo
Hi all -
I recently had need of a JavaScript map library that was small, efficient
and worked across touch and click devices.  I started the nanomaps project
to address this need.  It's still at a pretty early state, but it supports
the following:

   - OSM tiles
   - Continuous zoom
   - Scroll wheel
   - Touch gestures
   - Declarative map content
   - 5KB download

I haven't tested on IE or Android yet but supporting them should be
relatively easy.  There are also some improvements that I need to make to
the rendering logic for transitioning between native zoom levels more
smoothly and averaging the touch gestures ahead to improve perceived scroll
performance on the iphone.  I'll be working on some more demos later.  Watch
the github repo if you'd like to be kept up to date on enhancements.

Given that the OSM tiles are the obvious first choice for the maps, I
thought some of the people hanging out here might find this project useful.
 Here's the info:

   - GitHub: https://github.com/stellaeof/nanomaps
   - Demo: http://stellaeof.github.com/nanomaps/demo/demo.html
   - Api Docs: http://stellaeof.github.com/nanomaps/apidocs/

It's explicitly trying not to be a do-everything map library, just something
for all of those cases where you need a map and no frills access to put
interactive bits on it.

Enjoy.
- Stella
___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk