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

List:       kwrite-devel
Subject:    Re: I don't like "Python plugins"
From:       "Philipp A." <flying-sheep () web ! de>
Date:       2013-05-16 10:41:46
Message-ID: CAN8d9gnu68JFAK5shyB7MA5KAPuHC2ev5tP2=J44oGWovzWZeQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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 ;))

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2013/5/8 Dominik \
Haumann <span dir="ltr">&lt;<a href="mailto:dhaumann@kde.org" \
target="_blank">dhaumann@kde.org</a>&gt;</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>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><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&#39;d prefer to have all the python plugins listed along with all the other<br>
plugins. However, I&#39;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>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>



_______________________________________________
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]