Hacking GTG for dummies and very smart people

Hello prospective Getting Things GNOME! contributor, This is a short and self-contained guide to get you ready to hack gtg code in the easiest possible way. This guide supposes that:

If you don't fulfill those requirements or you're just not scared by the CLI and a good old fashioned guide, follow this link.

Now that the hardcore guys are gone, let's get to the point.

Getting the code

Assuming you're on Ubuntu or Debian, you can use groundcontrol, a nice GUI way to take care of getting the gtg code and sending changes in. First, execute these two commands to install it:

 sudo add-apt-repository ppa:doctormo/groundcontrol
 sudo apt-get install groundcontrol

Be sure to logout/login or restart Nautilus (ubuntu should ask you to do that), otherwise the next step will not work. Now, create a folder named "Projects" in your home folder and navigate into it.

You should see something similar to the following image (in your awesomer theme).

project.png

As you've probably figured out by now: click on "fetch project". Insert your launchpad credentials (if you don't have them, subscribe -- these credentials are the same of your Ubuntu One account, if you have that).

Search for "gtg", and select one of the projects listed (not the "Windows" one -- that is a porting project).

listprojects.png

Almost done! Now, enter in the newly created "gtg" directory and click on "Fetch branch"

gtgfolder.png

Select the "trunk" branch and name it "trunk" as in the picture. That is the place where we keep the latest version of GTG, still under development.

gtgbranch.png

There, you've made it though! In the "trunk" directory (or whatever you've called it), you'll find all the code. You can try that by entering in the "trunk" directory and double clicking "gtg" (If a dialog shows up, just click "run").

It's hacking time!

Now, to be a respected hacker you should open your terminal in your ~/Projects/gtg/trunk directory. From there, if you run

 ./gtg -d

You'll launch GTG in debug mode loading your tasks, as usual. If you don't want to test your code on your precious GTG tasks (and you shouldn't want to do that), you can run

./scripts/debug.sh -d

Which loads GTG with a different set of tasks, that can be safely tortured at will without affecting your normal GTG session.

Now you know all the basic stuff needed to hack on GTG.

Some general directions follow:

gtg/easyguide (last edited 2010-08-04 00:23:01 by BryceHarrington)