This is all I could think of so far:
// EZ.css 2009 -2010 (c) | ez-css.org ez-plug-min.css :: version
1.1 :: 01182010
.ez-wr:after,.ez-box:after{content:".";display:block;height:
0;clear:both;visibility:hidden}.ez-wr,.ez-box,.ez-last{display:inline-
block;min-height:0}/* \*/ * html .ez-wr,* html .ez-box,* html .ez-
last{height:1%}.ez-wr,.ez-box,.ez-last{displa\
y:block}/* */.ez-oh{overflow:hidden}* html .ez-oh{overflow:visible}.ez-
oa{overflow:auto}.ez-dt{display:table}.ez-it{display:inline-table}.ez-
tc{display:table-cell}.ez-ib{display:inline-block}.ez-fl{float:left}*
html .ez-fl{margin-right:-3px}\
.ez-fr{float:right}* html .ez-fr{margin-left:-3px}.ez-25{width:
25%}.ez-33{width:33.33%}.ez-50{width:50%}.ez-66{width:
66.66%}.ez-75{width:75%}.ez-negmr{margin-right:-1px}* html .ez-
negmr{margin-right:-4px}.ez-negmx{margin-right:-1px}.ez-negml\
{margin-left:-1px}* html .ez-negml{margin-left:-4px}
// for flash style
div.flash {
position: absolute;
float: right;
padding: 10px;
top: 0px;
right: 0px;
opacity: 0.75;
margin: 10px 10px 10px 10px;
text-align: center;
clear: both;
color: #fff;
font-size: 11pt;
text-align: center;
vertical-align: middle;
cursor: pointer;
background: black;
border: 2px solid #fff;
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
z-index: 2;
}
// for error messages
div.error {
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
background-color: red;
color: white;
padding: 3px;
border: 1px solid #666;
}
// to customize flash
.warn {
background-color: yellow;
color: black;
padding: 5px;
}
.info {
background-color: #E5FFE5;
color: black;
padding: 5px;
}
.error {
background-color: red;
color: white; padding: 5px;
}
// to prevent wrapping of labels in forms
label { text-align: left; white-space: nowrap; }
// for alignment in forms
form table tr td {
text-align: left;
vertical-align: top;
}
// for pure CSS tooltips
// requires
// <a href="">click me<span class="tooltip">and this pops up</span></
a>
a { position: relative; }
span.tooltip { display:none; }
a:hover span.tooltip, span.tooltip:hover {
position: absolute;
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
z-index: 100;
top: 1.2em;
left: 0.5em;
width: 200px;
display: block;
padding: 5px;
background: yellow;
border: 2px solid yellow;
color: black;
opacity: 0.75;
}
On Apr 3, 10:37 am, Yarko Tymciurak <[email protected]>
wrote:
> On Apr 3, 12:23 am, Yarko Tymciurak <[email protected]>
> wrote:
>
> > On Apr 2, 11:31 pm, Massimo Di Pierro <[email protected]> wrote:
>
> > > Hi Yarko,
>
> .....
>
>
>
> > > 4) one file with everything else (base.css) to be replaced is a custom
> > > layout.html is used.
>
> > If you mean for base.css to not be "replaced", but possibly be
> > inherited form, over-ridden by a custom layout, yes.
>
> > Otherwise, I would want to be sure things that gluon might depend on
> > (e.g. css for form control) would be guaranteed to be there;
>
> > Would "base" and "std" make sense? std you could completely
> > replace; base should always be there.
>
> > Anyway, in practice this may prove unnecessary, but I would be more
> > comfortable if we start out with that concept: fundamentals that are
> > always there (you can override them but the classes / ID's there
> > should be guaranteed to be defined; and other stuff you can replace
> > if you want for new layouts.)
>
> > Does this sound like it makes sense?
>
> > I think this will enable "helpers" from gluon that manipulate css,
> > that we can depend on being there (similar to html helpers, perhaps
> > something for form control.... not sure what else there would be -
> > perhaps layout helpers too??? --- we'll see).
>
> As I read my reply to Massimo on this, I am struck by a few things:
> - CSS helpers will not need to be in a file, as then can (and probably
> should) be generated from the core.
> - All that would be needed is a naming convention
> - how to build with / on top of std css would be more interesting, and
> some default settings that _use_ std stuff could be used, with (for
> Massimo's case) something like routes_example.py: a
> web2py_examples.css (or something like that)...
>
> BTW - I read an article about HTML-5: a couple of Google guys porting
> quake2 to the browser (!) and it's implicaitons (to join a game in
> progress, just post a URL to it in a page!). Check out the video and
> blogs:http://timepedia.blogspot.com/2010/04/gwtquake-taking-web-to-next-lev...
>
> Fun!
--
You received this message because you are subscribed to the Google Groups
"web2py-users" 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/web2py?hl=en.
