[prev in list] [next in list] [prev in thread] [next in thread]
List: kwrite-devel
Subject: Re: I don't like "Python plugins"
From: Shaheed Haque <srhaque () theiet ! org>
Date: 2013-06-11 19:51:58
Message-ID: CAHAc2jc4H17w5gu25H2=-FGA3tFterbqYm3gh+eiDMwaeh4+-g () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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
>
>
[Attachment #5 (text/html)]
<div dir="ltr">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:<div> \
<br></div><div style>1. Adopt the idea of using a .desktop file to facilitate the \
translation. So each Pate plugin get's a .desktop file.</div><div \
style><br></div><div style>2. We cannot use KTrader to find the plugins because it \
simply does not support the functionality I think we agree is needed (<a \
href="http://lists.kde.org/?l=kwrite-devel&m=136986686616467&w=2">http://lists.kde.org/?l=kwrite-devel&m=136986686616467&w=2</a>). \
However, by using KService in combination with the current "search path" \
logic, I think we can get what we need from the .desktop file.</div> <div \
style><br></div><div style>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?</div> </div><div class="gmail_extra"><br><br><div \
class="gmail_quote">On 16 May 2013 11:41, Philipp A. <span dir="ltr"><<a \
href="mailto:flying-sheep@web.de" target="_blank">flying-sheep@web.de</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"> <div dir="ltr"><div class="gmail_extra"><div \
class="gmail_quote"><div class="im">2013/5/8 Dominik Haumann <span dir="ltr"><<a \
href="mailto:dhaumann@kde.org" \
target="_blank">dhaumann@kde.org</a>></span><br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Right. It should just be an item in the list, no tree, please. It would expose<br>
information most of the users will never understand, for \
nothing.<br></blockquote><div><br></div></div><div>There is one important information \
for me as plugin developer, i.e. where the plugins come from.<br><br></div><div> \
Paté plugins can load from multiple directories and i'd like to see where from.<br> \
<br></div><div>But i think it's sufficient to make that an optional column in the \
list view (source directory, default: off)<br></div><div \
class="im"><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Finally a remark: Currently, all Python plugin are completely hidden behind<br>
the Pate-host plugin. And that is a tremendous advantage, since it keeps all<br>
the rest of Kate untouched. This also means you are flexible to change API,<br>
for instance. Once Python support gets more pulled into Kate itself, chaning<br>
this will be much harder in the long run.<br>
<br>
I'd prefer to have all the python plugins listed along with all the other<br>
plugins. However, I'd rather prefer not to rush this, and if needed only put<br>
this very late into KDE 4.11 (e.g. 4.11.8), or even KDE \
5.<br></blockquote><div><br></div></div><div>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 ;))<br>
</div></div></div></div>
<br>_______________________________________________<br>
KWrite-Devel mailing list<br>
<a href="mailto:KWrite-Devel@kde.org">KWrite-Devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kwrite-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/kwrite-devel</a><br> \
<br></blockquote></div><br></div>
_______________________________________________
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic