Reply to thread

Message

<blockquote data-quote="phunqe" data-source="post: 199714" data-attributes="member: 50050">Well I know for example that if you include a dynamically loaded GPL library into your commercial application, you don't have to open source it. You just need to make sure the you ship the library in it's original form and that users are able to link updated or modified versions of it (as long as it doesn't break APIs/compatibility).I don't know if this somehow would apply to these skins, if they are considered &quot;dynamically loaded&quot;. But in that case, you should be able to identify the skin files on the hard drive. You should also be able to replace them or modify them (as long as you follow an API of course).I might be completely wrong though, but I'm sure I'll be slapped around in that case <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue&nbsp; &nbsp; :p" loading="lazy" data-shortname=":p" /></blockquote>

[QUOTE="phunqe, post: 199714, member: 50050"] Well I know for example that if you include a dynamically loaded GPL library into your commercial application, you don't have to open source it. You just need to make sure the you ship the library in it's original form and that users are able to link updated or modified versions of it (as long as it doesn't break APIs/compatibility). I don't know if this somehow would apply to these skins, if they are considered "dynamically loaded". But in that case, you should be able to identify the skin files on the hard drive. You should also be able to replace them or modify them (as long as you follow an API of course). I might be completely wrong though, but I'm sure I'll be slapped around in that case :P [/QUOTE]

Verification