home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
MPEM Development Info & Testversion
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="chefkoch" data-source="post: 1012095" data-attributes="member: 10438"><p>No, definitely not! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>The same way the forum is integrated, which is also not Joomla <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue :p" loading="lazy" data-shortname=":p" /></p><p>Or the issue tracker.</p><p></p><p>Who has volunteered to work on the existing repository? Maybe I am wrong and it is meets the needs for the most of the plugins/skin devs. Great then there is nothing needed to be done.</p><p> </p><p>IMO it has two huge disadvantages:</p><ul> <li data-xf-list-type="ul">entering the same metadata for a plugin multiple times: 1. when creating the packages in the package creator 2. when uploading the package within the repository</li> <li data-xf-list-type="ul">There is no version management. The links change when uploading a new package and / or old versions won't be available anymore. Without the possibility to keep even older version it will not be possible to run a fine grained extension management with extensive dependency definitions to other plugins.</li> </ul><p></p><p>I don't assure that high sets up a new CMS: It's only about two components NuGet.Server (<a href="http://nuget.codeplex.com/" target="_blank">#1</a>, <a href="http://nuget.org/packages/NuGet.Server/" target="_blank">#2</a>) and <a href="https://github.com/NuGet/NuGetGallery" target="_blank">NuGetGallery </a>- And even those should definitely not be customized by high since this is part of extension management. The NuGetGallery is written in ASP.net so once you learned a few things it should be easy to make some small modifications for a .NET/c# developer. Of course this does not "look" good, yet, but that's where code, components or parts from the orchard gallery can be used. I might let it sound easy , yeah, but I am also aware that it is not easy, nevertheless I think it is worth it.</p><p></p><p>This was only the base for the Orchard gallery and the NuGetGallery. Both are maintain pretty well.</p><p></p><p>MPEM is not wrong, it's pretty good and perfect, but as far as I know there was no work done, yet "under the hood". Feel free to correct me if I am wrong. There are no connections to the online repo, yet, no versioning algorithm, no dependency specification. Such might be able to implement easily using nuget.core (even without the nuget.server or nuget.gallery)</p><p> </p><p> </p><p>EDIT: Yet another idea, I got a few minutes ago: Why not continuing the work on MPEM and the server etc. like it was planned without any nuget or wix things? Just introducing a replacement for the current MPInstaller and having the possibility to install these without the uac prompt should be a huge improvement already that is worth doing it, isn't it?</p><p> </p><p> </p><p>But it's correct all possibilities needs to be evaluated pretty well. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p> </p><p>Since I can't help with this, I will also stop promoting NuGet here in this thread, because I know that it is easy, but just unfair to say "hey why not doing it this way or that way" without actually helping. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p> </p><p>So it's up to the people who are actually spending their time on this task.</p></blockquote><p></p>
[QUOTE="chefkoch, post: 1012095, member: 10438"] No, definitely not! :) The same way the forum is integrated, which is also not Joomla :p Or the issue tracker. Who has volunteered to work on the existing repository? Maybe I am wrong and it is meets the needs for the most of the plugins/skin devs. Great then there is nothing needed to be done. IMO it has two huge disadvantages: [LIST] [*]entering the same metadata for a plugin multiple times: 1. when creating the packages in the package creator 2. when uploading the package within the repository [*]There is no version management. The links change when uploading a new package and / or old versions won't be available anymore. Without the possibility to keep even older version it will not be possible to run a fine grained extension management with extensive dependency definitions to other plugins. [/LIST] I don't assure that high sets up a new CMS: It's only about two components NuGet.Server ([URL='http://nuget.codeplex.com/']#1[/URL], [URL='http://nuget.org/packages/NuGet.Server/']#2[/URL]) and [URL='https://github.com/NuGet/NuGetGallery']NuGetGallery [/URL]- And even those should definitely not be customized by high since this is part of extension management. The NuGetGallery is written in ASP.net so once you learned a few things it should be easy to make some small modifications for a .NET/c# developer. Of course this does not "look" good, yet, but that's where code, components or parts from the orchard gallery can be used. I might let it sound easy , yeah, but I am also aware that it is not easy, nevertheless I think it is worth it. This was only the base for the Orchard gallery and the NuGetGallery. Both are maintain pretty well. MPEM is not wrong, it's pretty good and perfect, but as far as I know there was no work done, yet "under the hood". Feel free to correct me if I am wrong. There are no connections to the online repo, yet, no versioning algorithm, no dependency specification. Such might be able to implement easily using nuget.core (even without the nuget.server or nuget.gallery) EDIT: Yet another idea, I got a few minutes ago: Why not continuing the work on MPEM and the server etc. like it was planned without any nuget or wix things? Just introducing a replacement for the current MPInstaller and having the possibility to install these without the uac prompt should be a huge improvement already that is worth doing it, isn't it? But it's correct all possibilities needs to be evaluated pretty well. :) Since I can't help with this, I will also stop promoting NuGet here in this thread, because I know that it is easy, but just unfair to say "hey why not doing it this way or that way" without actually helping. ;) So it's up to the people who are actually spending their time on this task. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
MPEM Development Info & Testversion
Contact us
RSS
Top
Bottom
