On Fri, 8 Aug 2008 12:29:33 +0200, "Nic Roets" <[EMAIL PROTECTED]> wrote: > My head is spinning after reading through all the posts. > > A few constructive suggestions : > > Perhaps we should create a mailing list for discussion on mobiles > because currently it divided between talk, dev and routing. I'm always > unsure what I should post to routing because a lot of gosmore issues > are rendering etc.
I would think that you take it where the people that can help you are. Gismore is a router so people developing on gosmore would be here. Would they not? Interactive rendering is a big point in rotuers and differnt from tile-rendering or rendering in editors that people on the dev-list would know more about, wouldn't they? > Development is not all about design and programming. A lot of > investigation, analysis, testing and documentation is required : > * The ARM CPU has a builtin MMU and there's no point in duplicating > that. Mobile developers should really look into mmap() for their > programming language and operating system. It will be a major step > towards a mobile data format. Thanks for the suggestion. However this makes the assumption that a language that can do mmap is used (I used to write embedded java.) and limits input-checking (how to test a pointer for validity?). However on the pro-side it can make walking the graph very efficient. Does mmapping data-structures with links work when the file comes from another device where memory-locations may be different? > * Windows (incl WinCE) comes with fast rendering of rotated text. Can > other mobile platforms do it fast enough ? I find cairo a bit sluggish > on my notebook, perhaps it's really bad on OpenMoko... I don't think this affects the data-format at all. > If we want to achieve something, we'll have to stand on each other's > shoulders. For example I'm finding mobile editing extremely useful. So > for gosmore I implemented simple additive functions. Leave the > splitting and combining of ways to JOSM. But now the requirement > arises for a JOSM plugin to stream line the process. And such a plugin > may also be useful for postprocessing other mobile edits. Yes, mobile editing is usefull. Do you suggest to not limit the format? I fear this would make it inefficient for non-editors as we need to keep IDs, keep data we don't display, keep free space in files to allow for growth of data-strucures, re-generate indice (think indexed place-names for adress-searches) and keep a strong separation of ways and nodes. Editors also work on small data-sets as opposed to whole countries and continents for routers. My personal appinion is that supporting editors limit design too much for a format to be also usable for routers, navigators and moving maps. Do you have further arguments supporting the point I think you wanted to make? Marcus _______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/listinfo/routing
