Re: [Vala] How to check if GLib.List is empty?
On Tue, 2014-12-02 at 19:03 +0400, Виталий Кирсанов wrote: Is there a more simple and efficient way? If you don't have to use GLib.List, you can use Gee.List, which is much easier to use and doesn't have this problem. signature.asc Description: This is a digitally signed message part ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] VAPI bindings for external lib
On Mon, 2014-11-17 at 14:28 +0100, Gonzalo Aguilar Delgado wrote: Hello, I'm modifiying babobab to support a ceph cluster. And want to do add several tools to position files on OSDs, show fragemntation of underlaying filesystems, etc. Maybe this will generate other tool, but for now just modifying. The problem is that I cannot access directly to librados, libcephfs libraries from vala. Ehem, I can do it by just linking but figuring out what's the best way to do it. I suppose that creating a binding is the best. I saw some tutorials but all require that library already uses GObject system that's not the case. So, should I create a wrapping object lib, and then generate bindings from there? Or should I do another way? I'm thinking about just adding dep and call it from vala like c. But don't know what's the best way to proceed. Best regards There's a lot of documentation on this here: https://wiki.gnome.org/Projects/Vala/LegacyBindings signature.asc Description: This is a digitally signed message part ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] Building Vala Applications
On Wed, 2014-09-10 at 23:12 -0500, Canek Peláez Valdés wrote: I would love to have the guide there. What can I do to make it happen? The best way would be to clone the git repository, update it, then file a bug with a patch: https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-devel-docs The second best way would be to convince someone else to do that. :) I guess when working on gnome-devel-docs you can view your changes in yelp, but I haven't done this before so you might need to ask one of the maintainers if you can't figure it out. Michael signature.asc Description: This is a digitally signed message part ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] Building Vala Applications
On Wed, 2014-09-10 at 14:41 -0500, Canek Peláez Valdés wrote: This only took me a couple of days, and if there is interest I could do the same for the first chapter of the Gtk+ library documentation, and perhaps moving it to a more official location in the Vala/GNOME infrastructure. I only skimmed it quickly, but it looks like good documentation that ought to be on developer.gnome.org. The most appropriate location would probably be to somehow merge it into gnome-devel-demos (probably as a new section): https://developer.gnome.org/gnome-devel-demos/unstable/vala.html.en https://git.gnome.org/browse/gnome-devel-docs/tree/platform-demos/C signature.asc Description: This is a digitally signed message part ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] valadoc.org
On Wed, 2014-09-03 at 16:41 +0200, Florian Brosch wrote: Hey Michael, The site should be up-to-date now. Flo Thanks Florian! signature.asc Description: This is a digitally signed message part ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] Gtk+ bindings update
On Tue, 2014-08-26 at 12:01 -0700, Jim Nelson wrote: Yorba's applications were considered non-GNOME for nearly five years and are still not part of GNOME core (although we're now hosted on the infrastructure). We *definitely* care when we we're broken between releases of Vala. Right right. What I meant to say is if a non-GNOME application is going to be broken by either vala 0.26 or vala 0.28, it doesn't matter very much which one and not they don't care if they break. My assumption is that it'd be unusual for non-GNOME developers to compile with an unstable version of vala, so the point during the cycle at which the breakage is introduced is irrelevant. Anyway I see the new bindings are in, and none of the GNOME games needed any changes at all, which was great! Michael signature.asc Description: This is a digitally signed message part ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] Gtk+ bindings update
On Thu, 2014-08-21 at 19:28 +0200, Rico Tzschichholz wrote: I really like to push the staging changes to master despite being in the GNOME freeze. There was also no vala release yet which other projects could rely on. Official GNOME applications which are using Vala will be fixed as fast a possible. Currently known are gitg and geary which needs minor patching. There has already been an unstable release, one month ago. I suspect if you merge your changes now, the fallout will be manageable throughout GNOME. Non-GNOME programs certainly will not care one way or the other whether they are broken by vala 0.26 or by vala 0.28. And the changes are certainly bugfixes, not features or UI changes that would be affected by the current freeze. But it's still annoying to break programs this late in the cycle. In the future, it would be appreciated if you make unstable releases according to the GNOME schedule, and merge the last major changes prior to 0.x.90. Almost all of the GNOME Games, at least, depend on unreleased vala throughout the unstable cycle. This only works for distros because they don't usually patch our vala code, so they don't compile our vala code. Michael signature.asc Description: This is a digitally signed message part ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] Gtk+ bindings update
On Sat, 2014-08-23 at 10:12 -0500, Michael Catanzaro wrote: And the changes are certainly bugfixes, not features or UI changes that would be affected by the current freeze. Nope I was completely wrong, API/ABI is also frozen of course. signature.asc Description: This is a digitally signed message part ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
[Vala] valadoc.org
Hi, It looks like valadoc.org has not been updated since GNOME 3.10, judging by the lack of documentation for Gtk.Popover. Who's responsible for this site? Thanks, Michael signature.asc Description: This is a digitally signed message part ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] A brand new build system
On Sat, 2014-05-17 at 09:43 +1200, Robert Ancell wrote: (I'm the author of Bake). Bake has detailed documentation with it (as shown in that link) but lacks a website [1]. Help welcome :) [1] https://bugs.launchpad.net/bake/+bug/1215366 I'd never heard of Bake either. It seems to have built-in support for many GNOME-related build tasks, notably GSettings and Mallard help. I presume it is not being publicized because it is not considered ready yet? signature.asc Description: This is a digitally signed message part ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] question Gtk 3 + gstreamer 1.0
On Thu, 2014-03-06 at 08:42 +0800, Nor Jaidi Tuah wrote: /home/flavio/Documentos/JAMediaSuite/UbuntuRadio/vala/UbuntuRadio.vala.c:377:2: warning: 'g_type_init' is deprecated (declared at /usr/include/glib-2.0/gobject/gtype.h:669) [-Wdeprecated-declarations] g_type_init (); ^ You can avoid this one by passing --target-glib=2.36 (or --target-glib=2.38) to valac. But really, trying to fight warnings in the generated C code is a losing game. In my projects I always compile the C code with -w. signature.asc Description: This is a digitally signed message part ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] A suggestion for future releases
On Thu, 2013-11-21 at 00:06 -0008, Jim Nelson wrote: Geary 0.4.1 (released a little over a week ago) fails to compile with Vala 0.22.1. This is due to two changes in Vala: * The libnotify binding change This change broke gnome-break-timer as well. I'd like to request that in the future changes in stable dot releases be more conservative in nature. Seconded. Cheers, Michael signature.asc Description: This is a digitally signed message part ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
