Subject: Re: General performance [was: drawing performance]
From: Martin Sevior (msevior@mccubbin.ph.unimelb.edu.au)
Date: Mon Dec 18 2000 - 17:03:26 CST
On Mon, 18 Dec 2000, Sam TH wrote:
> >
> > Supporting uppercase attributes should be abandoned and my next patch will
> > abandon it forever. It is *bad* XML.
> >
> > <p props=""> and <p PROPS=""> should not both validate against any DTD.
> > Supporting uppercase should be considered a bug. The file format is not set
> > in stone and not yet at 1.0. Documents with these settings tend to be very
> > old ones or hand-crafter anyway.
> >
>
> Well, I'm not sure how old the change is, but I don't see a good
> reason for making these documents unimportable. Dealing with them
> shouldn't be too much work, and people should be able to upgrade
> easily enough. If you are going to do this, it might be preferable to
> give people an option, either at compile time or at import time (like
> old rtf). We don't want documents to be obsolete and unusable.
>
This must affect a tiny fraction of our users. In any case how hard would
it be write a perl or python script to convert docs with uppercase
props/attributes to lower case?
Actually it would be easy to add this to our importer. If an
attribute/property is unrecognized on import, covert it to lowercase and
run it through again. There is no performance hit for un-handcrafted abi
documents.
Given what Dom says about performance I can't wait to try it. Scrolling on
my home machine ( an old 133 PI) is the thing my wife (close enough to a
Church secretary) hates most.
Cheers
Martin
This archive was generated by hypermail 2b25 : Mon Dec 18 2000 - 17:03:46 CST