Re: [gtkwrapper-general] gtkwrapper LGPL issue

[Li L. <li...@ho...>]

Alex Shaduri wrote:

>Hi
>
>I saw your announcement of gtkwrapper library in the gtk mailing lists.
>I think this is a very good library, because you can add it to existing
>projects without rewriting them (porting to gtkmm or inti would require
>that) and you don't need any additional runtime linking. The API seems
>very good too.
>
Thank you very much for the nice word.  The gtkwrapper project is still 
in its infant state.  I will keep on improving it.

>...
>I suggest you look into the matter of licensing, as LGPL for a linkable library
>is not the same as LGPL for header-only library.
>  
>
I actually do not really understand what LGPL means.  I will follow your 
suggestion to change the license text so that every one can use it.

>Oh, and your .tar.bz2 contains win32 newlines (It's common that the zip file
>should contain win32 newlines and the tar.gz and tar.bz2 files should
>contain Unix newlines). You could use dos2unix program to convert them.
>And the files in tar archives should be chmod 644-ed (you have the
>executable permissions in your archives).
>  
>
Will fix this.  Thank you again...

>And another thing... Your headers are named like CanvasLine.h. This is a
>bit annoyance on Unix systems where filesystem is case-sensitive.
>It's a good practice to name the files lowercase, like canvasline.h or
>canvas_line.h.
>  
>
I am making a convention here: the file name is the same as the class 
name.  Is this acceptable?

I am actually quite new to the gtk/linux world.  Your encouragement and 
comments are very valuable for me.
There are actually still quite a lot can be done for the wrapper 
library.  I am currently looking at the possibility of generating 
gtw-based code from glabe files.  Any suggestions about this?  Another 
thing to be done is to wrap the properties with get/set functions.

Regards,
Lirong