Wedge

I don't know about Pete, but I tend to spend most of my time fixing implementations rather than implementing new things, and when I implement something new, I tend to go for what for will make Wedge better, rather than what I absolutely want in it. (Sometimes these go well together, though, but I try to be realistic!)

Only, we still use the addcslashes on double-quotes that's originally in SMF2.
So we get value="\"Something\"" which in turn some browsers will see as '' (empty), and others as \, but never as "Something".
So I got rid of the addcslashes.

I think that in non-Wys, I should reset the select box to default all the time, since it never updates when moving through the post.

Ain't got time to check (dozens of bugs at the same time :P), but how is it correct behavior exactly...?
Also, I suspect this would only happen in Wysiwyg?

Reusing the Wedge feature would be good.
With a profile setting to disable communication with FB if one doesn't want to share likes over there? Or maybe a per-post choice.
And making sure not to share the like if done on a non-public topic.

So, err... Just wanted to point out that I just restored the Media area on Wedge.org ;)
The importer doesn't deal with AeMe yet, but I transmitted my import notes to TE so that he can easily do the job.

So what's new in Wedge's Media area, compared to SMF's Aeva Media...?

Really, mainly two things:

- the Media area is based upon AeMe 2.1, i.e. the commercial version. (Feature list.)
- the Highslide lightbox (dozens of kilobytes of JavaScript code) was replaced with my very own Zoomedia (4kb of code, 1.75kb gzipped :P), which has the same feature set (except for slideshows and other details), and will eventually match it. Zoomedia is still under development, and its main reason for being, is that the Highslide license is quite unclear and couldn't possibly be used on 'commercial' websites, even if it's just a fan website with a few ads or something. So, Zoomedia's license will be much simpler -- it's the Wedge license -- so you can use it on commercial websites for sure. There you go.

Audio/video embedding is non-existent at best. Wedge is still using JWPlayer at this point, and I'm not sure where to go with it.
- Keeping it? Means that commercial websites need to buy the license... Same problem as with Highslide. (Except that the Highslide problem is fixed now :P)
- If keeping it: staying at the current version will prevent JWP from using its latest improvements. But OTOH it's also the last version that doesn't enforce the watermark logo, ah ah.
- Removing it? That would also mean removing the audio spectrum analyzer, which looks really cool (I do have the source code and I guess I could port it to something else, but... it's not like it'd be enjoyable a task). And then, replacing it with what?
- FlowPlayer? The license is unclear at best, while certainly better than JWPlayer's.
- MediaElementJS? It's a nice replacement indeed. But I don't know if it's ready for use in Wedge. Hadn't been on their website for some time. Last time, everything worked. This time, their audio player is broken... Hmm. And it seems that the volume control never records the current volume. (Although it could be done in JavaScript + cookies if using the non-Flash version of the player.) Also, MEJS currently doesn't support 'proper' playlists. Although Aeva Media's playlist system is 90% custom stuff and just expecting the Flash component to 'play along', I'm not sure it'd be easy to do in MEJS. Maybe even in Flow...
- Something else? What?

It feels like I've had these conversations last year already, it's probably even the case, but now would be, I guess, the right time to look into it again...

Oh, and... ZOOMEDIA FEEDBACK WELCOME :P

Even SMF has a phpBB importer ;)

Imagine that: clicking the submit button right when the autosave triggers.
It's only a problem for a week at the most, though.