On Fri, Dec 12, 2008 at 3:04 PM, Iain Duncan <[email protected]> wrote: > > On Fri, 2008-12-12 at 20:57 +0000, TurboGears wrote: >> #1992: Style a new start page and CSS before 1.1 stable >> ------------------------+--------------------------------------------------- >> Reporter: faide | Owner: iainduncan >> Type: task | Status: assigned >> Priority: normal | Milestone: 1.1 beta 2 >> Component: TurboGears | Version: 1.0.6 >> Severity: normal | Resolution: >> Keywords: | >> ------------------------+--------------------------------------------------- >> Comment (by jorge.vargas): >> >> what is the status on this one? From the discussion on the list it seems >> ready. > > Hi folks, I got it ready and it's working ( and checked in ), though it > is *not* IE6 compatible ( nor is intended to be). It can be deployed as > is, I've tested on the non-ie6 machines. I intend to put in a couple > more hours this weekend to do: > > - some sort of hard failure for ie6 ( instead of a broken page ) > - some sort of image for the header ( I had designed around a nice gears > photo from istock before realizing that our intended use was not going > to work with their license, dumb me ) > - some minor tweaks to the design > - a readme explaining the way the css works > - identity login back in the page > - some dynamic date item ( suggested by Chris ) > > I'm open to suggestions, though the design aspect does have to somewhat > be done by fiat as design by committee is a total recipe for > disaster. ;-) > > If anyone has some interesting TG theme related black and white photos > they might want used, feel free to send them to me off list. > > What do you all think is the best hard failure for IE<7? A simple > javascript popup that says the site is not <IE7 compatible? > > At any rate, I will keep it from now in a deployable state in trunk.
Hi Iain thanks for all the hard work on this one. But I'm really puzzled about the ie6 problem, is it really something that can't be fixed in a conditional ie block? keep in mind that even though all sane developers will not use IE and much less ie6, a lot of people will just edit our default template and work on top of it to have their basic sites, and I'll really don't want TG to stop supporting ie6 (regardless of how much I hate it), could you outline the problems? maybe someone else (me if no one steps up to the task) could take a look at this week's sprint and we can make it work for ie6. As a related note I'll take care of porting it to tg2. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
