Le 19/05/2014 07:10, Lex Trotman a écrit :
[...]
Just to be clear, libpeas only automates the bridge to the *loader*
and the plugins, it does nothing for the interface between the
Geany/Scintilla functions and the plugins (and neither does Thomas'
proposal).
That binding is independent
On 14-05-21 06:45 AM, Colomban Wendling wrote:
Le 19/05/2014 14:17, Thomas Martitz a écrit :
[...]
Sorry if I sound negative towards libpeas. I'm not fundamentally against
it. I try to objectively evaluate it, and it doesn't appear to be the
holy grail either, especially with our strong focus
On 14-05-18 10:10 PM, Lex Trotman wrote:
[snip]
2. the effort to incorporate it into the existing PM.
I don't think this will be very difficult, even from me who loathes
GtkTreeView :)
IIUC Thomas' proposal would use the existing methods so it doesn't
require any changes in these areas.
On 19 May 2014 19:58, Matthew Brush mbr...@codebrainz.ca wrote:
On 14-05-18 10:10 PM, Lex Trotman wrote:
[snip]
2. the effort to incorporate it into the existing PM.
I don't think this will be very difficult, even from me who loathes
GtkTreeView :)
IIUC Thomas' proposal would use the
Am 19.05.2014 13:13, schrieb Lex Trotman:
On 19 May 2014 19:58, Matthew Brush mbr...@codebrainz.ca wrote:
On 14-05-18 10:10 PM, Lex Trotman wrote:
[snip]
2. the effort to incorporate it into the existing PM.
I don't think this will be very difficult, even from me who loathes
GtkTreeView :)
Am 17.05.2014 03:43, schrieb Matthew Brush:
On 14-05-16 03:03 PM, Thomas Martitz wrote:
I think we want to maintain the ability to add loaders on our own,
With Peas you can, in fact it's designed with this purpose in mind,
unlike the existing C-only loader.
If it's designed for that, why
On 14-05-18 03:07 PM, Thomas Martitz wrote:
Am 17.05.2014 03:43, schrieb Matthew Brush:
On 14-05-16 03:03 PM, Thomas Martitz wrote:
I think we want to maintain the ability to add loaders on our own,
With Peas you can, in fact it's designed with this purpose in mind,
unlike the existing
[...]
After experimenting with this a bit, I believe it doesn't make much sense
to make a compatibility layer because a) you still need basically the same
code as the existing loader code, b) you would have to
change/refactor/re-write lots of it c) you would still have two distinct
ways to
On 14-05-13 01:43 AM, Matthew Brush wrote:
On 14-05-13 12:54 AM, Thomas Martitz wrote:
Am 11.05.2014 20:31, schrieb Dimitar Zhekov:
On Sat, 10 May 2014 21:56:30 +0200
Thomas Martitz ku...@rockbox.org wrote:
[snip]
So why adapt peas when it requires a lot of changes *too* but also
severely
Am 16.05.2014 11:16, schrieb Matthew Brush:
FWIW, I've been doing some experiments with libpeas as the loader in
Geany (in my peas* branches on Github) and for the Python demo plugin
(code not pushed to GH yet) I managed to get GObject-Introspection to
scan Geany's source code/headers. Most
On Fri, 16 May 2014 16:59:17 +0200
Thomas Martitz ku...@rockbox.org wrote:
I have a question regarding libpeas. There doesn't seem to be a public
(nor documented) API to add loaders. From what I can see the current
language support of libpeas is quite poor (only python and seed (that's
JS
Am 16.05.2014 19:32, schrieb Dimitar Zhekov:
On Fri, 16 May 2014 16:59:17 +0200
Thomas Martitz ku...@rockbox.org wrote:
I have a question regarding libpeas. There doesn't seem to be a public
(nor documented) API to add loaders. From what I can see the current
language support of libpeas is
On 14-05-16 03:03 PM, Thomas Martitz wrote:
Am 16.05.2014 19:32, schrieb Dimitar Zhekov:
On Fri, 16 May 2014 16:59:17 +0200
Thomas Martitz ku...@rockbox.org wrote:
I have a question regarding libpeas. There doesn't seem to be a public
(nor documented) API to add loaders. From what I can see
Hi Guys,
Some general observations, irrespective of the implementation.
1. There shall be only one plugin control GUI. The users don't care
how a plugin is implemented, or what language its in, they just want
to use it. Having to look in two places will often mean one group of
plugins is
On 14-05-16 06:43 PM, Matthew Brush wrote:
[snip]
As mentioned above, this doesn't seem worth the trouble and I don't
think it would be as easy/useful as it seems on the surface. We could
just leave the existing loader without breaking anything, it's quite
stable and works pretty well for plain
Note: Sorry for the shalls, I have been reading too many
specifications lately and it has worked its way into my brain.
On 17 May 2014 13:04, Matthew Brush mbr...@codebrainz.ca wrote:
On 14-05-16 07:34 PM, Lex Trotman wrote:
Hi Guys,
Some general observations, irrespective of the
On Tue, 13 May 2014 09:54:09 +0200
Thomas Martitz ku...@rockbox.org wrote:
Am 11.05.2014 20:31, schrieb Dimitar Zhekov:
On Sat, 10 May 2014 21:56:30 +0200
Thomas Martitz ku...@rockbox.org wrote:
On Sat, 10 May 2014 14:47:17 -0700
Matthew Brush mbr...@codebrainz.ca wrote:
+1 for
On Sat, 10 May 2014 21:56:30 +0200
Thomas Martitz ku...@rockbox.org wrote:
On Sat, 10 May 2014 14:47:17 -0700
Matthew Brush mbr...@codebrainz.ca wrote:
+1 for some form of introspection/code generation.
Just to be clear: by introspection, I don't mean *replacing* struct
GeanyDocument with
On Fri, 09 May 2014 22:18:41 +0200
Thomas Martitz ku...@rockbox.org wrote:
Am 08.05.2014 02:33, schrieb Matthew Brush:
Hi Thomas,
Disclaimer: I'm not a LibPeas expert or even user but from what I've
read about it (the docs, tutorials) it sounds like pretty much exactly
the end-goal
On 14-05-10 12:56 PM, Thomas Martitz wrote:
Am 10.05.2014 21:06, schrieb Dimitar Zhekov:
After that I'd say that LibPeas is perhaps something to be considered
for new application but not for our existing codebase. I think we want
something that enables proxy plugins while maintaining API and
On 14-05-10 12:06 PM, Dimitar Zhekov wrote:
[snip]
For python, maybe we can include geanypy/src/*.c in Geany or in
a .so library. But if we don't want to end up with more 150+ KB proxies
like geanypy, we'd better use introspection. I really admire Matthew
and Lex for writing this thing, but
Am 08.05.2014 19:25, schrieb Dimitar Zhekov:
On Wed, 07 May 2014 23:58:11 +0200
Thomas Martitz ku...@rockbox.org wrote:
Am 07.05.2014 19:59, schrieb Dimitar Zhekov:
On Wed, 07 May 2014 08:40:13 +0200
Thomas Martitz ku...@rockbox.org wrote:
I'm (as of now) motivated to implement proxy
On Fri, 09 May 2014 12:29:58 +0200
Thomas Martitz ku...@rockbox.org wrote:
The basic idea is that proxy plugins initially call a Geany API to
register themselves as proxies, providing criterias to select potential
plugins (for now, this is only a list of file extensions)
Geany will match
Like I think Dimitar was saying, adding custom scripts sound like they
should be second class plugins.
Sorry to be a broken record here, but my external tools plugin calls
whatever language you can make an executable for or call from the
command line:
Am 09.05.2014 19:15, schrieb Dimitar Zhekov:
On Fri, 09 May 2014 12:29:58 +0200
Thomas Martitz ku...@rockbox.org wrote:
The basic idea is that proxy plugins initially call a Geany API to
register themselves as proxies, providing criterias to select potential
plugins (for now, this is only a
Am 08.05.2014 02:33, schrieb Matthew Brush:
Hi Thomas,
If the goal is really to enable loading plugins written in other
languages, we should take a really extensive look at LibPeas before
ruling it out and duplicating it ourselves. It seems especially
appropriate since you want to eventually
I sent this email earlier and never saw it come back through the mailing
list, so I'll send it a gain to see if it is going through...
...
Like I think Dimitar was saying, adding custom scripts sound like they
should be second class plugins.
Sorry to be a broken record here, but my external
Am 09.05.2014 23:07, schrieb Steven Blatnick:
I sent this email earlier and never saw it come back through the
mailing list, so I'll send it a gain to see if it is going through...
It came through. As a tip, you can check the mailing list archives[1]
before sending the mail another time
Thanks! That's weird... I still haven't gotten either of the messages
myself. I just checked, and they're not in my spam folder. Does the
list no longer send the the sender? I used to get my own messages.
On 05/09/2014 03:14 PM, Thomas Martitz wrote:
Am 09.05.2014 23:07, schrieb Steven
On 14-05-09 01:18 PM, Thomas Martitz wrote:
Am 08.05.2014 02:33, schrieb Matthew Brush:
Hi Thomas,
If the goal is really to enable loading plugins written in other
languages, we should take a really extensive look at LibPeas before
ruling it out and duplicating it ourselves. It seems
On Wed, 07 May 2014 23:58:11 +0200
Thomas Martitz ku...@rockbox.org wrote:
Am 07.05.2014 19:59, schrieb Dimitar Zhekov:
On Wed, 07 May 2014 08:40:13 +0200
Thomas Martitz ku...@rockbox.org wrote:
I'm (as of now) motivated to implement proxy plugins (to my amusement,
until splitwindow2
Hello,
I'm (as of now) motivated to implement proxy plugins (to my amusement,
until splitwindow2 gets finally reviewed...). Therefore I would like to
receive comments on my proposed concept and APIs (further below).
I would also love to discuss about better terms for proxy and the
proxied
On Wed, 07 May 2014 08:40:13 +0200
Thomas Martitz ku...@rockbox.org wrote:
I'm (as of now) motivated to implement proxy plugins (to my amusement,
until splitwindow2 gets finally reviewed...). Therefore I would like to
receive comments on my proposed concept and APIs (further below).
Am 07.05.2014 19:59, schrieb Dimitar Zhekov:
On Wed, 07 May 2014 08:40:13 +0200
Thomas Martitz ku...@rockbox.org wrote:
I'm (as of now) motivated to implement proxy plugins (to my amusement,
until splitwindow2 gets finally reviewed...). Therefore I would like to
receive comments on my proposed
Hi Thomas,
A somewhat similar method that I had a (very rough) prototype for,
used a .so wrapper for each non-native plugin (I was using python and
used most of geanypy) providing the API wrapper for that language.
There was a language manager plugin for the language which did the
initialising
Sorry for the double post, but Murphys law says I found the code just
*after* posting :) More details below.
On 8 May 2014 13:03, Lex Trotman ele...@gmail.com wrote:
Hi Thomas,
A somewhat similar method that I had a (very rough) prototype for,
used a .so wrapper for each non-native plugin (I
36 matches
Mail list logo
