Wedge

rev 818
(10 files, 14kb)

* Replaced zoomedia's "rel" hack with actual class names[1]. Still not used for now, but it'll be better in the long run anyway. (Aeva-Embed.php, Aeva-Gallery.php, Aeva-Subs-Vital.php, Subs-Media.php) Media.template.php)

* Moved media details to the sidebar in case the browser is Safari Mobile. It can't cope with the width anyway. (Aeva-Gallery.php)

* Moved some media action bools to proper context variables. Added bonus: action bar won't show up at all if you can't do anything. (Aeva-Gallery.php, Media.template.php)

! Search was broken. (Search2.php)

! Hardcoded language string. (zoomedia.js)

* Some layout improvements in media homepage and media item pages. (Media.template.php)

- Removed shortcut keys from media strings, as they're no longer valid. (Media.language.php)

* Improved vertical alignment in error log. (Errors.template.php)

- No need for an id in auto-generated shims. (zoomedia.js)

1.	That's because they don't validate in the new html5 validator...

Ah AH!

I just had a tech guy from my ISP visit my place. They wanted to look into my line speed because they thought it was suspiciously bad -- I'd always been limited to around 5Mbps (at best) since I moved in.
Well, after looking at my phone connectivity, he pointed out a capacitator that didn't need to be there, he removed it in under a minute and... voilà! My Net speed is now at 8.3Mbps! That's over 850 KB/s in real conditions.

Shouldn't have I got this connection problem yesterday, I'd never have asked for a tech to come over -- and I'd still be 300 KB/s below my new limit (actually, I'd be at half the current speed, because I was limited to 410 KB/s these last few months and never cared to ask why.)
At last something good came out of these problems :)

How old are you, Unknown?
If you're younger than Pete is, does that mean you were one of those Dragooon-like wizkids back when you started SMF?

I hate those fucking wizkids, they always end up being faster and better than me :niark:

Actually, I hadn't tested Search in a while, and the errors were due to not removing a line of code from a deprecated feature. Thanks! Fixed now.

The last few days were interesting, to say the least.

I don't exactly know what's going on in the irony department up there, but it feels like someone's determined to make me waste my time. Apart from the usual real-life issues (including but not exclusively, my driving license, of which you can see a picture on my Facebook page because, yes, I'm that shallow), and from the PC apocalypse I told you about in my last post, I also faced two new problems this week-end.

First of all -- the new computer I bought has the Intel P67 bug with the SATA interface. Meaning half of my SATA ports are not usable. One of them was being used by a hard drive so I just moved it to a safe port, but it now means all 4 of my safe ports are taken (plus my only eSata port), and I can't add any other hard drive. Thankfully I didn't exactly plan to do that either, as I already have USB3 ports which will come in handy in the future.

The only question then, is whether or not I should bring back my computer to the shop. I mean they're not supposed to sell me a buggy motherboard when Intel recognized the bug and everyone recalled their motherboards months ago already. I'm definitely unlucky these days.

Also in the let's have fun category, my ISP apparently decided to go play with my Interwebs cables, and overnight my download rate went from about 4 Mbps to under 10 Kbps. Yes, I'm talking about bits per seconds, not bytes. See, I've been on the Internet since March 1996, at which time I had a trusted 28.8 Kbps US Robotics modem. Anyone remember these? They were the top modem makers at the time. But they still ran at 3 kilobytes a second. It wasn't funny. Well, my bandwidth was one third of that for nearly 48 hours. Back in '96, web pages were just a few kilobytes of HTML, possibly a few images, later a CSS file or two, but jQuery couldn't have even existed at the time. Even the first versions, which were very light and quick to load, would take many seconds to load on an old modem. This is one of the reason why I spent so much time working on reducing the footprint of both jQuery and general JavaScript code in Wedge, when I could just have stopped worrying and dropped the compressor. I was adamant that Wedge SHOULD be faster than SMF in every possible way, and most of the work had to be done on the final output. It took me weeks just to get to the point where, comparing stock copies of Wedge and SMF, I concluded that Wedge felt faster to load than SMF. It's a personal feeling, see, it can hardly be calculated with a stopwatch. But even reaching that point was hopeless to begin with, because we'd decided on including jQuery. So we got the best of both worlds. But I still have to fight myself to determine what version of jQuery we'll ship with in the end. I mean, we started Wedge with 1.4.4, then switched to 1.5.2 with absolutely no benefit to us, and then to 1.6 where I reported a handful of annoying bugs, and once again I don't see any benefits... I guess I'm waiting for 1.7 to determine whether it's worth upgrading. But right now, as it is, I'm actually tempted to go back to 1.4.4, and save the extra 5-6 KB that 1.6.1 uses. 5 to 6 KB may not be much to you, but it's worth a lot to others.

And somehow, after my horrible Sunday experience, I can't help but wonder: won't somebody please think of the analog modems? These days, it's all about working from home and avoid commuting. So, people can go live anywhere they want. What happens to those who happen to find a heavenly place with no DSL lines around? What happens when all of the web is optimized for broadband? Will analog users end up as the digital man's stoneman? Be viewed as disabled, maybe? WAI-ARIA to the rescue, or no future for losers?

We need to stop wasting resources. Just because a font looks cool doesn't mean you should force your user's browser to download it every time they come to your website. Interestingly, that's exactly what I did a few weeks ago. I went for PT Sans as the default header-type font in Wedge, but decided against specifically calling it from Google Fonts, as fast as the service is. I just don't see the point in doing that when you can simply tell your users to download the font and install them by themselves. Then they no longer have to download it again -- and the font can start popping up everywhere.

Install a font and save a tree!
Find your raison d'être!
To arms, my brothers!

rev 817
(5 files +1, 9kb)

+ Added support for IE 10 in the PHP code, and used it to provide real gradients for it. (Class-CSS.php, Load.php, index.ie10.css)

! Pretty URLs were broken. Again. (ManageSettings.php, Subs.php, Admin.template.php)

Aeva can be used as a download system btw.

Overall go read the feature list boards ;)

No, I'm not into football. I don't watch much sport in general.