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
WebService and Mobile Access
Graveyard
MPWebServices
Feature suggestions
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="orencha" data-source="post: 631364" data-attributes="member: 11329"><p>After playing around a bit with the plugin aspx files and cs code, and configured it to run under IIS, here's my feature suggestions:</p><p></p><p>- During installation, ask the user which web server to use: either an internal web server (the same one used today) or IIS (in this case, only a folder will be created with all required files in it. Configuration will still be available under TV-Server configuration).</p><p></p><p>+ Use a master page in aspx, and put the top menu (TV, Radio, Schedules, etc...) in it - so the menu will be available on all pages.</p><p></p><p>+ Use strings from the existing MediaPortal Language XML files for translation. Most strings should already be there, already translated. Missing strings can be added for future MediaPortal versions. This will make the plugin available in many languages!</p><p></p><p>+ In the login screen, add a "lightweight interface" checkbox. When checked, interface will be optimized for Cellular/PDA access (such as: skip tv logos). Additionally, the default state of this checkbox can be identified automatically by looking at the "userAgent" string.</p><p></p><p>+ Change the Picture Streamer so it re-creates a JPG with desired dimensions (WxH), rather than streaming the original file. This may assist with low bandwidth.</p><p></p><p>+ Optimize ASP.NET code, so less information is sent to the server each time (by removing viewstate where not required, and/or splitting tv/radio/recording etc pages into seperate ASPX pages). Again, this may be usefull in low-bandwidth situations.</p><p></p><p>+ Show detailed TV program information (including description, episode no. etc) when clicking a tv-show, rather than openning a generic search page for this show.</p><p></p><p></p><p><strong>Suggestions above marked with "+" can be developed by myself, as I have some ASP.NET experience. Please let me know if you would like to see these suggestions implemented, so I can start working on it.</strong></p></blockquote><p></p>
[QUOTE="orencha, post: 631364, member: 11329"] After playing around a bit with the plugin aspx files and cs code, and configured it to run under IIS, here's my feature suggestions: - During installation, ask the user which web server to use: either an internal web server (the same one used today) or IIS (in this case, only a folder will be created with all required files in it. Configuration will still be available under TV-Server configuration). + Use a master page in aspx, and put the top menu (TV, Radio, Schedules, etc...) in it - so the menu will be available on all pages. + Use strings from the existing MediaPortal Language XML files for translation. Most strings should already be there, already translated. Missing strings can be added for future MediaPortal versions. This will make the plugin available in many languages! + In the login screen, add a "lightweight interface" checkbox. When checked, interface will be optimized for Cellular/PDA access (such as: skip tv logos). Additionally, the default state of this checkbox can be identified automatically by looking at the "userAgent" string. + Change the Picture Streamer so it re-creates a JPG with desired dimensions (WxH), rather than streaming the original file. This may assist with low bandwidth. + Optimize ASP.NET code, so less information is sent to the server each time (by removing viewstate where not required, and/or splitting tv/radio/recording etc pages into seperate ASPX pages). Again, this may be usefull in low-bandwidth situations. + Show detailed TV program information (including description, episode no. etc) when clicking a tv-show, rather than openning a generic search page for this show. [B]Suggestions above marked with "+" can be developed by myself, as I have some ASP.NET experience. Please let me know if you would like to see these suggestions implemented, so I can start working on it.[/B] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
WebService and Mobile Access
Graveyard
MPWebServices
Feature suggestions
Contact us
RSS
Top
Bottom