• BlueDevil 1.0.7, 1.1.4, 1.2.3 and 1.3-rc2 bug fixing frenezy !

    Finally I have had the energy and the time to hunt the damn crashes that have been affecting BlueDevil since the beginning, fixing them has been relatively easy, be able to reproduce them instead has been quite time exhausting.

    Once I fixed all those damn crashes I proceeded to do bug triage and managed to fix all of the confirmed bugs, or said in another way BlueDevil is virtually bug free bug list :)

    There are still a couple of bugs with iPhones, but I will need one of those to be able to confirm and fix the issues. Any donation?

    The changelog looks as follow:

    Fixes for 1.0.7, 1.1.4, 1.2.3 and 1.3-rc2

    • BUG: 298633 // Crash in kded daemon (ObexFtp module)
    • BUG: 279911 // Crash after receiving a file
    • BUG: 297785 //Not confirmed if it is fixed
    • Updated pin databse for more automatic experience

    Fixes for 1.1.4. 1.2.3 and 1.3-rc2

    • BUG: 286466 // Be able to pair WiiMotes (needs BlueZ 4.96)
    • BUG: 276911 // Pairing Keyboards with SSPairing (Bluetooth 2.2)
    • BUG: 291708 // Now we show again the small overlay icon

    Fixes only for 1.3-rc2

    • BUG: 284052 // Nasty crash every time adapter is unplugged

    Now I can proceed and create new bugs by continuing with BlueDevil 2.0 and Screen Management.

    libbluedevil 1.9.2
    md5sum: b492db1825b239e5185c543badb21c26
    sha256sum: 00d56fc671fecda1e60aa8231ba167f11002148098d6510df0a409d19e840d59

    bluedevil 1.0.7
    md5sum: 27e48595679bac72f6ea0d1f496ce524
    sha256sum: 2294f921de0a2920dbfe8b3f824abd8b7d468da71a8bce5e4575be311bc0af65

    bluedevil 1.1.4
    md5sum: b485e0a710146536362cd607bcc3a418
    sha256sum: c0bab0d6a505dbe96d3f6acaad8bdf4aea4de84c342e0e6e59b47e0d5bcba6d6

    bluedevil 1.2.3
    md5sum: e792576d34956d27cd0c3eb3c81a5923
    sha256sum: 7744e0544d27960f21073cf4b48ba865162a2643b7e33f7f21fff43705b4e624

    bluedevil 1.3-rc2
    md5sum: 20452c528ab04c0551f3d8bfc5075c4b
    sha256sum: db6735d5a66634ce5d761c70df4ad7c4f39295ac4a6f9b59bcc25777dc720dd5

    Cheers !

     

     


  • Plasma Active 3 sprint

    A few days ago I attended to the PA3 sprint in Darmstadt, as always I enjoyed a few days with my friends not only working but also taking beers, going dinner etc. I have had a really good time there as I always do when KDE is in the formula.

    As far as I know this is the first PA sprint where a lot of community members external to the project attended, this is really great for opening the project to other areas of KDE, such Solid or KDEdu.  My work focus were:

    Getting to know the inside of the project
    Every project structure is different even between close projects such PowerDevil and BlueDevil. In the case of PA there are a few big differences that have to be taken into account:

    • Most people working on it are employed by companies (and most of them work on it full time).
    • PA should be always ready for release, no unstable or untested stuff allowed in.
    • Strong focus on well designed and usable interfaces.
    • Everything QML
    • There is a strong and shared Vision behind it
     It is important that you agree with the rules of the game before you start to play it, I find PA a really good example of how a professional project can be done together with the community without sacrificing anything. I agree with this rules so I will play this game :)

    Plan how Screen Management will be implemented in PA
    As some of you may know, I'm currently working on a new implementation of Screen Management, even though I'm really delayed on the original schedule the project is not abandoned and I hope to make PA one of the first use cases for it.
    When Thomas Pfeiffer and I started to look at how we can implement Screen Management into PA we quickly identify one valid use case:
    A user is reviewing a set of pictures on its Tablet, at some points he decides to plug its tablet in the TV and watch them in there. Once the TV is plugged the pictures are shown in both screens so the user can use the tablet to control the application while watching the images in the TV.
    A user just bought a movie via Bodega, he wants to play it in its big TV. In this case the controls of the movies will be in the Tablet while the movie itself will be reproduced at the screen.
    A user connects the Tablet into a projector and intends to do a presentation using Calligra Active. The controls of the presentation (Notes, countdown, thumbnails) will be shown at the tablet while the Slides will be shown at the projector.
    As you can see it makes only sense to do something with the external screen if, and only if there is an application that will make use of it, or said in another way we discarded to show the shell into the external screen.

    Plan how bluetooth should be implemented in PA
    As Thomas and I did with Screen Management, we took a look at how Bluetooth should be integrated with PA. Some parts of it can be already used and other parts need a nice QML interface. Following some conclusions we reached:
    • We don't want a Wizard, it is not needed
    • We need a Share Like Connect plugin
    • We need a PA system settings panel
    • Device configuration should be within the PA system settings
    When doing the analysis of how to implement Bluetooth into PA I realized mistakes done in the Desktop (I have been realizing those mistakes for quite some time now). I will implement them in a future BlueDevil 2.0 version.

    Social / Sharing / shiny stuff in KDE software
    Sharing, social, cloud, buzzwords all over that's true but nonetheless important. There are different efforts going on in KDE to make this happen, and make it quick. We had a super interesting BoF about all things that needs to done to make Social/Sharing/Cloud a natural thing in KDE software, it should be as natural as creating a file or as launching an application.
    List of points I remember:
    • Share/Like/Connect for the desktop must happen
    • Having a centralized place for Sharing is important (probably in the shell)
    • We need a centralized place to store Web/Online account information
    • We need to have a shared platform for streams (twitter, identi.ca, facebook...)
    • Having libkpeople finished is crucial, we must have unified personas to work with
    I will probably be working on the first point, but we will see about that later.
    Finally, a mandatory picture took by Martin K.
    PA attendees working
    This post was written on Match 14, information can be outdated.


  • AppMenu Runner, meet the KDE's HUD

    A few days ago Mark Shuttleworth announced the HUD menu, a  Unity dialog that lets you trigger menu actions in the focused application like:

    • look for bookmarks,
    • change your IM status
    • execute an action contained in the menu bar.
    This kind of features as well of how they are executed may sound familiar to you dear Plasma Worksapce user... Exactly! I'm referring to our beloved KRunner!

    KRunner can do a lot of stuff in both global and active application scope (though it tends to offer more global features) , just to mention a few: Math, Bookmarks, Files, Calendar, Contacts, Emails, Devices, Change IM Status, Recent documents...

    I have to say that I'm glad to see Unity going into this direction since it is something that we (KDE Community) have believe in for years, so having Canonical and its designer team walking into the same direction may indicate that we are not wrong or at least we are not the only ones mistaken :)

    Despite KRunner being able to do a lot of things it couldn't do something the HUD does, execute actions contained in the menu. No less than 7 months ago I did my first attempt on achieve exactly that and of course I blogged about it. I didn't continue with the effort mainly because: kdelibs was frozen, it worked only for KDE applications, it worked only if the menu bar was shown within the window.

    After watching the HUD video I got inspired and motivated to create a Runner which will use the same technology as HUD (and the oxygen-appmenu or the plasma-menubar plasmoid) to look and execute menu bar actions, this is the result:

    Direct link

     

    There are a few things to work on but I hope to put this in KDE Plasma Worksapce 4.9 if the Plasma teams like it of course.

    The code is in:

    git://anongit.kde.org/scratch/afiestas/appmenu.git

    Kubuntu packages are WIP
    Would be nice if somebody can write a manual of how to setup appmenu in Qt and maybe other toolkits.


  • Looking forward to 2012

    I'm sure 2012 is going to be an amazing year for Free Software and of course for the KDE community, a lot is happening within our community and we have just started the year ! Just to mention a few from the top of my mind: Calligra getting closer, Plasma Active2, 4.8 release, Frameworks 5, OwnCloud 3, Spark... I can go on for a while :) As every six month or so, here is the list of what I'm planing to work on:

    • AppMenu KRunner (you will see it tomorrow)
    • Finish new RandR supoprt 
    • libsolid in Frameworks5
    • BlueDevil 3.0
    • Kamoso-QML
    • Community work on Solid
    • Community work on KDE-España

    I hope to get all finished before Akademy-2012 and with a little bit of luck be able to work on more stuff. I promise, next post will be my "usual" post with pictures and videos :P!


  • Looking Back At 2011

    w--- layout: post title: Looking back at 2011 categories: - KDE - Software Libre tags: [] status: publish type: post published: true meta: _edit_last: '2' dsq_thread_id: '2226557068' author: login: afiestas email: afiestas@kde.org display_name: afiestas first_name: Àlex last_name: Fiestas ---

    Where are a few hours away from ending the year 2011 (some countries are already in 2012) so I feel like it is the perfect moment to look back at what happened during 2011 so tomorrow I can write what I hope will happen during 2012 :)

    If I had to sum up in one word what I have done this year in KDE I'd say BlueDevil. In the first entry from 2011 I'm asking for help on testing the 1.0.2 version, now 12 month later we are ready to release 1.3 which fixes "all known bugs" and we are preparing ourselves for 1.4 and 2.0.

    Let's take a look month by month on what happened in this blog:

     

    I'd say this year has been quite intense in the KDE front, I have done less than I wanted (which is normal) but more than I expected so I'm happy with the result. Also it is worth to mention that I'm now "Solid Overlord" though I haven't done much yet I know for sure that 2012 will be the year to amend that.

    Happy new year 2012 which for sure, Is going to be a good year for KDE as it was 2011 :)