> 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.
Hi everyone, re the new css. We discussed this aways back on the dev list and I said I was working on a new framework that could be used for the template, but that I did not think it would be ie-6 css compatible and asked for opinions. At that time, it seemed everyone was fine with no ie6, but of course at that time, ie 8 was also supposed to be out by now. Basically, what I did make a system whereby you can change a geometric measurement in only *one* place, and have the all the other components respond properly. So changing the widths or height or margin of the outer container will reflow all other components in nice alignment. I have never seen this work in any IE6 supporting css setup, there is always the necessity to change numbers in several places, especially if combining floating three column layouts with absolutes and so on. I also kept *all* layout and presentation controls out of ids, so that users can use semantic ids as they see fit. The nasty issues are that: - stretching absolutes by setting corners or margins to 0 does not work in ie6 ( key to the auto resizing of inner blocks ) - daisy chained class selectors don't work either, so all those selectors would have to be changed to ids, and then we force and id convention on the user Unfortunately, those two combine to just lay waste to everything in IE6 in a terrible terrible way, because of the way ie6 will go applying one of selector chain to all elements that share it. It's going to be a great system for building block like layouts and doing ajax manipulation dead quick with everything but ie6, but for ie6 it's unusable. That said, I won't be at all offended if we shelve it for now until ie8. That's cool, but I'll warn you that porting it is not pretty, I just did it for my own site here: http://www.flyingnotfalling.com ( that's me! ) Now we could still use the *look* and redo the css for now, but I'm not sure whether that is worthwhile. The disappointment I guess is that doing so means we have a xhtml/css setup that is neither here nor there. I don't think I can commit to retooling it for IE6 and fixing the other outstanding elements this weekend, but could probably do so over say another week. So what to do? I'm not worried about the work going to waste, I'll still be using it as soon as the last nail is in IE6's coffin. I think maybe given the unknown release date for IE8 ( quel surprise! ), that the dynamic framework might be better off being an optional template system for TG2 final. Thoughts? Iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
