On Apr 3, 12:23 am, Yarko Tymciurak <resultsinsoftw...@gmail.com> wrote: > On Apr 2, 11:31 pm, Massimo Di Pierro <mdipie...@cs.depaul.edu> 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-level.html Fun! -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
