January 16, 2017

Es siempre la gran esperanza de la Comunidad KDE pero nunca acaba de despegar. No obstante la noticia de que ha sido lanzado Calligra 3.0, la suite ofimática de KDE, es la luz al final del tunel de un proyecto que parecía estancado y que parece que despierta de su letargo.

Lanzado Calligra 3.0, la suite ofimática de KDE

Hacía más de un año que no hablaba de Calligra en en blog. Y es que ha sido un año duro para el desarrollo de la suite ofimática. A la siempre difícil transición de una tecnología a otra se le suma la siempre falta de recursos humanos que viene adoleciendo este proyecto desde tiempos inmemoriales.

No obstante, este pasado 15 de enero los desarrolladores de Calligra anunciaron el lanzamiento de la nueva versión de su suite: Calligra 3.0. Esto significa un gran paso en el avance del proyecto y ofrece las siguientes novedades respecto a su organización interna:

  • Todo el código ha sido migrado a KDE Frameworks 5 y Qt5, con lo que se mantiene a la vanguardia en lo que se refiera a herramientas de desarrollo.
  • Krita ha tomado un rumbo independiente y ya no forma parte de la suite.
  • Han sido discontinuadas Author y Brainstorm.
  • Y, de momento, han sido discontinuadas por falta de mantenedores Flow y Stage.

 

Lanzado Calligra 2.7.3

Personalmente, me encantaría utilizar Calligra pero nunca lo he encontrado suficientemente maduro para hacerlo. Esperemos que este nuevo lanzamiento sea el definitivo.

Más información: Calligra

¿Qué aplicaciones ofrece Calligra?

Como toda buena suite ofimática, Calligra nos ofrece varias aplicaciones para cubrir todas y cada una de las necesidades que nos generan nuestro que hacer diario. No obstante, el número de programas que ofrece ha variado, reduciendo su número por dos razones: para aligerar carga y porque algunas no estaban listas para dar el salto a KF5.

De esta forma tenemos:

  • Words, el procesador de textos.
  • Sheets, la hoja de cálculo.
  • Stage, la aplicación de las presentaciones.
  • Flow, la aplicación de los diagramas.
  • Kexi, el creador de bases de datos visual
  • Plan, la aplicación de gestión de proyectos
  • Krita, la aplicación para dibujo artístico.
  • Karbon, el programa para dibujos vectoriales.
  • Shapes, el módulo de dibujos para integrarlos en las otras aplicaciones.

January 15, 2017

A new wonderful era for the Calligra Suite has begun with the release of version 3.0.

We have chosen to cut back on the number of applications. Krita has left us to be independent and although it was emotional it was also done with complete support from both sides. We are saying goodbye to Author, which never differentiated itself from Words. We also removed Brainstorm the purpose of which will be better fitted by a new application (nothing planned from our side). Flow and Stage has gone in this release but we intend to bring them back in the future.

What’s New?

The 3.x series is built on top of KDE frameworks 5 and Qt5 which in and of itself doesn’t bring much new but it ensures that we stay current. It took a lot of effort which means we haven’t made many other new features.

Hi,

in the recent months, I didn’t find much time to spend on Kate/KTextEditor development. But at least I was now able to spend a bit more time on OpenSource & Qt things even during work time in our company. Normally I am stuck there with low level binary or source analysis work.

For our products, we were in the need of some online help. As our documentation is delivered as PDFs generated by the tools of the TeX Live distro, a natural idea was to use some PDF viewer and integrate it more tightly in our software than just “open the manual at page 1”.

We did review PDF viewers out there, but most (like Okular) have too many dependencies to be just bundled with our product (or a license not permitting that).

Without bundling, we can’t ensure that the tight coupling is working, without starting to test the integration with X different viewers which more or less all need other kinds of command line arguments to open the right page or even lack that feature or will not reuse an already running instance, ….

Therefore, as our GUIs are developed with Qt anyways, we did take a look at libpoppler (and its Qt 5 bindings), which is the base of Okular, too.

Easy enough, taking the small demo program shipped with the library and adding a small stdin based interface to tell it “goto <named reference>” we arrived at some small PDF viewer that is fit enough for our use case.

We named the thing “FirstAid”, the sources can be grabbed at github.com/AbsInt/FirstAid. Like libpoppler and the demo, its licensed as GPLv2+.

As already the README states, the aim of this small project is not to replace some full fledged viewer like Okular, the design goal is to have a small viewer that is auto-started by some host application and will jump to the requested labels for a tightly coupled online help. It can be used as a pure standalone PDF viewer, too, but that is more intended for testing it e.g. on the documents that should later be shown as online help.

FirstAid

I already annoyed Albert with some small issue I had with libpoppler, perhaps I will provide more useful fixes in the future if more things come up during FirstAid development. In any case, already THANKS A LOT for the Qt 5 bindings around libpoppler, they work nicely for us!

I really think this small project shows the benefit of OpenSource: We needed a PDF viewer, we were able to create a small one in less than a month based on OpenSource libraries and we can give back the results to the community (if it is useful for others is a different story, but perhaps other people have the same itch to scratch, if not, ignore it). I hope more possibilities for such things come up at work in the future.

For building: It should build out of the box if you have some recent Qt and libpoppler-qt5-dev installed, at least the Travis CI is able to build it out of the box with the given config. For me, it shows some small bugs if used with Qt 5.6/7 compared to the Qt 5.8 Beta I used here for testing.

Ya estamos a principio de año y los desarrolladores de KDE  lo empiezan haciendo lo que saben hacer: mejorar KDE.  De esta forma ayer nos ofrecieron la última versión de KDE Frameworks. De esta forma ya tenemos la actualización de enero de KDE Frameworks, es decir, la versión 5.29. Una gran noticia para todos ya que aunque no sea visible, estas mejoras tienen repercusiones directas en el usuario final a medio y largo plazo. No hay que olvidar que las mejoras de estas herramientas facilita el desarrollo del Software de la Comunidad KDE, proporcionándonos las herramientas y aplicaciones que utilizamos a diario.

Actualización de enero de KDE Frameworks

El pasado 14 de enero de 2017 fue lanzado KDE Frameworks 5.30, la trigésima revisión del entorno de programación sobre el que se asienta Plasma 5, el nuevo escritorio linux de la Comunidad KDE, y las aplicaciones que se crean con para él. Este KDE Frameworks facilita muchísimo la creación de software para el moderno ecosistema actual de la Comunidad KDE.

Actualización de diciembre de KDE Frameworks

Hay que recordar que los desarrolladores de KDE decidieron lanzar actualizaciones mensuales de este proyecto y lo están cumpliendo con puntualidad británica. La idea es ofrecer pocas pero consolidadas novedades, a la vez que se mantiene el proyecto evolucionando y siempre adaptándose al vertiginoso mundo del Software Libre.

Las mejoras de esta versión son extremadamente variadas destacando unos nuevos iconos mimetypes pero recibiendo casi todas más de un par de actualizaciones. No obstante las librerías más beneficiadas han sido Plasma Framework, KPackage Framework, Iconos Breeze, KWayland y KWidgetsAddons

¿Qué es KDE Frameworks?

Para los que no lo sepan, KDE Frameworks añade más de 70 librerías a Qt que proporcionan una gran variedad de funcionalidades necesarias y comunes, precisadas por los desarrolladores, testeadas por aplicaciones específicas y publicadas bajo licencias flexibles. Como he comentado, este entorno de programación es la base para el desarrollo tanto de las nuevas aplicaciones KDE y del escritorio Plasma 5.

Recuerda que puedes ver una introducción a Frameworks 5.0 en su anuncio de lanzamiento.

KDE's Google Code-in party is ending once again. Student work submitted deadline is January 16, 2017 at 09:00 (PST). 

Mentors, you have until January 18, 2017 at 09:00 (PST) to evaluate your student's work. Please get that done before the deadline, so that admins don't have to judge the student work.

Then it will be time to choose winners. We need to have our choices in by January 23, 2017 at 09:00 (PST). Winners and Finalists will be announced January 30, 2017 at 09:00 (PST).

To me, this contest has been lovely. Because there are more organizations participating now, there are more tasks for students, and less pressure on each org. It seems that the students have enjoyed themselves as well.

Spencerb said, in #kde-soc, This was my first (and final) gci, so I don't have much of a point of comparison, but it's been awesome. I've been an opportunity to meet new people and just get involved with KDE, which I've wanted to do for a long time. I've also learned a lot about serious software development that I wouldn't have otherwise.

"I'll turn 18 this Monday, which is why this is my last year :(  I'm so glad to have had the chance to participate at least once.

As a task, Harpreet filed a GCi review: http://aboutgci2016.blogspot.in/

So far, we've had 121 students. The top ten have 103 completed tasks so far! And 160 tasks completed so far. Most exciting for me is that Beginner tasks completed: 45. Getting kids acquainted with Free and Open Source Software communities, which is why every organization must have beginner tasks. I'm glad 45 kids got to know KDE a bit.


Pues eso. Que tenemos problemas con el tema del blog y estamos arreglándolo.

Disculpad las molestias

January 14, 2017

On FreeBSD, Qt4 is still a thing — for instance, for the KDE4 desktop that is still the latest full-KDE experience you can get from the official packages. And although that software is pretty old, the base system still evolves. FreeBSD 9 has been put to rest, and with it all the GCC-based FreeBSD systems. That frees us from having to deal with GCC and Clang at the same time, and we can generally patch things in just one way (usually towards more-modern C++). But the base system also evolves “out from under” older software. There’s an effort to update the base system compiler (for FreeBSD 12) to Clang 4.0 (sometime soon-ish), and that means that our older C++ code is being exposed to a newer, pickier, compiler.

Seems like I’ve been doing “fix KDE stuff relative to pickier compilers” since, like, forever (on Solaris, and then FreeBSD, and then Solaris again, and OpenSolaris, and then FreeBSD).
Anyway, today’s little fix comes from Qt4 Linguist (devel/qt4-linguist in the ports tree), where we find this code:
if (c->findMessage(m->text(), m->comment()) >= 0)
Here findMessage() returns a MessageItem*, so that’s a nonsensical comparison that should be != 0 instead (or idiomatically, just leave out the comparison but Qt4 sources are somewhat inconsistent in their formulation of null-pointer checks).
So there’s — for me — a brief interlude of messing with old codebases in preparation for new things, while the rest of the KDE-FreeBSD team deals with newer things like the latest KDE Frameworks and Plasma Desktop releases (which, as I’ve said many times, may be had from the area51 repository and work fine, but are waiting on various dependencies in the official ports tree).

January 13, 2017

We are proud to announce the first maintenance release for the 16.12 cycle. Besides the usual bugfixes and usability improvements this release also marks the official release of the Windows port.

Windows port

Last summer, thanks to a Google Summer of Code slot, Joseph Joshua started to work on a Windows port of Kdenlive. Vincent Pinon then continued to work on it and we are excited to offer today the much expected first version of Kdenlive for Windows. This is a first testing version, zipped in a folder that does not require an install. You must however separately install FFmpeg, following the simple instructions provided on the download page.

Packaging

Packaging effort is also going on the Linux side, with an up to date Appimage and *Ubuntu PPA containing the latest release, so you have no excuse not to try Kdenlive.

You can go straight to our download page to get the instructions to install Kdenlive 16.12.1

About Kdenlive

Kdenlive is an open source video editing software, based on the MLT framework and FFmpeg libraries. We are a small team and are always welcoming new contributors.

We hold a monthly IRC Kdenlive café where users and developers meet, and you can also exchange on our forum or on our mailing list. Some great tutorials are also available from the toolbox section of our website.

We are part of the KDE community, which provides, among other, all the infrastructure for Kdenlive.
Donations are always welcome: https://www.kde.org/community/donations/?app=kdenlive

Fixes and improvements in this version

More than 25 bugs were fixed in this release, as well as a few usability improvements.
See full changelog.

January 12, 2017

Today, KDE announces the public release of Kirigami UI 2.0 !

All issues that were identified during the ten days of beta testing have been fixed, and Kirigami 2.0 is deemed ready for general use.

Soon after the initial release of Kirigami UI, KDE's framework for convergent (mobile and desktop) user interfaces, its main developer Marco Martin started porting it from Qt Quick Controls 1 to Qt Quick Controls 2, the next generation of Qt's ready-made standard controls for Qt Quick-based user interfaces. Since QQC 2 offers a much more extended range of controls than QQC 1, the port allowed the reduction of Kirigami's own code, while improving stability and performance. Kirigami 2 is kept as close to QQC 2's API as possible in order to extend it seamlessly.

Beyond the improvements that the port to QQC2 brings, further work went into Kirigami 2's performance and efficiency, and it also offers significantly improved keyboard navigation for desktop applications. On Android, Kirigami 2 integrates better visually with Material Design.

Of course there are also smaller improvements in various places, such as better handling of edge swipes in the SwipeListItem or more reliable activation of the Overscroll / Reachability mode (which pulls down the top of the page to the center of the screen where it can be reached with the thumb).

Discover (Plasma's software center), a quite complex application, has already been ported successfully to Kirigami 2 without much hassle, so we are confident that most applications can be ported easily from Kirigami 1 to Kirigami 2. Since Kirigami 2 requires Qt 5.7, which is not available on all Linux distributions yet, Kirigami 1 is still maintained (receiving fixes for critical bugs) for the time being, but won't receive any new features or improvements.

You can get Kirigami 2.0 via its wiki page, or from your distribution's repository as soon as it is packaged there.
If you want to try it out on Android, the Kirigami Gallery demo app is available on Google Play.



KDE Plasma 5.9 Beta

KDE Plasma 5.9 Beta

Thursday, 12 January 2017. Today KDE releases the beta of this year’s first Plasma feature update, Plasma 5.9. While this release brings many exciting new features to your desktop, we'll continue to provide bugfixes to Plasma 5.8 LTS.


Be even more productive



Spectacle screenshot notifications can now be dragged into e-mail composers (including web mail)

Spectacle screenshot notifications can now be dragged into e-mail composers (including web mail)

In our ongoing effort to make you more productive with Plasma we added interactive previews to our notifications. This is most noticeable when you take a screenshot using Spectacle's global keyboard shortcuts (Shift+Print Scr): you can drag the resulting file from the notification popup directly into a chat window, an email composer or a web browser form, without ever having to leave the application you're currently working with. Drag and drop was improved throughout the desktop, with new drag and drop functionality to add widgets directly to the system tray. Widgets can also be added directly from the full screen Application Dashboard launcher.





Icon Widget Properties

Icon Widget Properties

The icon widget that is created for you when you drag an application or document onto your desktop or a panel sees the return of a settings dialog: you can now change the icon, label text, working directory, and other properties. Its context menu now also sports an 'Open with' section as well as a link to open the folder the file it points to is located in.





Muting from Panel Task Manager

Muting from Panel Task Manager

Due to popular demand we implemented switching between windows in Task Manager using Meta + number shortcuts for heavy multi-tasking. Also new in Task Manager is the ability to pin different applications in each of your activities. And should you rather want to focus on one particular task, applications currently playing audio are marked in Task Manager similar to how it’s done in modern web browsers. Together with a button to mute the offending application, this can help you stay focused.





Search Actions

Search Actions

The Quick Launch applet now supports jump list actions, bringing it to feature parity with the other launchers in Plasma. KRunner actions, such as “Run in Terminal” and “Open containing folder” are now also shown for the KRunner-powered search results in the application launchers.

A new applet was added restoring an earlier KDE 4 feature of being able to group multiple widgets together in a single widget operated by a tabbed interface. This allows you to quickly access multiple arrangements and setups at your fingertips.


More streamlined visuals





New Breeze Scrollbar Design

Improvements have been made to the look and feel of the Plasma Desktop and its applications. Scroll bars in the Breeze style, for instance, have transitioned to a more compact and beautiful design, giving our applications a sleek and modern look.


Global Menus



Global Menus in a Plasma Widget

Global Menus in a Plasma Widget

Global Menus in the Window Bar

Global Menus in the Window Bar

Global Menus have returned. KDE's pioneering feature to separate the menu bar from the application window allows for new user interface paradigm with either a Plasma Widget showing the menu or neatly tucked away in the window bar.





Neater Task Manager Tooltips

Neat Task Manager Tooltips

Task Manager tooltips have been redesigned to provide more information while being significantly more compact. Folder View is now able to display file emblems which are used, for example, to indicate symlinks. Overall user experience when navigating and renaming files has been greatly improved.


More powerful Look and Feel import & export

Look and Feel Themes

The global Look and Feel desktop themes now support changing the window decoration as well – the 'lookandfeelexplorer' theme creation utility will export your current window decoration to the theme you create.

If you install, from the KDE store, themes that depend on other artwork packs also present on the KDE store (such as Plasma themes and Icon themes) they will be automatically downloaded, in order to give you the full experience intended by the theme creator.

New network configuration module





Network Connections Configuration

Network Connections Configuration

A new configuration module for network connections has been added to System Settings, using QML and bringing a new fresh look. Design of the module is inspired by our network applet, while the configuration functionality itself is based on the previous Connection Editor. This means that although it features a new design, functionality remains using the proven codebase.


Wayland

Pointer Gesture Support

Touchpad Configuration

Wayland Touchpad Configuration

Wayland has been an ongoing transitional task, getting closer to feature completion with every release. This release makes it even more accessible for enthusiastic followers to try Wayland and start reporting any bugs they might find. Notable improvements in this release include:

An ability to take screenshots or use a color picker. Fullscreen users will be pleased at borderless maximized windows.

Pointers can now be confined by applications, gestures are supported (see video right) and relative motions used by games were added. Input devices were made more configurable and now save between sessions. There is also a new settings tool for touchpads.

Using the Breeze style you can now drag applications by clicking on an empty area of the UI just like in X. When running X applications the window icon will show up properly on the panel. Panels can now auto-hide. Custom color schemes can be set for windows, useful for accessibility.


Full Plasma 5.8.95 changelog

Live Images

The easiest way to try it out is with a live image booted off a USB disk. You can find a list of Live Images with Plasma 5 on the KDE Community Wiki.

Docker images also provide a quick and easy way to test Plasma.

Package Downloads

Distributions have created, or are in the process of creating, packages listed on our wiki page.

Source Downloads

You can install Plasma 5 directly from source. KDE's community wiki has instructions to compile it. Note that Plasma 5 does not co-install with Plasma 4, you will need to uninstall older versions or install into a separate prefix.

Feedback

You can give us feedback and get updates on Facebook or Twitter or Google+.

Discuss Plasma 5 on the KDE Forums Plasma 5 board.

You can provide feedback direct to the developers via the #Plasma IRC channel, Plasma-devel mailing list or report issues via bugzilla. If you like what the team is doing, please let them know!

Your feedback is greatly appreciated.

Carrying on the successful tradition of conf.kde.in since 2011, we are moving to the north-east region of India for this year's conf.kde.in. Join us for conf.kde.in 2017 on 10, 11, and 12 March at Guwahati in Assam, India. conf.kde.in 2017 will focus on the promoting Free and Open source including but not limited to Qt and KDE software.

The Venue

Event will be held at IIT Guwahati, Assam. IIT Guwahati is the sixth Indian Institute of Technology established in the India by the Government of India. Indian Institute of Technology Guwahati's campus is on a sprawling 285 hectares of land on the north bank of the river Brahmaputra around 20 km from the heart of the city. With the majestic Brahmaputra on one side, and with hills and vast open spaces on the other, the campus provides an ideal setting for learning.

IIT Guwahati

About conf.kde.in

conf.kde.in started in 2011 at RVCE in Bangalore as a 5 day event with 300 participants, initiating a series of such KDE events in India. There was a KDE Meetup in 2013 and conf.kde.in 2014 at DA-IICT, in 2015 at Amrita university, Kerala, in 2016 at LNMIIT Jaipur, which brought in members of the KDE Community from all over the world to attend the event, give talks, and share the spirit of KDE. The 2017 conference will cater to new members of KDE as well as seasoned developers, providing updates about what is going on in the KDE Community and teaching newcomers how to start making meaningful contributions. These events have been successful in attracting a lot of Indian students to mentoring programs such as Google Summer of Code (GSoC), Season of KDE and Google Code-In.

This year, the conf.kde.in 2017 organizers intend to generate even more interest and participation by creating a fertile environment for people to get started with KDE, Qt and FOSS through numerous talks, hands-on sessions and demonstrations.

Call For Papers

If the event seems exciting and valuable, this is an opportunity to join in.

Submit a paper explaining the content for a presentation of not more than 30 minutes on any aspect of KDE, Qt or other FOSS topic that you want to cover. Please include pertinent information about your background, other talks you've made (if any), and anything else that gives a sense of what attendees can expect from your presentation. The organizers await your innovative proposals, and are looking forward to an abundant gathering of the KDE Community.

If you want to talk at conf.kde.in please head to call for papers page

Dot Categories:

January 10, 2017

 

 

The hype is great: WikiToLearn India Conf2017 is almost here!

 

Hello WikiToLearn-ers! First of all, let me wish a happy new year to all of you!

How better to start the new year? With lot of news!

In less than two weeks WikiToLearn India Conf2017 is about to happen. We are extremely happy because this is the first big international event entirely dedicated to WikiToLearn. We have to thank the members of our community who are working hard to provide you this amazing event. For sure, the best thing about this conference is the great variety of speakers: Ruphy is flying from Italy to India to attend the conference and give a talk about WTL. For this event we have speakers lined up from Mediawiki, KDE and Mozilla Community. Several projects and ideas will meet at WTL India Conf2017 and this is simply amazing for us! The entire event will be recorded and videos will be uploaded online: you won’t miss any talk!

We have planned other great things for this 2017. Few days ago some members of the community met to have a discussion about our targets for the future. We came up with a new strategic plan for the incoming months: join our communication channels to discuss it with us. New talks, new posters and technical improvements are just around the corner. WikiToLearn1.0 is great, but what’s coming now is even better!

2016 was fantastic for us, but in 2017 a turning point is waiting for us. Stay tuned!

 

L'articolo Wiki, what’s going on? (Part20-2017 is here) sembra essere il primo su Blogs from WikiToLearn.

Let's start with some luridness:

Now from the beginning: I got to know quite a few people in the past decade (phew, I'm such a dinosaur!) who use Kate as their editor of choice to hack on C++ code, on a daily basis. While I totally agree Kate is an excellent editor -- don't get me wrong on that, I use it literally every day, too -- it doesn't and can't possibly provide the best experience when working with C++ code, in my book. This is not about Kate vs. KDevelop -- not at all. This is about a text editor vs. an integrated development environment for C++.

If you're working with QtCreator, Eclipse, Visual Studio, whatever, that's totally fine -- all those are decent IDEs you can use to work with C++, all those have immense set of features which help you get along while hacking.

They key thing me as a KDevelop developer fails to understand is:

Why would you want to use the Kate text editor to hack on C++, if the exact same text editor component is inside KDevelop; a fully-featured C++ IDE!

Just recently I've learned from another KDE community member that he (citing him here) doesn't seem to need any of the things KDevelop has over Kate. Unfortunately I've heard that a few times now, so I think we as the KDevelop team are just pretty pretty bad at marketing the capabilities of KDevelop or KDevelop just sucks.

In good faith I'm presuming the former, since we actually got plenty of cheerful reviews on social media sites (reddit, blog post comments, you name it) about the new KDevelop 5 release, featuring the new C++ support backed by Clang/LLVM. Let me show you a quick overview over how KDevelop 5 looks like, what it has to offer and how code browsing looks like.

Quick KDevelop feature tour:

Of course there are a lot more features (e.g. unit test runner, patch review, VCS integration, debugger integration, code refactoring utils, etc. pp.), but this was the best I could come up with my half-baked screencasting skills in a rush. Check out the Feature Tour on the KDevelop website for more information.

I'd love to get some input from this particular set of users who use Kate as their main C++ IDE (I'm not talking about users who occasionally edit some .cpp file in an editor, I'm referring to power users who work with Kate on C++ on a daily basis):

  • Did you ever try KDevelop? What did you not like?
  • What made you switch back to Kate?
  • What does Kate offer what KDevelop does not?
  • Under what scenarios would you consider switching to KDevelop?

Please enlighten me! :)

PS: If you didn't know yet: You literally need to type in three commands into your shell to get KDevelop on your distro via our AppImage.

PPS: I hope you're aware I'm just mocking you here, you're of course free to use whatever tool you like to use. I'd just like to get some data points where we (as the KDevelop team) can improve in future to provide a better hacking on C++ experience!

January 09, 2017

digiKam-5.4.0-Front

Dear digiKam fans and users,

Following the 4th release 5.3.0 for the 5.x series published in November 2016, the digiKam team is proud to announce the new release 5.4.0 of digiKam Software Collection. This version introduces several improvements to the similarity search engine and a complete re-write of video file support.

read more

Plasma is nearing a new release and with 5.9 coming shortly we have the question of should we switch Neon to use Wayland by default for the Developer Unstable edition. To evaluate it I updated the Plasma Wayland ISO and found it pleasingly functional on VirtualBox.  Time to install this setup on my real hardware and see what breaks.

VirtualBox_neon_09_01_2017_17_58_35

Facebooktwittergoogle_pluslinkedinby feather
Sorry guys, I  know this is super late, but better late than never!

Wow! Last July Google flew a group of 28 students and 28 parents down to San Francisco and we got treated to a taste of Google.

We did so much during this trip, it would get boring if every detail were to be explained, so the events below are in the right order, but not every event will be listed. Not that the omitted events aren’t just as cool, these just seemed like the most interesting

Sunday
Because there were few enough of us, Google was able to very flexible with our trip planning. Many of the students are from the absolute other side of the world (India, Kazakhstan, etc) and it would be a pity for them to just visit for 5 days, so many groups brought their entire family and stayed for weeks. In short, there wasn’t one day that everyone was flying in, but I can say the the majority of groups flew in on Saturday or Sunday. This gave most of the people some time before our first event, the meet and greet, which was held at 5:30 PM at the hotel. My father and I flew in early on Sunday, so we were able to do our own walking tour of Chinatown, Telegraph Hill, and the Embarcadero.

Our hotel was the Hyatt Regency in San Francisco, which was a very nice hotel, nicer than any I had previously been on. The most impressive thing was the layout. There were rooms around the perimeter of the hotel, with the massive atrium in the middle. And when I say massive, I mean the biggest in the world:



Our first formal activity together was this “Meet and Greet”. All that we knew about this activity was that there would be “Heavy Appetizers” and that we would be getting a goodie bag at the end. First, let’s talk about these “Heavy Appetizers.” I think it would be a little unfair to call this food Appetizers:


That set a standard for the food quality though. We were all thinking: “If these are appetizers, what is a meal!?” So the agenda for this meet and greet went something like this: Eat, listen to Stephanie, get free stuff, then hang out. What free stuff might you ask?


That’s right, not only a pretty cool computer bag, an official GCI coat, but also a Nexus 5X and case!

Monday
Monday was the longest day of activities. It started at 7:15, then we were all rounded up and tossed in two buses, some still half-asleep and some very much awake. Stephanie acted as our tour guide as we made our way to Mountain View.


I had never been to San Francisco before, so I was surprised how large the area was. Mountain View on a map looked right next door to San Francisco, but in reality it takes about an hour and a half to get there. Once we had arrived, we got our breakfast (sandwiches with ham and egg, lots of fruit on the side) then all filed into the room that we would be spending the majority of our day in.


The morning at the Googleplex was spent doing awards. Each Code-in winner got one of these:
Sacycwh-iNFAyGFeMv4EG0OwYfHu_UZkVnps92pTFBObFUGNQEcbKVG1ETpLpQYxu3ItC0NqzklG0QqCgQQZPyd-Du89dnfTLtNuRksyajQHKnZPmw1e7bckF1Hd6FDXS6oqrxH0MV0b8qjPm4Z0YbOcyzWxa766ctSCMecu-VtgHYu-ae3A5Vg4GMHK-Au1rK5m3_I1xCFi81FmnXkIZ2d5dg3fVtPDMTzGtF4M2Jl07ZBrG91KvDnGplxouSbtpwtnBQEBjWlZ0s6STLcVcUGMjGwLsCNJGYp5bRkbOYpgmL8P5OBleR3dOAl_r43EHWZ8nhdwuF1AKuspgagKfZs8D_lrLbkO3T2aGtHPhFMGkOFlmH0V5lDg4bCsXTQPx-L0HoYu8RxCyVCE6kfpDS4mGjb2hNJNQmTK9I23bXTsdc86t1HZn0InZ7znn7I30XhTCQZxvf5whiAbSFUbazBIWBLyTCQGn5gFO8DdUHC63CddYehMHa9CTQxvpyaFAu4AvGrUVxsg2p-g_pUgktc1fOrfYO6C4ycvHkaXb2F1eaGTrWZz9Hso4qJTJVvSSagSjJEAO5h1QKrUtxkS3cVqQsMbrqj_GhPYoGfYPSpoyfSjPY6cuC4klthS_5Hxsgtgv-xK8coXnFr70Ph2gU2jevIipc6Pn4lclF_A9jY=w1424-h949-no

along with more T-shirts.

Even though it seemed like we had just eaten breakfast, we headed out in smaller groups for lunch. What was lunch you may ask? We went to one of Google’s many many “Cafes”, but these aren’t Cafes in the traditional sense. This is how it works: you find some Googler to let you in, then you grab a tray and wander around, getting all sorts of food, from asian (yes there was sushi), american, indian, practically anything you could think of. Then you walk out and eat for free. No wonder restaurants can’t really survive in the Googleplex when there is so much free food...

We then continued back to the auiditorium where we did the morning’s activities in. Now came probably the coolest part of the entire trip: Googler talks. These were more or less exactly what you think they would be. Everyone is rallied into a room then we sit for about 45 minutes and listen to googlers talk about their job. And how is their job you might ask? Pretty pretty sweet.
ZRhsgi68PWhHDZ-3xzhkF9dZAFh_zGUidNdTxcFqwyAMF89z69I8lXFP3mZF97ggsJ-tguhwF1hVIUEieWkpy5vN_-mkwQZqyxtpjrF3khVi6G6DvhldSmF01AxoM0QPQ5I2g9px3i7BR3aZoEBZmVYHkx6i45grwpdqYAaQS1nXe_BwydEn8jCwkbYjA_3qWtg0LXOTIinMgXNo96gVlvjQ6C8zNDhJUCxiXsldKhxUId_zVwMux98TVz8pvPhZjMvmNdDSelDSo1xMlb_w3Uh2zXKCCYO5vA5H6Lb7uUy12LyydhdT2tgZMrfxddwCi90MaxzqoGNkET2xkhbAiUrF0ufDxFIjhHzO5vJq-odz3awDIJsKkfspM5IiQP18Ngp8pfhd7bxhU54xwc4Ue-aN8kPE1JJS2SbBozEYMDQTzGihgNOtSFajIygZ1Bue03oJNnNIbc_rNMJNvt1xN1p8qbXwU5wXlegQOKDPFoQYXvcpGtpmyvA9pnOHqvceVY0FRo1BDUtNyUvI-G0mBL_9DdMGN7ikHRsGqE1I3BUN1EjKluwDNLZs3kF87_0O3J2CAnvaUsCg45tHWrLUS2p-07WjkeILlOdOIsvMBcuFPcy6pqYhO-tXZ2HOC2sR3fKlWWwiW13BnvrEtMsaHB0ikarxGm_XaslDjd-djg=w1266-h949-no

Finally, around 4ish we headed out to the Google Merchandise store. What were we doing there? Oh yeah, blowing $150 that was given to us for the occasion. There were T-shirts, flash drives, plush toys,  chromecast, whew!

UhMZWFbaouB9H2YdR9RHgdVbfICSZplGyRZazMF25Wb8aUhpvOnUSFojzIa9ac1XVSPoQMGLLmcAbTlc5FBu9Wcm5_D6k9V1ogYyssS2o4DpI-YhL2TZECplvG9eluU8Ech-F_qm5cnnBWD3VPJ9qvXBoRB9s1xYnAdyPpYl_ATqcQRlADIOlf5w86UZS8sQlzpGOWZVBKt8DDZF73SXFBAkFqrGaQSApR77YXTCSsFFn8FzD2EYKre3hZGpPjkGskpBuAo8Hp0Oej-DSi8Jg-wn2VCoQONLIrJPeU1iLKWQykB5aX_DhB4dpiZ1Fb0lHrV9yCq57GMjmdfKScbDWbhJKBIN3QXrc2TChvQsoPyRFcbueiKBq0Cm7GIsCnUe_L4c3_iPxCGwczgFFuEfOO5qBQrAYQxQIMUe6TgNVUG4CW2fw1EL1UI23MvnxAE6Pg9NliRrHVS2wbBjGbfOsL8L5Bm_sgiXN29U3FJ4c-XhYW0I_7cVYGywJyjXYpAB6PwO3P18ilYgQ8R9PfGVTP38uS8F080-tCxtMoK9wgJqQjpV9_IlRv49b4LuFgm6nSS4wFWO2_19s97lMujT5WmYG6r5CLtn7wxb2B9XLuta5bgj99qJ2u9v6O3KDQI_WXK-ntuX_bbRR13SkEZ8qKwjHQA-0vZA6kxH27N5ow=w712-h949-no

Alright, so the day must be over by now! No...one more stop. The Google “Visitor Center”. Now this visitor center may not pass for what I think of as a visitor center, as the general public isn’t allowed in there, but it is still very cool nonetheless.

KxwHqZSyDhRy7_Rj0wVhuJTyIvq7qaks3sEMZahXHHl_HXA-HcabIGKPH-GBzqXBM75QlwV9wSd0L7ZyAPpVgXx_MMhIHKH7R97k1DhgkqSW2d2JJBnKfZm9cxHi6RyeavxkBEm7ODLOMJeHy2i2RcSKv0tdWXTn-vhiXyhlISvMffzNI14fME-8uvUDl8wyxwalWb1OyAh7N0nog-0RmqJe2adUfsMyLlyrw7cVKGTADU2bChL2Iav9jXVdz7GHf_j79UYCMQIM215diD0rGbYcIzg4VE7K7_5-QtKeHXvfYDO_Luq5SA2d0cO8Y9sKeKAQF1MKbn6hknw5dzOv_0wSXBr38xmOsjH9pZ4A302FacybvoP-rZ7OVkoCAwTIeNDRo4Kl05B_c5_PM6zpY-xArqYUWMfcavcy8WlWqHEx2elCd36QyAo17upTm2-MQbLCHRpmZjffZRr1AjoREI18HTevtiyYKG5shYAd6-4ld9FM1EJoqwN8sxiONnGvoEoaRlqgF3cQsWUkqk8RJKeIuoBKP-qAB8sX0V8kinM2Tn32WFr-HjjBwyV_RSX1x4D6T8UebXszsCax4dqSVPflESCb_23MBhEKGMzo4740LLzvLR7Wi9uLHl0W9ui8urfLLUXfsnarak-_006G4EN69PrExN1YEoI-x13alQ=w1266-h949-no

Sorry, I lied about that one more stop nonsense. But really this time, one more stop. Dinner. We got back to the auditorium and there were trays and trays of indian food, ready for the taking.

And so ends our day of activities at Googleplex. But what do you do when you are dead tired and just really want to go to sleep? Of course, stay up another three hours hanging out with the rest of the winners, making sure to minimise your sleep for the next day.

Tuesday
Tuesday was designed to be our fun day, and fun it was! First thing in the morning, many of the winners (myself included) stepped up onto segways to get a tour of the fisherman's wharf. I had never ridden a segway before, but I can say that they are pretty fun. They are super intuitive, and most everyone understood very quickly how they worked (not to say there weren’t plenty of crashes).

x8sW7umQhLxlb1ekTfB7H1pcza7QBJ75sep1WQEE-S0fPRyCRecmKjUeHYxXoZaPYDCX4Kj_Nfkd_oVjAPFJjjlHPLhWxPC-_VnemfloFLEJzMq7KPb-kv9-PvkCGvCUB_lMlK0XkEBU4Bl9gkU8V8X4yfjVHfihObM0EPFsREX7JvzdWVDSqEySajqhmyxHqk3kPVJ8MlQbFRYVwP2YP6XoN-795cBLMXdkiM5yAc8YcDUh2no-UdFXNJBezgpSNyG6izX_VhYAFJMAPssud7VJwWZHygNNnH6kaKPPzJnI4BYl1WYIOnPzSr9KcI3wytHomuy8S7t9uLubKnYxK7z0CbLIIG4TSaKieXotYbXaS1CO0tto4F4mzmxUQus98PI-F6b4gB4XBK4c5KABdxmarJ1ccMBaItHITDP5ZVBvPflnXvbP35wECM4jiik836r5-8yy0iE_Uf8PcFfCTWFGZoXfZ6BE69WBVRQ6EUKKXaVjhVmgoy5Eg_mWFHENvQaaMQBReljpUKrFEMHGlySyPxK-iFXETg8D0A0u5vtYF1snp70nBGje00_RTG5lPgawd-grxdXJ_lW07RkRRdn6WNptjU-6L_rzmeZvCmhMugnZbqX6qNIzhz6YPFaqSO09fNUDxAYAz2MvzYvx79ARqGfULR3lz9v1VbwoMw=w712-h949-no

The highlight of the day was still to come though. After a quick hike at the Golden Gate bridge, we stepped aboard a yacht, and toured for hours under the Golden Gate Bridge.

PljpGuIpqK6UkqoqCtTGTY4aalOiE0ggS25JM69F6MGt_FBkwLRZ_zN9YpMpDwFqMLYc-r72921zHWOMZxStMz6QpnxuzNfcTkfo3ngwOfCkeyayqkGnEOFzMzFquLh0jbAOioCAVQ-63nzRrlHD4VorJUoHWhzcYzTKWKOD2LYBrFWT0kF_-GU-5PGjCZ7pklLtHmAkoZT-SyOKkEVcURTxPOoSFIoQZ2-4IOv0DhImGLJT3KXOwqD2Sbhddxzmkx_KKJqNmUBPjnwBPfHaAxOqVWk394OxKWuPLePlgkhqxbNA7r2myFQLRIMAgKL3Q0oWOReyKn2Xy0h3Z_9Y86PVfCyGRm_zM1_ROpd3UJx9YJ4X9tUcqHSWP6mtVihnlvZ1yyu24r3FFwXoaFM1dr2SrjsDgVk5yXWALz-nZ-NyJ3vQhU0KtH49rjzgQ_sGtxY0NgVvVFBdhM1rTMvS-as_VJ51LJkoLyuMNNI-uaseSDlpYrWPXBuXVzp2EkcafMhiRKeN-axE65gViJTME8oMGci6vdcJvVAjGPPy6cK2eSpXDW0JNomca-GMCacN3dMORSFBluSDOzJ-pL1JMU62ZP0zxpVi-vJ8mq8Qjv0Oo97D-rnvtWyoUNwhMO4xmz9lZFYolr8xSIHu_pmhT20hpXC8Yi2p6nY1eZCGow=w1269-h949-no

Wednesday
Wednesday was the shortest day because some people were flying out in the afternoon, so our day’s activities ended at 4:00. In the morning, we walked from our hotel to the Google offices in San Francisco. We were treated with Breakfast at the Cafeteria, where we had fresh cooked omletes, smoothies, all you can eat bacon just to name a few. Stephanie had to have her obligatory yet inspiring talk about GSoC, then we went right into more Googler talks, featuring Kubernetes and design tecniques along with others. At this point, we were almost done with the formal activites of the trip, but there was one more important thing to do: get more free stuff!!! In the last hour, we were given at least 4 more T-shirts, a Google Cardboard, a Pixel C tablet, an Android doll [factcheck], and another copy of our nametag (because why not).

After, just because we had all left Google at that point, doesn’t mean the activities stopped. Personally, I stayed up until about 11:45 with other winners playing around with the Cardboards, the Pixel Cs, and creating our own wonderful VR experience. (aunali1.com/cardboard)


Thursday
The formal activities are done. People are leaving. Everyone is sad. Each winner’s story will be a bit different on Thursday; some toured colleges like Stanford. Before flying out, my father and I went to the exploratorium, which was a museum but so much better. For those who haven’t been, it’s like a museum, but everything is interactive, letting you figure out what is going on instead of spoonfeeding you on how it works.


Conclusion
So, was the GCI a blast? Hell yeah. Was the trip a blast? Hell yeah. Would I do it again? Actually, no. Surprised? Let me explain. The GCI isn’t designed for who I am now. The GCI has succeeded for me. I am part of the open source community. It is now my responsibility to bring more new faces into open source.

If you are a software developer who likes IDEs, please help to shape a new feature that is currently worked on for KDevelop, your attractive cross-platform IDE for currently C, C++, Python, JavaScript and PHP:

support for management of multiple author identities (name, email, …)

Please help by telling your user stories around data about your author identity in your development process. Add the things you would like to see supported (soon or one day) here:
https://community.kde.org/KDevelop/AuthorIdentities#User_stories

Other contributions to that page are welcome, too. It is a wiki ��
(If a wiki scares you, replying in the comments to this blog post is also fine, everything will be picked up.)

To give you an idea what kind of things are wanted, read on:

Some initial user stories

Do not get in the way:

As developer working alone on a private project, I do not want to have to deal with any identity stuff, any defaults are fine with me.

Multiple identities in same system:

As developer working with the same computer/system on different projects for different customers or different project groups, I want KDevelop to always inject the correct/matching copyright & author information on generating code from file & app templates for different projects/customers, instead of having to manually post-edit the generated code.

Multiple identities in same project:

As developer working on the same project with the same computer system both for job and privately, I want to quickly switch identity data to be used depending on whether I work for job or privately, to mark copyright of contributions accordingly.

Pick up identity on import:

As developer importing a project into KDevelop, I want to have the identity automatically derived from account/server/fetched project and have the option to create a new identity from the found data if there is none, or overwrite with an existing identity.

Highlight my contributions in VCS history:

As developer working on a project with VCS support, I want my easily see my own commits in the vcs history, e.g. by being highlighted.

Update existing identity data:

As developer working on a project, I want to have assistance when identity properties had been changed (like email address or name) and this should be reflected in all existing copyright/contributor notions of a project, where possible.

Following some more background info why work has been started on this feature:

Problem

When it comes to copyright notions in code/files and authorship/committer id in version control systems, the name and the contact information, like email address, can be a few different ones for oneself. E.g. when working in different FLOSS projects, with each email address dedicated to the project, or when working on a FLOSS project both in name of an employer, but also privately in free times.

Currently KDevelop is hard-coded to use whatever is set for the default profile of KEMailSettings when generating new code from file templates, the only place right now using authorship metadata. KMail, the well-known email client, seems to be feeding KEMailSettings via the KIdentityManagement module, but otherwise there might be no data in there. So the developer has to manually complete the fields in the generated code.

The integration of KDevelop with git also ignores the author and commiter metadata used by git for the repo. They need to be set manually and are nowhere linked to what KDevelop knows.

For a truely integrated development experience this needs to be improved.

Solution

KDevelop could know about the concept of author identity, could allow to have multiple identities available to select from for a project, and could allow plugins to make use of identity details e.g. on doing VCS commits or generating code.

Here a screenshot of some proof-of-concept code:
Draft of KDevelop settings: Configure Author Identitites

So, what do you also think in general? Anything related which is worth looking
into for this? Other comments?


January 07, 2017

If you can’t synchronize a folder in KMail and you are seeing “Multiple Merge Candidates” error after the synchronization fails, here’s a how to fix the folder to make it synchronize again – basically you force KMail to forget and re-sync the folder again.

 

  1. Open Akonadi Console.
  2. Go to the Browser tab.
  3. Right-click the broken folder and select “Clear Akonadi Cache” – this will remove all emails from the folder in Akonadi. This will NOT delete your emails on the server.
  4. Akonadi Console will freeze for a while, wait until it unfreezes (sorry, it’s just a developer tool, we don’t have a very good UX there :-)).
  5. Logout and login to make sure all PIM components are restarted.

 

After login start KMail (or Kontact) and hit “Check mail“. KMail will now re-download all emails from the previously broken folder. This may take a while depending on how large the folder is and how fast your internet connection is. After that the synchronization should work as expected.

 

In the upcoming KDE Applications 16.12.1 release Akonadi will have a fix that fixes the reason why the “Multiple Merge Candidates” error occurs, so hopefully in the future you should not see this error anymore.

My blog has been syndicated on Planet KDE and Planet Ubuntu for a long time, but sometimes topics I want to write about are not really relevant to these aggregators, so I either refrain from writing, or write anyway and end up feeling a bit guilty for spamming.

I decided to make some changes to fix that. I got my blog removed from Planet Ubuntu since I am no longer an Ubuntu member. I then pointed Planet KDE aggregator to a specific feed so that I can decide which posts end up on there. This will ensure Planet KDE receives mostly Qt or KDE related posts from me, even if I still sneak in a random post from time to time.

I plan to write on more diverse topics now that I know I won't be pushing off-topic content to Planet KDE anymore. If you want to get all my posts, subscribe to the full feed or follow me on Twitter.

January 05, 2017


This announcement is also available in Spanish and Taiwanese Mandarin.

The latest updates for KDE's Plasma and Applications series are now available to all Chakra users, together with other important package upgrades.

Plasma 5.8.5 provides another round of bugfixes and translation to the 5.8 release, with changes found mostly in the plasma-desktop, plasma-workspace and kscreen packages.

Applications 16.12.0 is the first release of a new series and comes with several changes. kdelibs has been updated to 4.14.27.

1. New features have been introduced in many packages:

  • marble ships with a live day/night Plasma wallpaper of earth and a new widget.
  • kcharselect can now show emoticons and allows you to bookmark your favorite characters.
  • cantor gained support for julia.
  • ark gained support for file and folder renaming, as well as copying and moving packages inside the archive. You can now choose compression and encryption algorithms when creating archives and also open AR files, e.g. Linux *.a static libraries.
  • kopete can use X-OAUTH2 SASL authentication with the jabber protocol and the OTR encryption plugin received some fixes.
  • kdenlive has a new Rotoscoping effect, support for downloadable content and an updated Motion Tracker.
  • kmail and akregator implement Google Safe Browsing to check for malicious links and can now print documents.

    2. The following packages have now been ported to KDE Frameworks 5, with new features introduced in many cases:

  • audiocd-kio
  • kalzium
  • kdegraphics-mobipocket
  • kdialog
  • keditbookmarks
  • kfind
  • kgpg
  • konqueror
  • kqtquickcharts
  • ktouch
  • libkcddb
  • libkcompactdisc
  • okular
  • svgpart

    3. kdepim further split into new packages: akonadi-calendar-tools, akonadi-import-wizard, grantlee-editor, kmail-account-wizard, mbox-importer, pim-data-exporter, pim-sieve-editor, pim-storage-service-manager
    If you want to install the whole kdepim group you can use:
    sudo pacman -S kdepim


    4. The following packages are no longer supported by KDE and have been dropped from our repositories. You should remove them from your system manually if you do not use them but happen to have them installed:
  • kdepim-common. In case this conflicts with another package (like kmail-account-wizard), it is safe to manually remove it with
    sudo pacman -Rdd kdepim-common

  • kdepim-console
  • kde-baseapps-kdepasswd
  • kdgantt2
  • gpgmepp
  • kuser

    In addition, the following notable packages have been updated:

    [core]

  • qt5 group 5.7.1
  • mesa 13.0.2
  • llvm 3.9.1
  • gpgme 1.8.0
  • gnupg 2.1.17

    [desktop]

  • kdelibs 4.14.27
  • qtcreator 4.2.0

    [lib32]

  • winetricks 20161228

    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.
  • My first contact with technology, and I mean the first time that I touched a computer, was when I was eleven years old. My mom subscribed me in an initial course about informatics in a public institute at my hometown. And since then I made all courses about technology that I could put my hands on. When I was in High School and my school bought a laptop so we could do presentations, was me that removed the thousand of the virus and solved the issues, so the laptop could be useful. So it makes sense go to college in the tech area.

    In 2011 I moved out from my hometown so I could start college. Computer Science was my choice. And my thinking until beginning of 2015 was: I will go to college, will finish, maybe do a master’s degree and then get a job.

    future-arrow

    Well, that plan didn’t work out. I was thinking that my career would only begin after I finish college, however, the way that technology is evolving, we can’t wait for after college.

    careerconfusion1-e1417093044460

    When 2015 started, I was planning one more year of college, but then I decided to go to one of the biggest events related to the technology of Brasil. When I got back home, I realized that I couldn’t wait. I need it to go to more events, do networking, meet people with the same interests or different. I need it to learn more that I was learning in the 4 walls of my classroom.

    And was with that work, were at the end of 2016 I could say: I have a career.  And I can’t say when it started. I only know that I have one.

    I don’t know if you can say: Was on this day, several years ago that my career started.

    I can’t.

    The moment that I started to realize that I had a career, was when I was at The Developers Conference in October of last year. For the first time, I was playing with my Arduino and a strip of led. On that moment, that I put the leds on with a code that I made on Arduino IDE. That moment, of full happiness, could not happen if I stayed at my home… I was able to do that because of all background that I built.

    img_20161007_112219

    When I realized that, my view of my life and future changed radically. I wasn’t a person that planned the future. I used to live the moment(Still do sometimes). I couldn’t plan more than the lunch of the next day. Maybe I have matured. Maybe now with my 24 years old I have more experience of life.

    I just know that I think that I’m on the correct path. I’m discovering my values, my weakness, and my strengths while trying to build a strong career. Without leaving my personal life behind.

    Don’t get worried when you career will start, just make sure when you have one, that you are doing the best to build the best career that you want for yourself.

     

    “We’re all stories in the end just make it a good one”

    Eleventh Doctor.

     

     


    Plasma 5.8.5 brings bug-fixes and translations from the month of December, thanks to the hard work of the Plasma team and the KDE Translation team.

    To update, use the Software Repository Guide to add the following repository to your software sources list:

    ppa:kubuntu-ppa/backports

    Instructions on how to manage PPAs and more info about the Kubuntu PPAs can be found in the Repositories Documentation

    January 03, 2017

    Cutelyst the C++/Qt web framework has a new release.

    • Test coverage got some additions to avoid breaks in future.
    • Responses without content-length (chunked or close) are now handled properly.
    • StatusMessage plugin got new methods easier to use and has the first deprecated API too.
    • Engine class now has a struct with the request subclass should create, benchmarks showed this as a micro optimization but I’ve heard function with many arguments (as it was before) are bad on ARM so I guess this is the first optimization for ARM ��
    • Chained dispatcher finally got a performance improvement, I didn’t benchmark it but it should be much faster now.
    • Increased the usage of lambdas when the called function was small/simple, for some reason they reduce the library size so I guess it’s a good thing…
    • Sql helper classes can now use QThread::objectName() which has the worker thread id as it’s name so writing thread safe code is easier.
    • WSGI got static-map and static-map2 options both work the same way as in uWSGI allowing you to serve static files without the need of uWSGI or a webserver.
    • WSGI got both auto-reload and touch-reload implemented, which help a lot on the development process.
    • Request::addressString() was added to make it easier to get the string representation of the client IP also removing the IPv6 prefix if IPv4 conversion succeeds.
    • Grantlee::View now exposes the Grantlee::Engine pointer so one can add filters to it (usefull for i18n)
    • Context got a locale() method to help dealing with translations
    • Cutelyst::Core got ~25k smaller
    • Some other small bug fixes and optimizations….

    For 1.3.0 I hope WSGI module can deal with FastCGI and/or uwsgi protocols, as well as helper methods to deal with i18n. But a CMlyst release might come first ��

    Enjoy https://github.com/cutelyst/cutelyst/archive/r1.2.0.tar.gz


    There is a documentary in the making about the hacker culture surrounding the Chaos Computer Club in Germany. The creators would like to make that movie without institutional funding to be free of any limitations imposed on by said institutions.

    I helped funding the project several months ago and would like to see it succeed in releasing everything under Creative Commons. So if you like the basic idea, read more about it on the project’s website and rob your piggy bank. :)

    Could you tell us something about yourself?

    My name is Ismael. I’m a self-taught artist from Tunisia, but I now live and study in Germany.

    Do you paint professionally, as a hobby artist, or both?

    I’m now painting only as a hobby, it’s a really fun and stress relieving activity. But I might do some freelancing work in the future.

    What genre(s) do you work in?

    I usually paint portraits and manga-styled characters, but I paint other stuff as well. I always try to expand my horizon and learn new things.

    Whose work inspires you most — who are your role models as an artist?

    Well, there is a long list of artists who inspired me. For example: Kuvshinov-Ilya and Laovaan Kite, I really like their style and their work always looks great. David Revoy is also one of my favorite artists, I really like his art and his web comic.

    How and when did you get to try digital painting for the first time?

    I actually only started last summer (2016). Before that, I mainly drew pencil portraits, which was limiting in nature. After seeing some amazing digital paintings on the internet, I wanted to be able to draw like that, and so it was decided. I bought a Wacom intuos art and tried it. It needed some getting used to, but I eventually fell in love with the infinite range of possibilities digital painting offers.

    What makes you choose digital over traditional painting?

    Well, I still paint traditionally from time to time. But I like digital painting more now, since it offers more tools which help me achieve good results with minimal effort. I also love the Ctrl+z shortcut (I wish real life had that!) so I’m not worried about ruining my work, and I can make more daring decisions which allow me to express myself more freely.

    How did you find out about Krita?

    I actually learned about form Blender forums, some users there recommended it over Gimp as a painting program, so I tried it and fell in love with it.

    What was your first impression?

    I was amazed by the sheer amount of features it offered, and the user interface looked good (I like dark-themed programs). For free software it was great, it even has features Photoshop doesn’t have. So in general, I had a positive first impression.

    What do you love about Krita?

    I really love the various brushes and the way they’re rendered, they felt so organic, and like real brushes. I also like the non-destructive filters and transformations, that is pretty rare in free software, and it really encourages you to try new and different stuff, and if you don’t like it, you can change it later (more freedom with minimal consequences).

    What do you think needs improvement in Krita? Is there anything that really annoys you?

    There are some features I want to see in Krita, for example: a small preview window: it’s essential to get a feeling of the painting in general, otherwise it might turn out weird. I also wish Krita could import more brushes from other programs. But nothing is really that bothersome about Krita, there are some bugs, but they are constantly being fixed by the awesome devs.

    What sets Krita apart from the other tools that you use?

    Canvas tilting, rulers, transformation and filter layers, and the Multibrush also. Quite neat features.

    If you had to pick one favourite of all your work done in Krita so far, what would it be, and why?

    I think I’d choose the stylized portrait at the top of this interview, which doesn’t have a name (I really suck at naming things). It started as a simple painting exercise, but it ended up looking pretty good, or at least better than my previous works, which is a good sign of improvement. But I hope it doesn’t stay my favorite painting for long. In other words, I hope I’ll be able to put it to shame in the near future.

    What techniques and brushes did you use in it?

    First, I made a rough sketch, then I started laying in some general colors using a large soft brush (deevad 4a airbrush by David Revoy) without caring about the details, only basic colors and a basic idea of how the painting is lit. Then I started going into details using a smaller sized brush (deevad 1f draw brush). I usually paint new details in a separate layer, then merge it down if I’m happy with the results, if not I, I delete the layer and paint a new one. I use the liquify tool a lot to fix the proportions or any anomaly. For the hair I used the brush (deevad 2d flat old) and the hair brush (vb3BE by Vasco Alexander Basque) which I also used for the hat. When the painting is done I use filters to adjust the colors and contrast, I then make a new layer for final and minor tweaks here and there.

    Where can people see more of your work?

    You can find me on DeviantArt (not everything is made using Krita): http://tarchoun.deviantart.com/

    Anything else you’d like to share?

    I just hope that Krita will get even better in the future and more people start using it and appreciating it.

    KDevelop 5.1 Beta 1 released

    We are happy to announce the release of KDevelop 5.1 Beta! Tons of new stuff entered KDevelop 5.1, a bigger blog post show-casing all the features in 5.1 will follow when we release the final version. Here's a brief summary of what's new in this version:

    LLDB support

    We had a great student for GSoC 2016 implementing LLDB support in KDevelop. The end result is that we now have a debugger framework which can be used both for the GDB & LLDB MI communcation. The LLDB plugin teaches KDevelop to talk to the standalone LLDB MI Driver (lldb-mi); so now it's possible to use LLDB as an alternative debugger backend for KDevelop. One interesting thing with LLDB that it's also potentially useful on OS X & Windows for us, especially when the Windows port of LLDB is getting more and more stable.

    Analyzer run mode

    With 5.1, KDevelop got a new menu entry Analyzer which features a set of actions to work with analyzer-like plugins. During the last months, we merged analyzer plugins into kdevelop.git which are now shipped to you out of the box:

    Cppcheck

    Cppcheck is a well-known static analysis tool for C/C++ code. Cppcheck is useful for taking a closer look at your source code checking for common programming faults such as out of bounds accesses, memory leaks, null pointer dereferences, uninitialized variables, etc. pp. With the Cppcheck integration in KDevelop running the cppcheck executable is just one click away. KDevelop will pass the correct parameters to cppcheck including potential include paths and other options.

    KDevelop with Cppcheck integration KDevelop with Cppcheck integration

    Other analyzers in the pipeline: Valgrind, clang-tidy, krazy2

    While the Cppcheck plugin is shipped out of the box, other analyzers are not considered 100% stable yet and still reside in their own repositories. The clang-tidy plugin looks super promising (another static analysis & refactoring tool for C/C++) as it really easy to use from the command-line and thus easy to integrate into our IDE. We plan to import more of those analyzers into kdevelop.git so they'll be part of the kdevelop tarball and are thus available to you without having to install yet another package.

    Improved Python language support

    Python language support now supports Python 3.6 syntax and semantics. In addition, thanks to the work of Francis Herne, various long-standing issues in the semantic analysis engine have been fixed:  most notably: loops and comprehensions infer types correctly in many more cases; type guessing works for arguments named by keywords (not only **kwargs), and works better for class/staticmethods; types are inferred correctly from PEP-448 syntax in container literals; unsure types are handled in subscripts and tuple unpacking, and uses are found for __call__() and __get/setitem__(). All these improvements were accompanied by cleaning up dusty code, making future changes simpler as well. Furthermore our style checker integration has been rewritten, making it much faster and easier to configure.

    These changes also mean that this beta is especially important for Python support, because we want to catch any potential regressions before the final 5.1 release. Please let us know about everything you notice!

    Perforce integration

    Thanks to Morten Danielsen Volden we now have Perforce integration in kdevplatform.git, which can be used freely starting with KDevelop 5.1. Perforce is a commercial, proprietary revision control system. The Perforce integration in KDevelop simply works by running a local version of the p4 executable (needs to be installed independently of KDevelop) with appropriate parameters. This is similar to how KDevelop integrates with other VCS, such as Git & Bazaar.

    Ongoing support for other platforms

    We're continuously improving the Windows version of KDevelop and we're planning to release a first KDevelop version for OS X soon. For the Windows version, we upgraded the KF5 version to 5.29 and the LLVM/Clang version to 3.9.1.

    Get it

    Together with the source code, we again provide a prebuilt one-file-executable for 64-bit Linux, as well as binary installers for 32- and 64-bit Microsoft Windows. You can find them on our download page in the Experimental Releases section.

    The 5.0.80 source code and signatures can be downloaded from here.

    Please give this version a try and as always let us know about any issues you find via our bug tracker.

    kfunk Tue, 01/03/2017 - 11:00
    Category

    Comments

    January 02, 2017

    Today, KDE announces the beta release of Kirigami UI 2.0.

    Soon after the initial release of Kirigami UI, KDE's framework for convergent (mobile and desktop) user interfaces, its main developer Marco Martin started porting it from Qt Quick Controls 1 to Qt Quick Controls 2, the next generation of Qt's ready-made standard controls for Qt Quick-based user interfaces. Since QQC 2 offers a much more extended range of controls than QQC 1, the port allowed the reduction of Kirigami's own code, while improving stability and performance. Kirigami 2 is kept as close to QQC 2's API as possible in order to extend it seamlessly.

    Beyond the improvements that the port to QQC2 brings, further work went into Kirigami 2's performance and efficiency, and it also offers significantly improved keyboard navigation for desktop applications. On Android, Kirigami 2 integrates better visually with Material Design.

    Of course there are also smaller improvements in various places, such as better handling of edge swipes in the SwipeListItem or more reliable activation of the Overscroll / Reachability mode (which pulls down the top of the page to the center of the screen where it can be reached with the thumb).

    Discover (Plasma's software center), a quite complex application, has already been ported successfully to Kirigami 2 without much hassle, so we are confident that most applications can be ported easily from Kirigami 1 to Kirigami 2. Since Kirigami 2 requires Qt 5.7, which is not available on all Linux distributions yet, Kirigami 1 is still maintained (receiving fixes for critical bugs) for the time being, but won't receive any new features or improvements.

    Although Kirigami 2 has of course been tested internally, this beta release allows us to make sure that the final release contains no bugs which only surface under circumstances we haven't thought of. Therefore we're happy for developers who would like to try out Kirigami 2 beta in their application and report issues they might encounter through one of our various communication channels. You can find those channels, as well as the link to the source tarball, on Kirigami's Techbase page.

    January 01, 2017

    So, 2016 has been a great year to me. Interesting in many aspects, but most has turned out to be for the better. I’ve gotten to know a bunch of awesome new people, I spoken about open source, Qt and Linux in Europe and USA, I’ve helped hosting an open source conference in Gothenburg, I’ve learned so much more professionally and as a person, and I’ve really enjoyed myself the whole time.

    2016 was the year that…

    • … myself and Jürgen where Qt Champions for our work with the qmlbook. It feels really great getting recognition for this work. I really want to take QML Book further – during 2016 both myself and Jürgen have been too busy to do a good job improving and extending the text.
    • … I had to opportunity to visit the Americas (Oregon and California) for the first time in my life. Felt really nice having been on another continent. Now it is only Africa and Australia left on the list :-)

    • … I picked up running and has run every week throughout the year, averaging almost 10km per week. This is the first year since we built out house and had kids (so 11 or 12 years) that I’ve maintained a training regime over a full year.
    • foss-gbg went from a small user group of 15-30 people meeting every month to something much larger. On May 26 the first foss-north took place. This is something some friends of mine and myself have discussed for years and when we finally dared to try it was a great success. We filled the venue with 110 guests and ten speakers and had a great day in the sunshine. In the events after foss-north, the local group, foss-gbg has attracted 40-60 people per meeting, so double the crowd.

    • Pelagicore, the start-up I joined in 2010 when we were only 6 employees, was acquired by Luxoft. We had grown to 50+ employees in the mean time and put Qt, Linux and open source on the automotive map. It has been a great journey and I feel that we being a part of something bigger lets us reach even further, so I’m really excited about this.

    2017 will be the year that…

    • … I make more time for writing – on qmlbook, this blog and more.
    • … I improve my running and increase my average distance per run as well as distance per week.
    • foss-north will take place again. This time with double the audience and dual tracks for parts of the day. I will share more information as it develops. This time, the date to aim for is April 26. In the mean time, foss-gbg will have fewer, but larger, meetings.
    • … Qt, Linux and open source becomes the natural choice in automotive. I will do my best to help this turn out true!

    Even as 2016 has been really good, I hope that 2017 will be even greater. I’m really looking forward to learning!

    Dear users,

    in my last post I’ll present two new icon themes La Capitaine and Papirus icon they are really sexy and work very well with Plasma and KDE Applications. As this two icon set’s are sort of monochrome icon set’s I’d like to resent you an non monochrome icon set like oxygen.

    I’ll port the elementary icon set to KDE, as the elementary developers focus on there platform, I’ll make my first git repository where all the kde specific changes were done.

    elementary-kde

    Have fun with elementary-kde icons, you can grab them from the store.kde.org.

    Next step: make plasma themes and look & feel packages for all the shiny icon set’s.


    December 31, 2016

    With 2017 starting, we’re getting ready for the next Plasma 5.9 release and with it a new Discover release.

    This will be a special release for two main reasons: further add-ons integration and Kirigami.

    New Stuff

    One thing pending for a long time was to actually better integrate the different parts of the system that can be integrated. To do so, Discover now will automatically import all knsrc files present on the system and offer them as categories.
    We’ll be able to go beyond Plasmoids and Comics (!) and make it possible to explore: Plasma Look and Feel themes, cursors, icon themes, window manager add-ons and different application-specific resources.

    This won’t have a big impact on Discover’s performance because the backend code was refactored to be able to have several backends loaded even without knowing all of the resources available. Queries are now asynchronous and parallel.

    Discover KNS Addons

    Kirigami

    Kirigami was adopted in the previous release already, and this release will use Kirigami 2, the port to which did not require much work.

    The most significant improvement is the inclusion of keyboard navigation, which was requested by several people and is now finally available. Do you hate it when you’re required to use the mouse? Rejoice!

    Extra: Snappy support

    It’s 2017, not all of the applications are coming from your distribution anymore. To start getting things in place for different software distribution sources I started working on a Snap backend, which allows us to manage applications coming from this system.
    Some work will still be required and it won’t be included by default, since it doesn’t yet support AppStream (although we discussed it and it seems it will happen soon), but if you’re curious feel free to take a look and give your feedback!


    Older blog entries


    Planet KDE is made from the blogs of KDE's contributors. The opinions it contains are those of the contributor. This site is powered by Rawdog and Rawdog RSS. Feed readers can read Planet KDE with RSS, FOAF or OPML.