Reply to thread

Message

<blockquote data-quote="powermarcel10" data-source="post: 948801" data-attributes="member: 108759">I preffer to include stable files to Titan Extended, and to be shure everyone is using always the latest version of skinfiles for Titan, include them also to the installer of browsetheweb.. &nbsp;It's not clear now wich files are been developed by the team, and wich skinfiles need to be done by the plugin developers.. By example; movingpictures is done by the team.. Don't know how they think about browsetheweb.. For some plugins, the team will also update Titan skinfiles after a plugin update. But for browsetheweb I think that only the plugindeveloper and/or comunity is responsible for the right skinfiles, also after a plugin-update.&nbsp;So there need to come a clear policy about this.. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="powermarcel10, post: 948801, member: 108759"] I preffer to include stable files to Titan Extended, and to be shure everyone is using always the latest version of skinfiles for Titan, include them also to the installer of browsetheweb.. It's not clear now wich files are been developed by the team, and wich skinfiles need to be done by the plugin developers.. By example; movingpictures is done by the team.. Don't know how they think about browsetheweb.. For some plugins, the team will also update Titan skinfiles after a plugin update. But for browsetheweb I think that only the plugindeveloper and/or comunity is responsible for the right skinfiles, also after a plugin-update. So there need to come a clear policy about this.. :) [/QUOTE]

Verification