Activity Not Available
I Use This!


Analyzed 3 months ago. based on code collected 5 months ago.
Posted about 8 hours ago by Chris Rizzitello
It has been about two weeks since I last wrote about AtCore. In that time Tomaz has commited a few changes that allow us to use a plugin system so that AtCore can specialize in speaking your firmware!? Or something like that. Really what It means is ... [More] that we should be able to keep most all of the common stuff within the AtCore object and use the plugins to give us firmware specific stuff when needed. Did someone say Test?. The test is pretty stright foward and that is to evaulate how well AtCore is doing at sending print commands to the printer to do this really we just need to be able to print an object that takes some amout of time. Late nights printing tiny pyramids I’ve been awake all night watching this thing print is working as expected. First I had to find a decent model to print and I came across this cool Fractal pyramid Model by ricktu     Mandatory hardware pictures ? Two computers.. one to record and play host while the other keeps my sanity durring the nights print.It would be along print the slicer estimates the print to take around 5 hours. Ok time for the mandatory hardware pictures of stuff Check out the computer that will be hosting the printer and recording video for later.In this Set up we will have chairs eyeview Two cameras extruder cam and an overview cam. Sadly my 3rd camera didn’t want to play along it was time for a new floor? just unable to get a decent focus on the printer LCD so we will have to go without this time.    Watch the Timelapse video ….7 hours later….. After 7 hours of printing we have it completed. The Best part i have saved for last when printing triangles……   i have used glow in the dark filiament. To quickly charge up the glowing i have placed   Glow the model between the lights of some very bright led lamps. Unfortunately the Camera didn’t do such a great job picking up the detail with the model glowing in the dark     So how did we do? Well the print was a success! The RAM usage was a bit high for my liking but is most likey due to our text log. We will do further tests to check that. The Firmware Plugin for Repitier seams to be printing stabily for any lenght print I would call that a success!     [Less]
Posted about 12 hours ago by Gilles Caulier (cgilles)
Dear digiKam fans and users, After a second release 5.1.0 published one month ago, the digiKam team is proud to announce the new release 5.2.0 of digiKam Software Collection. This version introduces a new bugs triage and some fixes following new feedback from more
Posted 1 day ago by Plasma Mobile blog
Today’s weekly mobile IMG update brings, Updated packages New appstream release Kirigami based new discover design You can flash using instructions at
Posted 2 days ago by Chakra OS
This announcement is also available in Italian and Taiwanese Mandarin. The latest updates for KDE's Plasma, Applications and Frameworks series are now available to all Chakra users. The Plasma 5.7.5 release is the final bugfix update for the 5.7.x ... [More] series, as 5.8.0 will be released soon. It includes a month's worth of bugfixes and new translations, with notable changes found in the plasma workspace, sddm-kcm and networkmanager packages. Applications 16.08.1 include more than 45 recorded bugfixes and improvements to kdepim, kate, kdenlive, konsole, marble, kajongg, kopete, umbrello, among others. Frameworks 5.26.0 include bugfixes and improvements to breeze icons, plasma framework, kio, ktexteditor and sonnet. Other notable package upgrades: [core] cups 2.1.4 git 2.10.0 mariadb 10.1.17 providing the security fix of MySQL 0-day "CVE-2016-6662" php 5.6.25 poppler 0.47.0 - this breaks backward compatibility, if you have any local/CCR packages depending on it you will have to recompile them [desktop] pdf2svg 0.2.3 [lib32] wine 1.9.19 [gtk] amule 10958 It should be safe to answer yes to any replacement question by Pacman. If in doubt or if you face another issue in relation to this update, please ask or report it on the related forum section. Most of our mirrors take 12-24h to synchronize, after which it should be safe to upgrade. To be sure, please use the mirror status page to check that your mirror synchronized with our main server after this announcement. [Less]
Posted 2 days ago by Aracele Torres (araceletorres)
Hi everybody, After announcing that our timeline was translated into Spanish, now I wanted to announce that it is also available in Chinese. Thanks to Leslie Zhai now we have one version of the timeline in Chinese simplified. Screenshot of Chinese ... [More] version. Besides that I did some adjustments as captions centralized, images turned into links, and improvement in the captions texts. If you also have any suggestions, translation, or adjustment, let me know.  Our repository can be cloned here. [Less]
Posted 2 days ago by Aracele Torres (araceletorres)
Hi everybody, After announcing that our timeline was translated into Spanish, now I want to announce that it is also available in Chinese. Thanks to Leslie Zhai now we have one version of the timeline in Chinese simplified. Screenshot of Chinese ... [More] version. Besides that I did some adjustments as captions centralized, images turned into links, and improvement in the captions texts. If you also have any suggestions, translation, or adjustment, let me know.  Our repository can be cloned here.  [Less]
Posted 2 days ago by Jeremy Whiting (jpwhiting)
A few weeks ago after discussing with Luke Yelavich about what to work on in speech-dispatcher next I decided to take a stab at making it use GSettings for its settings. (You can see the work in progress here if you like.) I've used GSettings before ... [More] for work projects so thought it would be a good/easy thing to take on.There are many advantages of using GSettings over plain ini-style files. Type checking (You can't enter a string for a numeric setting for example). Notification of setting changes. Command-line changing of settings. Default values for settings defined in the schema(s). On that wip branch speech-dispatcher itself has been changed to use GSettings and also reacts to many setting changes dynamically. It doesn't react to changing the port type or port number or unix socket path dynamically, since we have no mechanism to tell client applications that it is changing. There are also GSettings schemas for the output modules, just need to make them read their settings from GSettings instead of the old ini-style .conf files. spd-conf also has been modified to write to GSettings rather than .conf files. That change alone reduced the spd-conf python script by quite a few lines of code and made it a lot easier to read.As I was doing this work I got thinking about the differences between GSettings and QSettings. Besides one being glib/c based and the other being Qt/C++ they are really pretty similar. There are a few differences though: QSettings doesn't emit signals when a setting changes. (I found a few forum posts asking why this is with possible workarounds. Nothing built into QSettings though). QSettings doesn't have a schema for the settings themselves. There's no way to introspect a setting file to see what settings are possible. It just depends what keys the application reads. QSettings doesn't have a command-line tool to set the settings. Since QSettings is cross platform it uses the Registry by default on Windows, PList files by default on macOS, and ini-style files on linux QSettings does have type checking, but no range checking or anything like that. I was a bit disappointed that QSettings that I've used for many many years is lacking these seemingly obvious and probably useful features. I wonder if we as a community implemented these features in QSettings if the Qt company would accept them. [Less]
Posted 2 days ago by Kdenlive
We’ve added a new Toolbox section that has posts dedicated to new and improved functionality in Kdenlive. Check back regularily for updates.
Posted 2 days ago by Qt Dev Loop
In a few weeks the Qt World Summit 2016 will open its doors in San Francisco and I have been given the chance to speak there about my experiences while developing the Qt World Summit 2016 Conference App. This article series here will give you some ... [More] additional information to my presentation. For nearly 40 years I have been developing software, where the last 8 years I have focused on mobile App Development. I started mobile App Development with BlackBerry OS7 (Java) followed by BlackBerry 10 native Apps (Qt 4.8, Cascades UI Controls). In 2016 BlackBerry, for first time ever, started to build secure Android Phones and my customers asked for x-platform Apps. Personally, I liked the way BlackBerry 10 Apps were built using QML and Cascades. Fortunately Qt just started Qt 5.6 Tech Preview of new Qt Quick Controls 2. I did some first tests to see if Qt Quick Controls 2 will enable me to develop good looking and performant mobile Apps. First steps went well so I decided to spend some more time and to give Qt 5.7 and Qt Quick Controls 2 a try in real-life projects. Over the last 4 years I built many mobile business Apps for Enterprise and SMB and I also did some Apps for Developer Conferences. I asked Tero Kojo to develop the QtCon 2016 Conference App as a proof-of-concept to rely on new Qt Quick Controls 2. You can download the QtCon Conference App from Google Play (, Apple App Store (, Amazon App Store (, as APK ( or build it by yourself from Open Source Github Repo ( The App was built without any extra native Code – pure Qt only. Feedback was great and I just started to do the Qt World Summit 2016 Conference App – Github Repo will be public soon. Hopefully this time the App will also be available for Windows 10 from Windows App Store. Special thanks to Maurice Kalinowski for his help, the QtCon Conference App is running on Windows 10, although I had some problems uploading this to Windows App Store. There is a blog series about all my experiences using Qt Quick Controls 2 to develop mobile Apps (, also a series in (German) Web & Mobile Developer Magazin and now some articles here at Qt Blog, too. You can expect some 3 – 4 articles here at Qt Blog about developing Qt Conference Apps. All development is done in my spare time and my goal is to motivate mobile App Developers to try out Qt Quick Controls 2 to develop x-platform Apps. I never did Qt development before, also never did native Apps for Android, iOS or Windows but now I am able to develop and upload Apps to Google Play or Apple App Store I am also using Google Material Style to provide a modern mobile App feeling. Thanks to J-P Nurmi, Mitch Curtis and others for great hints HowTo customize Qt Quick Controls 2. From my experiences over the last 6 months, developing mobile Apps with Qt 5.7 and Qt Quick Controls 2 is much more comfortable and easier than using Xamarin, React Native, Cordova, Angular or Ionic. The good news for all my friends from BlackBerry 10 community: there is a great amount of re-use of C++ Code from Cascades and also architecture style is similar using Signals/Slots and QObject* as data model. Speed is key to success The first impression of any mobile App with regards to User Experience comes from starting the App. The User should never have the feeling that an App is slow. Some of my recipes for a speedy start are below: fast creation of C++ Classes immediately show something on the screen be dynamic: only instantiate UI Controls you really need How am I doing this? Only instantiate C++ Classes, avoid any initialization as open Databases, load Cache Files and more. DataServer::DataServer(QObject *parent) : QObject(parent) {     // Do NOTHING HERE } Use the fastest possible way to show some UI to the User. My root and main Navigation Control is a Drawer. The Drawer contains a list of “Destinations“, where a Destination is a specific area of the Application as Home Schedule Speakers Venue … Each Destination can be one of the Qt Quick Controls 2 Navigation Controls ( or Container Controls( Pane Page StackView SwipeView / Tab Bar Inside the Drawer you can use a ListView to let the User select a Destination – take a look at Qt Quick Controls 2 Gallery Example. I‘m using a Repeater to create different types of Controls: Destinations, Divider, Header, … To show the selected Destination best way is to use a StackView as your root UI Control and swap the content – so there‘s always only one Item at this root StackView. To startup immediately don‘t create all the Drawer – Destinations ! This can easy be done with a little trick: define the Repeater without a data model.         Repeater {             id: destinations             // Don‘t set the model here !             // model: navigationModel             Destination {                 id: destinationLoader             }         } So nothing will be created now. To show something to the User create a lightweight Control as initialItem. I‘m using a BusyIndicator.         // STACK VIEW INITIAL ITEM (BUSY INDICATOR)         // immediately activated and pushed on stack as initialItem         Loader {             id: initialPlaceholder             source: "pages/InitialItemPage.qml"             active: true             visible: false             onLoaded: {                 // Show BUSY INDICATOR                 rootPane.initialItem = item                 item.init()                 // Now something is VISIBLE - do the other time-consuming stuff                 startupDelayedTimer.start()             }         } The next trick is to start a Timer with a small delay to allow QML to show and animate the BusyIndicator. Then from Timer timeout execute all the initialization stuff and call some Q_INVOKABLE methods from your C++ Classes to load data from Cache and more. As soon as this is done you can go on with creation of UI Controls. To trigger this set the Repeater Data Model and all the Destinations will be created and HomePage will become current Item on root StackView.         Timer {             id: startupDelayedTimer             interval: 300             repeat: false             onTriggered: {                 initialPlaceholder.item.showInfo("Initialize Data ...")                 dataManager.init()                 settings = dataManager.settingsData()                 dataUtil.setSessionFavorites()                 // … and so on ...                 // inject model into Destinations Repeater                 destinations.model = navigationModel                 // show the Navigation Bars (Drawer and Favorites)                 initDone = true                 // now NavigationBars available                 // show first destination                 rootPane.activateDestination(firstActiveDestination)             }         }   Here we go: first „real“ Page is visible. But wait: not all Destinations will really be created from the Repeater – this would take too much time and consume too much memory. All the Destinations are created dynamically using Loaders and I implemented some Activation Policies: Immediate: The Control will be instantiated and remain. I‘m using this only for the first visible Page – the HomePage. When-Selected: First time a User selects a Destination will create the Control and remain. This happens for all Destinations a User normaly will use while the App is running: Schedule, Speakers,… While-Selected: Those Destinations are only created when needed and be destroyed if User changes the Destination. Candidates for this Policy: Help, Settings, About, … Take a look at the code how all of this is implemented, attend my Session at Qt World Summit 2016 in San Francisco ( or meet me at #QtWS16. Stay tuned – next article will cover the QObject* Data Model I‘m using, Caching and Data Binding. The post Qt Conference Apps – out of the Developer Trenches – Part 1 appeared first on Qt Blog. [Less]
Posted 3 days ago by Valorie Zimmerman (valorie)
Kubuntu 16.10 beta has been published. It is possible that it will be re-spun, but we have our beta images ready for testing now.Please go to, login, click on the CD icon and download the ... [More] image. I prefer zsync, which I download via the commandline:~$ cd /media/valorie/ISOs (or whereever you store your images)~$ zsync other methods of downloading work as well, including wget or just downloading in your browser.I tested usb-creator-kde which has sometimes now worked, but it worked like a champ once the images were downloaded. Simply choose the proper ISO and device to write to, and create the live image.Once I figured out how to get my little Dell travel laptop to let me boot from USB (delete key as it is booting; quickly hit f12, legacy boot, then finally I could actually choose to boot from USB). Secure boot and UEFI make this more difficult these days.I found no problems in the live session, including logging into wireless, so I went ahead and started firefox, logged into, chose my test, and reported my results. We need more folks to install on various equipment, including VMs.When you run into bugs, try to report them via "apport", which means using ubuntu-bug packagename in the commandline. Once apport has logged into launchpad and downloaded the relevant error messages, you can give some details like a short description of the bug, and can get the number. Please report the bug numbers on the qa site in your test report.Thanks so much for helping us make Kubuntu friendly and high-quality. [Less]