Reply to thread

Message

<blockquote data-quote="Pog" data-source="post: 1007675" data-attributes="member: 97724">I've been thinking about all the work done in this thread and the various ideas and solutions. One area of the skin engine in MP that makes life very difficult is lack of being able to abstract all the data to variables. Now it has improved with expressions and defines but they are inconsistant and due to regression it may be a big job to make the engine fully compliant.&nbsp;What would be nice is to build &quot;Skinlets&quot;, skining elements that can be used easily by any skin and just passing an xpos, ypos, size and let the skinlet do the work and add the offsets/scaling/timing whatever.&nbsp;Having a single element with 10 controls and having to change xy positions in every control just to see if it looks better 10 pixels over gets tiresome. Should be able to have an element xypos with each control being able to offset from that (&lt;posX&gt;element1.xpos+10&lt;/posX&gt;).&nbsp;So, my big idea is to use a <a href="http://en.wikipedia.org/wiki/General-purpose_macro_processor" target="_blank">macro preprocessor</a> to do all the grunt work and pass an MP readable xml file as output.</blockquote>

[QUOTE="Pog, post: 1007675, member: 97724"] I've been thinking about all the work done in this thread and the various ideas and solutions. One area of the skin engine in MP that makes life very difficult is lack of being able to abstract all the data to variables. Now it has improved with expressions and defines but they are inconsistant and due to regression it may be a big job to make the engine fully compliant. What would be nice is to build "Skinlets", skining elements that can be used easily by any skin and just passing an xpos, ypos, size and let the skinlet do the work and add the offsets/scaling/timing whatever. Having a single element with 10 controls and having to change xy positions in every control just to see if it looks better 10 pixels over gets tiresome. Should be able to have an element xypos with each control being able to offset from that (<posX>element1.xpos+10</posX>). So, my big idea is to use a [URL='http://en.wikipedia.org/wiki/General-purpose_macro_processor']macro preprocessor[/URL] to do all the grunt work and pass an MP readable xml file as output. [/QUOTE]

Verification