Reply to thread

Message

<blockquote data-quote="Rick164" data-source="post: 1195389" data-attributes="member: 17766">[USER=48495]@morpheus_xx[/USER]&nbsp; Not having to skin for MP2 would be a mayor benefit as we can port some of the code from MP1 that way and not worry about skinning as we have nobody for that <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />[USER=159827]@ElementalCrisis[/USER] currently there are a lot of specific features in MA3 so think we should make a list of features we would want in the MP2 plugin and check if it's still possible within MP2, from the top of my head these are the ones that would require an plugin rather than integrating it into a existing media library of MP2 (not sure how advanced that has gotten tbh):- Custom group views which are read out of the JMM server (All / Custom series / Global recently watched / &lt;user created/&gt; )- Custom pages which get data out of JMM server like:Continue watchingRecommendationsCalendarDownload managementUtilities (import management / matching etc..)- User profiles which are read out of JMM server with PIN code input if set- Local mappings relations to remote mappings, by default for MP1-MA3 the user has manually map those to their network ones or use streaming (new feature)- Subtitle selection settings, not sure if needed but that gets setup in MP1-MA3 config// UpdateSince JMM client is .NET 4.5 with XAML for the UI thought about maybe using parts of that in the future for MP2 to allow for easy updating (not having 2 code bases) but need more input from the other developers to check if that is feasible <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="Rick164, post: 1195389, member: 17766"] [USER=48495]@morpheus_xx[/USER] Not having to skin for MP2 would be a mayor benefit as we can port some of the code from MP1 that way and not worry about skinning as we have nobody for that :) [USER=159827]@ElementalCrisis[/USER] currently there are a lot of specific features in MA3 so think we should make a list of features we would want in the MP2 plugin and check if it's still possible within MP2, from the top of my head these are the ones that would require an plugin rather than integrating it into a existing media library of MP2 (not sure how advanced that has gotten tbh): - Custom group views which are read out of the JMM server (All / Custom series / Global recently watched / <user created/> ) - Custom pages which get data out of JMM server like: Continue watching Recommendations Calendar Download management Utilities (import management / matching etc..) - User profiles which are read out of JMM server with PIN code input if set - Local mappings relations to remote mappings, by default for MP1-MA3 the user has manually map those to their network ones or use streaming (new feature) - Subtitle selection settings, not sure if needed but that gets setup in MP1-MA3 config // Update Since JMM client is .NET 4.5 with XAML for the UI thought about maybe using parts of that in the future for MP2 to allow for easy updating (not having 2 code bases) but need more input from the other developers to check if that is feasible :) [/QUOTE]

Verification