On Mar 20, 6:57 pm, Pepe <pepea...@gmail.com> wrote: > Hello, > > i'm designer and before of that a human being, so i wonder: why make > web2py less human readable? > > what's "ez-negmr" "ez-50"??!!!!
ez: the prefix that identifies it as ez-css; negmr, as Thadeus correctly pouinted out, is negative margin, and 50 is 50%; By comparison, web2py base.css has width10em (for example) - while this is "more readable", that kind of readability is only suitable for really simple things (width50em, after all, describes just ONE css setting!!!). Thadeus also pointed out - there are so, so few of the ez-css, and they are short for some reason: makes it easy to combine severall classes in one div / span. Anyway, in practice, after doing one layout, I was surprised at how comfortable, easy it was. So (the truth comes out!) I "told" Massimo I'd "done" welcome in ez-css (I was sure it was trivial) --- when he asked me to send it to him, it was a very, very short time to do (and - if you look at the diff from Massimo's checkin, it really was a trivial change! that is a _good_ sign!). Regards, - Yarko > > the semantic of the most css framework is a problem, because they > haven't. > > ...On the other hand: > To have fewer elements is simpler to understand when you start to > learn and use something new. > To have a simple layout, without images, without a heavy css ... etc. > I think it's better, perhaps more ugly, but faster to learn. > Less elements = less uncertainty. This encourages the learning > process. > > well, it's just what I think. > > Greetings! > > Pepe. > > On Mar 20, 1:25 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > Yarko did it! The new welcome with ez.css is in trunk. We still need > > do add something to allow skinning and rearrange the css (right now we > > have: > > > applications/welcome/static/base.css > > applications/welcome/static/calendar.css > > applications/welcome/static/ez-plug-min.css > > applications/welcome/static/ez-plug.css > > > massimo > > > On Mar 19, 6:05 pm, Yarko Tymciurak <resultsinsoftw...@gmail.com> > > wrote: > > > > On Mar 19, 2:24 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > > I played with ez-css (which I like) but yet it reminded why I used > > > > tables. > > > > Yeah - the presence of tables in the layout really causes troubles! > > > > > Here is my problem and I am sure it is just me being dumb. Say > > > > I want a header, a footer and two columns in between. I want the left > > > > column of fixed with (a menu, 200px) and a right column to foll the > > > > rest of the space (content). Because of the way it works (and most of > > > > these frameworks work the same way), the columns float to right > > > > therefore I must specifycontent before the menu. Hence I cannot find a > > > > way to make the menu fixed width and the content fill the rest of the > > > > space without messing up the alignment of the boxes. Can you do it? > > > > If I understand you, I think this is pretty easy w/ ez-css. I have > > > now done a few layouts w/ it in web2py (as of last night), and have > > > sent you an ez-css layout.html for "welcome" app (it uses the css > > > classes from base.css, but a few settings that were assigned to table > > > elements, I had to update / put elsewhere - base.css has minor > > > changes; ez-plug.css remains stock). > > > > There are probably other things that could be cleaned up in base.css, > > > but this was pretty easy (once I realized how to go about it). > > > > - Yarko > > > > > Massimo > > > > > On Mar 18, 11:46 pm, Yarko Tymciurak <resultsinsoftw...@gmail.com> > > > > wrote: > > > > > > On Mar 18, 10:31 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > > > > The problem I see is that it is too simple. > > > > > > sizeXofY does not seem to guarantee that all columns have the same > > > > > > lenght (ez-css does it). > > > > > > I like to have the menu column fixed width and the main column > > > > > > elastic > > > > > > and it does not do that (not sure if ez-css does). > > > > > > I have installed ez-css to try out / play with... it does do fixed > > > > > width + variable width columns: > > > > > > In multiple ways, actually (depending on how you nest it); > > > > > seehttp://www.ez-css.org/layouts > > > > > > See module 2A, 2B, layout 2, layout 3, etc.... > > > > > > Each of these use "ez-50", a 50% width element, or "ez-33", a 33% > > > > > width element. > > > > > > ez-css encourages you to create your own width element if the pre- > > > > > defined ones don't "do it" for you - so, create a > > > > > ez-500px, and you'd have what you want. > > > > > > This seems like a really clean, easily modifiable and "combinable" > > > > > package... I'm going to play with it in the next few days to see how > > > > > my opinion holds up in use. > > > > > > - Yarko > > > > > > > On Mar 18, 8:59 pm, villas <villa...@gmail.com> wrote: > > > > > > > > Ez-css seems like a good enough option, but before making your > > > > > > > mind > > > > > > > up, have a look at the simplicity of oocss.org/grids_docs.html > > > > > > > (with > > > > > > > Firebug). Oocss might give more possibilities, but admittedly, > > > > > > > is > > > > > > > heavier. > > -- 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.
