07-18-2012, 05:40 PM
Dean Roddey Wrote:It would need to be stuff that isn't very complex since we are too close to 4.2 for that.One easy part for protocol 5 could be to accept the client's resolution during the login, without doing anything with it.
Then let say in 4.5 you could pre-scale everything server side, so that people can use their regular templates on devices of any resolution (matching the orientation)... No provided resolution would mean no pre-scaling...
Field Generator 0.65: Create CQC fields on the fly, from external applications.
Mobile templates 0.4: Main resolution of 320x480 with navigation side bars (384x544).
Sage Media Server 1.1.3 + Sage Player 2.7.8: Display and manipulate SageTV information or player.
TaRIVA 1.26: Android RIVA client.
Mobile templates 0.4: Main resolution of 320x480 with navigation side bars (384x544).
Sage Media Server 1.1.3 + Sage Player 2.7.8: Display and manipulate SageTV information or player.
TaRIVA 1.26: Android RIVA client.