root/tags/lgt2220/QUICK_START

Revision 1733, 3.1 KB (checked in by pmoura, 4 years ago)

Updated for changes in Logtalk version 2.22.0.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1=================================================================
2Logtalk - Object oriented extension to Prolog
3Release 2.22.0
4
5Copyright (c) 1998-2004 Paulo Moura.  All Rights Reserved.
6=================================================================
7
8
9Quick start
10===========
11
12
131. Install Logtalk by following the instructions on the "INSTALL" file.
14
152. Open the "manuals/index.html" file with a web browser.
16
173. Select the "Tutorial" link. This will provide you with a basic understanding
18of the main Logtalk concepts.
19
204. Go back to the "index.html" file and select the "User Manual" link and then
21the Installing and running Logtalk links. This will provide you with a basic
22understanding of how to start Logtalk and compile and load Logtalk code.
23
24
25Assuming that Logtalk supports your Prolog compiler:
26
271. Read the "NOTES" file in the "configs" sub-directory to check if any patch
28or workaround is needed for your compiler.
29
302. Start your Prolog compiler.
31
323. Change the current working directory of your Prolog session to the Logtalk
33installation directory. If you don't know which predicate to use, check the
34"configs/NOTES" file or your Prolog compiler reference manual.
35
364. Compile and load the config file for your Prolog compiler.
37
385. Compile and load the Logtalk compiler/runtime found on the "compiler"
39sub-directory.
40
416. Adapt, if needed, the file "libpaths/libpaths.pl" to match your Logtalk
42installation, Prolog compiler, and operating-system, and then compile and
43load it.
44
45Note that both the configuration files, the compiler/runtime files, and the
46library paths file are Prolog files. The predicate used to load these files
47depends on your Prolog compiler (consult your Prolog compiler documentation
48or take a look at the definition of the predicate '$lgt_load_prolog_code'/1
49in the config file. For most command-line compilers, you could type at the
50Prolog prompt something like:
51
52    | ?- ['configs/foo.config', 'compiler/logtalk.pl', 'libpaths/libpaths.pl'].
53
54Replace the file name foo.config with the appropriated config file name for
55your compiler.
56
57
58Now you may try some of the included examples:
59
601. Open the examples sub-directory. There you find several sub-directories
61with ready to run examples and a NOTES file containing general instructions
62and a brief description of each example. Select and open one of the examples
63sub-directory.
64
652. Read the example NOTES file for a description of the example.
66
673. Open SCRIPT file for instructions on how to load the example and for sample
68queries that you may try by copying-and-pasting or dragging-and-droping them
69on your Prolog interpreter top-level.
70
71
72Ready to start writing your own programs?
73
741. Read the User Manual sections on "Programming in Logtalk" and "Running and
75debugging Logtalk programs".
76
772. Take a look at the "wenv" sub-directory. There you will find syntax
78configuration files for popular text editors that enable syntax coloring
79when editing Logtalk source files.
80
813. Create a sub-directory with a suitable name to hold all the files of your
82application.
83
844. Copy to this sub-directory a loader file from one of the example directories
85and modify it to load your own source files.
86
875. Have fun!
Note: See TracBrowser for help on using the browser.