DevelopmentTasks
From SalasagaWiki
For anyone looking to get involved with the development of Salasaga, these are some of the short terms tasks that need working upon
Contents |
[edit] Windows coding
Three main things need to be done in this area:
[edit] Document getting MSYS up and running on WinXP, such that Salasaga can be build and worked upon
Silly me got it running on WinXP SP1 a while back, but didn't document the process. I have No Idea how to go about doing it again from a "clean" WinXP installation. :-/
[edit] Make Salasaga build in Win32. Absolutely no idea if it will/won't
Haven't even tried it for months. (nearly a year I think)
[edit] Write the code for selecting the window to capture
In X-windows, the user gets given a dialog box prompting them to click on the window they want to capture. This then does some X window (not GTK) calls to figure out the dimensions of the window.
The Win32 code needs the same thing written. At the moment it just pops open a dialog box directly asking the user for the onscreen dimensions they want to capture. Crappy usability. :(
[edit] Automake
The MacPorts guys have very strongly said we need to use automake for generating the make files rather than us hard coding them.
One of the tricky things that Salasaga experiences is finding out where it's been installed, and therefore where the icons, fonts, etc are. Moving to automake lets us put a "__PREFIX__" (or similar) in the salasaga.c source file, that gets updated correctly at compile time. Problem fixed. (apparently)
I have no clue with automake though. Tried following through some "quick tutorial" for it before releasing the last dev snapshot, but that didn't work and just got me frustrated. :-/
[edit] XGrabKey
At present, at application start we bind the Control-Printscreen key by writing to a metacity-specific GConf key.
So, the key grab only works for metacity.
The Freedesktop.org guys have recommended we use XGrabKey instead, as that lets us bind whatever key(s) we want and isn't tied to a specific window manager.
[edit] Packaging
Making a debian package for the latest Ming would be really useful.
It'll help the ming guys when they do the next Stable release there, and it should provide a base point they can use for subsequent releases.
It'll also mean that if we make a package for Salasaga, then people can just install both of these and not have to install -dev packages and compile from source.
