autocomplete list behavouir
pingou at pingoured.fr
Tue Oct 2 07:39:07 PDT 2012
On Tue, 2012-10-02 at 07:35 -0700, Dirk Hohndel wrote:
> On Oct 2, 2012, at 7:31 AM, Pierre-Yves Chibon wrote:
> > On Tue, 2012-10-02 at 07:25 -0700, Dirk Hohndel wrote:
> >> On Oct 2, 2012, at 6:50 AM, Henrik Brautaset Aronsen wrote:
> >>> Den 02.10.12 15:35, skrev Dirk Hohndel:
> >>>> I still think that a lot of people will go back to the same places over
> >>>> and over again... I sure do - but then I may not be typical. My guess
> >>>> is that anyone who does local diving or has a favorite vacation spot
> >>>> will have a rather small set of locations repeat. And very few people
> >>>> will go to hundreds of different dive sites (but again, that could be
> >>>> wrong).
> >>>> Is there anyone with a really strong preference and a good argument
> >>>> one way or another?
> >>> I usually dive a lot of the same dive sites, just like you. But we're still just two out of a bazillion divers...
> >>> Anyway, if we choose one or the other, I hope we'll have a way of maintaining dive sites in the future. This way we can add GPS coordinates, descriptions, dive maps... And in that case, I would at least want to have autocomplete on those.
> >> Yes - one of my post-2.0 ideas is to create a little web service with companion apps on iPhone and Android.
> >> Basically what this would do is this: you are at a dive site, you start your little app. It acquires the GPS coordinates, you can name the location / dive site, and then it pushes that tuple to the web server with your ID (just some numeric ID that you get when registering with the service).
> >> Then when you are back at home or at the hotel and start subsurface it connects to the same server and offers you the locations that you saved that way… there could even be some time based matching of dive and location acquisition time (with some fuzz factors based on the fact that you likely did this a few minutes before or after actually diving :-)
> >> Does this sound useful?
> > Do you consider python for such (web)app ? If so I'm definitively in :)
> I'm totally open to the implementation language. Since this would be running on my colo server (Mac Mail.App thinks this should read "cool server" :-) ) I have some concerns about security and about giving admin rights to others, but within those restraints I'm open to anything.
The server should be able to run anywhere no?
As in, you may have yours, someone else their but of course, up to us to
provide a 'public'/main one.
So no need for admin right at first I'd think :)
> My guess is that writing the Android / iPhone apps will be the harder part (but I guess that's just because I haven't really written either type of apps)
Ok here I have the same worries, I don't have apple products so
iPhone/iPad are out for me but I'll try to help on the Android side.
More information about the subsurface