Wedge

Shrunk where?
There's a default mobile theme. You can change it if you don't like it... But seriously, I don't understand how you could find the desktop version to be more desirable (for an HTC Desire) than the wireless skin, which is precisely geared towards improving readability and usability...
Heck, I can't live without it now.

rev 1569
(4 files, 3kb)

! Fixed attachment handler not correctly disabling/re-enabling the file input after going over or below the maximum file limit. (post.js)

+ Added slide animations to adding and deleting attachment files in the post page. This adds 20 bytes of code but I saved over 50 with some optimizations in the same time... (post.js)

* Saving a few bytes, again... (editor.js)

* I don't like redeclaring a local var... Will need to move all that code to a JS file later anyway. (Post.template.php)

* Aligning icons vertically in blog posts. (MessageIndex.template.php)

Saved another 14 bytes by converting the this.parentNode stuff with:


It sounds too good to be true, but jQuery allows objects to remove themselves... Any idea why you didn't do it that way, Pete? In case you didn't know it's possible, here's me making sure to spread the word :)

This is minor but should be fixed because there's code in the implementation that doesn't work as expected.

Reproducing: attach 2 files to a post (let's say there are 4 attachments max), and save.

Edit post again. There are two files in there, let's click to add one.. Done... Click again to add one... Done. The Browse button is still active, even though we technically reached the limit.
Now, go to post.js and do this.checkActive() BEFORE current_element is assigned to element. This fixes the bug.
However, it creates another one -- if you then click Delete to remove one of the files, the Browse button is still disabled. This bug might be due to my rewrite though, as I changed a few blocks in here (which is why I'd rather we discuss this bug than commit something and force me to resolve the conflict, eh eh.)

Anyway, I'm sure it's an easy fix, but I didn't write the code logic so I'm not sure how best to handle it without looking into it very seriously. (And I have to leave for now.)

rev 1568
(22 files -1, 11kb) (bit in a hurry, hope I didn't screw up anything...)

* Tweaked mini-menu code to make the resulting HTML shorter and avoid outputting empty strings. Note for later: array_map() is super-slow, especially compared to foreach. (Display.php, topic.js)

* Renamed we_prepareScriptUrl to weUrl because I added support for more than just dealing with we_script ($scripturl), and optimized the function (a bit). Also removed aeva_prepareScriptUrl which was unused (probably a SMF1 compatibility leftover.) (index.template.php, Packages.template.php, Post.template.php, SplitTopics.template.php, Themes.template.php, editor.js, mediadmin.js, post.js, register.js, script.js, stats.js, suggest.js, topic.js, up.js)

* I think that periods should be in language files, rather than in the template. Better support for exotic languages... (MoveTopic.template.php, ManageTopics.language.php)

* Removed AeMe feed icon and replaced it with the default one. (images/aeva/feed.png, Media.template.php)

* Saved a few bytes off the ajaxRating function, the wedgeAttachSelect object, the editor object, and various other JS areas. (Media.template.php, script.js, post.js, editor.js)

* Translation. (EmailTemplates.french.php, Login.french.php)

* Commenazi. (Subs-Cache.php)

So... I did a bit of a (tiny) rewrite to we_prepareScriptUrl(), which is 'the' function that did what I remembered: it takes the script URL and adds a question mark if not there, or a semicolon if a question mark is found.
So I renamed it to the more generic 'weUrl' and added a parameter to specify the original URL. If it's empty, it uses we_script. (Obviously!)
I'm a bit annoyed by the function itself... At some point it uses url.charAt(url.length - 1), when I could use url.substr(-1) (and save 6 bytes off the gzipped size...), but it's not supported in IE (even 10!). So I switched to url[url.length-1] but I remembered that we discussed this at some point and gave up on it because of poor support... However, I just tried in IE6 (emulated in a virtual box) and it frigging works...?!

Yeah I had a look at your code and, hmm... (sUrl.indexOf('?') > 0 ? ';' : '?') could be replaced by addQMark(sUrl), where we return ? or ; depending on whether ? is in the URL... It'd be a slightly shorter call but I don't know how shorter it would be in the final gzipped code... Probably not at all.