On 1 May 2011 10:37, Matthew Brush wrote:
> On 04/30/11 17:30, Lex Trotman wrote:
>>
>> On 1 May 2011 09:19, Matthew Brush wrote:
>>>
>>> The documentation, while not perfect, is here:
>>> http://live.gnome.org/Vala/Manual/Attributes
>>
>> That was the bit I couldn't find when I last looked, and
On 04/30/11 17:30, Lex Trotman wrote:
On 1 May 2011 09:19, Matthew Brush wrote:
The documentation, while not perfect, is here:
http://live.gnome.org/Vala/Manual/Attributes
That was the bit I couldn't find when I last looked, and someone else
agreed so thanks for pointing to it.
It honestly
On 1 May 2011 09:19, Matthew Brush wrote:
> On 04/30/11 05:46, Lex Trotman wrote:
>
>> But when I queried how these GObjects could be written in Vala no one
>> knew since its documentation is a bit lacking (as in missing entirely)
>> when it comes to interfacing to C.
>
> That's not true, the Vala
On 04/30/11 08:14, Nick Treleaven wrote:
Thanks for explaining. I still feel against the idea, but I won't try
to veto it.
I think this is pretty much where we left off the previous discussion on
GObject plugin API. Basically, the core developers are either against
the idea or don't have
On 04/30/11 05:46, Lex Trotman wrote:
But when I queried how these GObjects could be written in Vala no one
knew since its documentation is a bit lacking (as in missing entirely)
when it comes to interfacing to C.
That's not true, the Vala bindings for Geany provide the "thin" mapping
to the
On Sat, 30 Apr 2011 22:46:32 +1000
Lex Trotman wrote:
> Hi Nick, I have suggested that the new plugin API be GObjects which
> are just thin shells referring everything to the existing Geany
> structures like GeanyDocument. The GObject methods just called one or
> more Geany functions that work o
> It just seems like a lot of work. Vala is quite high level, I have to
> wonder whether all the disruption is worth it.
>
Hi Nick, I have suggested that the new plugin API be GObjects which
are just thin shells referring everything to the existing Geany
structures like GeanyDocument. The GObject
On Sat, 30 Apr 2011 00:24:10 -0700
Matthew Brush wrote:
> On 04/29/11 10:12, Nick Treleaven wrote:
> > On Thu, 28 Apr 2011 09:01:08 +0200
> > Frank Lanitz wrote:
> >
> >>> During the last weeks a huge number mails at this list was stating to
> >>> make usage of GObject on building up a new plugi
On Fri, 29 Apr 2011 19:19:00 +0200
Thomas Martitz wrote:
> Am 29.04.2011 19:12, schrieb Nick Treleaven:
> >
> > I think this is great. It might be doable to maintain this with Geany's
> > API when ready. This would be a big leap forward for plugin writers,
> > and little/no impact on the existing
On 04/29/11 10:12, Nick Treleaven wrote:
On Thu, 28 Apr 2011 09:01:08 +0200
Frank Lanitz wrote:
During the last weeks a huge number mails at this list was stating to
make usage of GObject on building up a new plugin interface. It has been
talked about libpeas and adding support for Vala, Pytho
Am 29.04.2011 19:12, schrieb Nick Treleaven:
I think this is great. It might be doable to maintain this with Geany's
API when ready. This would be a big leap forward for plugin writers,
and little/no impact on the existing API.
Will Geany's API ever be ready? I doubt so, especially at this
d
On Thu, 28 Apr 2011 09:01:08 +0200
Frank Lanitz wrote:
> > During the last weeks a huge number mails at this list was stating to
> > make usage of GObject on building up a new plugin interface. It has been
> > talked about libpeas and adding support for Vala, Python etc. Before we
BTW Colomban s
Am 28.04.2011 14:54, schrieb Frank Lanitz:
I think we had an agreement that we can develop it inside a new branch
(where of course you can commit) and once its stable its getting merged
into trunk.
If everybody is fine with it I'd suggest to give Matthew commit rights
for new branch to build up
Am 28.04.2011 09:32, schrieb Matthew Brush:
> On 04/28/11 00:01, Frank Lanitz wrote:
>> Hi,
>>
>> Am 12.03.2011 19:11, schrieb Frank Lanitz:
>>> During the last weeks a huge number mails at this list was stating to
>>> make usage of GObject on building up a new plugin interface. It has been
>>> tal
On 04/28/11 00:01, Frank Lanitz wrote:
Hi,
Am 12.03.2011 19:11, schrieb Frank Lanitz:
During the last weeks a huge number mails at this list was stating to
make usage of GObject on building up a new plugin interface. It has been
talked about libpeas and adding support for Vala, Python etc. Befo
Hi,
Am 12.03.2011 19:11, schrieb Frank Lanitz:
During the last weeks a huge number mails at this list was stating to
make usage of GObject on building up a new plugin interface. It has been
talked about libpeas and adding support for Vala, Python etc. Before we
do discuss any further I'd like to
Le 17/03/2011 09:17, Lex Trotman a écrit :
> On 17 March 2011 17:56, Matthew Brush wrote:
>> Unfortunately, there is some context around this which has been discussed
>> around the geany-vala-binding, that a lot of which wasn't on a ML. It's
>> very easy to summarize some of the ideas I've had/he
On 17 March 2011 17:56, Matthew Brush wrote:
> On 03/16/11 22:25, Lex Trotman wrote:
>>
>> Hi Matthew and All,
>>
>> @Matthew, I've looked at your dbus repo. I might not have understood
>> how you were relating it to this, but to me it looks like you are just
>> using the old plugin interface, ra
On 03/16/11 22:25, Lex Trotman wrote:
Hi Matthew and All,
@Matthew, I've looked at your dbus repo. I might not have understood
how you were relating it to this, but to me it looks like you are just
using the old plugin interface, rather than anything to do with a new
interface.
It's very bare
Hi Matthew and All,
@Matthew, I've looked at your dbus repo. I might not have understood
how you were relating it to this, but to me it looks like you are just
using the old plugin interface, rather than anything to do with a new
interface.
@All,
Having reviewed what has been said in the thread
On 13 March 2011 17:10, Matthew Brush wrote:
> On 03/12/11 19:46, Lex Trotman wrote:
>>
>> On 13 March 2011 13:36, Colomban Wendling
>> wrote:
>>>
>>> Agreed. Maybe the easiest way to go would be to write this wrapper
>>> library in Vala, at least as a start point:
>>> 1) it's an OO language, and
On 03/12/11 19:46, Lex Trotman wrote:
On 13 March 2011 13:36, Colomban Wendling wrote:
Agreed. Maybe the easiest way to go would be to write this wrapper
library in Vala, at least as a start point:
1) it's an OO language, and would save a significant part of the work
needed to write GObject co
On 13 March 2011 13:36, Colomban Wendling wrote:
> Le 13/03/2011 03:01, Lex Trotman a écrit :
>> On 13 March 2011 05:39, Matthew Brush wrote:
>>> [...]
>>>
>>> If there was someone with lots of GObject experience that would be willing
>>> to review my code on a regular basis, I'm willing to volun
Le 13/03/2011 03:01, Lex Trotman a écrit :
> On 13 March 2011 05:39, Matthew Brush wrote:
>> [...]
>>
>> If there was someone with lots of GObject experience that would be willing
>> to review my code on a regular basis, I'm willing to volunteer my time and
>> do most of the coding (or at least my
On 13 March 2011 05:39, Matthew Brush wrote:
> On 03/12/11 10:11, Frank Lanitz wrote:
>>
>> But before we can discuss about the positive/negativ points I just
>> want to ask who likes to take over this task as a kind of lead
>> engineer and project manager to be the lead here having in mind it wil
On 03/12/11 10:11, Frank Lanitz wrote:
But before we can discuss about the positive/negativ points I just
want to ask who likes to take over this task as a kind of lead
engineer and project manager to be the lead here having in mind it will
most likely not a 5-minute-task?
I would like to work o
Hi guys,
During the last weeks a huge number mails at this list was stating to
make usage of GObject on building up a new plugin interface. It has been
talked about libpeas and adding support for Vala, Python etc. Before we
do discuss any further I'd like to point to an email Enrico sent
earlier
27 matches
Mail list logo
