my only concern is to make sure that the traditional orbiter devices are supported. This includes:
* Cisco 7970
* Nokia 770/N800
* Windows Webpads
* Symbian/Windows Smartphones
because, I do _NOT_ want to lose retargetability to other devices, in the process of moving across platforms. I will scream bloody murder, if that happens.
A balance would be good though, to support the existing devices (or a reasonable subset of existing devices) but eventually new features/ desires/ capabilities will simply eclipse the capabilities of what we have now. I would hate to see future development restricted to support devices that have are out of production. Don't get me wrong, I have no desire to purchase new equipment, In fact I'm trying to see if it is possible to create a DCE template for my hauppauge MVP running mvpmc software.
I wonder if the discussion could start with looking at the layout description language (probably xml but not absolute) and then choosing the appropriate tools to use for the different devices. I realize that this could end up fragmenting development, but it doesn't need to.
I like the idea of open laszlo (or similar), and I would also suggest maybe the use of xforms or similar for layout as there are already reference implementations across many platforms and languages. I think the use of an international standard like this could entice more corporate development / sponsorship as well. I think the CORE will stay a restricted development environment, but bringing in something like webservices and xml based layouts will allow for some exciting interfaces. I could easily see adding something like Red5 with laszlo and having game consoles like the PS2/3, Wii, nintendo DS as orbiters, or a number of flashlite 3 enabled devices like the Chumby