[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: I don't like "Python plugins"
From:       Dominik Haumann <dhaumann () kde ! org>
Date:       2013-06-12 18:40:56
Message-ID: 6099758.mQx2Amo6Tt () eriador
[Download RAW message or body]

On Tuesday, 11. June 2013 20:59:44 Shaheed Haque wrote:
> Arrgggllll: Of course I meant 4.12, not 4.11

Strictly speaking, there is no KDE 4.12:
http://aseigo.blogspot.de/2013/05/plasma-workspaces-411-long-term-release.html

It's not yet clear what this means for Kate Part. Maybe it's simply taken from 
the 4.11 branch in the kate git repository for the next years (once it's 
tagged).

For the Kate application this might not be that influencing, since the freeze 
mostly holds for the desktop + libraries. So I can think of a new applications 
release, but it's still going to be KDE SC 4.11.

I think this will also be discussed in Bilbao at the KDE conference next 
months. Still, for now we even have quite a tough freeze until 4.11 is 
branched in git.

So the future development cycle is a bit unclear.

Greetings,
Dominik

> On 11 June 2013 20:51, Shaheed Haque <srhaque@theiet.org> wrote:
> > A bunch of interesting things have been brought up on this thread, but it
> > seems to me that one key issue is the plugin name/description translation
> > problem as that is currently just plain broken. I suggest we start there
> > as
> > follows:
> > 
> > 1. Adopt the idea of using a .desktop file to facilitate the translation.
> > So each Pate plugin get's a .desktop file.
> > 
> > 2. We cannot use KTrader to find the plugins because it simply does not
> > support the functionality I think we agree is needed (
> > http://lists.kde.org/?l=kwrite-devel&m=136986686616467&w=2). However, by
> > using KService in combination with the current "search path" logic, I
> > think
> > we can get what we need from the .desktop file.
> > 
> > I would like to get this "in" for 4.11. Now, this won't address the ideas
> > about how the plugins are presented in the UI or demand loading Pate
> > itself; and I'm not sure I have a definite proposal in mind for either of
> > those yet. Comments?
> > 
> > On 16 May 2013 11:41, Philipp A. <flying-sheep@web.de> wrote:
> >> 2013/5/8 Dominik Haumann <dhaumann@kde.org>
> >> 
> >>> Right. It should just be an item in the list, no tree, please. It would
> >>> expose
> >>> information most of the users will never understand, for nothing.
> >> 
> >> There is one important information for me as plugin developer, i.e. where
> >> the plugins come from.
> >> 
> >> Paté plugins can load from multiple directories and i'd like to see where
> >> from.
> >> 
> >> But i think it's sufficient to make that an optional column in the list
> >> view (source directory, default: off)
> >> 
> >> Finally a remark: Currently, all Python plugin are completely hidden
> >> 
> >>> behind
> >>> the Pate-host plugin. And that is a tremendous advantage, since it keeps
> >>> all
> >>> the rest of Kate untouched. This also means you are flexible to change
> >>> API,
> >>> for instance. Once Python support gets more pulled into Kate itself,
> >>> chaning
> >>> this will be much harder in the long run.
> >>> 
> >>> I'd prefer to have all the python plugins listed along with all the
> >>> other
> >>> plugins. However, I'd rather prefer not to rush this, and if needed only
> >>> put
> >>> this very late into KDE 4.11 (e.g. 4.11.8), or even KDE 5.
> >> 
> >> i'm very much in favor of this, too. maybe even a complete rework of the
> >> libkatepate hierarchy (i don't have specific problems, but ATM it seems
> >> to
> >> grow rather organically ;))
> >> 
> >> _______________________________________________
> >> KWrite-Devel mailing list
> >> KWrite-Devel@kde.org
> >> https://mail.kde.org/mailman/listinfo/kwrite-devel
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel

[prev in list] [next in list] [prev in thread] [next in thread]