<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Segoe'; font-size:10pt; font-weight:400; font-style:normal;">I'll try to not be offended by the "normal humans" statement... ;-)<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Ok, we could easily alter parsing like:<br>
- support fifo ('last occurence rules') "width" and "max-width" (as well as no width statement at all)<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>- additionally handle the value suffix, i.e. differ "<n>em" from "<n>%" (currently the scale isn't clear anyway) with no suffix indicating: (?)<br>
(i'd vote for em, pt and px make few sense in arranging text-only-item-witdths anyway and a factor feels natural than percentage)<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>- we still could keep encoding this info into the single double value or add two more bools ("widthIsPercent", "widthIsFix/Max" - wasting large areas of the double) =D<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Thomas<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Am Tuesday 13 January 2009 schrieb Nikolaj Hald Nielsen:<br>
> Sorry, but I think this is the wrong way to go about this. I think I<br>
> understand what you want to achieve, but I also think that by encoding<br>
> so much information into a single value, we are making the XML very<br>
> hard to parse for normal humans. I would much rather if we split these<br>
> 4 cases into separate attributes so we have size ( or width, that<br>
> proposal makes sense ) that acts like currently, and then have other<br>
> non mandatory attributes for the other cases. That will make it much<br>
> clearer what is going on I think.<br>
><br>
> Thoughts?<br>
><br>
> - Nikolaj<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p></body></html>