Our next beta is out the door and ready for your testing. Please do me a solid and help us test and shake out bugs. It’s pretty easy to install these days.
flatpak install --user --from https://git.gnome.org/browse/gnome-apps-nightly/plain/gnome-builder.flatpakref
flatpak run org.gnome.Builder
More installation options can be found here.
Long time GNOME contributor and foundation member Travis Reitter had a medical emergency earlier this month. You might consider donating to the gofundme to help him and his family out during the marathon to recovery.
Let’s remind everyone what GNOME is about, people!
I just finished the
JCON_EXTRACT() support and it is already making my consumption of JSON easier. Here is an example:
g_autoptr(JsonNode) node = NULL;
JsonArray *ar = NULL;
node = JCON_NEW (
"bar", "[", JCON_INT (1), JCON_INT (2), "]",
success = JCON_EXTRACT (node,
"bar", JCONE_ARRAY (ar),
And for now, you can just copy/paste the jcon.c and jcon.h files into your project, but I’d expect to come up with a patch we can push into json-glib at some point. It really belongs there.
Years ago during my tenure at MongoDB I worked on a couple libraries. Notably the
mongo-c-driver libraries. One neat feature we had was this concept called
BCON which stood for BSON C Object Notation. It was a succinct format for creating BSON documents that made it easier to reason about what you were creating.
So I decided to do the same thing this evening around
json-glib because I found I was writing a lot of code to create objects/arrays/etc.
It looks something like this
g_autoptr(JsonNode) params = NULL;
params = JCON_NEW (
"uri", JCON_STRING (src_uri),
"type", JCON_INT (FILE_CHANGE_TYPE_DELETED),
"uri", JCON_STRING (dst_uri),
"type", JCON_INT (FILE_CHANGE_TYPE_CREATED),
Since this uses
va_list it’s technically less type safe than your other options. But it uses some magic struct initializers to get things in a situation where we can bail at runtime if you did something wrong.
The other half that I’m currently still missing is the extraction support. If you replace
JCON_EXTRACT(node) and the values with pointers to values, you can quickly extract documents.
But that’s not done yet… so for next time…
Sri and many members of our community have spearheaded a wonderful new conference named Libre Application Summit. It’s hosted by the GNOME Foundation and has aspirations to bring together a wide spectrum of contributors.
This conference is meant to bridge a gap in Free Software communication. We need a place for application and game developers, desktop developers, systems implementers, distributions, hardware producers, and driver developers to communicate and solve problems face to face. There are so many moving parts to a modern operating system that it is very rare to have all of these passionate people in the same room.
This will be a great place to learn about how to contribute to these technologies as well. It seems likely that I’ll do tutorial workshops and other training for participants at LAS.
I’m very excited to see where this conference goes and hope to see you in Portland come September!
It’s no secret that one of the main features I wanted to land this cycle was introductory support for Xdg-App. There really was quite a bit to do to make that happen, including all sorts of seemingly unrelated plumbing.
One seemingly unrelated piece is the long-anticipated support for “Build Configurations”. I deferred on this feature for as long as possible because it needs to support many movable parts, for which we didn’t have a clear vision of. But now that our applications vision is becoming less and less murky, it was time to attack it.
IdeContext now contains an IdeConfigurationManager. This object can be used to get access to available configurations (IdeConfiguration). A configuration currently contains a target device (IdeDevice), a target runtime (IdeRuntime), environment variables (IdeEnvironment), and various other common properties.
We’ve ambitiously tried to avoid writing random dot files to your project, but time has come to add one. If you create a build configuration, we’ll drop a small .buildconfig GKeyFile in the root of your project tree. It contains the necessary information to bootstrap your project or build it with a given Xdg-App runtime.
Currently, we only have two runtime implementations. The default, is simply the host system. Think of it as a pass-through runtime. The second, is an Xdg-App runtime. It uses the runtime SDK installed via the xdg-app command line tool. For 3.22, I expect to have UI to install runtime SDKs.
You might imagine additional runtimes that we could create. Jhbuild is an obvious one, although hopefully it is less and less necessary now that we have a nightly GNOME SDK.