Reply to thread

Message

<blockquote data-quote="chefkoch" data-source="post: 1011904" data-attributes="member: 10438">Reading this again reminds me that we won't be able to catch all scenarios with one &quot;simple approach&quot;. From a MP2-developers pov, I don't expect the need for incremental updates for MP2 skins, as the most of the UI is defined as flexible and &quot;small&quot; XAML (xml-files) instead of static jpg or png-graphics.Maybe I am wrong, but we don't have the experience, yet since there is nobody interested in working on it.&nbsp;If there might be the case at sometime that requires such incremental downloads, I am pretty sure we can implement this as a &quot;plugin&quot;, which provides the service to download single files from svn /git repositories. The plugins/skins that make use of this internal service are registered with the required infos about the connection details to the online repo through the plugin.xml service.&nbsp;I also expect that there won't be a solution as a single application that fits for MP1 and MP2, because the requirements are different.Nevertheless, I strongly believe that the concept can be the same and so the majority of the code can be shared.For getting more specific feedback, tests, suggestions, support and ensuring the result can be used and fits the needs, going bottom-up (core &gt; apps &gt; glamour) will be better then top-down.</blockquote>

[QUOTE="chefkoch, post: 1011904, member: 10438"] Reading this again reminds me that we won't be able to catch all scenarios with one "simple approach". From a MP2-developers pov, I don't expect the need for incremental updates for MP2 skins, as the most of the UI is defined as flexible and "small" XAML (xml-files) instead of static jpg or png-graphics. Maybe I am wrong, but we don't have the experience, yet since there is nobody interested in working on it. If there might be the case at sometime that requires such incremental downloads, I am pretty sure we can implement this as a "plugin", which provides the service to download single files from svn /git repositories. The plugins/skins that make use of this internal service are registered with the required infos about the connection details to the online repo through the plugin.xml service. I also expect that there won't be a solution as a single application that fits for MP1 and MP2, because the requirements are different. Nevertheless, I strongly believe that the concept can be the same and so the majority of the code can be shared. For getting more specific feedback, tests, suggestions, support and ensuring the result can be used and fits the needs, going bottom-up (core > apps > glamour) will be better then top-down. [/QUOTE]

Verification