summaryrefslogtreecommitdiff
path: root/util/skingen.pl
AgeCommit message (Collapse)AuthorFilesLines
2009-01-15Moving style.css to data/Yorhel1-1/+1
2009-01-02Added possibility to hide the main title in skinsYorhel1-0/+2
Simply set the 'maintitle' to '0'
2009-01-02Fixed skin generator bug with \r characters in the conf fileYorhel1-0/+1
2008-12-23Added simple CSS compressionYorhel1-1/+10
...by removing all newlines, whitespace and comments from the generated CSS file. None of the CSS sent to the browser is maintained by hand now, so adding some compression is easy. :-) This compression is disabled if the debug config flag is enabled, considering debugging an unreadable CSS file isn't fun.
2008-12-23Removed skin directory name from the config files, and renamed fullname to nameYorhel1-4/+5
2008-12-23A DRY appreach to skins: there's only one main CSS file nowYorhel1-197/+11
So, instead of using separate smaller CSS files to overwrite directives in the main (/static/f/style.css) file, I decided to generate one CSS file for each skin, which includes everything needed to render the page. The template for this skin is now /data/skingen/style.css. I just don't feel like maintaining two separate files when changing something to the CSS. Also converted the old layout into a skin directory (angel), since the default skin isn't in the CSS template anymore.
2008-12-23Added grey layout for testing purposes and fixed a few bugs with the skin ↵Yorhel1-2/+2
generator
2008-12-21Made the category colors on VN edit changable in CSSYorhel1-0/+5
...but not yet in the skin generator, as I haven't really decided yet whether to generate those colors based on the other colors, or to make them configurable from the skin config (= more work for the people who create the skins)
2008-12-21Basic skin generator + example skin for testingYorhel1-0/+264
How it works: Create new directory in static/s/ Create a 'conf' file (see the test skin for a template) Run skingen.pl, which will generate a style.css and boxbg.png This process will probably be automated using a simple web interface or something... There's no skin selector yet, so Util/LayoutHTML.pm has to be modified to view the generated skin.