There's a new syntax highlighter now, so if anyone runs into any issues with the [html], [code] or [php] BBCode blocks, let me know. Looks like this now... echo 'Hello world!' exit; PHP: <html> <head> <title>New page</title> </head> <body> Hello world! </body> </html> HTML: confirm('Hello world!'); console.log('Hello world!'); Code (JavaScript): .helloWorld { color: #ff0000 } Code (CSS):
Issues? You mean LIKE IT BEING JUST MORE ILLEGIBLE CRAP I'M GOING TO HAVE TO OVERRIDE USING USER.CSS IN THE BROWSER? I mean, I'm not a fan of syntax highlighting in the first place, that's why I was using CODE instead of PHP or HTML as it was NOT providing those (and that was a good thing) -- but even if I were to allow it this REEKS of being done by someone who has NO business creating front end design. Why do I say this? SAME FREAKING REASON I'M ALWAYS SAYING IT! COLOUR CONTRAST! -- or more specifically the lack therein! I mean the background is what, #272822? That's a luma of 37... so MINIMUM luma for the text colour would be 164, and since for some jacked up reason you're NOT EVEN USING A MONOSPACE FONT FOR CODE (kiss complex formatting goodbye) in a thin glyph sans, that means a more ideal minimum luma would be 229; which pretty much means kiss having colouration goodbye... Of course that the line numbers are 153 luma, the HTML keywords are 144 Luma, the attributes are 136 luma, and the doctype is a pathetic 128 luma -- are you telling me there are people out there who can read this crap? .... and that's without even taking into account the dark box on a light layout pupil dialation, which would mean for legibility sake you'd be stuck at 240 luma as the minimum, which pretty much means white, white and more white since that's #F0F0F0 if you want ANYONE to read it. I mean, it's bad enough the complete and miserable /FAIL/ xenforo is on code efficiency, semantics (aka using HTML properly) and accessibility, without pissing all over it from orbit. In case you couldn't guess, not a fan to begin with, and then this implementation takes something annoying and makes it worse. Time to dive in with the object inspector and force more overrides into the user.css Seriously, if you're telling me people can read that magenta text with their head less than two inches from the display, you're full of ...
For those interested, here's my LATEST edition of "fix the blasted skin" user.css including a fix to make the code boxes actually be legible. @namespace url(http://www.w3.org/1999/xhtml); @-moz-document domain('digitalpoint.com') { * { font-size:100% !important; line-height:140% !important; font-family:arial,helvetica,sans-serif !important; } body { font-size:85% !important; } .messageUserInfo { width:12em !important; } .messageInfo { width:auto !important; margin-left:13em !important; } .navTabs { font-size:16px !important; } .navTabs a { line-height:25px !important; } .blockLinksList a { line-height:20px !important; } #header_middle, .socialBar { display:none !important; } .newIndicator { color:#EFC !important; } .privateControls span a { line-height:2em !important; } .button, .privateControls a.item, .publicControls a { height:auto !important; padding:0.2em 0.5em !important; } .publicControls a { display:inline-block; } .scrollable { height:2em !important; } .pageNavHeader{ padding-right:0.4em !important; } .button, .publicControls a, .privateControls a.item, .PageNav a { color:#000; background:#EFD !important; border:1px solid; border-color:#749B85 #749B85 #618872; -webkit-border-radius:7px; -moz-border-radius:7px; border-radius:7px; -webkit-box-shadow: 0px 1px 4px 0px #C8C8D2, inset 0 4px 8px #FFF, inset 0 -4px 8px #BDB; -moz-box-shadow: 0px 1px 4px 0px #C8C8D2, inset 0 4px 8px #FFF, inset 0 -4px 8px #BDB; box-shadow: 0px 1px 4px 0px #C8C8D2, inset 0 4px 8px #FFF, inset 0 -4px 8px #BDB; } .button:active, .button:focus, .button:hover, .publicControls a:active, .publicControls a:focus, .publicControls a:hover, .pageNav a:active, .pageNav a:focus, .pageNav a:hover { background:#CEC !important; } #AlertsMenu_Counter .arrow, #header_data, #header_middle, .underPost { display:none; } #AlertsMenu_Counter { position:relative !important; top:0 !important; padding:0.1em 0.4em; } .formPopup { width:16em !important; } #QuickSearchQuery { width:15em !important; } #QuickSearch * { line-height:1.4em !important; } #QuickSearch input.button.primary { width:auto !important; margin-right:0.4em; padding:0.2em 0.5em !important; } #QuickSearch a.moreOptions { overflow:hidden; display:block; margin:0; padding:0.2em 0 !important; height:auto !important; } #commonSearches { margin-left:0.4em; padding:0.2em 0.5em !important; height:auto !important; } .pageNavLinkGroup a { width:auto !important; padding:0.1em 0.2em !important; } #messageList li:nth-child(even) { background: #E0FFD0; /* Old browsers */ background: -moz-linear-gradient(left, #fcfcff 0%, #E0FFD0 50%, #fcfcff 100%); /* FF3.6+ */ background: linear-gradient(to right, #fcfcff 0%,#E0FFD0 50%,#fcfcff 100%); /* W3C */ } #messageList .messageInfo { background:transparent; } pre { background:#DEC !important; } code, code * { font-family:consolas,monospace !important; color:#120 !important; } .nodeLastPost { height:auto !important; } } Code (markup): For those of you who don't know what user.css is, it's CSS you run locally in the browser to override what a website tries to do -- and christmas on a cracker I need a LOT of it to even TRY and use this site. (along with a hefty dose of content and script blocking). I swear it's just gotten worse and more bloated and worse and more bloated to the point these forums are a fraction as useful as they were a decade ago. (and likely consuming two or three times the server hardware it should need because of it!)
Yep. BTW - the reason the code block isn't mono space for you is because you don't want it to be. lol
What do you use here? I know you released the GeSHI add-on for xenforo. Are you going to release the add-on that you use here?
What is wrong with GeSHI? Is it based off of another syntax highlighter, or did you make it from scratch?
Nothing is wrong with GeSHI. Just because we don't use it, it doesn't mean something is wrong with it.
Is the one you use here better? What is the one that you use here? What one should i use after i import?
The one we use here is better, yes. It doesn't have a name. I guess you can call it "a syntax highlighter" if you want.
Why publish it? There are a whole lot of parts to this site that we built that aren't given away to others.