Hi Paul, 2010/12/17 pdhaene <[email protected]>
> Thanks Mat I understand. > All the naming,finding around and understanding > of how things are knitted together is the reason why I want to wait > with poking around > in existing files in svn ( I have of course fetched the files you > mentioned) > Don't hesitate, put your files under SVN if they are working pieces of code. It's easier for everyone to follow your progress and review when possible, by diff'ing content for instance. When co-developing, files in SVN should remain the reference. Your libs, samples must also follow our style guide. Use "python tools/jallib.py validate <yourfile.jal>", or some tools within an IDE (Jaledit, JaluinoIDE) to check some of rules before committing your code. Automated builds (buildbot) will track for this and check all code base is working (valid, compilable). Cheers, Seb -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
