I thought I'd start up a thread on this since we've had several small discussions over the past year or two but nothing major discussing the +/- of different devices to be used as touchscreens/pads for XLobby.
Please add your comments, devices, and your goals to this thread. I think this is a great way to share experiences, ideas, and help eveyone get to the implimentation they want.
Currently I have no touchscreen at all (I sold my Neta980). I have decided not to use WindowsCE as it just does not seem to have the horsepower in many cases and also 802.11b does not seem to have the speed to keep up with higher resolution refresh with XLobby.
I'm currently leaning towards getting an older slate PCs... like Motion Computing M1300 or Compaq TC1100 due to the lower cost then for the current models.
My overall goal, for reference:
Aaron's Home Automation & Control Goals...
Use XLobby as my front-end for my Home Theater and Home Automation.
I currently use Homeseer (with an ASP front end) for home automation & control and XBOX Media Center (XBMC) for Games/Music/Movies/Pictures.
XLobby & Homeseer are being integrated via the xAP plug-in (thanks ptrinchi), thus this will allow me to use XL as the front end instead of the ASP pages. I'd like to control XBMC via HTTP commands; not sure if XLobby can send raw HTTP - this might be a feature request if it does not.
Homeseer will store any/all IR commands and send them via USB-UIRT to my entire system. It will also control all X-10 devices and events. If XLobby builds in X-10 controls/events I could completely replace Homeseer with XLobby, but I'm not sure if Steven's goal is to become a total "Home Media & Control" application.
XLobby will control the 6 zone audio I have throughout the house. I will build a PC with multiple sounds cards, one for each zone.
I'd like to control everything with a wireless touchscreen that does at least 800x600 resolution and has at least a 7", prefer 10" screen.
My thoughts on a few devices so far (though without actual hands on use)...
Viewsonic V110
+ Wireless and stays connected via wireless when docked.
+ Allows the back-end PC to have as much horsepower needed - upgrading less costly.
+ 10" screen
+ light weight
+ easy to carry around / handle
+ boot time is instant (not sure about reconnect time for wireless)
- low battery life
- only 802.11b
- Must have dedicated PC to run front end since it does not allow dual display output to only go to the V110
+/- Apps run remotely, not locally (rate per your specific needs)
WinXP Tablet/Slate PC
+ Wireless via 802.11g/b/a or anything upcoming
+ Stays connected via wireless when docked.
+ largest screen size avail
- horsepower is dependant on the tablet, not backend - upgrading more costly.
- high cost of tablet device
- heavier then standard remote display or WinCE touchpad
- boot time is slower then WinCE or Remote Display technology
+/- Apps run locally, not remotely (rate per your specific needs)