Sure, but I don't think it's possible. -Yaron
-----Original Message----- Date: Monday, February 02, 2009 6:09:53 pm To: [email protected] From: "Sergey Chernyshev" <[email protected]> Subject: [Semantic Forms] Re: Improving the Semantic Google Maps form input Actually, being outside of the map, local search makes it confusing and that's the problem of original and new solution so I think best bet would be to move it inside the map. On Fri, Jan 30, 2009 at 12:24 PM, Yaron Koren <[email protected]> wrote: > Okay, I made a version of this change on Discourse DB: > > http://discoursedb.org/w/index.php?title=London&action=formedit > > Does this improve things at all? Or would a more radical change be better? > > -Yaron > > > > On Wed, Jan 28, 2009 at 2:00 PM, Yaron Koren <[email protected]> wrote: > >> Well, in the change I'm talking about, the "local search" input would not >> be on the map, but under the map, just as it is now - only the text would be >> different. >> >> >> On Wed, Jan 28, 2009 at 1:43 PM, Sergey Chernyshev < >> [email protected]> wrote: >> >>> Yep, that's what what I was actually looking for - to have interface like >>> local search (text field and button on the map) but make it perform >>> geocoding instead. >>> >>> >>> On Wed, Jan 28, 2009 at 1:34 PM, Yaron Koren <[email protected]> wrote: >>> >>>> Yeah, that LocalSearch is a very intuitive interface. The fact that you >>>> can't set the text, and thus change the language, might be a deal-breaker, >>>> though. >>>> >>>> What about just making the existing address-lookup input look more like >>>> LocalSearch's? I'm imaging something that looks like this: >>>> >>>> ---------------------- >>>> | Search the map | Search >>>> ---------------------- >>>> >>>> (Hopefully that fixed-width formatting showed up correctly.) The input >>>> itself contains a gray "Search the map" string, that disappears as soon as >>>> the user clicks in the input; then there's a "Search" button or link next >>>> to >>>> it that the user presses to do the actual lookup. >>>> >>>> Potential solution? >>>> >>>> -Yaron >>>> >>>> >>>> >>>> On Wed, Jan 28, 2009 at 1:17 PM, Sergey Chernyshev < >>>> [email protected]> wrote: >>>> >>>>> Yep, I agree - clearing the input seems odd if you clear the input, but >>>>> if it's kept, then it's not clear to the user why that address is not >>>>> saved, >>>>> but coordinates instead - this can be solved by the in-pan control like >>>>> Local Search or similar where it's sort-of clear that this window is only >>>>> for looking stuff up. >>>>> >>>>> As for reverse geocoding, I think it well depends on the use case - for >>>>> things like specifying location for the event, it makes sense to know >>>>> where >>>>> it is but not knowing the address or another example - when you need to >>>>> post >>>>> location of the address of the Deli you go to every day - you know where >>>>> it >>>>> is on the map, but has no idea about coordinates or address. The question >>>>> is >>>>> if it should be used for entering map coordinates or for entering >>>>> addresses >>>>> (another type of data). >>>>> >>>>> Sergey >>>>> >>>>> >>>>> >>>>> On Wed, Jan 28, 2009 at 1:09 PM, Yaron Koren <[email protected]>wrote: >>>>> >>>>>> Thanks for this feedbac --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Semantic Forms" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/semantic-forms?hl=en -~----------~----~----~----~------~----~------~--~---
