On 22/02/11, martin brook wrote: > > I think Dave's point, which I fully agree with, is that > > the community would like to see things, and be able to get > > involved, at the design and "wireframe" stage. Even if the > > code isn't finished, I assume the design and wireframe specs > > which explain how the UX should act were finished, behind > > closed doors, many months ago. This isn't, I believe, how > > MeeGo was supposed to be. > > As far as I'm aware ISV's/OEM's are free to develop a UX on > top of MeeGo to differentiate themselves in the marketplace > ala TouchWiz, Motoblur, SenseUI etc. The UX is not part of > MeeGo compliance and does not need to be open.
That may be the case but with Intels Tablet UX one would think they, and MeeGo devs and users in general, would be very interested in seeing that interface in full public view so they could get feedback and patches. On 22/02/11, Alistair Buxton wrote: > > import MeeGo.Components 0.1 > > import MeeGo.Media 0.1 > > import MeeGo.Sharing 0.1 > > > > Anyone know where the source to these components is hiding? > > Does Intel want any feedback or patches for this interface? > > Is the Tablet UX not even part of MeeGos plans for 1.2/1.3? > > The UX repos are: > https://repo.ta.otcshare.org/UX/MeeGo_Trunk/ > https://repo.ta.otcshare.org/Tablet%3a/Staging%3a/UX/MeeGo_Trunk/ > They require a login, as does www.otcshare.org. There is not > even any indication of who owns the domain. > [...] Could someone from Intel please clarify the visibility status of their Tablet UX sourcecode and/or how to become involved with the above site? --markc _______________________________________________ MeeGo-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
