2007-06-28, 01:12
I would assume, they 're all on porting to linux.
I did not read the whole thread with all technical details, but if I understand you all correctly, I already had another thought long ago concerning this topic:
I personally need no fancy client side GUI and animation. What I really would like to see is really useful and presumably much easier and less work than the stuff discussed in this thread till now:
Simply
* generate a jpeg and/or other alternative picture formats on the XBox/server of the current screen
* send it to and display it on the client browser
* accept "clicks" on the picture, send them back to the server and execute them there
* loop
This approach has several advantages:
* the whole XBMC can be controlled
* all current XBMC features are available immediately
* every skin is available
* every new and future feature is available immediately
* if you want new fancy interfaces: develop skins on XBMC and have it for all: client and server
* Nearly all functions/features needed for this approach are already almost present in http-api.
* No big development necessary
* No big runtime burden for XBMC
* No special memory foot print
* What do you want more ...?
As far as I can see, jpeg is send only base64 encoded till now. Why? Send it native and embed it into html. Allow for resolution selection at the start of the session. Then it can be used on my computer with 1400x1050 or on my PocketPC (with WLAN) with VGA or on other PocketPCs with 320x240 or something else.
My PocketPC even has a real keyboard. Allow for keyboard input additionally.
I did not read the whole thread with all technical details, but if I understand you all correctly, I already had another thought long ago concerning this topic:
I personally need no fancy client side GUI and animation. What I really would like to see is really useful and presumably much easier and less work than the stuff discussed in this thread till now:
Simply
* generate a jpeg and/or other alternative picture formats on the XBox/server of the current screen
* send it to and display it on the client browser
* accept "clicks" on the picture, send them back to the server and execute them there
* loop
This approach has several advantages:
* the whole XBMC can be controlled
* all current XBMC features are available immediately
* every skin is available
* every new and future feature is available immediately
* if you want new fancy interfaces: develop skins on XBMC and have it for all: client and server
* Nearly all functions/features needed for this approach are already almost present in http-api.
* No big development necessary
* No big runtime burden for XBMC
* No special memory foot print
* What do you want more ...?
As far as I can see, jpeg is send only base64 encoded till now. Why? Send it native and embed it into html. Allow for resolution selection at the start of the session. Then it can be used on my computer with 1400x1050 or on my PocketPC (with WLAN) with VGA or on other PocketPCs with 320x240 or something else.
My PocketPC even has a real keyboard. Allow for keyboard input additionally.