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