> 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.
This is very nice, and I think we could support it in an alternate quickstart template, or provide an IE6 conditional include in the main quickstart template that uses an alternate CSS that works for IE 6. But, I was surprised to see that IE6 still has more than twenty percent market share, so it seems like we can't quite afford to totally ignore it. > 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 Wow, that sucks. > 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. We definitely should make it an optional template, and I wish we could do better. But I see the problem, and don't know a good way around it. I think the auto-resizing is great, but not 100% required, but the class selector stuff really makes life hard. :( --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
