On Dec 14, 2008, at 8:58 AM, Rob wrote:
> Hi Andrew,
>
> I''m continuing to add to the mapstraction library and wanted to
pick
> your brains.
> The following functions have now been added and committed to SVN,
> help has been updated, please copy over to website :)
Awesome - that''s a huge list. Can''t wait to play with them.
>
> I am a liitle concerned that this last bunch around radius searching
> (supporting points and polylines/routes) are dirtying the core
> library slightly. Would you prefer these were recreated as a
> seperate .js file?
Yes - but even better we should chat about how to do the migration to
the split apart architecture. In general I would like to drop the
overall file size and overhead of Mapstraction by loading in provider
and support JS files only as necessary. Have you seen the previous
emails about it? We could chat online perhaps tomorrow - I''ll be on
IRC in #geo in irc.oftc.net or #osgeo on Freenode.
>
>
> I also have an issue with the modified
> LatLonPoint.prototype.distance function. This was changed because
> the existing calculation doesn''t take into account current
> projection and skews the result. Problem is, the marker doesn''t
know
> its API until it is added to the map. Only way I can think of
> getting round this is to make the API a global variable. A major
> drawback of this is that multiple map types can''t then co-exist on
> the same page. What do you think?
I''d prefer to not preclude multiple map types on the same page -
though I doubt that''s a "widely" used feature except when
doing direct
comparisons (quality of the base map, etc.)
>
>
> Finally, I have one batch of new functions left around routing I am
> yet to add.
> It makes sense for these to go into the routing.js file, but they
> don''t quite match existing functionality.
>
> I have:
> Mapstraction.prototype.getRoute(points, callback)
>
> Which returns a polyline based on 2 end points. Your functions seem
> to be based on addresses (more geocoding rather than routing?) and
> return point arrays rather than polylines.
This was originally based on the MapQuest routing API due to their
support. I''m not opposed to fixing it up to make it more general to
work with other routing interfaces.
>
>
> How would you like to merge these?
>
> Kind regards,
>
> Rob
>
>
>
>
>
> 2008/12/8 Rob <mapstraction at thegecko.org>
> D''oh! I must remember to use those messages.
>
> They are a few of the functions I sent previously, have a few more
> to go but together they should make radial searching nice and easy.
> I''ll create a demo for the site once complete that you can
publish.
>
> New functions have been documented in the new doc build, I''ll list
> them all once complete.
>
> To get around the JSDoc issue, I commented out the containing
> ''(function(){'' and ''})()'' lines during
doc creation. With these left
> in place JSDoc says ''nothing to do''. Not sure how this
can be fixed
> without delving into the source :)
>
> Cheers,
>
> Rob
>
> 2008/12/7 Andrew Turner <ajturner at highearthorbit.com>
>
> On Dec 7, 2008, at 7:02 AM, Rob wrote:
>
>> I''ve updated the mapstraction javascript with a sprinkling of
new
>> functions.
>>
>> Andrew, I''ve regenerated the documentation and committed it
all,
>> but it hasn''t appeared on the website.
>
> Great! What are they? The log message from you is empty. :)
>
> There aren''t SVN hooks for updating the webpage. I''ve
pulled an
> update on the site.
>
>
>>
>>
>> As a side note, JSDoc doesn''t like the isolating
>>
>> (function(){
>> ...
>> })();
>>
>> so it requires commenting out during document generation.
>
> Hrm, I haven''t dug into JSDoc - is there a way to fix this?
>
>>
>>
>> Cheers,
>>
>> Rob
>>
>> _______________________________________________
>> Mapstraction mailing list
>> Mapstraction at lists.mapstraction.com
>>
http://lists.mapstraction.com/listinfo.cgi/mapstraction-mapstraction.com
>
> --
> Andrew Turner
> mobile: 248.982.3609
> email: andrew at highearthorbit.com
> blog: http://highearthorbit.com
>
> -- Helping build the Geospatial Web --
> http://geocommons.com --- http://mapufacture.com
> Introduction to Neogeography - http://oreilly.com/catalog/neogeography
>
>
>
--
Andrew Turner
mobile: 248.982.3609
email: andrew at highearthorbit.com
blog: http://highearthorbit.com
-- Helping build the Geospatial Web --
http://geocommons.com --- http://mapufacture.com
Introduction to Neogeography - http://oreilly.com/catalog/neogeography
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.mapstraction.com/pipermail/mapstraction-mapstraction.com/attachments/20081215/e12ba658/attachment.htm>