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="1gkar" data-source="post: 393024" data-attributes="member: 53076"><p>I hope I am not misinterpreting some aspects of this thread, but there seems to be some anger out there about how MP going to be coded in the future.</p><p></p><p>As someone who is only moderately PC literate, my only experience with using MPI was dismal. I won't state the plugin, but it was one I want to use -& still would. But it caused major bugs on my MP install (MPRC4) -ie, I lost ALL plugin icons within MP>config utility. No, I didn't bother with the bug-reports & all that, as I all I want is something that works. Sorry if that flys against opensource protocol: but too bad. If something doesn't work, I simply reimage & carry on. I don't have the time to read through some 8-15+ pages of forums posts for a <em>possible</em> answer. I just Ghost back & continue on with life.</p><p></p><p>My point: the documentation DOES need accurate representation of the plugin's capabilities, & it's limitations: in plain English. Also, I have never had any real issues with the system that stands at present: ie. using *.msi & manual installs of the various *.dll & other files. The plugin & skins devs do a great job, on the whole, at present & should be applauded for their efforts, especially in the continual improvements of their products. To force them to learn a whole new area of development, which will take them away from their area of concentration, & in a lot of cases, put their plugins' development back, may, in time be harmful to the entity that is Mediaportal. Again, I speak from a standpoint of one who has no real understanding of programming & coding. But I know what I need in a programme, & to date, Mp more than fullfils my requirements.</p><p></p><p>I have used MP for about two years, now & one of the reasons I started using it, was it's relative simplicity compared to other similar programmes on the market. Considering its status compared to commercial programmes, I believe it is THE BEST HTPC front-end option in the marketplace, & judging from the amount of MP donator badges I see on the forums, I'm not the only one to think that. Please, don't f*&^ it up for the sake of perceived improvements that may never be.</p></blockquote><p></p>
[QUOTE="1gkar, post: 393024, member: 53076"] I hope I am not misinterpreting some aspects of this thread, but there seems to be some anger out there about how MP going to be coded in the future. As someone who is only moderately PC literate, my only experience with using MPI was dismal. I won't state the plugin, but it was one I want to use -& still would. But it caused major bugs on my MP install (MPRC4) -ie, I lost ALL plugin icons within MP>config utility. No, I didn't bother with the bug-reports & all that, as I all I want is something that works. Sorry if that flys against opensource protocol: but too bad. If something doesn't work, I simply reimage & carry on. I don't have the time to read through some 8-15+ pages of forums posts for a [I]possible[/I] answer. I just Ghost back & continue on with life. My point: the documentation DOES need accurate representation of the plugin's capabilities, & it's limitations: in plain English. Also, I have never had any real issues with the system that stands at present: ie. using *.msi & manual installs of the various *.dll & other files. The plugin & skins devs do a great job, on the whole, at present & should be applauded for their efforts, especially in the continual improvements of their products. To force them to learn a whole new area of development, which will take them away from their area of concentration, & in a lot of cases, put their plugins' development back, may, in time be harmful to the entity that is Mediaportal. Again, I speak from a standpoint of one who has no real understanding of programming & coding. But I know what I need in a programme, & to date, Mp more than fullfils my requirements. I have used MP for about two years, now & one of the reasons I started using it, was it's relative simplicity compared to other similar programmes on the market. Considering its status compared to commercial programmes, I believe it is THE BEST HTPC front-end option in the marketplace, & judging from the amount of MP donator badges I see on the forums, I'm not the only one to think that. Please, don't f*&^ it up for the sake of perceived improvements that may never be. [/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