Ease : weekly report #1
Par Stéphane le samedi 29 mai 2010, 19:16 - GNOME - Lien permanent
Previous report was #0, actually.
It's available in PDF : Summer of code, weekly report #1.
1 What I have done
Actually, this report takes into account the last past two weeks, because I already had started a bit of work before the official coding starts (like every Summer of Code student). The list looks like this :
-
Autotools stuff : took me a while, but finally got it working, thanks to the help of the Sampala project1, a project to help you familiarize with Vala + autotools + gettext, the Vala project generator vala-gen-project, other Vala programs like gnome-scan, and some nice people on the #vala channel. First time I’m happy to use ./configure ;
-
We finally moved to git.gnome.org2 ;
-
Sent a mail to the GNOME Bugzilla people, and we have our bugtracker!3 ;
-
Last but not least, checked around for good translations platforms, had started working with Transifex but finally turned to GNOME Damned Lies, and we have our module4 there too! Now we have a German, French and Spanish translation. First time I’m happy to read Spanish ;
-
Walked around the code, and sent a couple of mails to my mentor regarding coding style and general design of the app. Noted that a 7 hours difference doesn’t really help communication ;
-
Got the nice people (they really are) of the #vala channel to upgrade the librest bindings, as well as the librest-extras one (thanks Adrien BUSTANY!), which now allows me to start toying with the Flickr API and build my stock images fetcher.
2 What’s next
Actually, my final exams are next week, so I’ll be a bit busy. But I’m going to try to build my image fetcher, as I think it’s a cool feature and that it won’t be much work to integrate it into Ease. Especially since I didn’t finish talking with my mentor about Ease design and directions, I’m not going to hack on the “core” at the moment.
3 Timeline
Even though I didn’t coded a lot, I’m quite satisfied with all the infrastructure work, as it was one of the “features” of my proposal.
4 Issues/Other news
-
I was quite impressed by the progress of the other GNOME SoC students. Congrats guys! ;
-
Considering the hard time I had to find the right way to use autotools (not using recursive Makefiles, Vala project, l18n, outdated documentation), I’m thinking about writing a dead-easy-but-not-stupid Vala tutorial, to bring more people into GNOME, once I’m done with my summer of code, right in time for GNOME 3.
That’s all for me. Cheers!
Commentaires
Why not using CMake instead of autotools? I think it's a lot easier.
@swilmet Last time I checked cmake support for GNOME was rather non-existent
@steph The PDF link gives a 404...
@swilmet : I read a page on the GNOME wiki about alternate build frameworks to replace autotools, and there was [minor] issues with most of them, CMake included. I decided to stick with autotools, it's the "standard" so I can get feedback on it, and moving to another build process won't be any more difficult :-) !
@DeeJay1 : Thanks! It's fixed.
I'm considering writing the Vala tutorial too. Went through the autotools outdated docs trip myself as well :D
May I suggest that you at least start taking notes for your tutorial now? Memories are still fresh, you still know what parts were difficult for you. I can understand that you don't want to waste time writing it now and would rather see some progress on your SoC project, but consider that you might forget things by the time you start writing.
Also, I noticed you speak French (maybe you even *are* French). Are you already on the #gnomefr channel :) ? If not, consider joining us, it is much fun to share with people from your area. If you're already there, consider waving afranke (that's me, in case that wasn't obvious enough).
Hi,
I've tried to build from git, but ./autogen.sh fails
It ends with
configure.ac:45: required file `./config.rpath' not found
When I try to execute ./configure (it is generated) it stops with
...
checking for shared library run path origin... /bin/bash: ./config.rpath: No such file or directory
done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'
It seems you have forgotten to add a file or something...
Hi Nathan,
I must investigate this issue soon. The fix is quite simple : create an empty file named config.rpath (`touch config.rpath` in your terminal), then run ./autogen.
http://www.bareyourfingers.com
http://www.bareyourfingers.com