Customize the design of the substitution table

[Helge]

Is it possible to use a separate CSS file when publishing the substitution table? I find the possibilities to customize the design a bit limited.

[Volker Dirr]

It's not possible at the moment, but i think it is easy to code. Sadly i am very limited this week. I might code it the next weekend.

I am just not sure how to do it best:
a) save the css in the database.
advantage: all users will produce the same output
disadvantage: i need to change the database structure

b) save the css file only local:
advantage: each user can produce a different output (i am not sure. is that useful?). Also no need to change the database.
disadvantage: each user can produce a different output.

What do you suggest? a) or b)

[Helge]

I would prefer b). The CSS file would only have to be created once and can then be uploaded to the server and remain there. Only the HTML file with the current substitution table needs to be uploaded regularly.

[Volker Dirr]

hmm... i fear you misunderstood. TiTiTo is a multi user tool. So if i use variant b) it will be overwritten by other users.
So, reading your reasons, you are in fact for a), because if it is stored in the database each user will have the same file and it won't change by that (in fact always overwriting the same; i might not overwrite if there is a file, but i am sure most guys won't understand that since html is always overwriting too).

[Volker Dirr]

ah... or you was maybe only about thinking about the printing on paper stuff? in that case it doesn't matter of course. But I must also think about guys that use it to print in on a server and display the file on a screen. There will be a problem with variant b) if several users use it.
hmm... i must think carefully about it.

[Volker Dirr]

hmmm... thinking some more is is currently bad that some ccs settings are done in menu "settings", some in the "print" tab and some in the "publish" tab.
i should move
a) all into settings
or
b) all into "print" and "publish" tab

i think the second variant will be better.

maybe the settings in "print" can be stored local, since in normal case you should have a printer local only.

but the settings in "publish" should be stored in database, since in normal case you will publish them on (several) screens.

i must some some more. Not as easy as i thought a few hours ago... (i don't talk about the coding itself; i talk about the "correct" variant where to place and store it.)

[Helge]

At first I only thought of the fact that there is a CSS file on the server and TiTiTo only specifies that it should be used. But your consideration that the CSS settings are stored in the database makes sense.

Variant b), all settings done in the "publish" or "print" tab is better. But then I would prefer that the settings in the "print" tab are also saved in the database. Then the printouts would always be in the same design, no matter on which computer you are working.