Wedge

As we recently discussed, Pete and I -- we're considering removing Wap2 support from Wedge.
I already removed iMode and Wap1, and improved Wap2 a (tiny) bit by giving it more styles.

However, there are still issues with this:
- it's really a limited subset of a SMF/Wedge forum... Basically, you can only view posts and PMs, and answer them.
- Google might still crawl your mobile page and offer links to them instead of your desktop site, even on its regular version. Wedge improved that, but it's still not completely flawless.

The main advantages of Wap2 are:
- it's definitely faster than a regular page. The only other way to quickly view an entire topic is the Print link. (Which is arguably much better at that task.)
- it works on very old non-smart mobile phones. Like mine. But basically, the main point is that people who actually browse the web with their phone have LONG since purchased an iPhone or similar.

So we think it could go, but we're just not sure. It's time for Wap2 to speak, or you shall remain silent forever! :geek:

rev 1312
(3 files +1, 2kb)

+ Restored corefeatures.gif file, under the name settings.gif, because it was used by a couple other menu entries. (Admin.php, admin/settings.gif)

- Removed a couple of remaining CoreFeatures references. (Admin.php, ManageSettings.php)

* French translation. (ManageSettings.french.php)

As implied in another topic -- my official word on this is that I don't give a damn about attachment approval, and I agree with you. At 'worst', you can always add a rule saying 'if post has an attachment...'. Maybe even extra rules like 'attachment over X bytes', 'attached image over X pixels' or 'attachment that is of the image/doc/zip type'.

Yeah absolutely, I even added the first new hooks back then... And then when Pete started coding the plugin system, it went totally out of my hands and became a much more extensive hook system ;) But using hooks as replacements for file edits was one of our strongest feelings about Wedge. I mean, we really, REALLY wanted to have this and disable file edits as much as possible.

Pete, while I'm at it. Your moderation code (which is looking great!) has a "matching" feature. I noticed that the only difference with "regex" is that it makes sure the text "starts" with the regex. Wouldn't it make more sense to ensure it starts AND ends with it...? (^this$) Or, just change the text string to say "starts with regex"...?

rev 1311
(1 file +1 -1, 3kb)

! Finally, finally fixed the Opera issues with select box animations. Well, I couldn't let it slip, it's still my favorite browser after all. After hours of debugging, I noticed that all bugs would go away if moving the inline-block declaration from .sbox to .display, which is what I just did. Because I seem to remember having had bugs in other browsers when doing that, I won't tempt the devil, and instead add an index.opera.css file that does the job in two lines. Right? The other good news is that this allows me to remove an Opera hack in sbox.js and save another 5 gzipped bytes. (sbox.js, Worg/index.opera.css)

- Also removed a custom.css file that wasn't supposed to be there. Harmless, but it defeated the whole point of custom.css -- being able to upload yours without fear of a Wedge upgrade replacing it. Please hit me if I forget to remove it again when Worg becomes the top-level skin... Okay? (Worg/custom.css)

rev 1308
(13 files, 8kb)

* Translators are gonna hate me... While I was in the process of renaming all of  these variables, I decided I wanted to fix Aeva Media as well. Subtext entries were using different suffixes, such as _info, _sub, _subtxt, _subtext and _desc. Renamed them all to _desc, except for _info which isn't always for a subtext anyway. Also replaced all mg_subtext entries with the commonly used (in Wedge) dfn tag. It's important that the admin area looks the same everywhere. Now I just need to remove the alternating color stripes... Arg. Also, various tweaks here and there, nothing worthy of an individual mention though. (Aeva-Foxy.php, Aeva-Gallery.php, Aeva-Gallery2.php, ManageMedia.php, ManageMedia2.php, ManageMedia3.php, ManageMedia.template.php, Media.template.php, Media.language.php, ManageMedia.language.php, media.css)

rev 1306
(6 files, 4kb)

! Select box width and scrollbar position were incorrectly set on complex boxes. I have no idea why, but it was fixed 'simply' by moving the .width() outside of the command chain and into the following line, at a cost of zero byte. I suspect it's an issue with the wrapAll method. (sbox.js)

+ Added a data-self parameter to the thought list, allowing to determine whether Edit/Delete buttons should be shown next to a particular thought. Takes 12 more bytes but I saved another 5 by removing the whitespace on the thought HTML. It's not like I'm going to change it a lot anyway... (script.js)

* Moved the Aeva (auto-embedding) section just below the Smiley and Attachment/Avatar sections, because they're all about 'visual'. (Admin.php)

* Details. (media.css, Worg/index.member.css, Worg/sections.css)

I don't mind WP, personally. If anything, the very fact that it's widespread means that it got something right... Maybe not in the code, but at least in its community handling.