I'd go even further than claudeb and say don't think in terms of libraries - think in terms of modules.
My reasoning is that even libraries can be pretty big projects (depending, of course, on what the library tries to accomplish) and will sure as hell become a terrible mess if don't keep them organized inside. It's therefore a better approach to clearly separate library projects into several modules which don't depend on each other, provided this is possible and the library is large enough to warrant this, i.e. not a single-purpose library like zlib.
Another useful thing to keep in mind is to both modify and rely on internal states as little as possible. Not changing any internal states obviously won't work, since your game wouldn't do anything, but if you've got two equally complex ways to implement a feature -- one way that relies on internal states and modifies these states, and another one that solely relies on the input it was given and returns a value -- I'd go for the second one. It will keep testing simpler, reusing your code will be easier and you won't experience a nasty surprise if the internal state was set to a value you didn't expect.
If I remember correctly, CMake can build .deb and .rpm packages and a NSIS Windows installer -- although this feature didn't work that good the last time i've tried and the packages might need some manual corrections.
I'm not sure if there are facilities for specific metadata, but PNG allows generic comments which could be used for such purposes. In gimp, these comments can be edited via Image > Image Properties.
EDIT: @bart: Wouldn't it be possible for OGA to automagically insert such comments based on the licenses and the attribution text the user selected?
If you have not started yet, I'd like to offer doing the German translations (I have done the majority of Flare's German translations for v0.15).
Edit:
However, if you've already started translating or if you want to do it, here are some tips:
Each mod contains a 'languages' subdirectory, which in turn contains the .pot files and .po files.
To update a .po file, run 'msgmerge -U --no-wrap --backup=none /path/to/data.de.po /path/to/data.pot'.
To speed up the translation process, you can search for the keyword 'fuzzy' (translations which need to be updated) and for two consecutive double quotes (strings which still need to be translated).
Another suggestion, what about an 'autofill' function that when typing in tags it trys to suggest what you are typing. Then take that one step further, once you add a tag, it can suggest you tagged it with 'sprite' did you want to tag it with 'sprite sheet' as well? then peolpe can just easy click and autifill their tags.
Not sure if we're thinking of the same thing, but there already is an 'autocomplete' function for tags: if you start to type a tag, OGA will suggest already existing tags.
You forgot to add the texture with bubbles to the files section. I did this for you.
Pro Tip: You need to separate individual tags with commas. This time, I'm gonna do this for you.
I support your suggestion - we should keep OGA free from art that can't legally be used worldwide.
I'd go even further than claudeb and say don't think in terms of libraries - think in terms of modules.
My reasoning is that even libraries can be pretty big projects (depending, of course, on what the library tries to accomplish) and will sure as hell become a terrible mess if don't keep them organized inside. It's therefore a better approach to clearly separate library projects into several modules which don't depend on each other, provided this is possible and the library is large enough to warrant this, i.e. not a single-purpose library like zlib.
Another useful thing to keep in mind is to both modify and rely on internal states as little as possible. Not changing any internal states obviously won't work, since your game wouldn't do anything, but if you've got two equally complex ways to implement a feature -- one way that relies on internal states and modifies these states, and another one that solely relies on the input it was given and returns a value -- I'd go for the second one. It will keep testing simpler, reusing your code will be easier and you won't experience a nasty surprise if the internal state was set to a value you didn't expect.
If I remember correctly, CMake can build .deb and .rpm packages and a NSIS Windows installer -- although this feature didn't work that good the last time i've tried and the packages might need some manual corrections.
http://cmake.org/cmake/help/v2.8.8/cpack.html
Thanks for sharing this great song, and for knowing that black is the only way to enjoy your cup of coffee ;-) .
I'm not sure if there are facilities for specific metadata, but PNG allows generic comments which could be used for such purposes. In gimp, these comments can be edited via Image > Image Properties.
EDIT: @bart: Wouldn't it be possible for OGA to automagically insert such comments based on the licenses and the attribution text the user selected?
@qubodup:
There isn't really much to translate anyway. I'm nearly done now, the only thing I'm still not sure about is this string:
It's from the poem "In Memoriam A.H.H." by Alfred, Lord Tennyson. You can find it here on wikisource. The whole stanza is:
I thought it would make sence to translate the whole stanza and then take the last two lines. That's what I've come up with:
It's obviously not a literal translation, but I'm quite content with it. What do you think?
Edit:
Wrong casus. Damn you, "Der Dativ ist dem Genitiv sein Tod" - syndrome ;-) .
@qubodup:
If you have not started yet, I'd like to offer doing the German translations (I have done the majority of Flare's German translations for v0.15).
Edit:
However, if you've already started translating or if you want to do it, here are some tips:
Not sure if we're thinking of the same thing, but there already is an 'autocomplete' function for tags: if you start to type a tag, OGA will suggest already existing tags.
Pages