Wedge

I didn't... Well, it had a couple of interesting ideas (not that much really), a handful of amusing jokes (nothing worth a LOL), the robots were the best parts, probably because they felt like they came from Douglas Adams.
Other than that... Too many friggin' plot holes for me. And I'm not one to scream at plot holes... It just didn't make sense overall. Things like, "okay you have control of the ship but we're still going to shoot the ship because we can", or "let's ride that slow Triceratops, it's certainly going to be more efficient than just running while dodging these lame laser shots from the dumb robots..."Same here -- except it's been the same since series 6 for me... I just can't take any more of that Doctor. He's supposed to be the same doctor, but where did our Tennant go? I know the Doctor has on occasion killed, but in such a cold-blooded way? Nope, that isn't the Doctor I know... He's always trying to be fair, even with the villains.

Anyway... It was far, far less interesting than last week. To me, it was the worst episode since season 5's Victory of the Daleks, and season 3's Daleks in Manhattan. And without any Daleks to help? Congrats!

I don't know. You tell me.

To me, it doesn't matter that much. @ is to help against mistaking commands for selectors. But @extends doesn't excite me so I decided tht any modifiers would be prefix free. But conditionals? Are they not commands?

I know it's a lot of questions (that's what life is about :P), but you don't have to answer them all ;)
Just gimme your feelings about whatever made you feel something!

Hopefully getting some opinions before I actually start work on implementing these :^^;:

A bit
Of a
Desperate
Bump.
Sadness ensues.

Getting close to something I really, really like...

So... I slept on it, and it's even worse now :)

I think WeCSS is getting a bit 'old' by my standards, and I should remove some of the dust. And maybe rename it to 'Wess', which I've been considering for a while...

- First of all, because I support 'base:' and added the 'extends' keyword to make it more objecty, I think it's only fair that I add a 'mixes' keyword that would do the exact same thing as 'mixin:'.

- Additionally, maybe mixins should be defined the same way as bases, that is, as regular selectors... (Or, at least, to enable virtuals to be used as mixins). To get the regular mixin behavior, we'd just need to define them as virtuals. The good thing is that it would mean .inline-block can be used both as a base and a mixin. Can you hear "solves the media query problem" already? Yes I'm sure you can...

- I went to check out LESS and SASS (my main 'competition' if I may say), and LESS has done a lot of progress in a year (I should have kept up with their new stuff really...). They now both support mixin parameters, and it's indeed something that could happen to be useful in WeCSS as well. I'm just trying to figure out the proper way of writing it if I'm going to use selectors for mixin declarations... Something like:


- As seen just above, there's already an undocumented feature in WeCSS which I like a lot:

background-color: ifnull($custom_color, #fff)

Meaning, "if $custom_color is set, then set background-color to it, otherwise set it to #fff".
Okay, so should this remain like this? Or would it feel more natural to use @ifnull instead of ifnull?

- Same for conditionals...


Should these keywords use @? Should whatever follows if be between brackets? if(ie) or if (ie), like in JavaScript or PHP... But maybe skin authors aren't too versed into these languages, I don't know.
Should we use @endif, too, or would indenting be enough to say "it's the end of the argument list"...? (I haven't tested for now whether or not it can allow for nested selectors in such a situation...)
Should we allow for single-line if statements?



(In which case, an @endif would mean end of statement, while a missing @endif would mean the statement ends at the end of the line.... But again, maybe it's too complicated?)

Or maybe, similarly to ifnull/@ifnull...


Just a few ideas like that. May add some in the future... Would like opinions from everyone interested in CSS in general, thank you :)

I don't know if it was the accent or something, but it did sound odd in the first few scenes... Then after a while, I surprisingly liked it. It sounded realistic -- i.e. a normal human being speaking, rather than a killing machine or whatever crap... In fact, thinking about it, Bruce Wayne has a more ridiculous voice than he does, because he chooses to use it!

Of course, I was kinda helped by the subtitles. (They were French, I tend to hate French subs these days and prefer to rely on English subs and handle the translation by myself) I was saying -- with subs, you can automatically read them if you don't understand what he just said. There was even a Conan O'Brien emphasizing the lack of clarity in his speeches... (I saw that one online.)

Ending isn't what's best in the movie I'd say. Or at least, if they wanted to have a 'shock ending', they totally failed, at least for me.


And yes, I did love TDKR. My 4th favorite Batman movie -- after Mask of the Phantasm, Dark Knight, and Under the Red Hood (in that order).

Should be fixed here too now.

Smileys -> they're Wedge.org specific. i.e. the smileys in Wedge are also in SMF 2. I have no qualms with releasing the smiley set as it is, but it won't be part of Wedge because I'm not sure I can claim ownership of it, even though I made many of them myself. (The rest is taken from the official PunBB smileys, or variations on it released on a fan forum.)