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
Development
General Development (no feature request here!)
MERGING MediaPortal Url Source Splitter & IPTV Filter
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="mm1352000" data-source="post: 1136308" data-attributes="member: 82144"><p>Ahhh, I understand. It's a bit confusing to use a file to store settings, because most (all?) other plugins store their settings in the TVE database.</p><p>So to be clear: is MPIPTVSource.ini still used?</p><p></p><p></p><p>It would be the same as with any other tuner (consistent <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> ): the user chooses the tuner which they will scan with. TV Server doesn't have to know.</p><p></p><p></p><p></p><p>Unfortunately "simple" and "complicated" aren't always objective.</p><p>To me it seems "simpler" (or at least more consistent) to have some/all of the plugin functionality built into TV Server configuration, rather than in a plugin. That would enable using the provider/device-supplied m3u files directly (no need for the user to modify URLs if the settings are applied automatically by TV Server). I'd also have said that all configuration should be stored in the TV Server database.</p><p>...but I'm sure some people will think another way is simpler. <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="mm1352000, post: 1136308, member: 82144"] Ahhh, I understand. It's a bit confusing to use a file to store settings, because most (all?) other plugins store their settings in the TVE database. So to be clear: is MPIPTVSource.ini still used? It would be the same as with any other tuner (consistent :) ): the user chooses the tuner which they will scan with. TV Server doesn't have to know. Unfortunately "simple" and "complicated" aren't always objective. To me it seems "simpler" (or at least more consistent) to have some/all of the plugin functionality built into TV Server configuration, rather than in a plugin. That would enable using the provider/device-supplied m3u files directly (no need for the user to modify URLs if the settings are applied automatically by TV Server). I'd also have said that all configuration should be stored in the TV Server database. ...but I'm sure some people will think another way is simpler. :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
MERGING MediaPortal Url Source Splitter & IPTV Filter
Contact us
RSS
Top
Bottom