On Sat, Dec 18, 2021 at 4:44 PM Valentin Petzel <valen...@petzel.at> wrote:


> And please don't feel offended by my last mail, I'm not in the best shape,
> as a friend of mine killed himself recently.
>
>
Hello Valentin,

This is really sad news, especially if it happens at a time of pandemic,
which in itself is hard. As a personal advice I tell you: dedicate your
time as much as possible to programming in these months, this will help you
to distract yourself. Don't worry about me, I didn't feel offended at all.
I was just sorry to see a so helpful and active helper/contributor like you
being unmotivated to participate in discussions.


>
> I did not mean a random specification, but a very important core
> specification at a random point.
>

If you read again my posts, you will find the core specification, with a
specific word, since the very first posts of this thread, not at a random
place. And I repeated it several times. The magic word is: *template*.
At a certain point, Jean highlighted the fact that LP currently lacks the
ability of stylesheeting in an easy way; then you focused the problem. But
the big picture is that LP currently lacks the ability of easy-templating
(and the stylesheet is only a part of this context). Currently, LP supports
only one generic template out of the box (header, body, footer), which
therefore needs to be customized (and its customization is somewhat
uncomfortable) for any variation. Customizing a template, as a general
procedure, is not a good idea, for several reasons, including readability
of the code and maintenance. Therefore, typography programs offer a *set*
of templates: then you pick the one that is closest to your specs, and do
customizations only if you really need to. Then your code is *clean*. To be
even more clear: the kind of customization you wanted to do is a hackish
and messy one. In fact, you violate the template rule by putting what
should be part of the body in the footer, by swapping it from the header
(!) ad using a non pertinent field (copyright) (with low-level functions).
This is not how I would proceed. I would avoid hacks at all on templates.
And I would customize templates only for dummy things (for example:
swapping header with footer) and only if I really need to.
I really don't know how to explain it better. But in any case, please read
again the previous posts with these observations.

Hold on for the bad period. I'm sure it will go away, after some time. And
consider this thread a way to get distracted from it...

Best,
Paolo

Reply via email to