root/tags/lgt2306/CUSTOMIZE.txt

Revision 3865, 3.1 KB (checked in by pmoura, 14 months ago)

Renamed compiler option "underscore_vars" to "underscore_variables". Renamed compiler option "supports_break_predicate" to "break_predicate". Renamed compiler option "supports_encoding_dir" to "encoding_directive".

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1================================================================
2Logtalk - Open source object-oriented logic programming language
3Release 2.30.6
4
5Copyright (c) 1998-2007 Paulo Moura.  All Rights Reserved.
6================================================================
7
8
9This file contains detailed instructions for customizing your Logtalk
10installation and working environment. Customization is mostly done on
11a per-user basis by editing files on the Logtalk user folder (whose
12path is stored on the LOGTALKUSER environment variable; the folder itself
13can be created by running the "cplgtdirs" shell command).
14
15
161. SETTING LIBRARY PATHS
17
18In Logtalk, a library is simply a directory containing source files. Library
19paths can be declared using a dynamic predicate. This allows compiling and
20loading of libraries and library files to be performed without worries about
21library paths.
22
23Inside your Logtalk user folder, you will find a "libpaths" folder containing
24a sample file which, when loaded, defines the library paths for the Logtalk
25standard library and for all the supplied examples. This file may need to be
26edited to match both your Logtalk installation and your Prolog compiler and
27operating-system requirements. For details, see the "libpaths/NOTES.txt" file.
28
29
302. CUSTOMIZING PROLOG CONFIGURATION FILES
31
32Logtalk interfaces with a specific Prolog compiler via a configuration file
33that can be found on the "configs" folder inside your Logtalk user folder.
34These configuration files can be customized by changing the default values
35of the flags that are used by Logtalk when compiling source files. For a
36full description of these flags, consult the "Running and debugging Logtalk
37programs" section of the User Manual. Some of the default flags that you may
38want to change include: "smart_compilation", "startup_message", "altdirs",
39"tmpdir", "portability", "underscore_variables", and the documentation-related
40flags ("xmldocs", "xmldir", "xslfile", "xmlspec", and "xmlsref"). Be sure
41to read the "configs/NOTES.txt" file for Prolog specific notes; some Prolog
42compilers do not support the whole range of compilation flag values. 
43
44
453. CUSTOMIZING DOCUMENTATION PROCESSING SCRIPTS AND SUPPORTING FILES
46
47Inside your Logtalk user folder, you will find a "xml" folder containing a
48set of shell scripts, CSS and XSLT style-sheets, and DTD and XML Schema files
49for processing the XML documenting files that are automatically generated
50when you compile source files. You may want to customize the CSS and XSLT
51files to modify the layout or style of the resulting PDF/(X)HTML files or to
52write new scripts and transformations to generate other formats. You may also
53edit the file "custom.ent" in order to specify XML entities for your personal
54data that can be used on Logtalk documenting directives. For details, see the
55"xml/NOTES.txt" file.
56
57
584. ADDING SUPPORT FOR EDITING LOGTALK SOURCE FILES TO TEXT EDITORS
59
60Inside your Logtalk user folder, you will find a "wenv" folder, containing
61configuration files for several text editors, which add support for syntax
62highlighting and other text editing services for Logtalk source files.
63For details, see the "wenv/NOTES.txt" file.
Note: See TracBrowser for help on using the browser.