On Tue, Nov 18, 2014 at 5:43 PM, Gabriel Roldan
wrote:
> +1 for autocomplete by default + find button. Looks really neat.
>
> (very) small observation: try using the appropriate CSS for the find
> button so it looks like the default OK/Cancel buttons.
>
Yep :)
Cheers
Andrea
--
==
GeoServer P
+1 for autocomplete by default + find button. Looks really neat.
(very) small observation: try using the appropriate CSS for the find button
so it looks like the default OK/Cancel buttons.
On Mon, Nov 17, 2014 at 5:19 PM, Phil Scadden wrote:
> But yes, good point. The “Find” button and di
But yes, good point. The “Find” button and dialog should suffice in
that case I’d guess as the alternative.
I like this too. Seems like good way to get best.
Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or d
The other option is, as said, to switch between combo and autocomplete text +
dialog based on the number of items,
but I'm afraid it would be surprising to people (what if you end up living at
the threshold... you get one control
or the other depending on the hour of the day? ;-) )
Think of it
On Mon, Nov 17, 2014 at 6:47 PM, Jonathan Moules wrote:
> Hi Andrea,
>
> +1 for autocomplete being the default, but there should definitely be a
> way for folks to use a non-autocomplete option too ( for < 1000 or whatever
> features).
>
That's why I put that "find" button on the side, you can
Hi Andrea,
+1 for autocomplete being the default, but there should definitely be a way for
folks to use a non-autocomplete option too ( for < 1000 or whatever features).
This way folks who are not intimately familiar with the project will be better
able to use it by navigating a list rather than
