On 04/22/12 00:06, Marco Leise wrote:
> Am Sat, 21 Apr 2012 21:46:18 +0200
> schrieb Artur Skawina :
>
>> On 04/21/12 19:16, Marco Leise wrote:
>>> I just noticed cairo.d is still a dummy. I am using image surfaces.
>>
>> Yes, cairo.d is generated from GI data too and only contains the few symbol
Am Sat, 21 Apr 2012 21:46:18 +0200
schrieb Artur Skawina :
> On 04/21/12 19:16, Marco Leise wrote:
> > I just noticed cairo.d is still a dummy. I am using image surfaces.
>
> Yes, cairo.d is generated from GI data too and only contains the few symbols
> and types required to use the other libs.
On 04/21/12 19:16, Marco Leise wrote:
> I just noticed cairo.d is still a dummy. I am using image surfaces.
Yes, cairo.d is generated from GI data too and only contains the few symbols
and types required to use the other libs. There are other cairo D bindings,
which
probably could be used with a
Am Sat, 21 Apr 2012 14:26:59 +0200
schrieb Artur Skawina :
> On 04/21/12 12:24, Marco Leise wrote:
> > At first I confused your project with GtkD. I'll take a look at it, to see
> > how it compares. Many examples for Gtk use C code, and I end up looking for
> > the correct GtkD class that offers
On 04/21/12 12:24, Marco Leise wrote:
> At first I confused your project with GtkD. I'll take a look at it, to see
> how it compares. Many examples for Gtk use C code, and I end up looking for
> the correct GtkD class that offers the function. Otherwise I quite like the
> classical inheritance t
At first I confused your project with GtkD. I'll take a look at it, to see how
it compares. Many examples for Gtk use C code, and I end up looking for the
correct GtkD class that offers the function. Otherwise I quite like the
classical inheritance that is possible with GtkD, whereas you use the
