Wedge

Pff. Texasman, do you have any idea how much time you've wasted here so far, and worse, how much time we've all been losing thanks to your antics?

They mainly get lost in endless discussions about features ;)

I tend to naturally get fed up after talking for a while, and jump straight into work to implement my ideas.
After all, there's no rule saying that whatever I'm committing shall remain that way. Nothing is set in stone.

Problem is, sometimes there are so many things we discuss at the same time -- I just end up forgetting a few things to implement. I would so love if readers could bump topics where a discussion was taking place and suddenly there's nothing else, without any mention of the implementation.

From me it did. But apparently it doesn't count eh...Please don't use words you don't even know how to spell.Hmm... How about "we've been working on Wedge for nearly 8 months, 700 commits so far, working fulltime on the thing and we still haven't managed to implement half the stuff we want"? How about "If we start implementing every other guy's incredible-idea-that'll-make-Wedge-so-much-better-than-SMF™[1], we won't release it for an extra ten years"?

1.	And believe me, everyone has their own idea... Which is, in general, related to a problem they're having with SMF -- but that not everyone may have, of course.

rev 701
(6 files, 11kb)

! Fixed lists of children albums looking really bad due to the new rounded corner markup. Well, I couldn't find a perfect solution so I made a couple of changes. I'm not satisfied though... (Subs-Media.php, media.css)
! Minor thingies. (ManageMedia.english.php, Media.template.php, hs.css)
+ Added .wrc_top and .wrc_bottom classes, in case they ever make themselves useful. Not for now though... (index.css)

Pete, speaking of permission profiles... I don't remember if anyone suggested that in the related private topic, but what about this change? UI wise it would make sense to edit permissions and fine-tuning per group, rather than edit membergroups and fine-tune permissions for each of them... Imagine that, instead of having "Post new topic (yes) (no)", you had "Post new topic: (regular members - yes no) (moderators - yes no) (group 1 - yes no)"... We could simply show the group names through JavaScript, to save on the page load. We could also add a "check all" checkbox above "yes" and above "no", things like that... Then, permissions that are set the same for all groups would show "yes" or "no" in bold, so that one could easily find permissions that are set differently for each group. Plenty of things that could be done via JS really...

rev 699
(2 files, 12kb)

- Removed self-closed tag closers (?) from Media templates and fixed a few things (labels, etc.) Source files aren't done yet. (Media.template.php, ManageMedia.template.php)

rev 700
(12 files, 15kb)

- These source files have tons of templating in them... So much for the MVC model uh. Removed all />'s where needed, and a few more fixes as usual. Renamed all remaining SMG tags to MEDIA. (Sources/media/*, ManageMedia.language.php, Media.template.php)

Okay, then we're the Nesquik fan club.
(Although I started hating them when they changed their mascot about 15 years ago. My childhood, up in smoke. All that for a stupid rabbit...)

I think Pete intends to do that.