There’s yet no packaged release of this project an you should download the subversion sources. These sources are subject to changes and might even not compile ! For any problem write to devel.
Since Jabberwocky++ is an Emacs interface, Emacs is absolutely required. It is needed to run Jabberwocky++ as well as to compile it. Jabberwocky++ has been yet tested with Emacs 22. I suspect that it will not run neither compile with versions lower thant 19. Anyway, since Eieio is required to run and compile Jabberwocky++, any restriction for Emacs version on Eieio will apply for Jabberwocky++ as well (see I.1.2.)
The whole Cedet project is not needed but only the Eieio part which is the CLOS implementation used by Jabberwocky++.
Nowadays if you have Emacs 24 or more recent versions you no longer need to install eieio separately since eieio is now part of Emacs. Anyway implementation has changed between 24 and 25 version. There is a compatibility module in Jabberwocky++ but it is possible that it lacks certain features. In fact Jabberwocky++ is known to work well with Emacs 25 or 26 …
A Svn client is needed to download Jabberwocky++s sources.
To download the sources simply type :
. Be patient when doing that since process may be slow due to server capacities en size of the package that is big. But please wait until transfer has finished or Svn reports an error.
Due to certain class dependencies Edext package should be downloaded and copiled as well. Things should certainly be reorganized in the future to make them more independent. so issue as well :
Notice that if you have already downloaded one of the archives above, or one of them, you might simply enter the so created directory and type :
Due to ede administration of the package a simple make may fail to compile the Jabberwocky++ system.
Enter successively directory where you downloaded Edext and that where you downloaded Jabberwocky++ and in both of them issue :
To use Jabberwocky++ in your Emacs, the directory where you downloaded both Jabberwocky++ and Edext should be part of the emacs loadpath. After compilation code is in this directory as well. Then simply put in your .emacs file (require ’j++).
A minimal .emacs file could look like that :
(add-to-list ’load-path (expand-file-name "~/jabberwocky")) (add-to-list ’load-path (expand-file-name "~/edext")) (require ’j++)
Jabberwocky++ contains a batch of basic classes contained in the basic subdirectory of the root project directory and packages that implement interfaces to Emacs external programs or some internal engines as well. To be a simple user of Jabberwocky++ packages features you need not knowing was class here means. if you want to learn more about the whole stuff implementation refer to A section.
The j++ browser package (cf. II.1 ,) implements a web browser. It still lacks many features but its object implementation allows very modular and simple improvements.
The j++ sound system (cf. II.2 ,) implements an Ecasound interface (through the EcaScheme client server API), an Mplayer interfaces as well as an aplay interface.
All these interfaces are based on the subsystem concept (cf. II.0 ,) and to use them you should first have a look at section II.0.2 to see how to launch them. There will maybe exist a more automated procedure in the future, but you have at the moment to execute all steps manually.
|Apache/2.4.38 (Unix) PHP/7.3.2 SVN/1.11.1|