about summary refs log tree commit diff stats
path: root/WWW/Library/Implementation/HTPlain.h
blob: 24fd66913113ae544e9bd360cc1a99ebf0d4421a (plain) (blame) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

/*                  /Net/dxcern/userd/timbl/hypertext/WWW/Library/Implementation/HTPlain.html
                                    PLAIN TEXT OBJECT
                                             
 */
#ifndef HTPLAIN_H
#define HTPLAIN_H

#include <HTStream.h>
#include <HTAnchor.h>

#ifdef __cplusplus
extern "C" {
#endif
    extern HTStream *HTPlainPresent(HTPresentation *pres,
				    HTParentAnchor *anchor,
				    HTStream *sink);

#ifdef __cplusplus
}
#endif
#endif				/* HTPLAIN_H */
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-15 00:59:05 +0000
about the color of a part of the titlebar now. There are a number of context tags, specified in /ranger/gui/context.py in the constant CONTEXT_KEYS. A Context object, defined in the same file, contains attributes with the names of all tags, whose values are either True or False. Implementation in the GUI Classes --------------------------------- The class CursesShortcuts in the file /ranger/gui/curses_shortcuts.py defines the methods color(*tags), color_at(y, x, wid, *tags) and color_reset(). This class is a superclass of Displayable, so these methods are available almost everywhere. Something like color("in_titlebar", "directory") will be called to get the color of directories in the titlebar. This creates a ranger.gui.context.Context object, sets its attributes "in_titlebar" and "directory" to True, leaves the others as False, and passes it to the colorscheme's use(context) method. The Color Scheme ---------------- A colorscheme should be a subclass of ranger.gui.ColorScheme and define the method use(context). By looking at the context, this use-method has to determine a 3-tuple of integers: (foreground, background, attribute) and return it. foreground and background are integers representing colors, attribute is another integer with each bit representing one attribute. These integers are interpreted by the used terminal emulator. Abbreviations for colors and attributes are defined in ranger.gui.color. Two attributes can be combined via bitwise OR: bold | reverse Once the color for a set of tags is determined, it will be cached by default. If you want more dynamic colorschemes (such as a different color for very large files), you will need to dig into the source code, perhaps add an own tag and modify the draw-method of the widget to use that tag. Run tc_colorscheme to check if your colorschemes are valid. Specify a Colorscheme --------------------- Colorschemes are searched for in these directories: ~/.config/ranger/colorschemes/ /path/to/ranger/colorschemes/ To specify which colorscheme to use, define the variable "colorscheme" in your options.py: colorscheme = "default" This means, use the colorscheme contained in either ~/.config/ranger/colorschemes/default.py or /path/to/ranger/colorschemes/default.py. Adapt a colorscheme ------------------- You may want to adapt a colorscheme to your needs without having a complete copy of it, but rather the changes only. Say, you want the exact same colors as in the default colorscheme, but the directories to be green rather than blue, because you find the blue hard to read. This is done in the jungle colorscheme ranger/colorschemes/jungle, check it out for implementation details. In short, I made a subclass of the default scheme, set the initial colors to the result of the default use() method and modified the colors how I wanted. This has the obvious advantage that you need to write less, which results in less maintainance work and a greater chance that your colorscheme will work with future versions of ranger.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-15 00:59:01 +0000