Hi
Perhaps I could make some comments here not as a developer, but as a user.
1) It's probably a good idea for us to start documenting the functions
we write and the APIs we create. For one, it's a reminder to think
about what specific problems the function/API is solving. Beyond that,
it
On 05/05/2011 07:50 AM, Colin Clark wrote:
Hi
Perhaps I could make some comments here not as a developer, but as a user.
1) It's probably a good idea for us to start documenting the functions
we write and the APIs we create. For one, it's a reminder to think
about what specific problems the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Do den 5. Mai 2011 um 8:50 schrieb Colin Clark:
What I find missing is high-level documentation, not low-level. An
overall description of the way the system is organised and how the
main functions and structures should be used.
True.
Hi
https://gitorious.org/geeqie/geeqie/archive-tarball/master
You can find that link if you look at the log of a branch on the right
side.
Thanks for the info.
During copy/move/rename there is no thumbnail displayed when there
is a destination file conflict (I've made a patch to do this,
Howdy, all. It's time for a thought on code cleanliness
1) It's probably a good idea for us to start documenting the functions
we write and the APIs we create. For one, it's a reminder to think
about what specific problems the function/API is solving. Beyond that,
it helps someone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello folks,
Am Mo den 2. Mai 2011 um 17:42 schrieb Omari Stephens:
Howdy, all. It's time for a thought on code cleanliness
:-) That is my objective to.
2) We need to have a maximum line length. It can be long, sure, but
it's pretty
