nathanY's dashboard

hmm, i guess this problem is a flash in firefox/leopard and not with modest maps.

i also have the issue in firefox3 and leopard. quitting and relaunching seems like a temporary fix, but it makes for a painful web development environment. occasionally, i can't get to any websites, when safari or other internet connectivity tools work.

well that's good to know. now i just have to figure out why my browser is screwy :)

Hi Nathan,

I can't reproduce your problem with Firefox 3 here... the map works great!

If anyone else can reproduce it, let us know.

I'm trying to optimize my application as well. It all runs great with 20-30 sprites on the map, but as the numbers rise above 100 it's another story. I'm calculating the location for all visible objects on panning and zooming, and it's pretty cpu-intensive. Has anyone of you found a way to optimize this?

I don't suppose there's a similar tutorial for as3 floating around?

... or maybe a better question: does anyone know the file structure that zoomifyer ez spits out? I having trouble figuring out what how the tiles are grouped.

That all helps a lot. Thanks! I have a feeling your last point is going to do the most.

By the way, Modest Maps is great, and I really appreciate you guys putting out the API. I'm spreading the word.

It's tricky to say without knowing when you're calling locationPoint...

Firstly, don't do it on every frame. Probably obvious but you never know.

Second, there's no need to redraw your lines calling locationPoint every time the map is panned. For panning, you can grab the offset from the pan event (store the start position on start pan, increment that, and only reset it and redraw everything on end-pan).

But if you're calling it every time the map is zoomed, that's probably correct, especially for in-between zoom levels. It's possible to scale your layer, but you probably want to clip things outside of the map bounds and things like that to stop your GPS lines being super-huge at large zoom levels.

Lastly, perhaps the node-edge metaphor is slowing you down? If you're making a new DisplayObject (Sprite, Shape...) for each node and line, and moving them all around (perhaps treating nodes as map markers?) that's going to be pretty heavy. Better would be to draw your GPS tracks on a single sprite, and only draw nodes as separate markers if you need them to be interactive.

Hope that helps!