This is what QML makes possible, too (and yes, it's heavily inspired by EFL). Plasma implemented something like that without QML and now starts to take advantage of it. It's not something the toolkit has to do, the developer has to take formfactors into account as well, btw. At least to some extend - like providing a different QML (UI) file for at least 2 formfactors (say desktop/netbook/big tablet/tv and one for small tablet/mobile phone).
I really doubt you can write an UI or toolkit in such a way it can automatically adopt any UI for ANY formfactor & input method, unless you're OK with rather sub-optimal results in quite a few cases...
Posted Jul 18, 2012 23:44 UTC (Wed) by bluebugs (guest, #71022)
[Link]
I agree that QML as Edje by separating UI and code provide the same solution. In some case, it will be providing one Edje/QML file per device, sometime you can do with one. As an example of what, we can do with Edje, look at this video around 0:34 : http://www.youtube.com/watch?v=y82SVGFvjG4 . Today it's even possible to take the finger size and scale into account, but you get the idea. It take some work and it's not always a good idea, as you may want sometime to have really different layout for different devices, but the technology provide the means to do it.
Akademy: Plasma Active and Make Play Live
Posted Sep 6, 2012 9:58 UTC (Thu) by jospoortvliet (subscriber, #33164)
[Link]
That is really a beautiful demo of EFL! Ok, the theme and animations continue to be - 1995 or so, but the hiding of elements upon resizing is brilliant.
How much of that had to be hand-coded? Do you have to make some hierarchy of importance of elements or so? I wonder if QML is even at this point... Doubt it, actually.