patch for src/playlist/view...

[Thomas Lübking]

I'll try to not be offended by the "normal humans" statement... ;-)

Ok, we could easily alter parsing like:
- support fifo ('last occurence rules') "width" and "max-width" (as well as no 
width statement at all)

- additionally handle the value suffix, i.e. differ "<n>em" from "<n>%" 
(currently the scale isn't clear anyway) with no suffix indicating: (?)
(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)

- 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

Thomas

Am Tuesday 13 January 2009 schrieb Nikolaj Hald Nielsen:
> Sorry, but I think this is the wrong way to go about this. I think I
> understand what you want to achieve, but I also think that by encoding
> so much information into a single value, we are making the XML very
> hard to parse for normal humans. I would much rather if we split these
> 4 cases into separate attributes so we have size ( or width, that
> proposal makes sense ) that acts like currently, and then have other
> non mandatory attributes for the other cases. That will make it much
> clearer what is going on I think.
>
> Thoughts?
>
> - Nikolaj


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/amarok/attachments/20090113/1d59cd43/attachment.html>