- # User set style: font, colour, etc (covers for visually impaired, dislike of fonts, size, and several others)
ita - you had this in your "Unneeded" list. I very much think it should stay on the list. It would solve a lot of issues.
I also like the idea of allowing a picture in the user profile.
you had this in your "Unneeded" list. I very much think it should stay on the list. It would solve a lot of issues.
I think having a set list of style sheets to choose from is a better way to go, honestly. Otherwise we're storing (potentially) a style sheet for every user. A set few -- no images, no white font, large, small -- that's manageable.
And then there's troubleshooting what other people have custom chosen for themselves. I feel a headache coming on.
I don't see the problem of storing a stylesheet for each user, but I see the troubleshooting headaches.
Rather than choosing among a set list of style sheets, maybe set up choices as a drop-down list for each element we want to allow control over?
Rather than choosing among a set list of style sheets, maybe set up choices as a drop-down list for each element we want to allow control over?
I was about to suggest this. They do it that way at LiveJournal, at least at their simplest level of customization.
I don't see the problem of storing a stylesheet for each user
You know me and minimising storage.
I don't see the problem of storing a stylesheet for each user
Which choices do you see as configurable?
They do it that way at LiveJournal, at least at their simplest level of customization.
Which makes me think of all those journals I can't read, but the magic here is that I won't have to. Though I'm wondering if an admin might need the right, for troubleshooting, to assume someone else's ... nah, probably not.
The phrase "If that style is causing problems, don't use that style" seems to work for the admins at LJ.
The phrase "If that style is causing problems, don't use that style" seems to work for the admins at LJ.
But we're not using styles in the way LJ does. If a user changes a passel of individual things and it messes them up, what do we tell them to not use? For that reason, if we don't go with a choice of presets, we should have a "delete all customisations" option.
Here are all the styles defined:
- p, li, td
- tt
- h1
- .biggertext
- .smallertext
- .nametext
- .tagtext
- .titletext
- .logintext
- .plus-sign
- .specialpost
- .thread-desc
- .message-text
- .section-header
- .bigger-section
- .asterisk
- .username
- .buffyquote
- .white-plus-sign
- .white-asterisk
- .bigger-bold
- .normal-text
- .normal-bold
- .normal-blood
- .normal-bold-blood
- .smallerbold
- .normal-italic
- .formtext
- .postnumboxtext
- .formtag
- .formdesc
- .formpost
- .editpost
- .noCSS
- .errortext
- .edited-by
- .spoiler
- .formmenu
- .times
How many of them do you think we should offer up for changes, and what attributes will we allow to be changed?
I really really regret not giving more styles names according to their function rather than what the style looks like. Bad coder! Bad!
Now would be as good a time as any. And by now, I don't mean now, it's just that I have this burst of tidying at precisely the same time other people have lives.
Oh, and Amchau? I don't think PostgreSQL is unneeded.