Ideally there should ~only~ be stuff + css class definitions. The hard part is providing default behaviour. Without being able to add css includes into the head it's so durned impossible..
Of course the recent mentions of the new MarkupWriter implementation would allow this to work. There's no reason why that new implementation couldn't be added into 4.1 is there? I don't see why not. No reason why not at all. This would fix previous issues related to cookies as well. So f- it. We'll add it into 4.1 either way. :) Down with manual styling and up with dynamic .css file includes! jesse On 3/8/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > replying to myself here - I'm back to where I thought I was before > today, making it easier for "the majority". [had to stop looking at a > bad example to get back to yesterday. :-/] > > Brian K. Wallace wrote: > > Sounds reasonable. (and yeah, I had to try it before replying ;-) ) > > > > One thing I've been fighting with in this regard is the header class. > > > > I think as it was, it worked for 80-90% of the people, but it was too > > hard for the remaining 10-20%. Now that I've been looking at the whole > > structure under different conditions, I think it's 100% too hard for > > 100% of the people who deal with CSS and localization due to the way the > > header's class is named. I'm not done with this, but what I'm looking at > > now is a completely different issue that will hopefully get us back to > > easier for everyone in all (read: most) situations. > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.5 (MingW32) > > iD8DBQFED5m7aCoPKRow/gARAoTqAJ9lvPvBSOX3+iQpOSfjZyzDwxkzCQCdGzGD > vjZFa9q62YSkwxGN+Qh0Cuo= > =Egof > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
