On Mon, Dec 10, 2007 at 09:33:25PM +0000, Adam Boardman wrote:
Kake,
I was purswaded to join this list :)
Does that fit in with what Adam wants his app to
do?
Yep that sounds like a grand plan. Assuming that the central server can
also be given any comments or new additions (why not be flexible), which
it would then return to the relivant local guide site.
I don't think any central service should be storing data; it needs to be
kept lightweight. I also see it being quite different to the main
OpenGuides code, so..
You would need to handle the case for new additions to
the guides that
are not within the bbox of any current guide, I'd suggest that these are
held on the central server waiting for a local guide for the specified
area to be setup (or to be assigned to an existign one if just outside
the bbox). Might be useful to guage a feeling of how much interest an
area would have in a guide.
..maybe there is also a need for a global OpenGuide that can be used as a
place to store such things.
Having a view the full guide in the browser on your
phone would be a
useful feature for those on all you can eat mobile tarrifs.
I don't quite understand what you're getting at here; what, technically
is required that isn't already provided by OpenGuides? Is it just a case
of mobile-friendly stylesheets?
Dominic.
--
Dominic Hargreaves |
http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)