Invalid Ticket Number: new-ticket
 

Version 9, last updated by AndreSomers at February 04, 2011 12:20 UTC

The SAINT tools presented here are a work-in-progress, and you are invited to be part of that!

For updates and some general introductions, take a look at my blog and on the official website for the toolkit.

The tools are build on the excellent, open source Qt toolkit by Nokia's QtSoftware (formally: Trolltech). To get started with development, download and install the Qt SDK from their website. You can use Qt's Creator program as an editor, but if you prefer some other editor, like QDevelop, KDevelop or even Microsoft's Visual Studio, you can use that too of course.

The source code is available as a Git repository, with several branches. The stable branch is where work on polishing and bugfixing the existing tools takes place, while more structural work and new tools are being worked on in the unstable branch. Please use one of these.

Reporting problems

We welcome your feedback, and encourage you to report any problems you encounter or ideas you have to make the tools more usefull to you. For all these, please use the Tickets tab above. You may have to create a login for yourself before you can add new tickets. If you are running into a problem, the first step to fix it is the ability for a developer to reproduce the problem on his own machine. That means that the description of your problem should include as much detail as possible. Describe what you were trying to accomplish, what you exected as a result, what you did, which settings you used, which buttons you pressed, and if possible, if you can reproduce the problem yourself consistently or not, and if at all possible, attach a minimal example of a data file on which the problem can be made to appear. It may be that you will be asked to provide more details, try a specific approach and report back the results, etc. Please be willing to do that if you report an issue. These things are often critical to locating the source of the problem you are observing.

Simon Tatham has written an essay about bug reporting, that I would recommend you to read. It explains the above in a bit more detail.