root/tags/lgt2261/QUICK_START

Revision 2470, 3.5 KB (checked in by pmoura, 3 years ago)

Updated release number to 2.26.1.

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