Kexi/Getting Started

From KDE Community Wiki

Ways for contribution

  • Tester
  • Developer
  • Promoter

Communication channels

See Contact.

Common tools

Specific for Developers

Specific for non-Developers

Other information

  • For testing, use the newest Kexi version you can get
  • After you start Kexi for the first time, you will be able to create a new empty database. Use the Handbook (old) to get information how to do this.
  • If you plan to use and test support for server databases, you will need access to a server. It can be the same computer as your desktop machine, but you'll need to install the database server software on your own. If you have not enough knowledge to do this, ask some one (e.g. a network administrator) to do so.
  • You may also want to use example databases as a reference.
    • These databases are saved in self-contained files for your convenience:
    • Example databases on a database server (MySQL, PostgreSQL) useful to test server connections. Will be provided, more information is PLANNED here. Please offere a server space if you can. Please provide test databases if you have such (must be legal)..
    <a class="totoc" href="[email protected]#__TOC">^ toc</a><a name="What_to_Test_"></a>

    What to Test?

    You can:

    • test for crashes or misbehaviour
    • locate places where Kexi is ineffective (e.g. for large data sets) or hangs
    • test particular functionality and propose entensions, e.g. data importing functions
    • compare the application to the competition and identify the most expected features that Kexi currently lacks
    • test for usability
    • test for accessibility
    • test for localizations issues, including support for right-to-left languages, etc. (note: errors in translations to other languages should be reported to a particular <a href="http://i18n.kde.org/teams/">translation team<img src="images/external.gif" align="top" alt="" border="0"/></a>)
    • locate errors in the <a href="[email protected]">Kexi Handbook</a>, report unclear or incomplete paragraphs, outdated or missing screenshots (the above note about translation teams also apply to translated documentation)
    <a class="totoc" href="[email protected]#__TOC">^ toc</a><a name="How_to_Report_Bugs"></a>

    How to Report Bugs