|
1.1.1
by LaMont Jones
Import upstream version 0.71 |
1 |
Kaptain - Universal Graphical Front-end
|
2 |
---------------------------------------
|
|
3 |
||
4 |
Universal Graphical Front-end for command-line programs. |
|
|
1.1.2
by Tobias Toedter
Import upstream version 0.72 |
5 |
(c) 2000-2004 ZsoltTerék <terek@users.sourceforge.net>
|
|
1.1.1
by LaMont Jones
Import upstream version 0.71 |
6 |
|
7 |
All bug reports and suggestions are welcome. If you have made a |
|
8 |
grammar that can be useful for others, prease send it to me. |
|
9 |
||
10 |
To compile and install, run |
|
11 |
./configure |
|
12 |
make |
|
13 |
make install |
|
14 |
||
15 |
||
|
1.1.2
by Tobias Toedter
Import upstream version 0.72 |
16 |
What's new in Kaptain 0.72
|
17 |
--------------------------
|
|
18 |
||
19 |
Bug fixes and minor changes for Qt 3.3 and gcc-3.3 compatibility. |
|
20 |
Run configure as shown below to specify the qt directory explicitly. |
|
21 |
The script will search for `bin', `include' and `lib' subdirs below.
|
|
22 |
./configure --with-qt-dir=/my/qt/dir |
|
23 |
||
24 |
||
|
1.1.1
by LaMont Jones
Import upstream version 0.71 |
25 |
What's new in Kaptain 0.71
|
26 |
--------------------------
|
|
27 |
||
28 |
Bug fixes and minor changes for Qt 3 and gcc-3.2 compatibility. |
|
29 |
Run configure as shown below to specify qt include directory explicitly. |
|
30 |
./configure --with-qt-dir=/usr/share/qt3 |
|
31 |
||
32 |
||
33 |
UPGRADING FROM Kaptain 0.6
|
|
34 |
--------------------------
|
|
35 |
||
36 |
Since Kaptain 0.7 was completely rewritten, the syntax of grammars has |
|
37 |
changed. To make your scripts work with Kaptain 0.7, check the |
|
38 |
followings: |
|
39 |
- All statements should end with a semicolon (;).
|
|
40 |
This was only needed for rules in Kaptain 0.6, but now it is neccesary |
|
41 |
for descriptions and constraints, too. |
|
42 |
||
43 |
- String constants and regular expressions should be closed on the
|
|
44 |
line they are opened. To write multi-line strings, the only way is |
|
45 |
to use the <<DELIMITER ... DELIMITER form. (Perlish style multiline |
|
46 |
string.) |