Re: [Zope-CMF] Pure CSS for main template
Am 06.10.2008 um 02:00 schrieb Jens Vagelpohl: Please make sure you stick to one functionality/change per branch to make it easier for others to make a diff and understand all the changes. I thought you wanted to use the branch for the folder_contents work only ;-) oops, sorry! It's just I'd been planning to work on this for about a year and yesterday was a good time to start. Should I create a separate branch just for this? The idea is not to do a redesign but to implement the existing one using CSS now that pretty much all of the browsers in use have at least adequate support. Customers will hopefully still want to have a different design but it should be easier to do. CMFDefault represents a simple sample application for the CMF. It doesn't have to be pretty by itself, but any changes should have these goals: - make it easier for people to customize the look-and-feel using CSS only, or... - make it easier to take the current main_template as a guideline for a new main_template by making it as simple and understandable as possible. I hope to achieve both of those. I'm using an em based elastic approach where the layout will grow with the chosen text size. I know that most browsers have now caught up with Opera and offer proper zooming but there are still lots of IE6 installs out there. I'm working on a baseline of 1024 x 768. Does anyone have objections to this? I'd be opposed to any template that uses fixed widths and which does not degrade gracefully with less or more width. hm, the current layout is fixed-width. The new one is not per se fixed- width is driven by the size of the font that a user has. The argument about growing and shrinking gracefully is important but it is also important to maintain usability and particularly readability: having a site expand to fit 100% can mean either extremely long lines or ugly gaps between columns or conversely columns with line-breaks every word. The following article covers the main issues concisely: http://www.htmldog.com/articles/elasticdesign/ What I am to do is to maintain the current design but make it much easier to adapt through CSS, ie. swap between font-size based and percentages. So good documentation of how the layout works is essential. Charlie -- Charlie Clark Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-938-5360 GSM: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Pure CSS for main template
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 6, 2008, at 09:21 , Charlie Clark wrote: Am 06.10.2008 um 02:00 schrieb Jens Vagelpohl: Please make sure you stick to one functionality/change per branch to make it easier for others to make a diff and understand all the changes. I thought you wanted to use the branch for the folder_contents work only ;-) oops, sorry! It's just I'd been planning to work on this for about a year and yesterday was a good time to start. Should I create a separate branch just for this? If all you want to do is tweak the main_template then a branch is overkill. I'd work directly on the trunk for that. What I am to do is to maintain the current design but make it much easier to adapt through CSS, ie. swap between font-size based and percentages. So good documentation of how the layout works is essential. No worries, you've obviously done your homework. And thanks for taking this up, the current template has indeed aged a lot. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkjpwq0ACgkQRAx5nvEhZLL4zQCfRAYaFeglskxTGSrCmMGEWWOY KhsAn1XneYNjThMRi9RFpJTApeTF2RhF =wvkC -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Pure CSS for main template
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 5, 2008, at 20:06 , Charlie Clark wrote: now that I've got my own branch I've finally made a start on a pure CSS version of main_template.pr for CMFDefault. Please make sure you stick to one functionality/change per branch to make it easier for others to make a diff and understand all the changes. I thought you wanted to use the branch for the folder_contents work only ;-) The idea is not to do a redesign but to implement the existing one using CSS now that pretty much all of the browsers in use have at least adequate support. Customers will hopefully still want to have a different design but it should be easier to do. CMFDefault represents a simple sample application for the CMF. It doesn't have to be pretty by itself, but any changes should have these goals: - make it easier for people to customize the look-and-feel using CSS only, or... - make it easier to take the current main_template as a guideline for a new main_template by making it as simple and understandable as possible. I'm using an em based elastic approach where the layout will grow with the chosen text size. I know that most browsers have now caught up with Opera and offer proper zooming but there are still lots of IE6 installs out there. I'm working on a baseline of 1024 x 768. Does anyone have objections to this? I'd be opposed to any template that uses fixed widths and which does not degrade gracefully with less or more width. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkjpVRAACgkQRAx5nvEhZLKTNQCgs3pmw9BO48mfjL7mm/Qwr/ut CZMAoLf+cGMThVL78uyftDpAA+QLMCRc =n+t3 -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
