Wedge

So, err, no comment on my post above? ;)

Err... What for?

rev 1633 -- the Zoomedia commit. :)
(7 files, 9kb)

! Rewrote Zoomedia's initialization routine to improve handling of titles and descriptions. Seriously, it was horribly broken. Plus, the new version is shorter by 150+ gzipped bytes. It's all in a day's work for Byte Repair Man. (zoomedia.js, zoom.css)

* Harmonized/simplified Zoomedia call code. (Aeva-Gallery.php, Aeva-Subs-Vital.php, Subs-Media.php)

* All attachment resizing is now done through Zoomedia rather than a window popup or the expandThumbs function. (Display.php, Display.template.php)

! Give access to hidden/forbidden user albums to users who have explicit permission to post in them. (Aeva-Gallery.php)

! Fixed centering of media items. (Aeva-Subs-Vital.php, Subs-Media.php)

Well, there's nothing wrong is using className (or anything purely JS) even when jQuery equivalents are available. I usually choose to use jQ in these situations because the code is shorter and thus compresses better.

Speaking of which, I just finished rewriting Zoomedia... The code works much better, and is about 150 bytes shorter :D

Hmm... I think we already had this conversation long ago ;)

I *did* mean setting the auto_increment to 1, it wasn't just an example... MySQL will 'fix' that to use the earliest possible id, which is what we want. ;)

Believe me, I do it all the time in phpMyAdmin!

You mean .hasClass('class')...?
Or simply .is('.class')? (A bit slower though.)
If you want to assign a class, use .addClass('class') or .toggleClass('class'). The opposite is .removeClass('class').
If you want to get a list of all classes, you'll have to rely on $()[0].className or $().attr('class'), AFAIK.

I'm obsessed with it! I think Pete pities me :lol:It's more complicated than that.
First of all, when I worked on AeMe, as I said I found out about a library to do cropping, but it was written in Ruby. Of course some of it was JS so I considered converting it to clearly use JS+PHP, it was actually in my to-do-list with a high priority. I also found out about Jcrop a few months after that. Anyway, what happened is that I try to fix bugs before adding major features, and I was at a point where I was considering dropping my work on AeMe to focus on non-SMF stuff, so I naturally never implemented that.

Secondly, and I think it's more important, the main reason I didn't implement that is because I was never sure about the upload process being too long already. I wanted to make it simpler, not more complicated, and adding an extra step like this, while certainly helpful in most situations, is not always going to be desired especially when you're trying to turn AeMe into a "perfect gallery", something that could be used stand-alone...
So, my plans were to use it only when requested -- i.e. keep the main file around, generate thumbnails and previews, and then if the user wanted, they could go to the item page, click a "Edit picture" button or something, and have the choice to (1) rotate the picture (and related thumbnail and preview), (2) resize and/or crop the picture, (3) crop the thumbnail or preview based on the stored picture.
I'm NOT very good at implementing good UI (it always takes me weeks to do that when others could do it in days), so at that point it became a low-priority item, even though it was officially high-priority. It's mainly because of UX (user experience), which I wanted to be 'perfect'.

Now, I'm still considering dropping attachments altogether from Wedge, and using AeMe instead. But first of all I'll need to fix some bugs (and even before that, try to spot them all), then work on a parallel implement of attachments vs uploads, and finally get rid of the attachment system and have someone develop a converter (or do it myself within Wedge...)

It's not an easy task, let me tell you. And it's not helpful that none of us is being paid for it...Well, size doesn't matter here, because it's a process guests don't get, so it has no influence over the apparent speed of a forum, and thus I'm not going to spend a lot of time optimizing it, if anything. Jcrop is a good enough solution, I could rewrite it to use 'proper' indentation and spacing according to my (Wedge's) standards, but I'd rather be able to easily update the script, and/or participate in its development. (Since it's available on github, it's something that can be done.)That is already 'done' in my mind.
As a reminder, AeMe has pictures (limited size but usually large), previews (usually 600x400 or something, for use on item pages) and thumbnails (usually 150x100 or something, for use on album pages). Depending on the type of preview (site homepage or blog), I'd automatically attach the thumbnail (on the left of the text preview) or preview (on top of the text preview, or in a carousel for instance).

Don't believe that just because it isn't in Wedge yet, I haven't thought about it a lot already ;)
Just check out http://nao.noisen.com for an example of how I want Wedge blogs to look like. And ideally I want to simply take the first graphic element in each post, get their thumbnail and offer this as post preview in smaller post lists. (eg site homepage, of which I currently have no example for you, except on sites I'm not related to.)