Here is some general information about the development of Laidout. As with any project, testers and coders are certainly encouraged to test and code!
Some general links which might be relevant:
Laidout has so far been coded by one person, Tom Lechner, along with a few patches and a translation submitted by various people. It would be pleasant if more people were involved!
Laidout is built on the Laxkit, whose sole purpose for existence at the moment is to be the windowing backbone of Laidout. Anything said about Laidout applies just as much to the Laxkit.
There is copius doxygen style source code documentation for you to whet your appetite, which is easily accessible by running "make docs", which basically just tells doxygen to do its thing. Running "make alldocs" will build all the documentation for Laidout and for the Laxkit, as long as you have a link in the top Laidout directory pointing to wherever you have the Laxkit source files. For release tarballs, the Laxkit is there already.
You can download the cutting edge, latest and (ideally) greatest version of Laidout from the git repository with this command:
Compiling directly from the dev source has a couple more steps then compiling a normal release. It is assumed that those compiling from dev source like pain. In a nut shell, you must install dependencies, download Laidout source, download Laxkit source, configure, compile, then make the icons.
- Install dependencies
On debian systems, you can use the following command to install everything for all current extensions:
apt-get install g++ pkg-config libpng12-dev libreadline-dev libx11-dev libxext-dev libxi-dev libxft-dev libcups2-dev libimlib2-dev libfontconfig-dev libfreetype6-dev libssl-dev xutils-dev libcairo2-dev libharfbuzz-dev libsqlite3-dev libgraphicsmagick++1-dev mesa-common-dev libglu1-mesa-dev libftgl-dev zlib1g-dev
On Fedora, you can install these with:
sudo dnf install -y cairo-devel cups-devel fontconfig-devel ftgl-devel glibc-headers harfbuzz-devel imlib2-devel lcms-devel libpng-devel libX11-devel libXext-devel libXft-devel libXi-devel mesa-libGL-devel mesa-libGLU-devel openssl-devel readline-devel sqlite-devel xorg-x11-proto-devel zlib-devel GraphicsMagick-c++-devel libstdc++-devel freetype-devel imake
- Compile everything
Hopefully, this will run without errors:
git clone https://github.com/Laidout/laidout.git
git clone http://github.com/Laidout/laxkit.git laxkit
At this point, Laidout is ready to run. You don't actually have to install it anywhere to make it run, you can just run src/laidout, though icons may not show up automatically without installing (see next section).
You may notice tons of garbage outputting to the console when you run this development source. This is info that is sometimes helpful for debugging. You can hide all this by running "make hidegarbage" before running "make", or by running with ./laidout 2> /dev/null.
You can modify ~/.config/laidout/(version)/laidoutrc to point to an icon directory that contains the icons (i.e. /path/to/laidout/src/icons).
If you need to generate the icons, they are currently created from source svg files in laidout/src/icons and laidout/laxkit/src/icons. Each source svg is scanned and broken down into individual icon pngs. You need to have compiled Laidout already, then:
Any translations done for either messages in Laidout itself, or of the Laidout web pages are greatly appreciated.
Translating Laidout to new languages is mainly a matter of translators translating a
couple thousand little words and phrases
from a file called laidout.pot.
Normally, you take that file, rename it to es.po (a spanish translation, for example), and then update all the strings in it.
You can do this by hand, or you might use a program like
Lokalize or poedit.
Once translated, the whatever.po needs to end up in the src/po directory of the Laidout source code. There is a README file in that directory with a lot more of the nitty gritty details for dealing with translation files, such as how to merge a new translation with an old one.
Current Translations (french and spanish translations getting very out of date)
- American (that is to say U.S.) English
- Spanish. from my slight knowledge of Spanish, and google translations
- French. by Nabyl Bennouri
Documentation for the Laidout file format is found easily through running:
This will dump out a pseudo-Laidout file with copious comments about each of the possible Laidout file elements. The format itself is an indented data file format, sort of in the same spirit of yaml, but is slightly more ad-hoc, making it even easier to read and figure out, in this developer's opinion. Laidout's indented format is simply a collection of nested name-value pairs, where both are scanned in as strings, at which point it is up to the application to decipher the strings into integers, points, and whatnot.