File: README

package info (click to toggle)
libooc-vo 20010807-2
  • links: PTS
  • area: main
  • in suites: woody
  • size: 2,060 kB
  • ctags: 42
  • sloc: sh: 235; makefile: 195; ansic: 28
file content (151 lines) | stat: -rw-r--r-- 5,560 bytes parent folder | download | duplicates (2)
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
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151

                             VisualOberon
                             ------------

This is a version of VisualOberon (VO). The purpose of this
text is to give a short introduction to VO and the purpose of this
release. Also included is a description of what the various files
in this archive are and how the can be grouped into parts with
different functionalliy.

Also you can find information how to compile/install VisualOberon in
this file.

Fore even more informationen look at the homepage of the
VisualOberon project:

http://ping.de/sites/edge/VisualOberon.html


Why this release?
-----------------

A more in detail desription of the purpose of this release can be found
in the file ABOUT in the same directory.


What do you need to use VO?
---------------------------

You need to install a number of programms/packages before you can
compile and use VisualOberon.

Please look at the VisualOberon homepage for information about this
packages, how to get and how to install them.

VO was implemented using Linux for x86 (Currently current Debian version)
under GNOME. However different versions of VisualOberon have
been successfully compiled under various unix-plattforms which
support X11. So no problems should occure.


How to compile and install?
---------------------------

Copy the complete archive anywhere you like and where you can compile
it using oo2c.

Call the configure script located in the main directory of the archive.
Call "configure --help" to see what options you can set.

The configure script the will find out what software you have installed
and where it is placed. It exspecially looks for imlib and the various
libraries supported by imlib. Imlib is a library supporting the loading
of various graphics formats.

At the end fo the analysis of your system the configure script will
generate a makefile.

To then compile VisualOberon just type "make". The makefile will then
automatically compile a static or dynamic library (depended of your
system features).

After that you can type "make install" which will install the created
library within the oo2c directry tree. Note, that you may need special
rights on your system to install VisualOberon. You may have to be
superuser.

After that VisualOberon has been installed and you can then start
hacking away.

For first test, go to the "demos" subdirectory and just type "make"
again. This will compile a number of  demos. Note, that you can only
compile the demos successfully when you have installed VO before
(make install).

After that you can run the demos and watch. A short description of the
demos can be found in the info documentation, too.

If you just want to install the library without the sources (maybe because
you want to modify and improve VisualOberon itself and thus want to
hold the sources local. You may have to enhance the various search paths
in your local "~/.oo2crc" file to do this.) you can type "make installlib"
on the command shell. This will compile the current local sources,
generate a library (you may have to do a "make clean"the remove the old
local copy of the library) and then installs it.


Preferences setting.
--------------------

If you want to change the look and the behaviour of the used objects
you can use the VisualPrefs program, which will also be compiled while
creating the demos.

For using preferences setting You also need to create a directory
named .VisualOberon in your home directory. That is where all the
textual configuration files are stored.

You can then start the VisualPrefs program, make your changes and
save them. This will result in  human readable file within the
.VisualOberon directory.

The used colors and fonts (and some other settings) cannot be changed from
within VisualPrefs because VisualOberon does not yet support color and
font selectors. You have to edit the "Display"-files in your
".VisualOberon" directory by hand after storing the settings to create
them.


What is the function of the different modules?
----------------------------------------------

See the supplied texinfo/info/dvi documentation for more information
about each module and a general cross reference of the classes
and methods supplied by VO.


Where to start investigating the source?
----------------------------------------

Starting point for an in-to-deep lecture of the current sources of VO
are the three main modules "VO:Object", "VO:Base:Object", "VO:
Base:Display" and VO:OS:Display.

I have tried to comment them as fully as possible. However, if there are
any questions I will give you as much help as possible. For people who want
to write their own objects, I've also put a number of comments in
"VO:Button", so take a look at it, too. Use the suplied docmentation in the
"docs" subdiretcory for a detail description of VisualOberon and its
concepts. It also contains automatically generated crossreferences
for the sources.


I want to help, what can I do?
------------------------------

Read ABOUT in the same directory and the documentation given in
various formats. It should answer all your questions. However if there
are still unanswered questions, mail me or subscribe to the mailinglist.


Copyright?
----------

The VisualOberon library itself is under the GNU LIBRARY GENERAL PUBLIC
LICENSE if not otherwise stated. Read the file COPYING.LIB for more
information.

The rest of the package - exspecially the various demo programs - is, if not
otherwise stated under the GNU GENERAL PUBLIC LICENSE. Read the file COPYING
that comes with this package for more information.