Re: remove khelpcenter from next Plasma release?

[R.Harish Navnit]

​Hi,​

On Wed, Mar 9, 2016 at 10:07 PM, Yuri Chornoivan  wrote:
>
>
> But generally, I cannot say that I like the way the things are going. The
UserBase project does not have significant updates on applications pages
(although it was claimed that users are willing to write docs online),
there is a trend to sweep docs under the carpet, move them online, cut off
docs from applications, compile and package without docs, release without
docs at all. That's not pretty and fair.
There was some reorganization of KDE's wikis done, earlier this month.[1]
We were at a sprint and we had just a week and had to target three wikis. I
can assure you, that of the three(community, techbase and userbase),
userbase needed the least tweaking. Largely because, the applications in
KF5 differ mostly in look and feel and fortunately, there hasn't been a
drastic change in the feature set. So a good number of articles over at
userbase still hold valid or can be considered useful, in someway. The same
can't be said of techbase, for instance and it needed(and probably, still
needs) some reworking.

Obviously, I haven't looked at whole of userbase and you might be able to
find cases where I am wrong. But having said that, I agree, that userbase
needs some love, but I don't think bringing that up in this thread is a
good idea. I strongly urge you to create a new thread to discuss this and
let's try to arrive at a solution.

​[1]
http://blogs.churlaud.com/somefoobar/2016/03/17/sprint-at-cern-things-got-done/
​

Thanks,
R.Harish Navnit
The Enigma 

Re: KFileMetaData: External Plugins

[Boudhayan Gupta]

On 28 March 2016 at 00:22, Varun Joshi  wrote:
> Hi,
>
> As a part of my Season of KDE project, I added the ability for
> KFileMetaData to use plugins written in languages other than C++.
> These plugins have dependencies (like the PDF writer plugin depends on
> PyPDF2) that we probably shouldn't add to the core kfilemetadata
> package.
>
> Boudhayan Gupta suggested making a new package 'kfilemetadata-extras'
> to handle all the external plugins and their dependencies. Or maybe we
> could have individual plugins live in individual packages. What is the
> best way forward?

My 2c for an all-in-one extras package, but with a CMake config that
allows building individual plugins too if need be.

Question is, where do we put it? frameworks, or kdesupport, or
somewhere else entirely?

-- Boudhayan

>
> --
> Regards,
> Varun Joshi

KFileMetaData: External Plugins

[Varun Joshi]

Hi,

As a part of my Season of KDE project, I added the ability for
KFileMetaData to use plugins written in languages other than C++.
These plugins have dependencies (like the PDF writer plugin depends on
PyPDF2) that we probably shouldn't add to the core kfilemetadata
package.

Boudhayan Gupta suggested making a new package 'kfilemetadata-extras'
to handle all the external plugins and their dependencies. Or maybe we
could have individual plugins live in individual packages. What is the
best way forward?

-- 
Regards,
Varun Joshi

Re: [Kde-pim] Qt 4 Builds

[Martin Steigerwald]

On Sonntag, 27. März 2016 10:01:09 CEST Thiago Macieira wrote:
> On domingo, 27 de março de 2016 15:31:47 PDT Martin Koller wrote:
> > The latest openSuse (Leap 42.1) ships the Qt4 based kdepim, although it
> > uses plasma5 desktop.
> > 
> > Speaking of it: given that openSuse decided against shipping KF5-based
> > PIM,
> > how stable is KF5-based PIM considered these days ?
> > Is it ready for productive daily professional use ?
> 
> Tumbleweed has already switched to the KF5-based PIM and it's working mostly
> fine. There are some minor issues like requiring the shortcut to go to the
> next unread message in any folder to be pressed multiple times before it
> decides to do its job, but nothing major.

Shortcuts are still completely broken with self-compiled kdepim from git 
master. They have been broken for months already.

I can´t use arrow right in threaded mail list to switch to a mail of the next 
thread for example.

I think if not already done I will file a bug about it. I didn´t yet, cause I 
thought it was just a temporary development hic-up initially.

-- 
Martin