On CSS and Layout stuff, it sounds like Yarko is picking this up, this is fine with me I am super busy, our access non-profit is officially in startup mode and I need to shift into fund raising mode big time.
Cheers, Chris On Apr 3, 3:15 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > 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? > > yes. that what we need. somebody needs to do the homework of making a > list of what should be fundamental. > > > > what about the css convetions in SQLFORM(formstyle=...)? If I commit > > > this the canny be changed? > > > I very much like the idea of "layout / style" helpers for forms (form > > as a visual entity) .... don't understand the end of your sentence, > > sorry.... :-/ > > I do not either... need sleep. I think I meant "If I commit what is in > trunk the new CSS naming conventions for SQLFORM(formstyle=....) > cannot/should not be changed" I am trying to make sure you and others > look at it NOW instead of raising issues about them LATER. -- 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.
