=== yofel_ is now known as yofel [11:45] * obengdako is away: Away obengdako is idling about [11:45] * obengdako is back (gone 00:00:06) [11:46] * soreau is wondering: why some clients allow away/back messages [11:47] * obengdako i allowed mine to do so soreau [11:48] obengdako: They are really useless and annoying messages [11:49] soreau, i know i just wanted to let those i chat with know when i've stepped away from the pc [11:49] Hint: No one cares if you are there or not [11:50] They certainly dont need message to proclaim absence or presence. If you are talking, they will know you you are at your computer [11:50] obengdako: it's considered rude to do public away messages like that [11:51] please don't do them [11:51] if you set normal /away then people can use /whois to see if you're around or not [11:51] (or if they PM you, they'll get a message that you're away) [11:51] Yes, that is much more concise way of putting it [11:51] Pendulum, oh really then i'll disable [11:51] Pendulum, so i use the command "/away" instead? [11:52] yep [11:52] /away [11:52] and /back [11:52] (or just /away) [11:52] * obengdako is away: trying the away feature [11:52] the problem is not with 1 person doing them, but everybody starts to use those messages after some time 90% of the traffic in the channel is only that ;) [11:52] Right, and its useless messages no one needs to read [11:53] * obengdako is back (gone 00:00:29) [11:53] okay but it still shows up in the channel Pendulum [11:53] obengdako: seems like you have a script or alias or something that overrides teh default /away [11:53] obengdako: what IRC client do you use? [11:54] xchat Pendulum [11:54] i changed some of the away settings [11:54] okay now it is working Pendulum i changed the announce away setting [11:55] now i'm away [11:55] hehe [11:55] thanks! [11:55] Cool [11:55] check my whois and tell me if i did it right [11:55] and what is my reason [11:56] Pendulum, please check my status and my reason i want to be sure those interested can tell i'm away [11:56] * [obengdako] is away (hehe) [11:56] obengdako: got the same thing as soreau [11:56] thank you for fixing it so it doesn't announce [11:56] okay thanks Pendulum soreau [11:56] no problem [11:57] BTW: in xchat you can right-click a nick to see the away message [11:57] lol [11:59] so no one really uses away here in irc even when they are away? [13:06] Hi [16:50] The last Ubuntu App Developer Week day is starting in ~10 minutes \o/ [16:52] salut a tous [16:55] hello all [16:55] Hi [16:59] hi [17:00] Ok everyone, welcome to the last day of an Ubuntu App Developer Week packed with interesting content and speakers! [17:00] Let's welcome jryannel once more, who is going to talk about how to extend Qt Quick with C++ === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu App Developer Week - Current Session: Qt Quick: Extend with C++ - Instructors: jryannel [17:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/04/15/%23ubuntu-classroom.html following the conclusion of the session. [17:01] Hi, I'm from QtDF my name is Juergen Bocklage-Ryannel [17:02] I'm mainly doing training and training material [17:02] today I would like to talk about Qt Quick and how you can extend it with c++ [17:02] For all of you who don't know Qt Quick... [17:03] it's a declarative language build on top of Qt C++ to create great user interfaces [17:03] I prepared a small project for today [17:03] please download it from: https://github.com/jryannel/ubuntu-qtquick-webinar [17:04] I will try to guide you through the project. While you are downloading I will tell you something about Qt Quick and C++ [17:04] Don't worry if you can't download you will also understand without [17:05] Qt Quick is based on a Qt module called QtDeclarative [17:05] saimanoj asked: how to download the project? [17:05] Please go to: https://github.com/jryannel/ubuntu-qtquick-webinar [17:05] you need to have git installed [17:06] or grab the zip file under downloads [17:06] QtDeclarative uses our graphicsview (a 2.5d canvas based on graphics items) [17:08] QtDeclarative is a ui runtime [17:08] it contains an QtDeclarativeEngine which will interpret your qml file [17:08] and a QtDeclarativeView which will paint the items [17:09] If you open the project (QtCreator ->Open Project) QmlCppExample.pro in [17:09] ubuntu-qtquick-webinar/QmlCppExample source tree [17:10] You will see the project files. [17:10] Please open the QmlCppExample.pro file [17:10] in the .pro file I added "QT += gui declarative" [17:11] This is to make the project aware we want to use the QtDeclarative modue [17:12] Now we can use the module in the main.cpp [17:12] Please open the main.cpp file [17:12] There we create a view "QDeclarativeView view;" and set the [17:12] qml source with "view.setSource(QUrl::fromLocalFile("main.qml"));" [17:13] As usual in qt you need also call show " view.show();" [17:13] You will find the main.qml file in "Other Files" in Qt Creator [17:14] It's a simple Rectangle with a blue color and a MoouseArea, which doesn't do anything currently [17:14] Just try to run the project [17:14] for people which don't use qt creator... [17:15] qmake; make; ./QmlExampleCpp [17:15] You need to have Qt 4.7 installed and in you rpath [17:15] If you get an error running the project in creator, you need to uncheck the shadow build [17:16] This is on the side-bar under the Projects tab [17:16] Just uncheck there "Shadow build" [17:16] If you run the project, you see a blue window, which is our blue Rectangle [17:17] In our project we would like now to change the color from c++ side [17:18] You need to uncomment the code between //1{ ... //1} markers [17:18] in main.cpp and main.qml [17:18] Also comment the code between //{0 markers in qml [17:18] in main.cpp the line "view.rootContext()->setContextProperty("value", QColor("green"));" [17:19] pushes a property "value" into our rectangle with the value of the color green [17:20] We access the value in our qml file with "color: value" [17:20] This right side value actually comes form the c++ side. [17:20] So far so easy [17:21] Now we want to push something more complicated into our declarative environment, [17:21] a QObject which has a value, which again is a color. [17:22] Please comment the code between //{1 markers and uncomment the //{2 markers [17:22] in main.cpp and main.qml [17:22] We have a class derived from QObject called ValueObject which contains a value property [17:23] If you look up the valueobject.h file you can see how you declare properties for qml [17:23] You have a setValue(...) a value() method and [17:24] a valueChanged() signal [17:24] all 3 are required for a read/write property [17:24] We make them aware to the object as property with... [17:24] Q_PROPERTY(QColor value READ value WRITE setValue NOTIFY valueChanged) [17:24] This says, make a property of type QColor named color ... [17:25] the read method is the value() method, [17:25] the write method is the setValue(...) method [17:25] and to notify qml about changes use the valueChanged() signal [17:26] All methods are pretty simple, the only one worth mentioning is... setValue(...) [17:26] Please have a look in the valueobject.cpp file for the setValue implementation [17:26] if(_value != value) { [17:26] _value = value; [17:26] emit valueChanged(); [17:26] } [17:27] The if ( ... ) is a guard to avoid loops. [17:28] Only if the value has really changed you should emit the changed signal. You need to obey this rule, otherwise you can get infinite change loops [17:28] So now we have q ValueObject with a value property ready to be used in qml [17:28] In main.cpp we create a object of this value with: "ValueObject* value = new ValueObject(QApplication::instance());" [17:29] and push it into qml with "view.rootContext()->setContextProperty("valueObject", value);" [17:29] This says, make our value object known to qml as "valueObject" [17:30] So we can use it now in our main.qml file [17:30] "color: valueObject.value" [17:31] You should see a blue rectangle. You can change the color simple by changing the color in valueobject.cpp (look for _value(Qt::blue) [17:31] Another way to change it is inside qml. Here we use the mouse area [17:32] "onClicked: valueObject.value = "yellow"" will make our valueObject color property change to yellow [17:32] This change is cascaded to our rectangle [17:32] remember we have our rectangles color bound to "color: valueObject.value" [17:33] So when you click on the rectangle the onClicked handler is called and the color should change to yellow [17:33] I hope you can still follow me :) [17:33] Next case would be we would instead of a simple property, we want to create a new qml element. [17:34] We want to have a ValueObject element in qml, where we can get the color value from. [17:34] For this please comment the //{2 marker code and uncomment the //3{ markers code [17:35] So instead to push an object, we want to register a new type to qml. [17:35] Look in the main.cpp file... [17:35] Here we find: "qmlRegisterType("Application", 1, 0, "ValueElement");" [17:36] This line says, register the type ValueObject under the module name "Application" in version 1.0 as ValueElement element [17:37] So now we have in a module Application a new qml element calles ValueElement [17:37] Let's see how we can use it: open the main.qml file [17:37] The line "import Application 1.0" imports our new module [17:38] which we registered with the qmlRegisterType from c++ code [17:38] Sure you can have many elements inside one module. [17:38] We use the new element with "ValueElement { id: valueElement }" [17:39] Our new element is now accessible under the id: valueElement. [17:39] As this is a new element you can create as many of them as you want [17:39] with "color: valueElement.value" we access the color of our new element, by the id [17:40] and in our mouse area we can change the color using "onClicked: valueElement.value = "red"" [17:40] I hope you get the idea [17:40] Jus to recap... [17:41] You can push simple properties into qml, complex properties (e.g. objects) [17:41] and also new elements. [17:41] But this is just the start... [17:42] You can create own elements which can paint, for example an ellipse [17:43] For this you would need to derive a class from QDeclarativeItem [17:44] But I think we are running out of time to show this here... [17:44] So I post some links with comments [17:44] have a look at :http://qt.nokia.com/developer/learning/online/training/materials/qt-essentials-qt-quick-edition for the "Training Module Integrating QML with C++ from" [17:45] This explains how to create a simple ellipse item and adds on this more complicated stuff, e.g creating other types, using enums, ... [17:45] You you want to learn more about what we did currently please read: Qt Declarative Binding [17:45] http://doc.qt.nokia.com/4.7-snapshot/qtbinding.html [17:45] and Extending QML Functionalities using C++ [17:45] http://doc.qt.nokia.com/4.7-snapshot/qml-extending.html [17:46] You can also create qml modules as plugins [17:46] This is explained in the training module, but also in QDeclarativeExtensionPlugin Class Reference [17:46] http://doc.qt.nokia.com/4.7-snapshot/qdeclarativeextensionplugin.html#details [17:46] If you want to mix traditional widget code and qml please look at: Integrating QML Code with Existing Qt UI Code [17:47] http://doc.qt.nokia.com/4.7-snapshot/qml-integration.html [17:47] If you want to see how the Qt developers have written their declarative items, checkout the qt source code and navigate to: /src/declarative/graphicsitems/ [17:48] There you find the code for the Item qml element in "qdeclarativeitem.h" [17:48] And for the Rectangle element in "qdeclarativerectangle_p.h" [17:49] Please note the rectangle has a _p in the name, which declares it as private. So you can't derive from it in c++. [17:49] Only the QDeclarativeItem class is meant to be derived [17:49] I would recommend you checkout the Example: Minehunt [17:49] http://doc.qt.nokia.com/4.7-snapshot/demos-declarative-minehunt.html [17:50] This shows how to make a minehunt game in qml, where the game logic is in C++ [17:50] You find other examples at: More Examples: [17:50] http://doc.qt.nokia.com/4.7-snapshot/qdeclarativeexamples.html [17:51] From the DevDays 2010 in Munich we have also a video, which explains QtQuick and C++ very nicely: TechTalk Developer Days 2010 [17:51] http://qt.nokia.com/developer/learning/online/talks/developerdays2010/tech-talks/qt-quick-for-c-developers [17:51] This closes my talk on Extending Qt Quick with C++. [17:52] I hope some of you where able to compile the example and get an idea about how qml and C++ can work together. [17:52] Remember you can use JavaScript in QML, but you should not make to much use of it for performance reasons. [17:53] But this truly depends where you run your code. [17:53] A tip at the end, you can also embed qml files as resource files in your executable. [17:53] By this deployment get's much easier [17:54] I would like to see how someone uses Qt Quick with a WebFramework like Rails or Django [17:55] QtQuick is network transparent so you can load qml files form a server or let them dynamically generate by a webframework :) [17:55] Okay take care and I leave the stage for the next session. Bye! === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu App Developer Week - Current Session: Phonon: Multimedia in Qt - Instructors: apachelogger [18:02] You'll know him not only for his good looks and legendary coding skills, but also for having rocked this AppDeveloper Week: there he is - KDE/Kubuntu developer apachelogger talking about how to write a multimedia app in virtually no time! [18:03] apachelogger, let's roll! [18:03] :D [18:03] thanks dpm [18:03] bonjour, ahoy and welcome everyone! [18:04] ...for the third time this week ;) [18:04] Today's special on the menu: Phonon, the most awesome terrific super cool magical unicorn multimedia abstraction library ever! [18:05] First let's get dependencies sorted out as we will have a bit of coding later on. [18:05] If you like GStreamer you might want to use this command: [18:05] sudo apt-get install phonon-backend-gstreamer libphonon-dev qt4-qmake libqt4-dev build-essential [18:05] If you like VLC you might however want this one: [18:05] sudo apt-get install phonon-backend-vlc libphonon-dev qt4-qmake libqt4-dev build-essential [18:06] If you have a very old version of Ubuntu OR like xine: [18:06] sudo apt-get install phonon-backend-xine libphonon-dev qt4-qmake libqt4-dev build-essential [18:06] At any rate a simple text editor will suffice for the editing part ... it is all nicely prepared for copy and paste :D [18:07] Should there be any questions, please just drop your QUESTION: in #ubuntu-classroom-chat at any point. [18:07] But enough of that nonesense. [18:07] Let us talk about Phonon \o/ [18:07] Phonon is a multimedia abstraction library powered by pluggable backend components, adapting the Phonon API to specific multimedia frameworks/libraries. [18:08] ^ I actually made that description up just 5 minutes ago, though it captures Phonon pretty well, plus it got buzz word factor ;) [18:09] Primarily Phonon is an abstraction layer between multimedia consuming applications (such as music players, games or sound notification systems) and a specific multimedia library (GStreamer, VLC, Xine, Helix, QuickTime, DirectShow, Microsoft Media Foundation, etc.) [18:10] Possibly the fact that I listed 7 of such libraries and yet could not resist appending an 'etc' might give you an idea of why exactly abstraction makes sense. [18:11] Who seriously would want to maintain good multimedia experience on >3 operating systems? [18:11] Well, the Phonon team, obviously ;) [18:12] Especially in a Qt context you really do not want to make your application depend on one of those 300^31000 libraries for multimedia, or implement your own abstraction system just to become portable to all platforms (read: operating systems) that you might have time to implement support for. Instead we could just do it once ... in Phonon. [18:13] Additionally. If one of these libraries decides to change their API, why would every Qt application developer need to spend their Monday afternoon changing their code to suite the new API? [18:13] If we just as well could do it once ... in Phonon. [18:14] I suppose highlighting all the advantages and disadvantages of abstraction is a bit of apointless exercise, so I better stop now. [18:14] Actually. [18:14] Do not let me blind you... Phonon is not the solution to every problem in computer science. It is abstraction after all. [18:15] If you have a look at the Wikipedia artcile on abstraction you will probably read something like "using a common denominator". === tubadaz_ is now known as tubadaz [18:15] This implies being more limited. As always ... the general is less specific than the specific ;) [18:16] Due to the given constraints of abstraction Phonon does not try "to do it all". [18:16] It does not strive to support every possible use case that might or might not exist for a multimedia library. [18:17] Instead we are focusing on the (actually very small) number of key features that are of use to the greatest possible amount of application developers. === marcel___ is now known as MAWSpitau [18:17] Phonon tries to provide the common set of features you will require in your off the shelf media-enabled applications. [18:18] This ranes from simple (non 3 dimensional) games to video and music players. [18:18] In particular, if you have a look at the Phonon API [18:18] (i) http://doc.qt.nokia.com/latest/phonon-overview.html [18:18] you will hopefully notice that the core set of features of the key classes are actually able to cover jsut about everything most multimedia applications will ever want to do. [18:19] This of course primarily is playback. [18:19] More precisely: simple playback in the manner of just needing to throw a URL at Phonon and it will try to do something meaningful. [18:20] More advanced features are usually bound to the availability of support in the underlying libraries and thus more dynamic (they might be there, or not, or partially etc.). [18:20] That way it is possible to implement a common denominator and at the same time stay powerful enough to enable terrific media-centric applications such as good looking video players. [18:21] ....talking about video player... [18:21] I think it is about time to start doing some coding, because I am getting bored writing all that stuff and would like to copy and paste a bit more ;) [18:22] At FOSDEM I boldly claimed that I could do a video player with 3 lines of Phonon specific code in C++. Whether that is any useful is a question that shall remain unanswered. [18:23] It is however perfect to grasp the basic concept, even if I do not know any application that would only need 3 lines as you usually want to do more engaging things anyway. But oh well... :) [18:23] You can get a template for this from [18:23] (i) http://people.ubuntu.com/~apachelogger/uadw/04.11/phonon-template.tar.gz [18:23] Simple extract it somewhere. [18:24] Inside you can find a main.cpp, a qmake build file and a video and audio file (or so I hope). [18:25] The code I will present goes into the main.cpp in the main function in between the 2 statements that are already there. Includes are also there, so if all goes well you should be able to build this stuff right away. [18:25] Talking about building, you can do that by running [18:25] qmake . [18:25] and [18:25] make [18:25] and then [18:25] ./demo [18:25] to run the application. [18:25] Right then. [18:25] Let us start with a simple audio player. [18:26] The first thing you always need when working with phonon is a media object. [18:26] With Phonon you build a thing we call the media graph, which at its root has the media object. [18:27] To the media object you can attach various outputs (AudioOutput, VideoWidget ...) and even 'inject' effects between the media object and the outputs. [18:27] Very easy to understand I shall hope. [18:28] The media object is like the heart of every media graph. It controls what file you are currently playing, if you are playing at all, at what time the media is .... [18:28] And the best thing about the media object is, that it is insanely easy to create ;) [18:28] (i) Code samples is always indented with 4 spaces [18:28] MediaObject mo; [18:29] That did not hurt at all, right? [18:29] Now let us also add an AudioOutput while we are at it... [18:29] AudioOutput ao; [18:30] You can have many of these media objects, each doing a different thing. For example if you are creating a game, you might want to have a media object (thus graph) for background music and another media object for event sounds (like when a pony rides through the screen). [18:31] Due to this we will need to tell our media object that it should be connected to our audio output. Otherwise there will be probably no sound... wouldn't be much of an audio player then ;) [18:31] Doing this is very easy, we just call Phonon::createPath(a,b) [18:31] like this: [18:32] createPath(&mo, &ao); [18:32] Now that we have a media object and an audio output and have told the media object to spit out audio via the audio output, we only need to set a source and ask our nice media object to start playing the source. [18:33] As the template already includes some music (in particular Amarok's first run jingle in case anyone is interested) you can use the following: [18:33] mo.setCurrentSource(MediaSource("./first_run_jingle.ogg")); [18:33] mo.play(); [18:34] Putting the pieces together you should have something like this in your main.cpp: [18:34] MediaObject mo; [18:34] AudioOutput ao; [18:34] createPath(&mo, &ao); [18:34] mo.setCurrentSource(MediaSource("./first_run_jingle.ogg")); [18:34] mo.play(); [18:34] You can compile it using the commands mentioned earlier [18:34] qmake . && make [18:34] If all goes well you shoudl be able to run ./demo and hear music. I at least do \o/ === tubadaz is now known as tubadaz_away [18:36] Now let us dive into video playback. But I must warn you, it is going to be just as difficult as audio! :O [18:36] First we create a video widget (which is about the video version of audiooutput), then attach our media object to it. === tubadaz_away is now known as tubadaz [18:37] VideoWidget vw; [18:37] createPath(&mo, &vw); [18:37] Should you have worked with Qt before you will probably expect that VideoWidget is a QWidget and needs to be shown explicitly... and you are right. [18:38] Simply add [18:38] vw.show(); [18:38] So that is 3 more lines to get video. [18:39] Of course the amarok jingle is only audio, so that source is not going to be any good. I just get a black video window :( [18:39] But fear not, your well prepared instructor has thought of this problem and also bundled a video into the template :P [18:39] Simply exchange the previous line where we setCurrentSource() with this one: [18:39] mo.setCurrentSource(MediaSource("./konqi_ad1.ogg")); [18:40] Again run [18:40] make [18:40] and ./demo should now show a video window with a rather old advertisment for the KDE Desktop \o/ [18:41] But what is this? We are far away from 3 lines of code! Oh noes! [18:41] Maybe I was too daring, claiming such a silly thing :/ [18:41] Or not... :P [18:42] Please remove all that plunder we carefully pasted into the main.cpp and let us start from scratch. [18:42] Let us think about this again. [18:42] We want a video player, we want it to play a video, and we want it to show a video..... [18:42] maybe we should do it just like that. [18:42] VideoPlayer vp; [18:42] vp.play(MediaSource("./konqi_ad1.ogg")); [18:42] vp.show(); [18:43] Voila! A video player (with audio) in 3 lines of code :P [18:44] aha! [18:44] akshatj_ just complained that I cheated by hardcoding the URL. [18:45] I suppose it depends on the POV, I could add Qt magic to get a file open dialog or something and it still would be only 3 lines of phonon specific code ;) [18:45] Which was my original scope for the mission. [18:46] Well. [18:46] Qt to the resuce. [18:47] Let us be user friendly here. [18:47] Exchange our previous hardcoded media source with [18:47] MediaSource(QFileDialog::getOpenFileName()) [18:47] So that our vp.play warps into: [18:47] vp.play(MediaSource(QFileDialog::getOpenFileName())); [18:48] There. Still 3 lines and even with a file selector dialog at start up :) [18:48] * apachelogger hopes akshatj_ is happy now :) [18:49] Just to go one step further. In the future you will also be able to create a video player without any code *at all*. In about 30 seconds. [18:49] (i) http://www.youtube.com/watch?v=HrMSIrhFYlY [18:50] I hope I was able to interest you in Phonon and would be super happy to see your amazing new applications become even more amazing through superb multimedia :) [18:50] More information on Phonon is avilable in the Qt documentation [18:51] (i) http://doc.qt.nokia.com/latest/phonon-overview.html [18:51] As well as an overview of the in Qt included classes: [18:51] (i) http://doc.qt.nokia.com/latest/phonon-module.html [18:51] There are 10 minutes remaining in the current session. [18:52] ClassBot: Thank you, you are the sweetest :) [18:52] If there should be any questions, you now have <10 minutes to get them answered.... [18:53] Meanwhile I can also tell you a bit about future developments in Phonon. One of the amazing new things we will see appearing in (stable) Phonon hopefully before 2012 is audio and video capturing. [18:54] I have been playing around with this a couple of months ago and it is really easy to use and enables the creation of real fun applications I believe. [18:55] Also, so Google and KDE will, we will get superb QML support and simple encoding capabilities. [18:56] There are 5 minutes remaining in the current session. [18:56] It would also appear that there are rumors that a new version of the VLC backend component is just around the corner (but don't tell anyone ;)) [18:57] * apachelogger is out of things ot tell and his fingers hurt [18:57] I think we can wrap this up. [18:57] Thanks for reading and have a nice day :) [18:57] o/ [19:00] right [19:00] hello folks [19:00] so the plan for this session is to discuss integrating with the sound menu === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu App Developer Week - Current Session: Integrating music applications with the Sound Menu - Instructors: ronoc [19:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/04/15/%23ubuntu-classroom.html following the conclusion of the session. [19:01] firstly I would like to point out that early in the O cycle we will make available via libunity the ability to integrate with the menu [19:02] this will mean developers will not need to worry about mpris interfaces and will just need to use this api [19:02] Can I ask which of you here are interested in implementing a compliant player from scratch ? [19:03] right so nobody so far, for Maverick we used libindicate for registration with the menu [19:04] i reworked this during the natty cycle so as a compliant mpris interface was all that was needed to integrate with the menu [19:04] but there is abit more involved than just raising an mpris interface [19:05] mpt went to great lengths to define a preferred workflow with players and the menu so as players can optin or opt out of the menu through their own UI [19:05] more info on all of this can be found on the wiki (wiki.ubuntu.com/SoundMenu) [19:06] each player should allow the user to to have the option to opt in or opt out. The functionality behind all of this is in the indicator-sound's gsettings [19:06] again info on all of this can be found on that wiki page [19:07] also there is a mailing list which you should join if you are developer interested in this [19:07] * ronoc digs up the lp page [19:08] https://launchpad.net/~indicator-sound-developers [19:09] I use this to announce to devs about upcoming changes [19:09] I feel though after this cycle must of the architecture is settled [19:09] so no major changes planned for now [19:10] back to what I was saying previously, one of my main reasons for moving away from libindicate and using a strictly dbus registration mechanism [19:10] was to reduce / remove any i-s related dependency for clients [19:10] i-s = indicator-sound [19:11] clients = players = banshee, rhythmbox etc [19:11] by doing this it means that players like spotify work seemlessly without any i-s specific work by the spotify team [19:13] furthermore the change to use gsettings as a way of recording blacklisted applications or applications which have previously registered means that the menu dynamically updates when some change has been wrote to the i-s gsettings [19:13] this did happen before with the maverick version [19:13] any questions anyone [19:13] anything in particular you would like me to go through ? [19:14] ok, so for clients,the main thing is to raise an mpris interface with the desktop entry properly filled in [19:15] the mechanism works so as when an mpris interface appears on the bus the service attempts to load the desktop file defined on the root mpris interface for the client [19:15] if all is good , then the player is inserted in the menu [19:16] the mpris people have been very supportive in redefining the spec over the last year which has really made this all work nicely [19:17] whether you support the playlist interface or not is determined by the service at start up by querying the interfaces listed by your player [19:18] if the service finds a playlist interface then its exposes the relevant dbusmenu items [19:18] any questions anyone ? [19:19] we had a scrub bar at one point but it was removed due to design clutter which in retrospect was a good call by mpt [19:20] the back end for pulse has been totally refactored this cycle and pretty confident that it should work well now (before it was a bit of fudge due to time restrictions) [19:20] also this cycle I introduce the voip slider [19:21] next cycle we will do work which allows for the voip slider to be added for applications that are not just necessarily voip apps [19:21] so gnome-sound-recorder running will trigger the appearance of the voip slider [19:22] i have done the work for this in a branch but won't merge until the O cycle begins [19:22] what else ? [19:22] i feel though now ( a year down the road) [19:23] the code and the architecture of the i-s is pretty stable/completed [19:23] obviously new features require new code but as the spec stands I have all angles covered [19:23] is there anything people would like to see added ? [19:24] I suppose 7pm in Europe on Friday isn't the best idea [19:24] although there must be some Americans here full of beans [19:25] As I expressed earlier one of the main reasons for the reworking of the registration architecture was to allow players to easily integrate [19:26] there are still some players though that do not integrate [19:26] totem being one [19:26] which I have not got around to writing [19:26] nothing ubuntu specific is required anymore just a compliant mpris interface [19:27] !q any questions [19:28] * ronoc is getting the hang of using the classbot [19:29] * ronoc waits for some interaction [19:31] don't really know what else really needs to be covered ... [19:39] Any question guys, please ping me [19:42] * ronoc enjoy Richard Skelton's latest release on type [19:51] There are 10 minutes remaining in the current session. [19:56] There are 5 minutes remaining in the current session. [19:59] Ok folks all done here I think [19:59] Good weekend all [19:59] thanks ronoc [19:59] Cheer james_w [20:00]