Reply to thread

Message

<blockquote data-quote="chefkoch" data-source="post: 995408" data-attributes="member: 10438">I also agree to these two points.But, besides MPEM itself (container-format, external WPF-Management app, inbuilt plugin/browser), especially these two points are heavily related to the online component: the repository, gallery or call it whatever you want.&nbsp;I don't see these issues being resolved completely by keeping the existing repository.&nbsp;<a href="https://forum.team-mediaportal.com/members/sa_ddam213.89205/" target="_blank">sa_ddam213</a>No offense, your work is very important and highly appreciated on the client (access to the plugins) side.&nbsp;My only concern is that others might expect improvements from the MPEM tool for the overall process, which are affected by the server component (hosing the plugins). Do you have any concepts or plans which server components will be used?If we stay with the current repository, i.e. it will still be required to fill in the plugin information (metadata) twice. Once in the plugin package and once on the website when uploading it, unless upload and release of new packages can be done via API from within the MPEM tool.&nbsp;It might also be problematic to store multiple versions (best would be all official ones) of the same extensions, keeping the download stats, etc...</blockquote>

[QUOTE="chefkoch, post: 995408, member: 10438"] I also agree to these two points. But, besides MPEM itself (container-format, external WPF-Management app, inbuilt plugin/browser), especially these two points are heavily related to the online component: the repository, gallery or call it whatever you want. I don't see these issues being resolved completely by keeping the existing repository. [URL='https://forum.team-mediaportal.com/members/sa_ddam213.89205/']sa_ddam213[/URL] No offense, your work is very important and highly appreciated on the client (access to the plugins) side. My only concern is that others might expect improvements from the MPEM tool for the overall process, which are affected by the server component (hosing the plugins). Do you have any concepts or plans which server components will be used? If we stay with the current repository, i.e. it will still be required to fill in the plugin information (metadata) twice. Once in the plugin package and once on the website when uploading it, unless upload and release of new packages can be done via API from within the MPEM tool. It might also be problematic to store multiple versions (best would be all official ones) of the same extensions, keeping the download stats, etc... [/QUOTE]

Verification