Revision 048f2af4
Von Kivitendo Admin vor fast 10 Jahren hinzugefügt
SL/Layout/Base.pm | ||
---|---|---|
105 | 105 |
sub get_stylesheet_for_user { |
106 | 106 |
my $css_path = 'css'; |
107 | 107 |
if (my $user_style = $::myconfig{stylesheet}) { |
108 |
$user_style =~ s/\.css$//; # nuke trailing .css, this is a remnand of pre 2.7.0 stylesheet handling
|
|
108 |
$user_style =~ s/\.css$//; # nuke trailing .css, this is a remnant of pre 2.7.0 stylesheet handling
|
|
109 | 109 |
if (-d "$css_path/$user_style" && |
110 | 110 |
-f "$css_path/$user_style/main.css") { |
111 | 111 |
$css_path = "$css_path/$user_style"; |
... | ... | |
179 | 179 |
|
180 | 180 |
=head1 DESCRIPTION |
181 | 181 |
|
182 |
For a description about the external interface of layouts in general see
|
|
182 |
For a description of the external interface of layouts in general see
|
|
183 | 183 |
L<SL::Layout::Dispatcher>. |
184 | 184 |
|
185 | 185 |
This is a base class for layouts in general. It provides the basic interface |
... | ... | |
189 | 189 |
=head1 IMPLEMENTING LAYOUT CALLBACKS |
190 | 190 |
|
191 | 191 |
There are eight callbacks (C<pre_content>, C<post_content>, C<start_content>, |
192 |
C<end_content>, C<stylesheets>, C<stylesheets_inline>, C<javscripts>, |
|
192 |
C<end_content>, C<stylesheets>, C<stylesheets_inline>, C<javascripts>,
|
|
193 | 193 |
C<javascripts_inline>) which are documented in L<SL::Layout::Dispatcher>. If |
194 | 194 |
you are writing a new simple layout, you can just override some of them like |
195 | 195 |
this: |
... | ... | |
265 | 265 |
|
266 | 266 |
=head1 GORY DETAILS ABOUT JAVASCRIPT AND STYLESHEET OVERLOADING |
267 | 267 |
|
268 |
The original code used to store one stylehsheet in C<< $form->{stylesheet} >> and
|
|
268 |
The original code used to store one stylesheet in C<< $form->{stylesheet} >> and |
|
269 | 269 |
allowed/expected authors of potential C<bin/mozilla/> controllers to change |
270 | 270 |
that into their own modified stylesheet. |
271 | 271 |
|
272 | 272 |
This was at some point cleaned up into a method C<use stylesheet> which took a |
273 | 273 |
string of space separated stylesheets and processed them into the response. |
274 | 274 |
|
275 |
A lot of controllers are still using this methods so the layout interface
|
|
276 |
supports it to change as few controller code as possible, while providing the
|
|
275 |
A lot of controllers are still using this method so the layout interface |
|
276 |
supports it to change as little controller code as possible, while providing the
|
|
277 | 277 |
more intuitive C<add_stylesheets> method. |
278 | 278 |
|
279 | 279 |
At the same time the following things need to be possible: |
... | ... | |
299 | 299 |
|
300 | 300 |
Sanitizing |
301 | 301 |
|
302 |
C<stylesheets> needs to retain it's sanitizing behaviour.
|
|
302 |
C<stylesheets> needs to retain its sanitizing behaviour. |
|
303 | 303 |
|
304 | 304 |
=item 4. |
305 | 305 |
|
... | ... | |
309 | 309 |
|
310 | 310 |
=item 5. |
311 | 311 |
|
312 |
Preserving of Inclusion Order
|
|
312 |
Preserving Inclusion Order |
|
313 | 313 |
|
314 | 314 |
Since there is currently no standard way of mixing own content and including |
315 | 315 |
sub layouts, this has to be done manually. Certain things like jquery get added |
Auch abrufbar als: Unified diff
Typos in Dokumentation