I’ve used your code and it works great. But I need to make the call synchronously. How can I do that? Doing this:
const _httpSession = new Soup.SessionSync();

Didn’t seem to work… :S

But my point is that there should be a way (the OFFICIAL way) of clicking an icon which starts up a development environment where you can write code, click another button to build/run/debug and be done with it, rinse and repeat until you have your program ready.

It’s a shame that we don’t have that. Yes, there is MonoDevelop (which is the closest to what I have in mind — but is mono :-/ ). Nothing similar (and mature enough to be usable) for python, c, c++, vala.

There is this thing called Quickly which tries to tackle the same problem, but it’s not integrated enough: you have to use the command line, gedit and glade. Three different applications: not well integrated.

Although I do prefer Linux over Windows or OSX, we have to give credit for what they achieved with VisualStudio and XCode respectively.

We _need_ something like those for Linux as well!

This might help a lot. Also, throwing yourself into a terminal helps. I had to learn how to use some basic commands as RedHat 6.2 didn’t support my graphics card without lengthy manual configuration as it was a cheapo piece of junk. I was left in the CLI for a long time, which was a good learning experience. Also, I did not have an Internet connection so learning was slow from magazines.

Try changing your system run level from 5 to 3 and you’ll learn CLI stuff quickly

Happy hacking on your journey. The blog updates are interesting, thanks!

Jhbuild has received lots of love recently, but it still is an experienced hacker tool :-/. Again, please do not refrain from commenting on this problem, the fresh and first hand experience is gold!

It turns out there is one issue with the code as you have it – when you do:

function getWeather(callback) {
var session = new Soup.SessionAsync();
var request = Soup.Message.new(‘GET’, ‘http://api.geonames.org/weatherIcaoJSON?ICAO=EFHF&username=demo’);
session.queue_message(request, function(session, message) { …});
}

There is nothing keeping the ‘session’ variable alive, so it could be garbage collected by the JS runtime before the request completes. This should simply result in your request not working, but right now it also can cause your program to crash in obscure ways, as I just tracked down in a 4-hour debugging session when trying to figure out why the weather extension causes GNOME Shell to crash at random times.

The best thing to do is to create a single HTTP session for your program. This also gains some efficiency by not creating extra objects and possibly reusing persistant connections. At the toplevel scope of your file, do:

const _httpSession = new Soup.SessionAsync();
Soup.Session.prototype.add_feature.call(_httpSession, new Soup.ProxyResolverDefault());

Then just use _httpSession whenever you use a session. (The second line gets libsoup to use HTTP proxies when the user has configured that for their desktop. The weird syntax is to work around a GJS quirk for cases where there are properties and functions with the same name.)