<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>----- Original message -----
<br>> Hello list,
<br>> here follows a short resume of what discussed during the yesterday's
<br>> meeting :)
<br>>
<br>> - *Media Fetcher Backends:*
<br>> Hayri is responsible for this with his GSoC. Currently we have 2
<br>> dataengines, called *picture *and *video*.
<br>> Both were intended as a bridge among different fetching backends and the
<br>> PMC browsing view.
<br>> Their API is really similar except for little specific stuff and so we
<br>> decided to merge them into one, unique,
<br>> WebMedia DataEngine (the name can be, of course, changed to a better
<br>> one): the common data structure we'll use to return the fetched
<br>> information from web services will be wrapped into something like:
<br>> MediaResource and MediaResourceCollection. The DataEngine and its backend
<br>> will all be written in JS given the nature of the data: web-driven.
<br>> We currently have everything to provide such kind of DataEngine except
<br>> for the *add-on finder* which is something Aaron will likely work on
<br>> soon. Also there's something we can eventually share with the kde-silk
<br>> project, so maybe we should have a talk with them in case we already have
<br>> tools for such stuff.
<br>> Additional for Hayri: as stated by Aaron: Network  access is already in
<br>> the bindings while xml parsing can be done via
<br>> <a href="http://xmljs.sourceforge.net/">http://xmljs.sourceforge.net/</a>
<br>>
<br>>
<br>> - *QML into PMC:
<br>> *We're gonna make use of QML for layouts in PMC and specifically in our
<br>> State Machine.
<br>> Christopher Blauvelt is contributing a lot with QML into PMC.
<br>> Currently the aim is to have a new view for the mediabrowser, inheriting
<br>> its AbstractItemView,
<br>> that takes advantage of QML in order to show pictures in a fancy way :p
<br>> For those who are curious some stuff is there under the declarative/
<br>> folder in the root directory.
<br>
<br>This will be great. Eager to check those out once exams are over :)
<br>
<br>>
<br>> - *QGestures and input abstraction in PMC*
<br>> This is a bit tricky part and probably needs some further discussion. The
<br>> aim is to have a sort of layer that maps different input events
<br>> into common Media Center events like *play, pause, next-picture,
<br>> previous-picture, volume-up *and so on..
<br>> This way we can have different input devices to be recognized and ready
<br>> to be used (think about remotes and/or keyboards for example).
<br>> As discussed we'll probably use the QGestureEvent and eventually create
<br>> our own PMC events in order to ease the mapping.
<br>> Later events will be sent to the components loaded into PMC that will be
<br>> able to perform the proper action.
<br>> I also think that we can have virtual event methods in our base MCApplet
<br>> classes like playEvent, volumeUpEvent and such.
<br>> In each applet the gesture recognition would call the proper virtual
<br>> event method.
<br>> Of course i might be wrong so, please, point out your thoughts about
<br>> this.
<br>>
<br>> I think this is all; please add what i eventually missed from the
<br>> meeting.
<br>>
<br>> Cheers!
<br>>
<br>> P.S.: How to upload the IRC log to plasma.kde.org?
<br>>
<br>send it to Aaron with a request and he'll upload it :)
<br>
<br>> --
<br>> Alessandro Diaferia
<br>> KDE Developer
<br>> KDE e.V. member
<br><br></p>
</body>
</html>