Wedge

I don't see the point of using youtube-nocookie, really..? Aren't you being a bit paranoid? What's in that cookie anyway?

It's either iframe or flash, not both. Although I did keep the flash version in a comment and explained how to reset it... And you could just as well include a new sitelist entry with the flash version, so that you could choose from the admin area, but that would imply you can't have both enabled at the same time obviously, and that would be confusing to do by default.

For those who have issues with the sidebar position -- I modified Wine and Warm to use the same as the others.
Total time taken: 2 seconds per file :P (changing 'left' to 'right' in the options file.)
Oh BTW I quickly changed it back to have the sidebar on the left and the avatar box on the left (instead of on the right), just in case what bothered you guys wasn't the sidebar position, but instead the avatar position (I'm aware that it can be disturbing, cf. phpBB3.)

I'll resume work on this topic tomorrow, ah ah...Even if the paddings and margins are awfully done?Yeah, sorry, a wrong manipulation on my side -- I overwrote a file with a version that wasn't my custom one.
See, until now the skin selector would add a variable at the end of the URL and redirect to that. I didn't like it for two reasons: (1) the variable had 'theme' in it, which is basically a 'temporary' setting for the current session, so it could generate situations where you get two different skins on two different browsers at the same time, (2) well, it adds too much code to the HTML... Even if it's at the end, which is fine usually, it's still extra bandwidth. So I chose a solution that will probably not work for everyone (if your antivirus removes your referer information, you'll be redirected to the skin selector instead of the current page), and may also not work correctly (it's possible that you'll be redirected to a page reloaded from cache, making it impossible to see the new skin without hitting F5.) But in all honesty, my Opera is set to ALWAYS load from cache, and yet the feature works for me every time.

Tell me if you have any problems with it... (I need to commit these changes.)

PS: just realized -- first at 11.111 posts! 8-)

(Fixed.)Yeah, it's really mood dependent for me too.... But since I wrote Weaving to be the 'best' of all (as well as the most neutral), I'd be really displeased if I wasn't using it 90% of the time ;)
Well... First of all, SMF provides one new theme in every new major version, not three like I'm doing ;) (Well, 4 for now, but I only have plans to release the best 2 or 3.)
I think that Weaving is a much better skin than most anything I've seen on SMF. There are a couple of themes by Bloc that I like as much as I like Weaving, and a few themes by Dziner which I like as much or more than Weaving. Mostly because they have more coherence overall. (Wedge is still in alpha, I know...!)As was explained in the posts in between -- yeah, it's not that easy.
I try to keep in touch with reality. XenForo did away with a few horrific forum concepts -- but added oddities of its own. Invision evolved in a nice way, but it's still basically the same as in the beginning, only with a modern twist. vBulletin is... oh well, vBulletin is a joke for a wanna-be designer like me. There's so much to say, I wouldn't know where to begin...
phpBB is another example of boring classicism (in your mind?), but OTOH phpBB3 introduced something that none of the other forums had done so far (except for my custom SMF back in the day for a few weeks -- until I got bored with it): showing avatars on the RIGHT of the messages. (Something, you'll notice, that is available in one of my skins.) SMF has always been about classicism too, but at least Curve added some modern (at the time!) features like rounded corners and daring padding. FluxBB went for modern simplicity too, perhaps way more than the rest of the pack -- but it's also probably a feeling due to the fact that they don't ship many features by default. Making it easier to provide a site-wide cleanliness.

So, most of the forum software is built around the same concepts, but tries to customize it in a way that doesn't scare people away, and yet establishes a visual theme that ensures people 'stick' with it or at least recognize the forum software across multiple websites.

What Wedge did was exactly the same. I went through the code to make it more modern, and tried to make the designs interesting while still retaining the classic forum layouts.
You may or may not believe me -- but I find it harder to do than starting from scratch.
Because what you don't want is finding yourself with the mess that Vanilla is. Here's an example of a 'popular' forum system that actually makes me want to facepalm everytime I see a forum running it. Perhaps even more than when I see a vBulletin-powered forum.

Conclusion: Wedge does provide one of the most original layouts for a SMF fork. Really. Can I make it stand out even more? Obviously yes. Do I have time to do it? Not really. Do I want to do it? Again, nope. I think maybe I can work on that for Wedge 2.0, but we need to retain our SMF-friendly aspects for now.Well, just because the previous header said 'new ways for a new age' doesn't mean I announced Wedge as the 'new era' of forum software... It's mostly a 'level up', like the Aeva links say. I'm taking it to the next phase, but it doesn't mean it's a complete rewrite. You'll want to look for smCore for that. Which won't be out for another couple of years...

Or maybe they'll recognize the one on the left the same way ;)

I'm still making tests internally. My current version has an additional drop shadow, distorts the lines and is a monochrome logo. It's... Interesting.

My favorite of today's batch... Pretty much what I described above, except without the monochrome aspect.

Johnny, you didn't tell us what your browser is... (And version!)

Also, to agent47, Johnny54, markham, spoogs: can you try and be more specific about what you like in Wuthering? I swapped the fonts (Segoe UI / Arial) for Weaving and Wuthering yesterday to, maybe, help you determine if this is due to the font choice. (You can easily switch between fonts with developer tools like Firebug or Dragonfly, of course.)

What about we just set id_board to a mediumint, and same for id_group..? We can increase their size again later... No? Because I really don't see myself leaving id_group be like that... Increasing its size will be an incentive for early release of contact lists.Hmm, yeah, yeah...
There are already lots of changes btw... I'm sure the old packman no longer works, here. I know that it crashed my local install because of a few missing fields.Nope, the PHP code isn't committed, only the YouTube fixes which I never committed in the first place. To be specific -- my Aeva-Sites.php file had the iframe code in it, and my Subs-Aeva-Sites.php didn't. Meaning that I'd updated the sitelist file, then tested, then was happy, then reverted manually before doing a commit at some point (because of the lack of test), and forgot to re-introduce the iframe code... You won't believe the number of times that kind of crap happened to me!I just need to figure out what to put into the URL...
i.e. I don't see a need to have a 'mobile' keyword in the URL, *but* if the current device is a mobile device, *AND* one of the files it needs has a mobile keyword in it, then I need to add that keyword to the URL too, and thus create an extra css file.
The goal being to avoid having the more 'generic' keywords when not needed... But then a new problem occurs. If I use $variable {mobile} = "This is a mobile device" in the CSS code, I'll suddenly find myself with the need to record somewhere that it's a mobile device...

See what I mean..?
I don't. Guess it's time for bed...