On Mar 20, 8:27 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > Just for fun: > > http://web2py.com/zengarden > > then click on the [zengarden] link under the menu, under the "index" > link. You can change the skin per user, per session. > This is a bare bone welcome app with the layout
:-) Loooovely!!! :-) > > http://web2py.com/zengarden/static/layout.html > > Problem: all zengarden layouts hardcode text in images for each skin. Yeah - that's not _really_ a problem for us... the "layouts" we can parse; the css we can include; > This makes them not as general as we need them. > It makes it more of a proof of concept than a useful tool > unfortunately. Actually, it's potentially a good proof of concept - by us shifting to css-based (away from table, html based layout) we are entering new, nice spaces. The fact that zengarden (for example) has provided a "template" css and html files, which contain "more than you'll use" - what they've effectively done (for graphics artists, non-programming designers) is made this tractable. For us, what this does is provide an example of a namespace - we can look at what others do, and adopt / adapt, or design a namespace based on their example. It would make sense (as an excercise) to try to automate their css names, and see if there are useful rules we can develope to actually make something usefully skinnable... (I'm likely to try this, just because of my surprise of how trivial / easy esy-css was; my experience with yahoo frames, other such solutions left me... with more to digest / think about than I cared to for layout....) > > Other problem: some layouts are broken because assume a few divs that > we do not have. Well, that's the first thing we can do: find a compatible class / id set in our "base" css; I think I'll play around w/ this, perhaps tomorrow... first to try compatability w/ zengarden (just as an excercise, if nothing else). The second step will be to name, and programmatically output sections - to see how that works; The third will probably be to catalog use, so you can tell what web2py applications "use" from the css set (since many skins are necessarily a subset). Fun awaits! :-) - Yarko > > Massimo > > On Mar 20, 7:18 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > > > Well... the quickest way to change layouts is to store the > > configuration in the database... > > > So have a table for web2py meta information, that contains > > "current_layout" which is value is "layout.html" or "mynewlayout.html" > > etc etc. > > > In all views instead of {{ extend "layout.html" }} it will be {{ > > extend current_layout }}. Then do the same with the CSS as well. > > > {{ response.files.append(my_current_css) }} > > > Cache these variables in RAM to save from un-necessary dbio > > > -Thadeus > > > On Sat, Mar 20, 2010 at 5:11 PM, Yarko Tymciurak > > > <resultsinsoftw...@gmail.com> wrote: > > > Having said this, the zengarden shows how to accomplish some standard > > > naming, and now to switch css to affect things.... > > > > That by itself is quite useful - and worth (for me at least) more > > > closely... > > > > On Mar 20, 1:53 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > > >> I envision having an app create wizard, you select a layout (based on > > >> ez-css), and then select a skin for the layout. :) > > > >> -Thadeus > > > >> On Sat, Mar 20, 2010 at 1:50 PM, mr.freeze <nat...@freezable.com> wrote: > > >> > I think the ability to select a skin when creating an app would be a > > >> > major plus and help kick-start development for the design-impaired > > >> > such as myself. > > > >> > On Mar 20, 1:32 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > >> >> I just came across this: > > > >> >> http://www.csszengarden.com/ > > > >> >> It is one simple html layout (only divs) with 210 PURE CSS skins: > > > >> >> http://www.mezzoblue.com/zengarden/alldesigns/ > > > >> >> This could be an option for the welcome app. If we use their html, it > > >> >> would be trivial to add a small admin option that downloads a team to > > >> >> zengarden and applies to skin. Options that require overriding the > > >> >> HTML are more complex to handle. > > > >> >> What do you think? > > > >> >> Massimo > > > >> > -- > > >> > 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 > > >> > athttp://groups.google.com/group/web2py?hl=en. > > > > -- > > > 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 > > > athttp://groups.google.com/group/web2py?hl=en. > > -- 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.
