On Nov 28, 2017, at 3:12 AM, Johan Kuuse <[email protected]> wrote: > > I think the one important thing is that all involved HTML elements have a > 'class' or 'id' tag.
Yes. Several times in making my last custom Fossil skin, I’ve had to employ some rather clever CSS selector trickery to target the elements I was interested in, when it would have been simpler if the elements could have been targeted directly. All these duplicate id and class attributes compress very nicely, so they’re not very costly. It’s just tedious to remember to add them in the Fossil source ahead of need. I don’t know that *every* tag needs to have an id or class, but if you can think of a way to identify or classify an element, someone else can probably think of a way to style it specially. > Some people like borders and rounded corners, others don’t. Yes, so rather than try to please everyone, let’s ship something that is pleasant enough to ward off charges of ugly defaults, but which gives lots of ideas for tweaking, to inspire custom skins. In a word, the new design should be “featureful.” It’s easier to see something and say, “I don’t like that, it should be like *so*,” than to have a page you consider ugly because it lacks enough styling for your taste, but where all the affordances to fix that are hidden as currently-unused id and class tags. So, when adding new id and class attributes, think also of a way to show them off visually via the default skin. If someone doesn’t like the new styling, they can strip it back off with a bit of CSS tweaking. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
