During Akademy there was finally enough time to finalize the porting of KTextEditor to KSyntaxHighlighting.

Thanks to the help of Dominik and Volker, the needed extensions to the KSyntaxHighlighting framework were done in no time ;=)

Thanks for that!

The branch for the integration was merged to master yesterday, unit tests look OK and I am using that state now for my normal coding work. Beside minor glitches that should now be corrected, no issues came up until now.

But as with all changes, for sure some regressions slipped in.

If you notice strange behavior of the highlighting in master, please report the issues on bugs.kde.org or on our mailing list (or even better: provide a fix on phabricator).

For sure there are potential further cleanups and now that we have only one implementation of the highlighting infrastructure, we will be able to move forward with extensions of it much easier.

We contacted the QtCreator people, to see if we might be able to share a common implementation, as they have an own one at the moment. Hopefully that works out in a nice way and our KDE syntax-highlighting framework gets an even broader user base!

Starting with the KDE Frameworks 5.50 release we decided to remove the capability in Kate/KTextEditor to download / update syntax highlighting files from the Kate homepage.

The reasons for this are as follows:

1. The KTextEditor framework is released once a month, meaning that users who use latest KDE software usually anyways have the most recent versions. Other users who do not follow the latest development releases (like your mom) are likely not the target audience for downloading highlighting files.
2. There are technical problems with only updating certain highlighting files, since it can lead to an inconsistent state when one highlighting file needs another one that was not updated or does not exist, or also if a highlighting file needs a certain indenter that does not yet exist or contains bugs.
3. We have a nice small cleanup in the UI, since we have now one button less.

Git changes:

• Code: https://cgit.kde.org/ktexteditor.git/commit/?id=705f8e0419c441ecb618d35b70b4373be453a94e
• Documentation: https://cgit.kde.org/kate.git/commit/?id=c07523227d1cd3edd756978a6c48d9857963f705

Contributing new Highlighting Files

By the way, we are always very happy to accept new highlighting files under MIT license. Documentation about how to write a syntax highlighting file can be found in the Kate Handbook. When you are done, please contribute your highlighting file in phabricator for the ‘syntax-highlighting’ framework (click Code Review, then on the very top right “Create Diff”). You can find nice instructions also on the Community wiki.

Hi All,

In this post I intend to inform about the final status of my GSoC project Verifying signatures of pdf files.

Things Completed:

1. Signature Properties Dialog

In this version of dialog I got rid of the icon label. The dialog has three sections displaying information about signature validation status, signer, and document revision.

2. Certificate Viewer

This certificate viewer is similar to that of chromium’s. It contains two pages. The “General” page displays sort of summary and the “Details” page has all details. On bottom it provides a push button to export the certificate. This dialog can only be accessed from signature properties dialog.

‘General’ tab

‘Details’ tab

3. Revision Viewer

This is a dialog similar to print preview dialog but instead of previewing what is about to be printed it loads the data covered by a signature in a read-only KPart. On top it shows a message informing the user about the read-only nature of the view and on bottom it provides a “Save As” button so that the signed version can be saved. This dialog can be accessed from signature properties dialog and signature panel’s context menu.

4. Signature Panel

This is a sidebar widget which presents all signatures in a tree structure. A context menu is available for this widget through which signed version of a document and signature properties can be accessed. Also selecting any top-level item will change document’s viewport to the page where the signature form field is located.

5. Popup

Now when a signed document is opened there will be two notifications. The former will (as usual) inform about the (signature) forms present and the latter will tell user that the opened document is signed. A toggle button will be there in the second message widget to access signature panel.

Things remaining:

Menu actions

Due to making frequent changes to API and other graphical components I wasn’t able to decide on what actions to add and where to put them.

Getting the code

The patches for okular are listed in the phabricator task.

The git branch with all patches applied : gsoc2018_digitalsignature

The patches for poppler : 107055 and 107056

Finally, the following gif sums up my progress.

Thanks for reading :)

Wooo... this is the last day of coding phase of GSoC. I am writing this blog to share my experience and work done in the coding phase. I want to specially thank my mentor David Rosca for his help, suggestions and reviews. This was my first exposure to the KDE community and I am proud that it was great. I really enjoyed the whole program from proposal submission - intermediate evals - then now this final evaluation. Also, I had learned a lot working on my project. Frankly speaking, I didn't knew about i18n and l10n much but with the help of my mentor now I have a quite good understanding of how these works and are implemented. I can truly say this was one of my best summer vacations.

The code will soon be merged with the master branch of falkon. You can see my status report page for more details about the work done during GSoC. Also in the last weeks I have implemented an extensions page for falkon similar to about:addons in firefox. Below is the screenshot of falkon:extensions page. This also enables to remove the extension from local storage. Also, the themes can be viewed and controlled by the theme panel on the same page.

Happy August

Virtlyst – a Web Interface to manage virtual machines build with Cutelyst/Qt/C++ got a new release.

This new release includes a bunch of bug fixes, most importantly probably being the ability to warn user before doing important actions to help avoid doing mistakes.

Most commits came from new contributor René Linder who is also working on a Bootstrap 4 theme and Lukas Steiner created a dockerfile for it. This is especially cool because Virtlyst repository now has 4 authors while Cutelyst which is way older has only 6.

For the next release I’ll also try to add user management (today you have a single admin account, and to add new users that need to be done via SQL) which wasn’t available on the original WebVirtMgr project but is surely the most important lacking feature.

Have Fun! https://github.com/cutelyst/Virtlyst/archive/v1.2.0.tar.gz

Google Summer of Code is finishing and many things have been done on WikiToLearn since previous post. A little recap is needed.

Talking with mentors has been crucial because they told me to focus on finishing CRUD interaction with API backend instead of working on “history mode” viewer.

On the CRUD part, users now have full control of courses and chapters, they can:

• Edit courses title
• Add new empty chapters to a course
• Reorder course chapters
• Edit chapters title
• Add new empty page to a chapter
• Reorder chapters pages
• [WIP] Write content of a page

Chapter editor have the same UI of course’s one because you can do similar actions in both of them. Here you can see a real web app screenshot of it

Chapter editor user interface

Now there is some important work to do: let users write organized content in a useful and easy manner.
They need an editor that lets them insert:

• Math formulas (with real-time compiling and rendering)
• Theorems and demonstrations
• Images

For these tasks we make use of CKEditor (now at the 5th version, compatible with our build system), we have to create/use existing plugins to let users write beautiful content ready to be read.

The difficult part is that this information needs to be structured to be easily saved and reused. I read most of CKEditor docs and I integrated it in our webapp, I prepared a local repo for it because we need to plugin some custom modules for make it working with math, images and with our data structure and we have to lock-down some features we don’t use. It is a bit difficult to know which part has to be touched in order to make it working but I am on the way because I understood CKEditor fundamentals by reading the docs.

The work on WikiToLearn webapp will continue even after the end of GSoC, I’ll let you know how it goes.

L'articolo What’s next for WikiToLearn? sembra essere il primo su Blogs from WikiToLearn.

So, my plans was always finish the full KDE1 port, and now on Akademy i have some time to get back to this pet project. Starting on Qt1 porting entirely to CMake because the experience on Qt2 was so good that i decided going back to that and do some of the same love on Qt1.

KDE 1 for that new port next. For now, i’m working on github, so https://github.com/heliocastro/qt1

And guess what, on Akademy you can get all possible surprises

Thanks to our kdesrc-build hero Michael Pyne, there’s *just* Qt 1 running on Windows 10 with WSL.

All credits on this picture to mpyne

For this phase, I started with implementing Stamps feature in the Drawing activity. This feature allows users to use different stamps images in their beautiful arts. For now, I have added images from solar activity to use as stamps.

Users can also import an image to use as a stamp. Size and opacity of the stamp can also be adjusted from tool options menu.

I also added added sounds and audio effects, which includes feedback on selecting a tool and using stamps and for other notifications.

Implementation of basic keyboard navigations like undo, redo, save, load, etc. is also completed.

Added a help section, which describes the basic key board shortcuts and other useful information.

All basic tools are implemented as planned, at present I am testing drawing activity on various platforms and fixing various bugs reported by mentors. List of bugs and improvements can be found on — https://phabricator.kde.org/T9138.

Work branch — https://cgit.kde.org/gcompris.git/log/?h=gsoc_asagtani_paint.

Happy coding

This week we’re all at Akademy–KDE’s yearly gathering of developers, designers, system administrators, and users. I’m giving a presentation later today about how we can make KDE Software irresistible!

As such, it as a bit of a lighter week for the Usability & Productivity initiative, what with all the preparation and conference-going, but we still managed to get quite a bit done. And all the in-person interactions are setting the stage for many more good things to come.

Bugfixes

• Disks and volumes formatted with the NTFS filesystem are once again visible in the Places panel (Kai Uwe Broulik, KDE Framewotks 5.50)
• Text in the Timer widget now looks correct after resuming a paused timer (Peter Mühlenpfordt, KDE Plasma 5.14.0)
• When KRunner finds System Settings pages (AKA “KCMs”), adding them to the desktop as shortcuts now works (Kai Uwe Broulik, KDE Plasma 5.12.7)
• When connecting to new password-protected wireless network, the resulting password dialog’s text is no longer cut off in certain circumstances (Ivan Razzhivin, KDE Plasma 5.13.4)
• The lock screen no longer consumes 100% of your CPU’s processing power when using software rendering (David Edmundson, KDE Plasma 5.14.0)
• Fixed a memory leak affecting comboboxes (David Hallas, KDE Frameworks 5.50)
• Fixed a case where Dolphin could hang when browsing files on slow mounts (Kai Uwe Broulik, KDE Frameworks 5.50)
• The volume control on Gwenview’s built-in video player is now always positioned correctly (Peter Mühlenpfordt, KDE Applications 18.08)

UI Polish & Improvement

• Ctrl + 0 is now a global shortcut for “Zoom to actual size” (Peter Mühlenpfordt, KDE Frameworks 5.50)
• When the Properties dialog is used to view an item whose name can’t be changed, the name is displayed as a label rather than non-editable text field (Shubham Jangra, KDE Frameworks 5.50)
• The Configure… button in the Widget Style System Settings page now has an appropriate icon (Kai Uwe Broulik, KDE Plasma 5.12.7)
• The “you can’t name a folder ..” dialog received some polish: it now has a cancel button, the message is worded more naturally, the “choose a different name” button uses a more appropriate icon, and its text is written in Title Case (me: Nate Graham, KDE Frameworks 5.50):
  

Next week, your name could be in this list! Just check out https://community.kde.org/Get_Involved, and find out how you can help be a part of something that really matters.

If my efforts to perform, guide, and document this work seem useful and you’d like to see more of them, then consider becoming a patron on Patreon, LiberaPay, or PayPal. Also consider making a donation to the KDE e.V. foundation.

Pheww..so GSoC 2018 is in its last stretch now with only 3 days remaining!! Coming to the last week, the activity Note_names is finally developed and being tested on different platforms. Principle: This activity aims to teach sight reading the musical notes and their position on the staff by presenting several notes one-by-one with animation …

Continue reading "GSoC 2018: Final week"

If you are interested in community data analytics, you will have several opportunities to discuss them during Akademy.

Firstly, there will be my talk titled Bringing Community Data Analysis Back to KDE (why the hell did I use "Analysis" there... I only used "Analytics" everywhere so far, odd). It will happen on Saturday at 15:30 in room IE7. The slot is a bit small for the topic, but I'll try my best to create interest. Indeed you can catch me around talks to chat about it, and...

Secondly, there will be a BoF "Discussing Community Data Analytics" on Monday at 10:30 in room 127. We hope to see people coming up with interesting questions to explore or willing to lend a hand in those explorations. See you there!

And of course it also means I'm on my way to Vienna, see you all during Akademy 2018!

You probably have seen that Freenode has been getting lots of spam lately.

To protect against that some channels have activated a flag that only allows authenticated users to enter the channel.

If you're using the regular "nickserv" authentication way as I was doing, the authentication happens in parallel to entering the channels and you'll probably be rejected from joining some.

What you want is use SASL, that is a "new IRC" protocol that will first authenticate and then join the server/channels.

More info at https://userbase.kde.org/Konversation/Configuring_SASL_authentication.

Thanks Fuchs on #kde-devel for enlightening me :)

And of course, I'm going to Akademy ;)

Hello Planet,

It has been some time. I come back from the shadows to announce the release of Ring-KDE 3.0.0, A GNU Ring.cx client. GNU Ring is a secure and distributed communication platform based on open standards. It weaves industry standard technologies to work together and provides audio calls, video conferences, chat, screen sharing and peer to peer file transfer between you and your friends. Additionally, its use of open standards allows to bridge to various other systems like the main phone network or SIP compatible devices.

When joining the GNU Ring, no servers or centralized accounts are needed. Beside an optional blockchain-based way to reserve your username against takeover, nothing leaves your device. All your data is kept under your control. Ring-KDE provides a simple wizard to help you create credentials or import your personal information from other devices.

This release is a full rewrite of the application to use more modern technologies such as touch support, QtQuick2 and KDE Kirigami adaptive widget framework. The old Ring-KDE was a fork of an older KDE application called SFLPhone. At the time, it was focused on being a office phone replacement for your KDE desktop instead of being a more generic multimedia communication software.

The screenshots below show the old SFLPhone/Ring-KDE 2.x versus Ring-KDE 3.0.0:

This blog entry wont try to list every single change from the 2.x series because
that’s too much amazement for a single post. A more useful introduction is how to use it.

Ring 2.x and the older SFLPhone versions used mostly the history and address book to select who to call. This made sense for a phone, but the newly expanded scope changes this. While they are both still available, from now on, the user interface is based on the timeline concept:

Version 3.x also has better support for video, screen sharing and file streaming.

Most relevant audio call features have been ported to the new application including multi-call support, hold, recording and notifications:

The basic chat support has been replaced with an integrated timeline that contains all the calls, chat messages, video capture, recordings and eventually file transfer and images.

Navigation has been revamped and is now using a search box as the primary way of finding your friends. It uses locally stored data to avoid uploading too much potentially private information to the cloud. Only looking for registered user names normally uses the internet. It is optionally possible to download this information locally, but it uses more disk, CPU and network resources to keep up-to-date.

In the immediate future, the next few versions will try to fix bug, improve performance and catch up with recent improvements to Kirigami2, KDE own touch-friendly set of widgets and application design guidelines. Since beginning to work on Ring-KDE 3, Kirigami has made great progress, but Ring-KDE 3.0 still mostly reflects the state of the art from a year ago.

Download:

Ring-KDE can be built from source if the ring-daemon is also built from source. The source code for Ring-KDE 3.0.0 can be downloaded here.

For everyone else, Ring-KDE is available as an easy to use AppImage:

https://download.kde.org/stable/ring-kde/3.0.0/ring-kde_3.0.0_x86_64.AppImage

To use the AppImage, download it, right click, choose Properties -> Permissions and check “is executable”, Then open the file. When using the AppImage, no other dependencies are required. If you also have another GNU Ring.cx like the Gnome client, please close it and run “killall dring” before executing the AppImage to avoid conflicts between the two versions.

Hi everyone, The coding period phase three is now completed. After the second evaluation, Poppler’s maintainer Albert Astals Cid commented on my bug report https://bugs.freedesktop.org/show_bug.cgi?id=107151#c3 stating that the current parsing and creation of DA string is handled by Qt5 frontend whereas the API should be changed and the creation and parsing of the DA string and font … →

The post GSoC :: Coding Period – Phase Three (July 8th to August 6th): Create and parse DA string in poppler-core and font family implementation appeared first on Dileep Sankhla.

Before getting started with Poppler, let’s first understand the PDF structure and different terminologies used. Annotations are PDF objects that enable user-clickable actions as well as contents text or other graphics and media. The following is a snippet of FreeText annotation created on a PDF page in Acrobat Reader. It is in the decompressed form: … →

The post FreeText Annotation :: Font family implementation in Poppler appeared first on Dileep Sankhla.

A lovely lunch and a shared afternoon and evening with Ade was a pleasant interlude in our time together here in beautiful Deventer. We changed tables a few times to avoid the sun! Last night we were wakened at around 2am with wind blowing rain into the open windows, which was quite exciting. Thunder roared in the south. It was still quite cool and breezy this morning so we ate inside.

So, After a month-long delay, I finally managed to got my VISA approved, it was a really close call. I reached the VISA agency, today for receiving my application and after opening the application, I saw my visa on my passport! So yes I am coming to Akademy, this will be my first Akademy to attend, I am really excited to meet my mentors and all the people who make KDE awesome :D. Looking forward to attend, all the events, workshop and see the beautiful Vienna city!

Little about me: I was selected for this year’s GSoC project for Fwupd-Integration in Discover Software Center.

Google Summer of Code with KDE

Hey everyone, one more month has passed now, Fwupd-Backend is now finally merged in discover master branch, though it took quite a number of changes. This post will relatively small as in the past month I have worked mainly on fixing the mistakes and improving the code and getting it merged.

#1 Phabricator Merge diff: (https://phabricator.kde.org/D14050 ) This is the phabricator request, for merging the code into the master( commit: a30850900bbf9487f08bd43d988267e2ec034fd0).

#2 CI fail after Merging:  So after the code was merged the build started to fail on the CI system, the main problem behind that was some issue in the findLIBFWUPD.cmake code and the backend dependency was not installed on CI system, For it, I added the request for sys-admins (https://phabricator.kde.org/T9305). Though I violated some community code, the dependency got installed in CI system, thanks to bcooksley, (link: https://phabricator.kde.org/R857:1b0c2d39907a90bf6854fffafdab3d461fe8e69e), also thanks to adridg for pointing out the issue in my License in the cmake file, I fixed that in the (commit: 03aeb5ba2077c344b5de38ec37858a3603b07733) with some other fixes.

It was fun working with the KDE community, special thanks to my mentors Aleix Pol and David Edmundson, for guiding me throughout this summer break very much thanks to people at IRC for entertaining my problems!

It’s not a goodbye, I am currently working on another project for driver management which will use Linux driver management (https://github.com/solus-project/linux-driver-management) libraries to enumerate and discover devices and provide the suitable drivers for their hardware! (https://cgit.kde.org/scratch/abhijeetsharma/kdrivermanagement.git/), currently, the only temporary file structure is added, still, a long way to go!

Disclaimer: The Fwupd-Backend code is not been tested on a real device, may contain issues.

FeedBack Feel free to write comments below!

Thanks

So after a (too long) break, I am going back to Akademy this year! Having been away from KDE work for a while now, this will be the first time I attend the conference as a user. It's going to be interesting to see how this feels. In any case, I am looking forward to the sessions and to catching up with old friends.

I will only be attending the first two days unfortunately, but I will try to make the best of these days to meet as many people as possible.

Now time to go packing, as I am actually landing in Vienna tomorrow to do some sightseeing before the conference. See you there!

As a first KDE application, KStars got localization working on Android. KStars has the traditional gettext translations in the KDE system and these translations had to be downloaded, converted and packaged inside the apk.

The basic steps were to enable localization on Android:

1. Set CMake variable KDE_L10N_AUTO_TRANSLATIONS to ON. This step will automatically download the translations during the build with a custom build target "fetch-translations".
2. Convert the translations from .po extension into .mo format. This step was done with a custom build target in CMake:

IF (ANDROID)
    ADD_CUSTOM_TARGET(convert_translations_to_android ${CMAKE_SOURCE_DIR}/tools/convert_translations.sh ${CMAKE_BINARY_DIR}/android/export/share/kstars
                        WORKING_DIRECTORY ${CMAKE_BINARY_DIR})
    ADD_DEPENDENCIES(convert_translations_to_android fetch-translations)
ENDIF ()