> Joel, > > getting some UX's from the community sounds like a plan. For clarity sake, > what would you envision defines a UX? Is it as simple as a WM? Or is it > a suite of apps (along with a WM)? > > Nasa
I don't think there are any firm rules that need to be set. So here are just some of my suggestions. 1> Installable package or set of packages maintained and supported in build.meego.com. Without someone willing to keep the packages working in the MeeGo build and respond to community discussion or issues, it's probably a waste of everyone's time 2> Should include an initial user screen, and ability to launch additional programs. The very minimal would be something like xterm with command line app launch. But presumably folks will want to show a more rich in-vehicle experience The idea is to provide a space for anyone to demonstrate their vision of what an in-vehicle user experience should be. It seems reasonable to have some original content, but there is no reason to not allow re-use of existing upstream projects. So for example a UX might provide its own window manager or it might re-use an existing one. Previously we have had XFCE, Matchbox, and "mcompositor". My view of desirable features in an IVI UX 1> multiple windows 2> multiple display support 3> compositing 4> multiple user support 5> touchscreen, voice command, text to speech 6> input from vehicle controls (steering wheel, center console etc) 7> entertainment apps 8> driver assistance apps 9> social networking apps 10> system configuration apps 11> data sync with multiple devices Lots of possibilities regards Joel _______________________________________________ MeeGo-ivi mailing list [email protected] http://lists.meego.com/listinfo/meego-ivi
