Concerning Re: exclude parts of a file from ve
Bogdan Cristea wrote on 5 Aug 2008, 10:30, at least in part:
> You could separate those parts into different files.
As said this would make things more difficult - bloating the script
with use cases & conditions, the config clumsy, and even more
complicated for the users who incidentally are not programming
literate - they write content and the script shall enable them to add
it to the website easily and in bigger chunks than one by one. I
can train them to edit some parts of the output embedded in the
Perl code or move them around and even to add something
following the given pattern, but only as long as they see things in
the general context. Just giving them a bunch of (explained)
variables in a config file would be too complicated for them to
understand what actually will happen. IOW, within the full block of
print to file code they recognize how their content will come out in
HTML. From config variables they won't.
Separating the main config (input filename, location of images,
where to put the output to) would be no issue, but part of the output
production (print to file) has to be adjusted for each use (e.g. actual
position of the image, standard copy each item might receive or
not, depending on what it is).
Jan Hendrik
---------------------------------------
Freedom quote:
If there is any fixed star in our constitutional constellation,
it is that no official, high or petty, can prescribe
what shall be orthodox in politics, nationalism, religion,
or other matters of opinion or force citizens to confess by word
or act their faith therein.
-- Robert H. Jackson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-05 11:27:01 CEST