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)
The future of MPI - we need your opinion!
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="infinite.loop" data-source="post: 361080" data-attributes="member: 10723"><p>I totally agreed that the manual is a big problem. Sadly writing manuals is not very popular<em> (not even among community plugin devs. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /> )</em></p><p>I will try to get some free time to rework the manual of it in the wiki, and update with features we will add.</p><p></p><p></p><p>Indeed, the whole configuration application should be re-created from scratch.</p><p>But then again, we want to focus on MP2, and not start to re-creating one after the other feature of MP1.</p><p></p><p>As you can see we try to make a balancing act between maintaining and improving MediaPortal 1 and not shifting all our development power back to MP1. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" /></p><p></p><p>This is why i think that button which opens the MP-Extensionsinstaller, should be done for MP1.</p><p>In MP2 we will integrate MPE into the configuration application from the start. <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="infinite.loop, post: 361080, member: 10723"] I totally agreed that the manual is a big problem. Sadly writing manuals is not very popular[I] (not even among community plugin devs. ;) )[/I] I will try to get some free time to rework the manual of it in the wiki, and update with features we will add. Indeed, the whole configuration application should be re-created from scratch. But then again, we want to focus on MP2, and not start to re-creating one after the other feature of MP1. As you can see we try to make a balancing act between maintaining and improving MediaPortal 1 and not shifting all our development power back to MP1. :S This is why i think that button which opens the MP-Extensionsinstaller, should be done for MP1. In MP2 we will integrate MPE into the configuration application from the start. :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Skins and Plugins Installer (MPEI)
The future of MPI - we need your opinion!
Contact us
RSS
Top
Bottom