If the Tablet UX is this scalable, what's the point then with the separate Handset UI which seems to use a different UX paradigm at least to some extent?
It sounds from Stekeeps response above there might not be hence why Intel just want to use the one meego ui in future?
can any one help. i have downloaded the images from the site (http://sagestechblog.blogspot.com/20...t-release.html) and got kernel file from the repo. but when i am flashing the kernel file its show me dos thn something written on it and then it got to a black or dark blue like screen and stops there.. wht could be the problem?
If the Tablet UX is this scalable, what's the point then with the separate Handset UI which seems to use a different UX paradigm at least to some extent?
Exactly. And I don't get how this doesn't have the panes were used to on tablet devices? What's going on here? Or is this a view of the apps menu (only)? I hope no time was wasted making Handset and Tablet, only to see them come this close towards the end.
I hope no time was wasted making Handset and Tablet, only to see them come this close towards the end.
I am not sure if we ahve actually ever seen an handset UI but if one was developed then no doubt all that time & effort has been wasted, but perhpas this sums up what was going on in the Nokia developement world before Elop arrived i.e. not real joined my thinking between various developers?
Handset and Tablet are really Intel work, nothing to deal with Nokia work except some shared components.. Tablet (or unified UX as some call it) is an evolution of Handset (which was made in MeeGo Touch Framework), with a lot of things remade in QML. And it's actually a lot better.
Funny enough, I kinda liked some of the elements of the handset UX more... like the panels of this thing, and I like the plan of unifying handheld and tablet UIs. More unification between UXs means less users feeling like their devices actually are unified, more intuitiveness when switching, etc. That said, this makes me happy, since another UX going open source certainly is a good thing.
I can't wait for people to get cracking on this now that it's open source. Why is it o-s only now, though? I bet some closed-s compinents had to be finished before it could be "released" as o-s?
Because Intel like to do big reveals of mostly working code. Which is kind of cool if you like suprises. But is also a good tactic for marketting the platform
