Hi,
noticed the syntax highlighting has been added back to the
style editing page, woot!
Few minor observations here:
http://www.flickr.com/photos/29110296@anonymised.com/2741261268/in/set-72157606470246729/
1) there is no description
2) the "toggle editor" check seems a little misplaced, afaik it's
created by editarea itself, it would be nice if its label was
on the same line as the checkbox, ideally it would be nice
it checkbox was placed before the edit area (not sure if
Chris can do anything about it)
3) there is something going on with the submit/cancel button.
I guess it's part of that "geoserver wicket" guide we have
to write, in particular on the topic of html/css conventions
Cheers
Andrea
Andrea Aime ha scritto:
2) the "toggle editor" check seems a little misplaced, afaik it's
created by editarea itself, it would be nice if its label was
on the same line as the checkbox, ideally it would be nice
it checkbox was placed before the edit area (not sure if
Chris can do anything about it)
Whoops, did not notice Chris already provided this feedback here:
http://jira.codehaus.org/browse/GEOS-2106
The idea of tabs looks promising, the toggle is provided by
editarea and thus it may not be easy to replace, but we can hide it
all right. I just don't rememeber if there is a javascript api
to pilot the toggle or not (if there is, we can use whatever other
control to perform the switch).
Cheers
Andrea
3) there is something going on with the submit/cancel button.
I guess it's part of that "geoserver wicket" guide we have
to write, in particular on the topic of html/css conventions
This brings up something that popped into my mind yesterday. I am finding it hard to "style" things properly and consistently when adding ui components. Now part of the problem is that i have a severe lack of css knowledge, but the style sheets we are using don't seem all that self explanatory.
Anyways, a set of conventions and guidelines would be great, so if it is something that is coming i eagerly await it. Until then I will continue using firebug and all its great tools to figure out how i should be doing styling.
Cheers
Andrea
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
I'm planning on working on a GeoServer UI Development guide sometime real soon, but until we have something to point people at the guide is quite simple:
When you are building a form, group all the elements like so:
<ul>
<li>
<label for="fieldname"><wicket:message key="namekey">Default Name</wicket:message></label>
<input wicket:id="fieldname" type="text"></input>
</li>
</ul>
(in the case of radio buttons and checkboxes, the label comes after the input; for all other elements it should be before it.)
For everything else, there is not a well-established set of practices so just ask in the IRC channel; tenzochris is our current CSS guru (but he won't be available to us for too much longer.)
-d
Justin Deoliveira wrote:
3) there is something going on with the submit/cancel button.
I guess it's part of that "geoserver wicket" guide we have
to write, in particular on the topic of html/css conventions
This brings up something that popped into my mind yesterday. I am finding it hard to "style" things properly and consistently when adding ui components. Now part of the problem is that i have a severe lack of css knowledge, but the style sheets we are using don't seem all that self explanatory.
Anyways, a set of conventions and guidelines would be great, so if it is something that is coming i eagerly await it. Until then I will continue using firebug and all its great tools to figure out how i should be doing styling.
Cheers
Andrea
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
On Thursday 07 August 2008 12:36:19 pm David Winslow wrote:
I'm planning on working on a GeoServer UI Development guide sometime
real soon, but until we have something to point people at the guide is
quite simple:
When you are building a form, group all the elements like so:
<ul>
<li>
<label for="fieldname"><wicket:message key="namekey">Default
Name</wicket:message></label>
<input wicket:id="fieldname" type="text"></input>
</li>
</ul>
(in the case of radio buttons and checkboxes, the label comes after the
input; for all other elements it should be before it.)
any chance the label for checkboxes and radio buttons to appear at the right
of the input field instead of bellow? is it just a matter of css?
For everything else, there is not a well-established set of practices so
just ask in the IRC channel; tenzochris is our current CSS guru (but he
won't be available to us for too much longer.)
-d
Justin Deoliveira wrote:
>> 3) there is something going on with the submit/cancel button.
>> I guess it's part of that "geoserver wicket" guide we have
>> to write, in particular on the topic of html/css conventions
>
> This brings up something that popped into my mind yesterday. I am
> finding it hard to "style" things properly and consistently when adding
> ui components. Now part of the problem is that i have a severe lack of
> css knowledge, but the style sheets we are using don't seem all that
> self explanatory.
Just layout the buttons like this (I seem to remember you can use either a
link or a button, I'm using a SubmitLink for the submit action though)
<div class="buttons selfclear">
<a href="#" wicket:id="cancel"><wicket:message
key="cancel">Cancel</wicket:message></a>
<a href="#" wicket:id="save"><wicket:message
key="save">Save</wicket:message></a>
</div>
>
> Anyways, a set of conventions and guidelines would be great, so if it is
> something that is coming i eagerly await it. Until then I will continue
> using firebug and all its great tools to figure out how i should be
> doing styling.
>
>> Cheers
>> Andrea
>>
>>
>> ------------------------------------------------------------------------
>>- This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge Build the coolest Linux based applications with Moblin SDK &
>> win great prizes Grand prize is a trip for two to an Open Source event
>> anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge Build the coolest Linux based applications with Moblin SDK & win
great prizes Grand prize is a trip for two to an Open Source event anywhere
in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel