Ooo my two cents - I like the override system, especially with the new file-based (rather than directory-based) naming convention. My only issue with the current override scheme is that it isn't always clear what you can put in the override file and what you can leave out but there are lots of examples to check.
Aside from that bit of head-scratching, it's nice that overrides are clearly seen at the directory level, and 'special' code doesn't clutter the 'mainstream' code. Basically, I like it. Rich On Tue, May 22, 2012 at 10:15 AM, C Anthony Risinger <[email protected]>wrote: > On Mon, May 21, 2012 at 10:33 AM, Phil Charlesworth > <[email protected]> wrote: > > I seem to recall a recent statement that Pyjs would drop support for > > versions of IE prior to IE8 but I can't now find a reference to it. > > i'm guessing you are referring to a random dump here: > > https://groups.google.com/d/msg/pyjs-users/CZLdbYzjQh8/VKtjXHUmPZAJ > > ... which is a purge of a small text file i had :-) > > > Is it in > > fact the intention to do that and, if so, is the policy already active, > so > > that modifications to existing code no longer need to incorporate > platform > > overrides for IE6 if IE8 does not need them? > > i see no reason whatsoever to make new accommodations for the browser. > we should avoid purposefully breaking stuff (for now), but i don't > have any inclination to ensure it continues to work. > > unless someone has a reeeeeally good reason (and i mean *really* good, > like "aha! what a fool i've been! i <3 IE6!" kind of epiphany) then > consider it DEAD. > > RIP. > > IE7 however we'll need to continue supporting, probably a bit too > premature for that. > > the override system is something i'd like to address in the coming > months. personally i'd prefer if everything were in a single file, > so: > > a) it's visible > b) it's visible enough to annoy and possibly work to remove > > ... ideally we would identify a feature matrix of sorts and implement > shims to close the gaps between browsers (so different browsers can be > "patched" and share more base code), but that might bee too > aggressive, need more exploration here. > > -- > > C Anthony >
