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
Support
Skins and Plugins Installer (MPEI)
Extensions: A GUI Plugin for MediaPortal's MPEI Installer
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="Dadeo" data-source="post: 800603" data-attributes="member: 27204"><p>Hi huha - you don't HAVE to add it to the Repository. That field is for plugins that do not have a Google Code or other SVN/site to upload the update.xml. Since you use google code for your update.xml you can just update it there in future and changes will automatically display in MPEI and Extensions plugin.</p><p></p><p>However, you are correct that the first time you create a project file/new update.xml it is a bit awkward, </p><ol> <li data-xf-list-type="ol">Upload the update.xml file somewhere (repo or google code for example) if you want to get the exact URL</li> <li data-xf-list-type="ol">In MPE Maker, add the onlne location/url, and generate the update.xml,</li> <li data-xf-list-type="ol">Upload the new update.xml with the new info (both Repo and Google Code retain the same url/link)</li> <li data-xf-list-type="ol">At this point you can install it locally using your mpe1 file and check it all out in MPEI if you want</li> <li data-xf-list-type="ol">Once you are happy with it, go back to MPE Maker and publish it (users won't see it until you publish it)</li> </ol><p>You only have to do all that the first time. After that you can just update the update.xml either in Repo/Google code or wherever and the changes will appear in MPEI as soon as users update online data.</p><p></p><p>There has been some discussion of trying to grab the data from the repo and I know dukus looked at it - there are some issues (but don't ask me what, I barely understand it all!). However, it is something I hope will get looked at for MP 1.3.. The current system is not ideal, but remember when dukus first developed MPEI the new Repo did not exist, AND there were very few testers. If you follow the MPEI thread you will see Migue even had trouble getting testers for the changes for 1.2.0 (mainly version compatibility). MPEI has come a long way already, and I think it still has potential to improve a lot more. Now that more and more extensions are starting to use it I think we can push for more improvements . Plugin developers are already capable coders and could easily submit patches to help improve it. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="Dadeo, post: 800603, member: 27204"] Hi huha - you don't HAVE to add it to the Repository. That field is for plugins that do not have a Google Code or other SVN/site to upload the update.xml. Since you use google code for your update.xml you can just update it there in future and changes will automatically display in MPEI and Extensions plugin. However, you are correct that the first time you create a project file/new update.xml it is a bit awkward, [LIST=1] [*]Upload the update.xml file somewhere (repo or google code for example) if you want to get the exact URL [*]In MPE Maker, add the onlne location/url, and generate the update.xml, [*]Upload the new update.xml with the new info (both Repo and Google Code retain the same url/link) [*]At this point you can install it locally using your mpe1 file and check it all out in MPEI if you want [*]Once you are happy with it, go back to MPE Maker and publish it (users won't see it until you publish it) [/LIST] You only have to do all that the first time. After that you can just update the update.xml either in Repo/Google code or wherever and the changes will appear in MPEI as soon as users update online data. There has been some discussion of trying to grab the data from the repo and I know dukus looked at it - there are some issues (but don't ask me what, I barely understand it all!). However, it is something I hope will get looked at for MP 1.3.. The current system is not ideal, but remember when dukus first developed MPEI the new Repo did not exist, AND there were very few testers. If you follow the MPEI thread you will see Migue even had trouble getting testers for the changes for 1.2.0 (mainly version compatibility). MPEI has come a long way already, and I think it still has potential to improve a lot more. Now that more and more extensions are starting to use it I think we can push for more improvements . Plugin developers are already capable coders and could easily submit patches to help improve it. :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Skins and Plugins Installer (MPEI)
Extensions: A GUI Plugin for MediaPortal's MPEI Installer
Contact us
RSS
Top
Bottom
