Howdy folks,

The deadline for KDE Applications 19.08 is fast approaching and we need
release notes! I've created
<a href="https://notes.kde.org/p/applications_19.08_new_features" title="https://notes.kde.org/p/applications_19.08_new_features">https://notes.kde.org/p/applications_19.08_new_features</a> and done a first
pass on populating it with notes, but more are needed.

If your awesome features and bugfixes will land in the Applications
19.08 release, please add it to that document so it can be included in
the release announcement -- ideally before July 29th (sorry for the
short notice on this).

Hi everyone,

in <a href="https://phabricator.kde.org/T11093#192549" title="https://phabricator.kde.org/T11093#192549">https://phabricator.kde.org/T11093#192549</a> (Consistency, one of the goal
proposals for this year) I presented a small overview of different auto
scrolling behaviours across KDE applications.

- Some views already start auto scrolling when you drag something inside them
/near/ the edges, others start when you drag /beyond/ the edges.
- Some views do fast autoscrolling, others slow.
- Some views scroll pixel-wise, others item-wise.
- Some views scroll with 60 fps, others with 33 fps...

Does someone know more about this topic (implementation details,
intentions,...)?

Would i

I am happy to announce that CMake 3.15.0 is now available for download at:
<a href="https://cmake.org/download/" title="https://cmake.org/download/">https://cmake.org/download/</a>

Documentation is available at:
<a href="https://cmake.org/cmake/help/v3.15" title="https://cmake.org/cmake/help/v3.15">https://cmake.org/cmake/help/v3.15</a>

Release notes appear below and are also published at
<a href="https://cmake.org/cmake/help/v3.15/release/3.15.html" title="https://cmake.org/cmake/help/v3.15/release/3.15.html">https://cmake.org/cmake/help/v3.15/release/3.15.html</a>

Some of the more significant changes in CMake 3.15 are:

* The "CMAKE_MSVC_RUNTIME_LIBRARY" variable and
"MSVC_RUNTIME_LIBRARY" target property were introduced to select the
runtime library used by compilers targeting the MSVC ABI.

Make sure you commit anything you want to end up in the 19.08 release to them

We're already past the dependency freeze.

The Freeze and Beta is this Thursday 18 of July.

More interesting dates
August 1, 2019: KDE Applications 19.08 RC (19.07.90) Tagging and Release
August 8, 2019: KDE Applications 19.08 Tagging
August 15, 2019: KDE Applications 19.08 Release

<a href="https://community.kde.org/Schedules/Applications/19.08_Release_Schedule" title="https://community.kde.org/Schedules/Applications/19.08_Release_Schedule">https://community.kde.org/Schedules/Applications/19.08_Release_Schedule</a>

Cheers,
Albert

I am proud to announce the fourth CMake 3.15 release candidate.
<a href="https://cmake.org/download/" title="https://cmake.org/download/">https://cmake.org/download/</a>

Documentation is available at:
<a href="https://cmake.org/cmake/help/v3.15" title="https://cmake.org/cmake/help/v3.15">https://cmake.org/cmake/help/v3.15</a>

Release notes appear below and are also published at
<a href="https://cmake.org/cmake/help/v3.15/release/3.15.html" title="https://cmake.org/cmake/help/v3.15/release/3.15.html">https://cmake.org/cmake/help/v3.15/release/3.15.html</a>

Some of the more significant changes in CMake 3.15 are:

* The "CMAKE_MSVC_RUNTIME_LIBRARY" variable and
"MSVC_RUNTIME_LIBRARY" target property were introduced to select the
runtime library used by compilers targeting the MSVC ABI.

Announcing GammaRay 2.11.0

Highlights of this Release:
=====================
* Drop support for Qt 4 and Qt <= 5.4.
* Drop support for MSVC 2010 and MSVC 2012, as well as GCC < 4.8.
* Add support for more QtNetwork properties.
* Add new network operations monitoring tool.
* Fix inspection of QJson types.
* Add thread affinity check to the problem reporter.
* Add new event monitoring tool.
* Initial forward compatibility with Qt6 build system.
* Improved performance of the Qt Quick 2 inspector and the signal monitor.

The source code can be found on GitHub at: <a href="https://github.com/KDAB/" title="https://github.com/KDAB/">https://github.com/KDAB/</a>

Hi people,

So that you know this is the release schedule the release team agreed on.

<a href="https://community.kde.org/Schedules/Applications/19.08_Release_Schedule" title="https://community.kde.org/Schedules/Applications/19.08_Release_Schedule">https://community.kde.org/Schedules/Applications/19.08_Release_Schedule</a>

Dependency freeze is in *two* weeks and feature free one after that. Get your stuff ready!

Cheers,
Albert

Previously, I have presented my project to you. The current name of my
project is PCYNLITX.

PCYNLITX platform offers completely new programming technology which can be
named as Programmable Meta-Programming System and PCYNLITX platform is just
a particular application of this new programming methodology.

Basically, PCYNLITX is an intelligent integrated development environment (
IDE ) which can produce an application-specific multi-threading library
based on your needs and assists you in multi-thread software development
process. PCYNLITX is not a multi-threading library.

I am a developer for the McCLIM <https://github.com/McCLIM/McCLIM> graphics
toolkit, and I would like it to be able to integrate better with KDE.

Currently, McCLIm has a hardcoded font scale which is problematic when on a
high DPI screen. It's possible for a user to customise it but recomputing
the default fonts, but that's not ideal.

What I'd like to do is to read the KDE "Force Fonts DPI" setting, and use
it to automatically compute the new font sizes. However, it's unclear to me
how this value is propagated to applications.

Hi,

Two weeks ago I tried to contact a former developer of KTimeTracker
[1] to license two files under GPL. I got no response from him since
then, but may be we can assume the license is still GPLv2...

The reasons why it might be OK to just add a GPLv2 license header
without asking:
1. When these "unlicensed" files were committed into KDE SVN
repository in 2009, the root directory for KTimeTracker sources also
contained a COPYING file with GPLv2 terms. This could imply that
anything committed under the directory is automatically licensed under
GPLv2.
2.

08th June 2019. KDE today announces the release of KDE Frameworks 5.59.0.

KDE Frameworks are 79 addon libraries to Qt which provide a wide
variety of commonly needed functionality in mature, peer reviewed and well
tested libraries with friendly licensing terms.

Dear KDE Developers,

I'm Ferencz Kovacs and I'm currently working on LabPlot for GSOC 2019. My
project is here
<https://summerofcode.withgoogle.com/dashboard/project/6436659309051904/overview/>.
I'm trying to use KNewStuff to upload and download some metadata files. For
starters I wanted to try the UploadDialog, however I was faced with a
problem.

I am proud to announce the first CMake 3.15 release candidate.
<a href="https://cmake.org/download/" title="https://cmake.org/download/">https://cmake.org/download/</a>

Documentation is available at:
<a href="https://cmake.org/cmake/help/v3.15" title="https://cmake.org/cmake/help/v3.15">https://cmake.org/cmake/help/v3.15</a>

Release notes appear below and are also published at
<a href="https://cmake.org/cmake/help/v3.15/release/3.15.html" title="https://cmake.org/cmake/help/v3.15/release/3.15.html">https://cmake.org/cmake/help/v3.15/release/3.15.html</a>

Some of the more significant changes in CMake 3.15 are:

* The "CMAKE_MSVC_RUNTIME_LIBRARY" variable and
"MSVC_RUNTIME_LIBRARY" target property were introduced to select the
runtime library used by compilers targeting the MSVC ABI.

Hello everyone,

I am currently trying to produce a flatpak for Smb4K. However, the build
process always fails when the KAuth helper binary is to be installed into the
flatpak folder.

Hi everyone,

can someone explain me how (not) to use Kapidox?

I tried to build Okular class documentation with Kapidox, whether that is
easier than with doxygen.

So I followed the README on <a href="https://cgit.kde.org/kapidox.git/tree/README.md" title="https://cgit.kde.org/kapidox.git/tree/README.md">https://cgit.kde.org/kapidox.git/tree/README.md</a>,
and got a kapidox_generate in ~/kde/kapidox/src/. 'python setup.py install'
and so on.

Then I mkdir-cd-ed to html_kapidox/ in the okular base directory, and called
kapidox_generate with the okular base directory as argument.

I am experiencing my KDE Plasma session not being locked when I
suspend the laptop while closing down the lid. Since it is a serious
security problem, can anybody please tell me how to retrieve useful
Plasma debug messages for kscreenlock related stuff?
Thank you

We are pleased to announce that CMake 3.13.5 is now available for download.

Please use the latest release from our download page:
<a href="https://cmake.org/download/" title="https://cmake.org/download/">https://cmake.org/download/</a>

Thanks for your support!

Brad King (3):
target_link_libraries: Fix static library private deps in other dirs
Help: Add 3.13.5 release notes
CMake 3.13.5

Nils Gladitz (1):
CMake: Fix WiX installer downgrades with versioned binaries

Hi everyone,

Thank you KDE community for giving me the opportunity to participate in
Google Summer of Code 2019, with KDE. I have been selected for the
project "Data Sync for Falkon"
(<a href="https://summerofcode.withgoogle.com/projects/#5177773792952320" title="https://summerofcode.withgoogle.com/projects/#5177773792952320">https://summerofcode.withgoogle.com/projects/#5177773792952320</a> ).

Any tips on how to make the most out of the Community Bonding Period
will be welcome.

Thank You,
Prasenjit Kumar Shaw

Hi folks,

I've been hacking on Spectacle again :-P

I wanted to refactor the platform backends to make it a little bit cleaner
and more stateless, and also factor out invoking the rectangular cropper
from the platform backend - so that it's now invoked by SpectacleCore
rather than the backend. But mostly I did this to clean up the crap I wrote
back in 2015 when I didn't know better.

I'm working on this in the bgupta/platform-backend-refactor branch. I
haven't hooked up the rectangular cropper back yet, but everything else
should work (I've tested the Xcb backend only, not Wayland).

Howdy folks,
I'd like to bring people's attention to the 2019 Usability & Productivity sprint in Valencia, Spain on June 19th - June 26th: <a href="https://community.kde.org/Sprints/Usability_%26_Productivity/2019" title="https://community.kde.org/Sprints/Usability_%26_Productivity/2019">https://community.kde.org/Sprints/Usability_%26_Productivity/2019</a>. We've got a fun and ambitious agenda planned (<a href="https://notes.kde.org/p/usability-productivity-sprint-2019" title="https://notes.kde.org/p/usability-productivity-sprint-2019">https://notes.kde.org/p/usability-productivity-sprint-2019</a>), and there's still room for up to 6 more people at our venue. On that subject, it's being held at the same place and time as the Plasma sprint so participating in both is also a possibility.

Please don't hesitate to let me know if you're interested in attending!

Nate

Hi all. I hope you'll forgive a potentially ignorant question, but I'm curious about something that confuses a lot of people.

I'd love to be able to 'script' KDE applications at runtime.

It *looks* like you can do this at least with the Plasma desktop using Javascript:

<a href="https://userbase.kde.org/KDE_System_Administration/PlasmaDesktopScripting" title="https://userbase.kde.org/KDE_System_Administration/PlasmaDesktopScripting">https://userbase.kde.org/KDE_System_Administration/PlasmaDesktopScripting</a>

Is it possible to do something similar with KDE apps as well?

Thanks for tolerating a newbie question.

-Chris

We have a huge list of playground kde4 repos that are being processed for l10n.

This takes some resources that make no sense since you should really not be developing for KDE4 anymore, and if you really really really need it, it shouldn't be in playground.

So on May 10 i'll make sure scripty doesn't waste CPU on them.

Cheers,
Albert

P.S: Anyone interested in the list <a href="https://ghostbin.com/paste/823jo" title="https://ghostbin.com/paste/823jo">https://ghostbin.com/paste/823jo</a>

We are pleased to announce that CMake 3.14.2 is now available for download.

Please use the latest release from our download page:
<a href="https://cmake.org/download/" title="https://cmake.org/download/">https://cmake.org/download/</a>

Thanks for your support!

Brad King (9):
MSVC: Fix MSVC_TOOLSET_VERSION for VS 2019 v142 toolset
ARMCC: Do not identify ARMClang as ARMCC
IRSL: Fix discovery of VS 2019 v142 toolset redistributables
Tests: Clarify hand-written cases in RunCMake.ParseImplicitIncludeInfo
Tests: Teach RunCMake.ParseImplicitIncludeInfo to m

I'm unsure if this applicant contacted the KDE Edu team in advance, but I
heard nothing from them until seeing this proposal this morning.

The short description of the proposal:

"As a student, I use graphs in almost everything related to my master’s
research. Graph Theory is a great mathematical tool for programmers and
mathematicians, as it facilitates some computational problems resolution
and modelling.

Greetings,

I won't be going into history but right now we have two developer-facing
wikis: TechBase and Community. On paper, the division between the two is
clear: "external" vs "community". In addition to still being in transition,
the distinction doesn't always work well in practice:

- Tutorials and information for external developers (a.k.a.

Hello Everyone,

My name is Disha Devaiya. I am a computer science graduate student at the
University of Lethbridge in Canada. I am here to invite you to participate
in a research study about a tool for creating a recommender that will help
with bug report assignment.

We are looking for 30 experienced software developers, bug triggers or
quality assurance persons to participate in the study. A candidate must
have more than 1 year of experience in software development or bug triaging
or quality assurance. The research survey is open until April 14, 2019.

We are pleased to announce that CMake 3.14.1 is now available for download.

Please use the latest release from our download page:
<a href="https://cmake.org/download/" title="https://cmake.org/download/">https://cmake.org/download/</a>

Thanks for your support!

Brad King (11):
VS: Fix x64 host recognition by x86 cmake process
find_program: Restore leading double slash on Windows network path
Eclipse: Fix extra generator to not crash on interface libraries
ARMCC: Fix identification of ARM compiler when it defines GNU macros
Help: Clarify policy CMP0082

Greetings KDE Community!

I'm Juan Carlos Torres (Jucato on IRC) and I've recently been hired as a
contractor to get the ball rolling on updating our developer documentation.
Over the years, our community has produced an incredible wealth of
knowledge that now needs our attention and love. While the job description
focuses on new contributors, improving the documentation can benefit even
KDE veterans.

I made a cursory survey of what I considered to be four important areas:

1. <a href="https://kde.org/develop" title="https://kde.org/develop">https://kde.org/develop</a> - where most will probably start their search
(if they didn't use Google)
2.

Hi all,

Over the past few weeks we've had a discussion on whether we'd like to
migrate from Phabricator to Gitlab, for handling both our code reviews
as well as internal tasks (user facing bug reports are explicitly out
of context at this time)

Based on the comments the overall consensus seems to be at this stage
to favour switching to Gitlab.

This however is subject to a caveat around multiple task boards, which
would be needed for larger projects to effectively coordinate amongst
the various sub-projects.

As part of the transition we will also arrange for the email interface
to be enable