<!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;">Hi 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>The attached patch<br>
---<br>
1) fixes a bug with right aligned "display:block" elements (they were globally aligned instead inside the block)<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>2) extends "size" interpretation: (see updated demo layout)<br>
0.0: autosize (display:inline)<br>
( 0.0, 1.0 ]: row percentage width (display:block, as originally)<br>
( 1.0, +inf ): absolute width (in "em", i.e. char width) this is eg. helpful to align track numbers<br>
( -inf, -1.0 ); [ -1.0, 0.0 ): absolute and percentual limited inline display (that is: the text is written as for "0.0", but never covers more than the given limit)<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>More ideas:<br>
---<br>
= personally i don't mind, but maybe the "size" attribute should rather be "width" (as size is usually used for e.g. font sizing etc.) leading to:<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>= what about more text attributes, like:<br>
- other weights (light, black)<br>
- other signs (italic, (small) caps, maybe underline)<br>
- font sizes (maybe just per row?)<br>
- text opacity (so you can e.g. have light tracklength etc.)<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>= regarding storage:<br>
imho the layouts should be stored in separate xml files, this will<br>
- allow to use incremental storage (i.e. some system defaults and stuff in the local user dir)<br>
- thus make it easy to add a button "EditLayout.Pro", opening a texteditor with (a userlocal copy of) the layout xml (maybe together alongside a textbrowser showing possible nodes and attribs)<br>
- and (especially ;-) prevent /one/ invalid layout (open tag etc.) from breaking /all/ others...<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>= the editor for "the unskilled":<br>
what about a simple xine pp-chain like "editor", i.e.:<br>
- you get a button "new row" -> adds e.g. a (toggable? using comments in the xml structure) groupbox<br>
- inside the group, you have 2 buttons:<br>
* "add element" -> adds a (focussable) hbox<br>
* "remove element" -> removes the focused element...<br>
- the hbox includes:<br>
[prefix lineedit][item combo][suffix lineedit][width spinner][alignment combo][font sign checkboxes]<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>together with a global lineedit for the name and a close button this may not be as "nifty" as some dnd "editor", but efficient and passes detaild control to the user (i'm still wainting for a WYSIWYG html editor to compete kwrite/qwebdev...) without requiring him to know anything about xml and autoshows supported attributes/values<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</p></body></html>