Hello,
may be I can help you. I'm not a vala developer, but I also looked at source
code.
Do the following
1. Try to download the source
2. Open vala.vapi from vala source (vala-version/vala)
Here you have an overview of all used classes in vala-compiler.
I think you can start reading at
To the wonderful wizards of Vala... I need some help... I have an
object that presents certain information in a dialog. Other instances
of that object also share the same dialog. Nothing else in the program
needs to know that the Dialog even exists, it will manage its own
lifetime.
I assume
2009/7/13 Fredderic magen...@gmail.com:
To the wonderful wizards of Vala... I need some help... I have an
object that presents certain information in a dialog. Other instances
of that object also share the same dialog. Nothing else in the program
needs to know that the Dialog even exists,
2009/7/13 Uwe Strempel u.strem...@googlemail.com
Hello,
may be I can help you. I'm not a vala developer, but I also looked at
source code.
Do the following
1. Try to download the source
2. Open vala.vapi from vala source (vala-version/vala)
Here you have an overview of all used classes in
2009/7/13 Vlad Grecescu b100d...@gmail.com:
2009/7/13 Uwe Strempel u.strem...@googlemail.com
Hello,
may be I can help you. I'm not a vala developer, but I also looked at
source code.
Do the following
1. Try to download the source
2. Open vala.vapi from vala source (vala-version/vala)
Hello,
I'm using vala and the gstreamer bindings and currently there are some
methods of the Gst.XML class that take uchar arrays as parameters instead of
strings.
Here is the patch that fixes this in the vapi metadata.
Regards,
Eric
diff --git a/vapi/gstreamer-0.10.vapi
Hello,
I use libxml-2.0 and I noticed that there was no method to create a
namespace in the vala binding.
xmlNewNs is not available in the vapi.
That's why I added a Xml.Ns.create static method that wraps xmlNewNs. I
don't know if it's the right place, but xmlNewNs is required to create a
2009/6/29 Levi Bard :
I agree that creating a general-purpose library that doesn't expose a
C api is annoying and moderately selfish. Coincidentally (considering
the context of this thread), I see that actually happening much more
often with python and ruby than I do with mono.
Watch out
