[prev in list] [next in list] [prev in thread] [next in thread]
List: kwrite-devel
Subject: Re: I don't like "Python plugins"
From: Joseph Wenninger <jowenn () kde ! org>
Date: 2013-05-08 14:17:06
Message-ID: 57F0CCB5-2EF8-4A8E-BC02-70894A244C4F () kde ! org
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
+1
But why a tree, wouldn't it better to just merge the lists of the providers? Why does \
a user care, if the plugin is written in C++, Python, JavaScript, ....?
I think, it would be even better if the list could show the python plugins, even if \
PATE is not loaded and load pate on demand. python plugins + desktopfiles and \
automatic dependency resolution
Joseph
Am 08.05.2013 um 15:30 schrieb "Philipp A." <flying-sheep@web.de>:
> i have a more radical idea: get rid of the separate Paté plugin list.
>
> for the end user (as you said) it's not clear that Paté just enables another list \
> of plugins, which makes those plugins unnecessarily hidden. also i as end user \
> wouldn't care where the plugins i enable come from.
> ————
>
> i think we should
> 1. if it's not already done, make the plugin list extensible by allowing adding \
> more plugin providers make the plugin list into a treeview (like the Paté plugin \
> list is) with each provider being a node, and it's plugins being a tree below that. \
> 2. split Paté into such a plugin provider and a plugin that provides Paté's \
> remaining functionality (the documentation tab and the "reload modules" button for \
> Paté plugin developers)
> ————
>
> mockup: http://i.imgur.com/amkeQS6.png
>
>
> 2013/5/8 J. Pablo Martín Cobos <goinnn@gmail.com>
> Hi all,
>
> I don't like the name of the "Python plugins"... With this name I would think that \
> these are plugins for Python, plugins with features to python.... but this is not \
> true. There are features to python, js, c++, xml, etc
> I think that we should change this name and the description, "Pâté host for \
> Python Plugins".
> I think that the name could be: "Python plugin engine", and the description, "If \
> you enable this plugin you will have another list of the plugins write in python".
> do you think about this??
>
> Best regards,
>
> --
>
> Pablo Martín
>
>
>
> _______________________________________________
> 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
[Attachment #5 (unknown)]
<html><head></head><body bgcolor="#FFFFFF"><div>+1</div><div><br></div><div>But why a \
tree, wouldn't it better to just merge the lists of the providers? Why does a user \
care, if the plugin is written in C++, Python, JavaScript, \
....? </div><div><br></div><div>I think, it would be even better if the list \
could show the python plugins, even if PATE is not loaded and load pate on demand. \
python plugins + desktopfiles and automatic dependency \
resolution</div><div><br></div><div>Joseph<br><br>Am 08.05.2013 um 15:30 schrieb \
"Philipp A." <<a href="mailto:flying-sheep@web.de">flying-sheep@web.de</a>>:<br><br></div><div></div><blockquote \
type="cite"><div><div dir="ltr"><div>i have a more radical idea: get rid of the \
separate Paté plugin list.<br><br></div><div></div><div>for the end user (as you \
said) it's not clear that Paté just enables another list of plugins, which makes \
those plugins unnecessarily hidden. also i as end user wouldn't care where the \
plugins i enable come from.<br> <br>————<br><br></div><div>i think we \
should<br></div><div>1. if it's not already done, make the plugin list extensible by \
allowing adding more plugin providers<br></div><div> make the plugin list \
into a treeview (like the Paté plugin list is) with each provider being a node, and \
it's plugins being a tree below that.<br> </div><div>2. split Paté into such a \
plugin provider and a plugin that provides Paté's remaining functionality (the \
documentation tab and the "reload modules" button for Paté plugin \
developers)<br><br>————<br><br></div><div>
mockup: <a href="http://i.imgur.com/amkeQS6.png">http://i.imgur.com/amkeQS6.png</a><br></div></div><div \
class="gmail_extra"><br><br><div class="gmail_quote">2013/5/8 J. Pablo Martín Cobos \
<span dir="ltr"><<a href="mailto:goinnn@gmail.com" \
target="_blank">goinnn@gmail.com</a>></span><br> <blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
dir="ltr">Hi all,<div><br></div><div>I don't like the name of the "Python plugins"... \
With this name I would think that these are plugins for Python, plugins with features \
to python.... but this is not true. There are features to python, js, c++, xml, \
etc<br>
</div><div><br></div><div>I think that we should change this name and the \
description, "Pâté host for Python Plugins". </div><div><br></div><div>I think \
that the name could be: "Python plugin engine", and the description, "If you enable \
this plugin you will have another list of the plugins write in python".</div>
<div><br></div><div>do you think about this??</div><div><br></div><div>Best \
regards,</div><div><br></div><div>--</div><div><br></div><div>Pablo \
Martín</div><div><br></div> <div><br></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> </div></blockquote><blockquote \
type="cite"><div><span>_______________________________________________</span><br><span>KWrite-Devel \
mailing list</span><br><span><a \
href="mailto:KWrite-Devel@kde.org">KWrite-Devel@kde.org</a></span><br><span><a \
href="https://mail.kde.org/mailman/listinfo/kwrite-devel">https://mail.kde.org/mailman/listinfo/kwrite-devel</a></span><br></div></blockquote></body></html>
_______________________________________________
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