Jump to content

Multimedia/Sprint2010/Notes/QMLIntro: Difference between revisions

From KDE Community Wiki
Created page with 'problems it tries to solve: single ui to go to, central place, same principle as phonon why use them together? if you got an app that's not using phonon, phonon config doesn't ma...'
 
No edit summary
 
Line 1: Line 1:
problems it tries to solve: single ui to go to, central place, same principle as phonon
QtQuick ultimately separates model and view.
why use them together? if you got an app that's not using phonon, phonon config doesn't make sense at all
runtime in one language, model in something else and view in qml
pulseaudio is the lower level, and the UI change in kde reflects the phonon configuration
currently you can use stylesheets - hard
what doesn't work? primary issue: qt version of phonon vs kde phonon. in mandriva they compile qt with phonon but they don't install phonon: fool qt into thinking it has its own phonon. arch and kubuntu had some issue where they were apparently compiling in pulse audio support but actually it wasn't compiled. any hope of having there hacks upstream? it's already in kde-phonon problem: backends are variable, but the interface to the backend is fixed.
in qml all components could be scripts
what do we do when people come to #amarok crying about pulseaudio? coling will do some screenshots how it should look like. it shouldn't be visible to the user.
 
completely skinnable apps (yay).
the most difficult part in qt UI is layouts.
in qml we have anchors: e.g.
rectangle{
  height = ...
  text
    anchor.left = rect.left
 
}
full control of any objects, and child objects are affected. threaded model ==> careful with multiple animations
nasty things: communication between c++ and qml, easy to expose c++ stuff, but exposing things from qml to c++ is *very* difficult
note: in qml you're still using stylesheets: we'd need an oxygen qml style
raster rendering works very well, X11 sucks
you can do custom delegates (this *could potentially* be seriously interesting for our playlist)

Latest revision as of 14:45, 21 May 2010

QtQuick ultimately separates model and view. runtime in one language, model in something else and view in qml currently you can use stylesheets - hard in qml all components could be scripts

completely skinnable apps (yay). the most difficult part in qt UI is layouts. in qml we have anchors: e.g. rectangle{ 

 height = ...
 text 
   anchor.left = rect.left

} full control of any objects, and child objects are affected. threaded model ==> careful with multiple animations nasty things: communication between c++ and qml, easy to expose c++ stuff, but exposing things from qml to c++ is *very* difficult note: in qml you're still using stylesheets: we'd need an oxygen qml style raster rendering works very well, X11 sucks you can do custom delegates (this *could potentially* be seriously interesting for our playlist)

Retrieved from "https://community.kde.org/index.php?title=Multimedia/Sprint2010/Notes/QMLIntro&oldid=2999"