Implement custom theming #17
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Depends on
#4 Add footer to each page
meta/site
#14 new network application
meta/site
#15 Add Git Server to navbar
meta/site
Reference: meta/site#17
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'd like to implement trinity's javascript sheet selector. Here's the relevant page on their site.
I'm going to rewrite some of the site to use divs so that theming is more intuitive.
oops my bad. i need to change the colors of these buttons i thought it was a cancel button
@emma what are the dependencies for?
I want to implement those before I start work on this.
But is this absolutely necessary? If not, the dependencies aren't either.
Maybe we can convey priority some other way? Maybe project boards with different columns for high versus low priorities.
It doesn't really need to be conveyed in another way if these things need to be done before I do this.
The point of sheets.js and cookies.js (both are public domain, changes can be relicensed freely) are to be very simple drop-in scripts that only need a boilerplate change and maybe a bit of love in order to work. css/ is now an m4 file that's generated out into HTML but I think that makes it easier to see the format of the selector (where
$1
is the name of the CSS file):Then at the bottom of the selection page:
This requires my js/cookies.js, js/sheets.js, and adding the following boilerplate to pages' heads:
Or something like that. I could probably do it myself to a website in an hour or so, certainly it would take a lot less time than I did to write these scripts (coming up with them was a pain and it would probably take me about as long to re-implement them).