Wedge

rev 2278 -- while waiting for someone to comment on my newest privacy/contact list topic... :P
(5 files, 3kb)

* Refactored credits page's multi-column to a generic class; this should make it easier to re-use through other code, and plugins. (Who.template.php, index.css, sections.css)

! SSI pages would show header and footer twice if rendering through ssi_run(). (Subs-Template.php)

! Fixed an undefined variable if current page didn't specify a title (e.g. SSI-run page.) (Subs-Template.php)

! Non-global @removes in Wess didn't accept wildcards, due to a last-minute test. Doh. (Class-CSS.php)

* Give more visibility to some profile homepage links. (sections.css)

- Removed some unneeded styling on flexbox-enabled browsers. (sections.css)

And what's the point of going OOP/MVC..?
Wedge uses OOP where it makes sense. Does Elk do that?
As for MVC, to me, it simply looks like the usual SMF file structure is gone, and replaced with tons of files that make no sense to me anymore. If I'm to find some portion of code, I have to do a global search.
Pete argues that more files = better performance, but I don't believe him a bit. What Wedge and SMF load are usually needed at some point in the page's life, so splitting into multiple files wouldn't help performance by more than 5% -- if not an actual loss of performance, I'd say.Like what? The action array? Dispatcher.class.php is much messier than Wedge's index.php (to which you still have source code access, BTW. When exactly did you become a developer at a Wedge competitor..?)I don't see anything special in there. You'll need to be more specific.
Currently, all I see is Elk taking features from SMF 2.1, and from Wedge (the footnotes tag, SERIOUSLY...?)Yes, as I said -- footnotes, ugh. Post by e-mail is actually the only Elk feature I openly congratulated the team for. I don't know if it works, though, but I've always wanted to have such a feature on my own sites, but I didn't know where to start, and some of my 2005 experiments with POP communication were bad. (At the time, I didn't know much about PHP, but it still traumatized me.)
Anyway-- I'm not stealing this one from you guys...
Likes are a Wedge feature. Gravatars, too. Improved anti-spam, too. Drag & drop for boards, yep. Custom stuff? Yup... Video embedding? Aeva invented it. Disregard topics is an easy hack to implement (set the view date to MAX_INT for a given topic), and I'm working on doing a better feature than that, but anyway: not impressed. Open ID, I have no idea if this thing still exists. I think we removed support for that years ago. And none of us cared about rewriting it. Quote to new topic, I don't really see the point of this feature.

Like I said, I'm impressed with Post to e-mail. And that's pretty much all, I'm afraid.
I'm not saying the Elk team did nothing for 2 years. There are tons of commits to account for. They certainly added more features than SMF 2.1, too. I may not be in love with Elk (the software), I may not be in awe with what I see, but I'm perfectly aware that some of your team did a great job with it. Just not as great as what Pete and I did on Wedge for 3 years. You're telling me not to underestimate Elk. I'm guessing the same goes for you.

Because one thing is sure, in my mind -- in terms of innovation and sheer number of new features, none of the other SMF derivatives hold a candle to Wedge. No, I'm not particularly proud of it or anything (anyone investing as many man-hours into the project as I did would have reached the same results), I'm just saying it because that's just the *plain truth*, and I'm realistic when I try to evaluate competitors. Wedge has more features, it's simple math. It doesn't mean you *can't* beat it. In fact, you certainly will, because you have a large team (especially now that I'm alone on the project), and I'll also soon be slowed down by the fact that I go public and will have to deal with support requests. Don't worry about that. But if you're speaking on Wedge.org as an ElkArte developer, don't be surprised that the general idea here is that Elk is inferior to Wedge. Otherwise, I'd be pushing my PRs to Elk, not here.

Feature: Contact lists
Developer: Nao
Target: users
Status: 80% (contact lists implemented, format is final; privacy implemented. need to remove buddy lists.)
Comment: this is a bit like the Facebook feature, but Noisen-style. Feel free to ask if you want more details.

rev 2276
(8 files, 4kb)

+ Skin option parameter url-* (url-action, url-board, etc.) can now take a wildcard value. i.e. url-board="*" will run the option only if you're within a board, any board. (Subs-Cache.php)

+ Added new skin option parameter: board-type="blog|board" will run the option only if we're within a blog or board. This was required by the fact that it isn't possible to determine the board type just from looking at the URL, eh. (Subs-Cache.php)

* Homepage will now systematically show the info center in the sidebar if you're on a desktop. Really, there's enough space in it for that, and it makes sense. The only situation where it's a problem is when there isn't enough space to show the sidebar itself, but then you just need to middle-click, so... Whatever? (Home.php)

* Renamed JS string is_ff to is_firefox, as apparently they want to be called Fx, and is_fx is misleading IMO. Might as well just waste a couple of bytes and use the full name, eh..? (editor.js, script.js, sha1.js, topic.js)

* Trying a new method for middle-clicking to trigger sidebar. More precisely, I'm now dismissing clicks if they're done over an item that has any events associated to it. Should work, but I want to be cautious here. Needs more testing. (script.js)

- Removed unused strings. (Who.language.php)

rev 2274
(3 files, 2kb)

* Rewrote message icon handler for clarity: split into multiple named methods, list is no longer a child of the body itself, body click handler is removed when list is closed, etc. It also saves a few bytes of JS and CSS, not many, but that's still a plus. (topic.js, index.member.css, sections.css)

! I'm not sure why I've been using $(document).find() instead of just $() in some code, as well as using .bind/.unbind when I switched to modern jQuery (and .on/.off) long ago, but... I guess it happens even to the best. (topic.js)

- Unused class no-flex. (sections.css)

:edit: ! Fixed code blocks in Firefox. Just like Chrome, Firefox doesn't like white-space: pre blocks when they only generate an horizontal scrollbar, but it doesn't cause the same glitch, and it can't be fixed the same way, so I'm disabling flex on these posts when such a situation occurs. It's very unlikely they'd benefit from flexbox anyway, as flex is mostly for very, very short posts. (topic.js)

(Sorry for forgetting to log the last one.)

Suggestion: just look at wedge.org, elkarte.net and whatever demo site they have for SMF 2.1.

I'm not saying the competition is bad. I'm saying they just never had a chance to keep up with us. Amf was busy fighting internally, and elk is too young and there are too many cooks in the kitchen IMHO. Thus, they spend most of their time fixing bugs.

The novels?Again: why waste time on this? I said it above: I'm no longer into flame wars. They're an utter waste of my precious time. I already didn't have enough time on my hands back when you did half[1] of the work on Wedge.
You got overwhelmed, too, but you didn't have my optimism, so you left. It's definitely not the highlight of your career, and I'm sure you'll agree. No need to elaborate on that for days on end.

So, apparently, you still need an answer from me, so I'll be answering your post... But I'm not happy about that. I'm going to have to say unpleasant things, things I'd rather have kept for myself. Read or ignore, it's your call.The extent of which I only learned after you left. I don't have fantastic people skills, but yours..?What did you expect? You're the one who left the project. I'm the one who's struggling hard to look into the admin are and get up to speed with what you did on it, so that I can work on it too in the future. I wouldn't have had to do it if you hadn't left, so I have all reasons to be unhappy with your departure. So, as I said: you left. Don't expect Wedge followers to send you flowers, and don't think that SMF followers won't fear that you end up doing the same for SMF, in a few months. You are well known in the forum community as an unstable person. And that's your own doing. How many times did you remove your sm.org account, already..?Which one? Tortoise? Smart? GitExtensions?
To me, any tool is just the same story: they don't show rev numbers. Even if I tag a release, it won't show the number of commits since that tag, I have to do 'git rev-list' or 'git describe --tags' on the command line, which sucks. At least, Mercurial has out-of-the-box supports for rev numbers, so if definitely has my preference, at least in the future.

Anyway, in recent weeks, you only mentioned git as 'an additional obstacle' on joining SMF. And, again, after everything you said about SMF, and its team in particular, it's always baffling to see you completely back out on what you said before. And, contributing your Wedge code to SMF? Definitely not cool, man. Yes, you can do it. But don't expect my sympathy afterwards.Yep. And suddenly, poof, it's like it never happened. Next thing you know, you're gonna tell me they never backstabbed me either, and they were hours away from offering me a dev position when someone decided to kick me out instead.
See, these things happen because of people, not because of the concept behind the team. And these people-- most of them are still here. And you're suddenly very forgiving towards them.Why don't I get that feeling when working alone on Wedge, then..?
Oh, maybe because I'm more realistic than you are, when it comes to sorting between feature suggestions and determining which are realistic goals, and which aren't?How can I get the full story if you're only willing to share it in obscure hidden comments in a SMF mod you know I'll never see..? That wasn't cool back then, and it still isn't.I chose to ignore your whims, because I already went through these last year, and I knew (well, I thought I knew) that they were part of you, and discussing them could only bring more frustration. 90% of the time, we worked alone on our areas of expertise, occasionally asking for each other's opinions on what would be best here or there. It worked *great*. We did that for the better of these three frigging years. And if you disagree with that, then it's you who's ignoring reality, not me.Nice of you.Seriously? I'm the one who should be saying that...<tired>
Ah, well. If you need to prove yourself, young grasshopper, then set yourself a reasonable goal, and keep at it. And don't work with anyone, because you'll only end up comparing yourself to them.

1.	To make things simple.

rev 2273 -- a small one.
(4 files +1-1, 3kb)

* Redid the Modify button icon; it was so long, it looked like a trident. Plus, the new version is twice smaller in size. (modify.png, modify.gif, index.css)

* Remove whitespace when linktrees are empty. (index.template.php, index.css)

! Don't prevent non-default events when middle-clicking an element to open the sidebar. In the real world, it means: if you middle-click a '+' button somewhere, the associated link will correctly open in a new tab. My only goal is to avoid that dreaded Windows 'auto-scroll' mode. Sorry, I hate that one so much, it's just unbelievable... (script.js)