1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
# Copyright 1999 Daniel Elphick and others
# Licensed under Eiffel Forum Freeware License, version 1;
# (see forum.txt)
To compile eglade you will need smalleiffel, gobo and eGTK.
See the RELEASE file for the current versions.
Eglade will only work with smalleiffel, because it generates a loadpath.se
file and no Ace file for use with ISE. It should be possible to make an Ace
file yourself easily enough, but I don't have ISE.
Compile Instructions
====================
In the top-level directory of eglade, type:
make
Usage
=====
eglade -
Makes eglade parse standard input. Seems a bit useless to me so I might
remove it
eglade <project>
Makes eglade parse <project>, where <project> is an XML file
produced by glade..
eglade generates a class <base>.e where <base> is defined in the glade
file <project> and certain other classes dependent on what windows have
been defined.
Generated Classes
=================
The root class of the generated code is the project name (shifted to
upper case). There is a separate class for each top-level window
(main windows, dialogs and pop-ups) and there is a once instance of
each of these in the class TOP_LEVEL_WINDOWS. CUSTOMISATION contains
the application name and version number.
CUSTOMISATION is an example of a preserved class, which does not get
overwritten if the project is regenerated; other preserved classes are
signal handlers. These classes are those where the programmer is
expected to write the particular logic for each program.
A preserved class may be identified by the `on_regeneration' line in each
class's indexing section. A preserved class will read:
on_regeneration: "The current class text will be preserved"
whereas all other classes read:
on_regeneration: "This class text will be overwritten"
Clearly, there is no point in writing your own code in the latter type
of class!
Problems
========
Look in the TODO list for things that aren't implemented totally
eglade was written by me, Daniel Elphick and I can be contacted at :
de397@ecs.soton.ac.uk
It was sponsored by LFIX Limited : info@lfix.co.uk
|
