Wedge
Public area => The Pub => Topic started by: dorje on March 30th, 2011, 07:22 AM
-
Ok, we can't have a look at wedge at the moment.... But... Is there some document to read / study? Just to be ready - I can't stay there and wait without doing nothing! :yahoo:
Another question: are there many differences between the core smf db tables and the wedge one? I mean - I know that wedge has many feature smf haven't - but I guess if the "forum stuff" tables structure are the same. :)
-
No, there isn't. Kind of hard to document something that is a moving target and being modified regularly as it evolves...
There are quite a few differences, and likely there will be more as time goes on.
-
No, there isn't. Kind of hard to document something that is a moving target and being modified regularly as it evolves...
There are quite a few differences, and likely there will be more as time goes on.
-
Welcome to the world of "feature hot", as opposed to feature frozen :eheh:
For instance, I started redoing the CSS system in mid-January, and I finished a few weeks ago and it's still not considered 'stabilized' (I'm still working, as of this moment, on improving class inheritance.)
Because of the rewrite, it means you can't import your theme CSS "like that". You'll have to rewrite it entirely (or, at best, to do a long series of automatic search & replace sessions, which I myself did to rewrite the SMF css files.)
Since right now I could just call it quits at any point in time and just revert back to the SMF system (which I'll never do but it's an example :P), there's no point in documenting it too much.
Hopefully I'll be able to write said docs just by going through Class-CSS.php once it's 100% stable :P
-
Welcome to the world of "feature hot", as opposed to feature frozen :eheh:
Because of the rewrite, it means you can't import your theme CSS "like that". You'll have to rewrite it entirely (or, at best, to do a long series of automatic search & replace sessions, which I myself did to rewrite the SMF css files.)
Hopefully I'll be able to write said docs just by going through Class-CSS.php once it's 100% stable :P
Sound's great. :eheh:
-
You have to see Class-CSS to believe it, BTW... It's one of the best pieces of code I ever wrote. Eheh. Okay, ego, sit down now!
-
It's one of the best things I've seen in a long while, it makes creating theme variations and theme editing a ton simpler IMO. (I was able to navigate around that a whole lot faster than SMF's own CSS, certainly)
-
About the CSS... there will be no more main_block.png right? No more annoying CSS sprites that made you just for a simple change of color have to do major edits in PS?
-
There are sprite images, but they're not stupid ones. The bbcode images, for example, is a sprite - but they can be overridden. The little images by menu icons (like here) are a single sprite, but again it's possible to override that to individual images.
But the core of the default theme is not to use massive images like that where possible, and use CSS normally to achieve things.
That said, it's not a huge amount of work if you want to revert things; one of the things Nao did was create a meta code of sorts, <we:cat> and <we:title> that get turned in to the relevant divs and h3 tags that make the cat and title bars. Here's where it's neat: that's defined in the settings of a theme or theme variation, which means the templates all use <we:*> (so it's trivial to keep consistency in add-ons) and the theme dictates the code it wants to use, meaning you could use Curve's HTML if you wanted. Not that it would be a good idea... but you could if you wanted.
-
You have to see Class-CSS to believe it, BTW... It's one of the best pieces of code I ever wrote. Eheh. Okay, ego, sit down now!
You can not increse my amount of frustration by writing these things! :lol: :lol:
-
Well, that's a positive aspect. Basically, using meta code made the design even easier, but, would it made a valid XHTML or HTML (4 or 5) document?
-
Considering that the code is replaced with HTML of the theme's choice later, yes...