[Tux4kids-tuxtype-dev] Reviewing code and tasks

[David Bruce]

Hi Santiago,

We aren't really using the bug/task tracker to any real extent,
although perhaps a good todo item would be "start using bug tracker"
;-)

Generally, the code in tuxmath is in better shape than the code in
tuxtype.  Last summer, we started extracting code from tuxmath to make
libt4kcommon, with the idea that we will base both tuxmath and tuxtype
on libt4kcommon once it gets mature enough - this will represent a
bigger change for tuxtype than for tuxmath.

Regards,

David Bruce

On 3/14/10, Santiago Lizardo Oscares <santiago.lizardo at gmail.com> wrote:
> Hello developers!
>
> I'm reviewing the source code of the tux4kids projects, and looking how to
> help starting from the open tasks listed here:
> https://alioth.debian.org/pm/task.php?group_project_id=312&group_id=31080&func=browse
>
> To start, I would say task #442 is already done, so it should be closed in
> Alioth.
>
> Finally, if nobody is working on task #430 of *tuxtype* and you consider is
> neccessary and an improvement, I suggest to change the way the command line
> arguments are handled to *getopt* (
> http://www.gnu.org/s/libc/manual/html_node/Getopt.html ) or the
> *handle_command_args(int
> argc, char* argv[])* like the one used in *tuxmath*.
> What do you say?
>
> Thank you!
>
> --
> Santiago Lizardo Oscares
> IT architect & manager
>