librfm  5-
About: Librfm is a basic library for the Rodent (file management) applications.
  Fossies Dox: librfm5-  ("unofficial" and yet experimental doxygen-generated source code documentation)  

No Matches
librfm Documentation

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the steelblue colored "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies librfm5- contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).
Librfm and librodent

To regenerate the build system entirely, you should execute the ./
script. In order for this to work, you need have autoconf, automake, autoheader,
libtool, aclocal, intltool, gettext installed.

This library contains the basic functions for rodent file manager and other 
applications like rodent-diff. Librfm contains the primary functions
which get loaded first. Librodent consists of secondary functions which 
are loaded later on. The idea to split the library into two is to speed 
up initial load. Furthermore, actions which require user input are put into
modules so that they will get loaded on demand and only when needed (again,
there is no need to slow things down when they can be done more efficiently).

Loading the secondary library into memory can wait until after primary
library is loaded. Thus, actions which only require primary library can
 be executed before secondary library is loaded. Or something along those 

The modules, mentioned above, are a responsibility of the application, not 
the library. So you won't find them here.