Development guidelines
Tigermouse is a publicly run project hosted on Sourceforge. It is free/libre/open source software, which means it gives you freedom of use, it costs you nothing and you can download complete source code if you desire.
who can praticipate?
Anyone. We encourage geeks of all traits to help us grow Tigermouse. Developers are welcome, but we are also looking for documentation writers, testers, web site maintainers, artists and whole lot of people with new ideas and visions.
development process
Tigermouse is developed using concurrent version control system Subversion.
All discussion takes place on tigermouse-devel@lists.sourceforge.net
(subscribe|archive).
You can send your patches there in diff format. Please follow coding style
described in next paragraph to save your effort from being rejected.
coding conventions
If you wish to contribute please try to stay close to the following rules:
- class names in PascalCase (e.g. FrontCtrl)
- interface names in PascalCase prefixed by 'I' letter (e.g. IDataSource)
- methods, properties and local varriables names in camelCase (e.g. selectTab)
- class files
<class name>.class.php - interface files
<interface name>.interface.php - only one class/interface per file
- keep
{in the same line as its respective if, for, function, class, etc. - use UTF-8 charset
- use Unix style end-of-line characters
- use
\tas tab character and do not format code with spaces - use triple
\nto separate methods - document your code using Doxygen tags
- set ERROR_REPORTING to E_ALL | E_STRICT in php.ini for both CGI and CLI
Please remember not to save any data in session unless it's absolutely necessary. Debugging session data is difficult and Tigermouse is intended to be simple and stateless as much as it's possible.









