… | |
… | |
74 | return load "$HOME/sunday.png"; |
74 | return load "$HOME/sunday.png"; |
75 | } |
75 | } |
76 | } |
76 | } |
77 | |
77 | |
78 | This inner expression is evaluated once per hour (and whenever the |
78 | This inner expression is evaluated once per hour (and whenever the |
79 | temrinal window is resized). It sets F<sunday.png> as background on |
79 | terminal window is resized). It sets F<sunday.png> as background on |
80 | Sundays, and F<weekday.png> on all other days. |
80 | Sundays, and F<weekday.png> on all other days. |
81 | |
81 | |
82 | Fortunately, we expect that most expressions will be much simpler, with |
82 | Fortunately, we expect that most expressions will be much simpler, with |
83 | little Perl knowledge needed. |
83 | little Perl knowledge needed. |
84 | |
84 | |
… | |
… | |
119 | width and doubles the image height: |
119 | width and doubles the image height: |
120 | |
120 | |
121 | scale 0.5, 2, load "$HOME/mypic.png" |
121 | scale 0.5, 2, load "$HOME/mypic.png" |
122 | |
122 | |
123 | IF you try out these expressions, you might suffer from some sluggishness, |
123 | IF you try out these expressions, you might suffer from some sluggishness, |
124 | because each time the terminal is resized, it loads the PNG image agin |
124 | because each time the terminal is resized, it loads the PNG image again |
125 | and scales it. Scaling is usually fast (and unavoidable), but loading the |
125 | and scales it. Scaling is usually fast (and unavoidable), but loading the |
126 | image can be quite time consuming. This is where C<keep> comes in handy: |
126 | image can be quite time consuming. This is where C<keep> comes in handy: |
127 | |
127 | |
128 | scale 0.5, 2, keep { load "$HOME/mypic.png" } |
128 | scale 0.5, 2, keep { load "$HOME/mypic.png" } |
129 | |
129 | |
… | |
… | |
159 | left corner of the terminal window)- the result is pseudo-transparency: |
159 | left corner of the terminal window)- the result is pseudo-transparency: |
160 | the image seems to be static while the window is moved around. |
160 | the image seems to be static while the window is moved around. |
161 | |
161 | |
162 | =head2 COLOUR SPECIFICATIONS |
162 | =head2 COLOUR SPECIFICATIONS |
163 | |
163 | |
164 | Whenever an oprator expects a "colour", then this can be specified in one |
164 | Whenever an operator expects a "colour", then this can be specified in one |
165 | of two ways: Either as string with an X11 colour specification, such as: |
165 | of two ways: Either as string with an X11 colour specification, such as: |
166 | |
166 | |
167 | "red" # named colour |
167 | "red" # named colour |
168 | "#f00" # simple rgb |
168 | "#f00" # simple rgb |
169 | "[50]red" # red with 50% alpha |
169 | "[50]red" # red with 50% alpha |
… | |
… | |
905 | C<keep> block so it only is reevaluated as required. |
905 | C<keep> block so it only is reevaluated as required. |
906 | |
906 | |
907 | Putting the blur into a C<keep> block will make sure the blur is only done |
907 | Putting the blur into a C<keep> block will make sure the blur is only done |
908 | once, while the C<rootalign> is still done each time the window moves. |
908 | once, while the C<rootalign> is still done each time the window moves. |
909 | |
909 | |
910 | rootlign keep { blur 10, root } |
910 | rootalign keep { blur 10, root } |
911 | |
911 | |
912 | This leaves the question of how to force reevaluation of the block, |
912 | This leaves the question of how to force reevaluation of the block, |
913 | in case the root background changes: If expression inside the block |
913 | in case the root background changes: If expression inside the block |
914 | is sensitive to some event (root background changes, window geometry |
914 | is sensitive to some event (root background changes, window geometry |
915 | changes), then it will be reevaluated automatically as needed. |
915 | changes), then it will be reevaluated automatically as needed. |