I have found boilerplate CSS (on googlecode) to be easily adaptable to suit bake. I have just checked to see how it performs in print preview and all holds up
2008/7/10 Jon Bennett <[EMAIL PROTECTED]>: > > Hi patrick, > > >> An edge case should by no means include 'printing a webpage'. > >> Comptrollers and account executives typically don't store screenshots > >> in filing cabinets and that is why I (in my own personal opinion) feel > >> the ability to print is integral to any information based web > >> application. > >> > > > > Still an edge case, as the vast majority (I'd even say 99%) of web > > applications do not have a requirement for "looks pretty when printed" > > output. > > I've always thought of Bake as a tool to get the bare bones of an app > built quick for testing purposes via the browser. You can of course > write your own bake templates - in which case bake can be used to > knock up more complex, custom views, but I've found it quicker to do > it manually. > > css aint tricky really, just takes a little bit of time to learn and > the FireBug extension to tweak effectively. If you're working on an > app that requires specific printable reports, design the reports then > customise the views to suit - that's no different from having a > browser based design and having to cut that to html/css then customise > the baked views (or start from scratch) to match. > > cheers, > > Jon > > -- > > jon bennett > w: http://www.jben.net/ > iChat (AIM): jbendotnet Skype: jon-bennett > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
