Difference between revisions of "Developing"
Line 63: | Line 63: | ||
=== Gestinux development Rules === | === Gestinux development Rules === | ||
− | * The source must be compilable with : Lazarus 1.0. | + | * The source must be compilable with the last stable versions : Lazarus 1.0.8 and FPC 2.6.2 |
* Do not use features available only in Lazarus 1.1 or other SVN. | * Do not use features available only in Lazarus 1.1 or other SVN. | ||
* Only use English for identifiers and comments. | * Only use English for identifiers and comments. |
Revision as of 12:08, 5 June 2013
FrançaisDeveloping Gestinux
Gestinux is an open source software and anyone can help to its development.
Some guidelines for project maintenance follow, which can be discussed in the development forum.
Translation
You can easily translate gestinux into your mother language, and existing translations can definitely be improved.
Documentation
To help improving documentation, that is to create or edit pages in this wiki, you must before subscribe in the development forum.
Then, in this forum, ask for the right to edit this wiki, introducing yourself briefly.
You will have to learn how to use WikiMedia (used by Wikipedia), and follow some editing rules. The account and password are the same as in forum.
For any question or remark, it is necessary to use only the forum and not the wiki.
Programmation
Gestinux is being developed using Lazarus 1.0 (and FreePascal).
Obtaining the sources
Gestinux source code is managed using subversion. You must use a SVN Client and connect to it.
The svn command line is : svn checkout http://svn.code.sf.net/p/gestinux/code
Use your username and password on sourceforge.net
- You can change sources in the trunk branch only.
- The 1.0 branch should be released stable as soon as possible. You can only add or edit languages files in this branch.
- The 0.5 branch is for history only, you can't work on it.
Packages which are required
Releases 1.0 or trunk should compile with the following packages. You can use more recent versions of the packages, but at your own risk !
Let us know if using a newer version of any of these packages works sucessfully.
- Zeos DBO 7.0.3-stable
- Download the package and unzip to any directory.
- Open packages/lazarus/zcomponent.lpk and click Install
- Power PDF 0.9.10
- Download the package and unzip to any directory.
- Open pack_powerpdf.lpk
- Install.
- LazReport 0.9.8
- Open components/lazreport/source/lazreport.lpk in the Lazarus installation folder (/usr/share/lazarus/<version> on Linux)
- Install.
- LazReportPDFExport 0.7
- Open components/lazreport/source/addons/pdfexport/lazreportpdfexport.lpk in Lazarus installed files.
- Install
- Gestinux_util : a package containing the components Gestinux uses
- Open util/gestinux_util.dpk in the gestinux sources (svn)
- Install. For Gestinux 1.0, it will be Gestinux_util 1.1; For the trunk, install Gestinux_util 1.2 or higher. You can't have both at the same time.
Gestinux development Rules
- The source must be compilable with the last stable versions : Lazarus 1.0.8 and FPC 2.6.2
- Do not use features available only in Lazarus 1.1 or other SVN.
- Only use English for identifiers and comments.
- Use the Code Formatter (CTRL+D) to indent modified sources, with default options.
- Read the gestinux_util documentation, and do not use a Txxxx component when there is a TGxxxx component in this package
Ask to be granted a developer profile in SourceForge. Don't forget to lock the files before any change.
What to do
Everyone can help ! If you are a beginner, there are some simple things you can do, and this would save time. For gurus, we do need better components.
You can look at the Tracker to see what is the most useful improvement you might make.
Before starting anything, you are advised to discuss your proposal a bit in the development forum.
Database
Supported DBMS
MySql 5 and PostgreSQL are supported. My Sql because it is common and administration is quite simple. PostgreSql because it is completely free software. In the future, we may try other DBMS, but that would require a bigger development team.
In the main sources, avoid SQL statements specific to MySQL or Postgres. When there is no alternative, compatibility procedures should be made. They are all centralized in one unit (unitdatamodule.pas for now).
Table and fields definitions and properties
In Gestinux_util there is a TGTable component used to store all the metadata of tables used in Gestinux. With this component, there is no need to store table definitions elsewhere, and no SQL script is required to initialize or upgrade the database.
The database and table structures are created by the main executable, as specified in unitdatamodule.pas, in TGTable properties. See the component TGTable for more details.