root/tags/lgt2293/QUICK_START.txt

Revision 3297, 3.6 KB (checked in by pmoura, 23 months ago)

Updated release number to 2.29.3.

  • 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.29.3
4
5Copyright (c) 1998-2007 Paulo Moura.  All Rights Reserved.
6=================================================================
7
8
9Quick start
10===========
11
12
131. Install Logtalk by using either the installer provided for your
14operating-system (when available) or by following the instructions
15on the "INSTALL" file. Depending on your operating-system, working
16environment, and favorite Prolog compiler, you may already have a
17script or a shortcut installed for easily running Logtalk with your
18favorite Prolog compiler. If so, skip the instructions below for
19starting up Logtalk.
20
212. Open the "manuals/index.html" file with a web browser.
22
233. Select the "Tutorial" link. This will provide you with a basic
24understanding of the main Logtalk concepts.
25
264. Go back to the "index.html" file and select the "User Manual"
27link and then the Installing and running Logtalk links. This will
28provide you with a basic understanding of how to start Logtalk and
29compile and load Logtalk code.
30
31
32Assuming that Logtalk supports your Prolog compiler:
33
341. Read the "NOTES" file in the "configs" sub-directory to check if
35any patch or workaround is needed for your compiler.
36
372. Start your Prolog compiler.
38
393. Change the current working directory of your Prolog session to the
40Logtalk installation directory. If you don't know which predicate to
41use, check the "configs/NOTES" file or your Prolog compiler reference
42manual.
43
444. Compile and load the config file for your Prolog compiler.
45
465. Compile and load the Logtalk compiler/runtime found on the "compiler"
47sub-directory.
48
496. Adapt, if needed, the file "libpaths/libpaths.pl" to match your Logtalk
50installation, Prolog compiler, and operating-system, and then compile and
51load it.
52
53Note that both the configuration files, the compiler/runtime files, and the
54library paths file are Prolog files. The predicate used to load these files
55depends on your Prolog compiler (consult your Prolog compiler documentation
56or take a look at the definition of the predicate '$lgt_load_prolog_code'/1
57in the config file. For most command-line compilers, you could type at the
58Prolog prompt something like:
59
60    | ?- ['configs/foo.config', 'compiler/logtalk.pl', 'libpaths/libpaths.pl'].
61
62Replace the file name foo.config with the appropriated config file name for
63your compiler.
64
65
66Now you may try some of the included examples:
67
681. Open the examples sub-directory. There you find several sub-directories
69with ready to run examples and a NOTES file containing general instructions
70and a brief description of each example. Select and open one of the examples
71sub-directory.
72
732. Read the example NOTES file for a description of the example.
74
753. Open the SCRIPT file for instructions on how to load the example and for
76sample queries that you may try by copying-and-pasting or dragging-and-droping
77them on your Prolog interpreter top-level.
78
79
80Ready to start writing your own programs?
81
821. Read the User Manual sections on "Programming in Logtalk" and "Running
83and debugging Logtalk programs".
84
852. Take a look at the "wenv" sub-directory. There you will find syntax
86configuration files for popular text editors that enable syntax coloring
87and other goodies when editing Logtalk source files.
88
893. Create a sub-directory with a suitable name to hold all the files of
90your application. You may want to add the directory path to the libpaths.pl
91file mentioned above in order to easily load your application.
92
934. Copy to this sub-directory a loader file from one of the example
94directories and modify it to load your own source files.
95
965. Have fun!
Note: See TracBrowser for help on using the browser.