| |
jailbird
Registered: Dec 2001
Posts: 1578 |
A minimalistic CSDb style for Stylish
I couldn't sleep last night so I decided to restyle CSDb a bit, maybe some of you will find it useful.
Since the HTML is not semantic at all, and it was a real pain in the ass to make it work, I am pretty sure it's full of shit, so feel free to improve/change it.
Oh, and it works only when you're logged in.
Get it from https://github.com/csisztaiarnold/csdb_stylish
Preview on YouTube: https://www.youtube.com/watch?v=mLMcTCREKf8 |
|
... 25 posts hidden. Click here to view all posts....
|
| |
jailbird
Registered: Dec 2001
Posts: 1578 |
Plus another update :
- it looks better (except the PM, but who uses that anyway)
- votes look better:
And similar small improvement stuff but I have to pee and sleep |
| |
chatGPZ
Registered: Dec 2001
Posts: 11384 |
Quote:But seriously: if (part) of the source code would be made available (f.e. in a repository) there should be imho enough people willing to help switching to a more semantic approach.
after looking at the code myself, i dare to say that those who look at it only want to do one thing: delete it all. |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
Quote: Quote:But seriously: if (part) of the source code would be made available (f.e. in a repository) there should be imho enough people willing to help switching to a more semantic approach.
after looking at the code myself, i dare to say that those who look at it only want to do one thing: delete it all.
That is indeed usually the case when it comes to bad code. The only viable approach would be to expose the content of the database as an API imo (since giving the full database exposes private messages between persons etc).
Another approach is of course to gut out everything personal from the database and keep it a pure tracking of releases (i.e. remove PMs, forum, user comments) then make everything public domain with public read only access. Read write access for selected trusted implementors. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11384 |
even the db itself needs a serious rework / restructuring.
think of the C code you wrote 20 years ago. its that bad. |
| |
Peacemaker
Registered: Sep 2004
Posts: 275 |
Jailbird: Looking good. If you it could only beeing applied by inserting your .css why, not? :D |
| |
CreaMD
Registered: Dec 2001
Posts: 3057 |
Quote: BTW a single class on the <body> depending on the first URI segment would help ALFULLY a lot! Perffffff pls!
Jb, contact Perff directly, that should be a simple and straightforward task for him.
Other way, parse url with js, add body class dynamically with js. (using js not possible, right?)
roman |
| |
Perff
Administrator
Posts: 1679 |
Nice things I see people are saying about my old code here! ;)
But, yes it IS bad. :/
@Jailbird: Let me know what you like me to do (didn't get it from your comment), and I'll look at it. :) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11384 |
I'd say exactly the same about my own code from 20 years ago. Horrible =) |
| |
jailbird
Registered: Dec 2001
Posts: 1578 |
HTML and CSS aint code anyway ;)
@Perff: I/we would need a unique (but permanent) class in the body of each page based on the first URI segment. Fe. forum for this, home for home, release for the release page, event for the events, etc. So I could write direct selectors which don't influence elements on other pages. I am sure it would be easy to automate it. Thanx! XOXO
Ps: plus a unique class for the menu items, but that's useful just for the lurkers so no priority |
| |
bOOZElEE
Registered: Dec 2002
Posts: 35 |
Quoting JailbirdWTF, I'd never thought I'd communicate, nevertheless to agree with Rayden, but yeah.
Nonetheless you're welcome :)
I highly appreciate the work you put into the CSS, but the stylish approach feels to me like a Bondo Bucket: shiny at the first glance, but as the base isn't solid she starts falling apart if you take her out for the first ride in town ;)
But it cleary shows what could (and imho should) be done to give CSDb a more contemporary look and feel. I like.
A repository/archive just containing the current templates (no DB involved) would be a first step - just to take a look at the current code. But given the age of the code, I suspect some fancy interwoven HTML/PHP stuff and I doubt I really want to see it... ;) (@Perff: no offence meant) |
| Previous - 1 | 2 | 3 | 4 - Next |
