|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | 03-May-2022 | - |
| art/ | H | 03-May-2022 | - | 465 | 394 |
| m4/ | H | 30-Aug-2013 | - | 2,912 | 2,689 |
| po/ | H | 03-May-2022 | - | 9,410 | 7,247 |
| rc/ | H | 03-May-2022 | - | 4 | 2 |
| src/ | H | 30-Aug-2013 | - | 8,215 | 4,994 |
| ABOUT-NLS | H A D | 30-Aug-2013 | 65.8 KiB | 992 | 945 |
| AUTHORS | H A D | 30-Aug-2013 | 35 | 2 | 1 |
| COPYING | H A D | 30-Aug-2013 | 17.6 KiB | 341 | 281 |
| ChangeLog | H A D | 30-Aug-2013 | 12.6 KiB | 372 | 317 |
| Doxyfile | H A D | 30-Aug-2013 | 61.9 KiB | 1,512 | 1,085 |
| INSTALL | H A D | 30-Aug-2013 | 9 KiB | 230 | 175 |
| Makefile.am | H A D | 30-Aug-2013 | 155 | 9 | 3 |
| Makefile.in | H A D | 30-Aug-2013 | 23.9 KiB | 767 | 676 |
| README | H A D | 30-Aug-2013 | 1.8 KiB | 73 | 41 |
| README.xmlrpc | H A D | 30-Aug-2013 | 1.5 KiB | 56 | 39 |
| aclocal.m4 | H A D | 30-Aug-2013 | 74 KiB | 2,017 | 1,808 |
| config.guess | H A D | 30-Aug-2013 | 39 KiB | 1,364 | 1,177 |
| config.h.in | H A D | 30-Aug-2013 | 2.7 KiB | 102 | 69 |
| config.rpath | H A D | 30-Aug-2013 | 14.5 KiB | 572 | 480 |
| config.sub | H A D | 30-Aug-2013 | 28.9 KiB | 1,471 | 1,330 |
| configure | H A D | 30-Aug-2013 | 260.4 KiB | 8,805 | 7,256 |
| configure.ac | H A D | 30-Aug-2013 | 2.7 KiB | 99 | 77 |
| depcomp | H A D | 30-Aug-2013 | 13 KiB | 465 | 298 |
| install-sh | H A D | 30-Aug-2013 | 6.2 KiB | 277 | 169 |
| missing | H A D | 30-Aug-2013 | 10 KiB | 337 | 263 |
| mkinstalldirs | H A D | 30-Aug-2013 | 3.3 KiB | 151 | 102 |
README
1
2 xCHM - the CHM viewer for UNIX
3 (c) 2003 - 2013 Razvan Cojocaru <rzvncj@gmail.com>
4
5
6 * Prerequisites
7
8 In order to be able to compile the code you need to have wxWidgets and
9 CHMLIB installed. You can get wxWidgets from:
10
11 http://www.wxwidgets.org
12
13 Get the GTK+ version (also known as wxGTK). xCHM currently compiles
14 with all flavours of wxWidgets, but only works well and looks truly
15 appealing with wxGTK, so I recommend against bothering to use it with
16 anything else.
17
18 You can get CHMLIB from:
19
20 http://www.jedrea.com/chmlib/
21
22 After you've installed the above you're ready for the next phase.
23
24
25 * Installing
26
27 Type ./configure --help if you're interested in parameters you can pass
28 to configure for compile switches. Most people will be perfectly happy
29 doing a:
30
31 ./configure && make
32
33 Once everything is built, type
34
35 make install
36
37 and the executable should be somewhere in your $PATH (hopefully :)).
38 Now you can just type
39
40 xchm
41
42 and start your session.
43
44
45 * Generating documentation
46
47 If you'd like to generate developer documentation go to the root
48 of the distribution and type
49
50 doxygen
51
52 This of course implies that you have doxygen installed. The documentation
53 will be generated in the doc directory in HTML and LaTex format. The doc
54 directory will be created in the process of creating the documentation so
55 it's ok that it's not present by default in the tarball.
56
57
58 * Legal stuff
59
60 As far as I know this is legal code. If you know that the code is in any
61 way illegal in your country, please drop me a note and stop using it / do
62 not install it.
63
64
65 * Contact
66
67 For bug reports and patches, please use the address above.
68 For everything else, count to 10 and if you still want to send the
69 message, go ahead. Can't promise I'll answer everything though.
70
71
72 * Happy reading!
73
README.xmlrpc
1XmlRpc interface documentation
2
3XmlRpc support enables 3rd party applications to issue load, change page, and
4close instructions to xCHM.
5
6In order to make use of the XmlRpc support in xCHM you must configure with the
7--enable-xmlrpc flag. You must also have the XmlRpc++ (0.7 or higher) library
8installed on your system. You can aquire this library at:
9 http://xmlrpcpp.sourceforge.net/
10
11
12Calls
13param 1
140 - Shuts down xCHM
15
161 - Loads a chmfile specified by param 2, and an optional contextID as param 3
17
182 - Loads a specified contextID within the file as param 2
19
20Results
210 - The request was not completed, this indicates a failure in the command. For
22 example if the call (1,file,id) is made with a valid file, but invalid id
23 the correct file will be loaded but the id will not be. Thus it will report
24 that the request was not completed.
25
261 - The request was completed successfully.
27
28
29Notes:
30
31File paths are relative to the xCHM executable, thus full path names are the
32recommended method for opening files via XmlRpc.
33
34Example using Python:
35
36Launch xCHM with the XmlRpc server activated
37xchm --with-xmlrpc=port
38
39Launch python
40>>> import xmlrpclib
41
42# establish connection to xCHM XmlRpc server
43>>> s = xmlrpclib.Server('http://localhost:port')
44
45# tell xCHM to open /path/to/sch/file.chm
46>>> s.xCHM(1,'/path/to/chm/file.chm')
471 # success
48#tell xCHM to load the contextID from the current file.
49>>> s.xCHM(2,1234)
500 # failure
51>>> s.xCHM(2,1235)
521 # success
53# close xCHM
54>>> s.xCHM(0)
551
56