Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Nao
7531
Off-topic / Re: quirksmode.js
« on October 7th, 2011, 03:01 PM »
It's still a reference to me, though. Most of my IE compatibility tests are done against quirksmode. :) (Such as, recently, testing for :only-child not being supported by IE6-8... While :first-child:last-child is apparently supported in some situations.)
7532
Features / Re: New revs
« on October 7th, 2011, 02:50 PM »
rev 1070
(5 files +1, 11kb)

* Forgot to restore page title in non-Ajax errorlog file viewer. (ManageErrors.php)

* Moved Go Up and Go Down JavaScript code to an external script. (Display.template.php, topic.js)

- Moved sJumpToTemplate from JumpTo object to the HTML itself, saving us a few bytes and the need to escape the text string (which, incidentally, wasn't escaped in the first place.) (Display.template.php, MessageIndex.template.php, script.js)

@ Oops... I committed /images/.htaccess by mistake. Will remove it from the trunk in my next commit. I can't afford to have it committed until I've decided whether these files really should be cached forever...
7533
Features / Re: New revs
« on October 7th, 2011, 11:39 AM »
rev 1064
(5 files, 7kb)

* Always set is_ajax (whether true or not), and never set hide_chrome unless through actually calling hideChrome(). (ManageErrors.php, QueryString.php, Subs-Template.php, Help.template.php)

* Simplified errorlog viewer code which was needlessly adding headers. (Errors.template.php)
7534
Features / Re: New revs
« on October 6th, 2011, 07:33 PM »
rev 1061
(2 files, 6kb)

! An admin maintenance page had broken HTML. (Admin.template.php)

+ Reintroduced $modSettings['compactTopicPagesContiguous'] to the page index code, but only for compatibility with SMF imports, i.e. new installs will never use it. (index.template.php)
7535
Features / Re: New revs - Public comments
« on October 6th, 2011, 06:53 PM »
Quote from Arantor on October 6th, 2011, 05:50 PM
Quote
We should probably get started on removing the bin right now...
That's cool, provided that we come up with a functional replacement.
The ''approved' bit...? Setting it to '2' for future posting (or whatever), and '3' for 'deleted'...? Isn't it enough?
We could simply rename it to 'status', 'state' or 'online'... (Well, that would be something we need to correctly import from SMF... ;))
Posted: October 6th, 2011, 06:52 PM
Quote from Arantor on October 6th, 2011, 05:50 PM
I didn't get into the error in recycling topics, I didn't see a lot of point, but I did look into the other error that was mentioned at the same time in repairboards.
But I suspect we'll be getting more of this 'empty skeleton' error where we expect it the least... Maybe I should give up on that 'feature'.
7536
Features / Re: These two bytes may not matter to you...
« on October 6th, 2011, 06:48 PM »
Maybe I just didn't port that bug fix into my copy of Noisen/Wedge.org...? I mean, originally Noisen runs on SMF 2.0 Beta 1 (the September 2007 release), and I applied all subsequent updates manually...
Quote from Arantor on October 4th, 2011, 06:45 PM
Therein lies the issue. I don't really expect to do much maintenance, even less than with BB.
Then, you may easily compress the files.
Anyone can re-download them from the relevant website (getid3 or libsecsomething) and replace their minified files with the originals...

The comments aren't needed for phpseclib and with the header that retains the copyright and so on, I spent 15 minutes on it and got it down to 280KB or so, then just spent time faffing about cleaning the code, didn't really change the size but it did make it tidier. It'll zip fairly well, I think, haven't tested it.

Oh, speaking about zipping... I made a few tests with a Sep. 15 revision of Wedge.
I didn't test with WinRK (it's not free), but I think it wouldn't be (much) better than PAQ...
Also, please remember that the Wedge package is currently 50% bigger than SMF's -- add 1.5MB for AeMe, 500KB for /other/stupid-sub-folders/*, and the rest is mainly new features, new code etc...

ZIP: 3653kb (by comparison, SMF = 2610kb)
ZIP (best): 3642kb
tar.gz (best): 3132kb (85% of the zip file) (by comparison, SMF = 1941kb, i.e. 74% of the zip file)
RAR (best): 3006kb
tar.bz2 (best): 2734kb (75% of the zip file) (by comparison, SMF = 1598kb, i.e. 61% of the zip file)
7z SFX LZMA (ultra): 2688kb
RAR (solid best): 2464kb
7z SFX PPMd (ultra): 2450kb (67% of the zip file)
ZPAQ: 1983kb
PAQ8o: 1828kb (50% of the zip file)

So... PAQ does twice better than ZIP, but it's not very realistic to use it (too long to compress, too much Ram needed....), so 7z SFX PPMd (which doesn't require any decompression program per se) would be a good alternative for offering a downloading to non-techies. (Okay, Mac users may be non-techies as well but I'm catering only to Windows users for now...)
I'm not exactly sure, though, why bz2 is less efficient on Wedge than on SMF... Do we have that many extra image files in it, for instance...?

Oh, and where are you now, regarding the SMF 2.0.1 patch?
Quote
How important is it to keep the download size small vs readable? I'm not actually that fussed myself.
Anything we maintain should be readable. Anything else we use, the smaller the better. We don't want a big download size, not because it's "big", but because it costs money to cover for the bandwidth -- although we can probably share the files via Mediafire and so on... Or just extra mirrors... And because I'm not sure people would like to download and reupload a big file 10 times a year just because we release early and often. I know I wouldn't...
(Then maybe we should have some kind of system that automatically sends the updated files to the server.)
Quote
Quote
- doing on-the-fly minification (i.e. not cached...) on inline JS and CSS. Do you think it's realistic? I'm not sure myself, but I could cook up a simplified minification function, although I wouldn't know how to deal with strings. Hmm. Still, just as an example, if I manually minify the noi_resize() code, I save something like 60 to 80 bytes off the page, and a reasonable ~20 bytes when gzipped. Considered it's to be found on every single page...
If it's on every single page, why is it inlined? Or, at least, not minified by hand?
It's inlined because I need to execute it ASAP. Waiting for jQuery to run is out of the question. It would save probably a hundred bytes, but would create a very noticeable delay when loading a page that doesn't match the expected viewport width. Then again, onresize() doesn't execute when using the Back button (at least in Opera), so it's not exactly a 'perfect' solution anyway. Doing my best...

Can be compressed manually, yeah. But I figured I'd rather have it done logically -- if one part of the inline code is compressed, then all of it should be compressed. And I'm not sure what to use to minify JS when it comes to something that has to be done on-the-fly for everyone, on every page, instead of done once and cached...
Quote
Aren't the timestamps included in the filename? They are for avatars.
No, I don't think they are (for media files). If you update the file with the same file, it gets the same filename.
Which is a bit of a bummer...

Oh, and I'd love us to consider showing preview & full sizes in plain view as well. As long as the filenames can't be 'found out' by analyzing the thumbnail URL...
Quote
I wouldn't worry about YepNope, because you're still doing more work that doesn't - ultimately - benefit the user. It just fools a score.
Yeah, I suppose so... And even YSlow doesn't care about jQuery being there. Only Google PageSpeed does. And it would only save at BEST 2% because I get a maximum score of 98%, even with jQuery loaded normally.
Quote
Quote
- Considering using "FileETag none" in all htaccess files. I'm not a specialist though... But as soon as we have an expiration date, ETags aren't useful at all. I'm not sure if it should be done for all files.
If you have an expiration date, the ETag is still good until that date.
But technically it's not used at all because the browser will no longer request the resource (as long as it caches it, of course.)
Hmm, seems like YSlow doesn't recognize my FileETag query. Maybe I should also do 'Header unset ETag'... And any removed header means more space for pure data...
Does Chrome have an extension to help view request headers?
Quote
It's embedded into the HTTP request, which is only sent once for the request,
Phew...
Quote
even if the header is split across multiple packets because of lots of extra headers. It's still worth keeping it as small as possible (though, frankly, I don't see how else we can!) simply to hope we can keep it into as few packets as possible.
Yeah, well, I suppose it's not as scary if the cookie is loaded sent once. The first packet will be shortened a lot, but not the rest.
Quote
http://tracker.wedge.org/?sa=ticket;ticket=28 ;) Yes, we save multiple PHP/DB requests *per page load*.
Ah, I forgot about that ticket...
Then I guess we agree on this, eheh.
Do you want to implement the change?
7537
Features / Re: New revs - Public comments
« on October 6th, 2011, 05:39 PM »
Quote from Arantor on October 6th, 2011, 03:05 PM
Works for me.
Done...
Also converted the floor((int) x/2) to just x>>1, which does exactly the same thing... Only faster :D
It's funny that SMF's version of the conversion is even more complicated, something like ((int) x - ((int) x % 2)) / 2... Lol.
Quote
On the one hand I see the wisdom of this, and on the other, I find I'm not actually that bothered by setting it.
I think we renamed a few 'important' things in the past... Can't remember which, though. Well, I guess our users will tell us in time ;)
Quote
Then let's figure out how it should work instead of trying to fix issues that will be obsoleted out.
We should probably get started on removing the bin right now...
Quote
You are allowed to have a break, you know :)
I'm not sure about that... My schedule... It's... Oh well, I guess we can screw my schedule...
Quote
It was down to how the select handling worked, I've since made a change to Subs-Menu that deals with these cases, though repairboards is the only case of it.
Are we talking about the same thing...? The empty skeleton error?
7538
Features / Re: These two bytes may not matter to you...
« on October 6th, 2011, 04:08 PM »
Is this on Wedge, or Wedge.org...?
Wedge.org is running SMF2 RC4, not Wedge.
7539
Quote from Arantor on October 6th, 2011, 03:16 PM
They can disable smileys at read time? First I've heard of it.
Well, I'm not even sure whether they can change the smiley set... :P
7540
Well... Actually... Now that I think about it, even if someone uses a different smiley set than the author's, it should show their own smiley set -- because Wedge uses divs with a class name, and the class name is the same in all sets... So I'm cool with that.

(Except I'm not sure anymore whether people can disable smileys at read time... In which case we'd have to do a preg_replace or something to delete smiley classes.)
7541
Features / Re: New revs - Public comments
« on October 6th, 2011, 02:58 PM »
Suggestion with contiguous pages:

$contiguous_pages = isset($modSettings['contiguous_pages']) ? $mod[..] : 5;

(Can't remember the name of the variable off the top of my head.)
This would allow Wedge to simply re-use the imported SMF's value; although probably not very important...
Similarly, every time we change the name of an SMF variable (from $modSettings and $settings, I mean), we should ensure it's also reflected in the import tool.

Thorsten, do you keep track of these...?
Quote from Nao on October 4th, 2011, 11:11 PM
Re: restore posts, I couldn't find the origin of the skeleton error. Argh. If you could look into it as well... I have no time to actually go and try to restore posts for now.
Headache... Tried to delete another post, and it doesn't show up in the recycle bin. I probably disabled it... But then why did my earlier topic get put into it...? I suspect there's something awry here.
Again, not really worth much of my attention, as I'd really like to get rid of the bin before we go alpha...
Quote
Loosely related: when deleting a post, Wedge should update its 'children' posts to use the deleted post's parent ID. Should be easy enough, but we then have to update their own children, too... I'm not sure how to do this with minimal impact on the DB performance.
I committed my query for this. Heck, it pissed me off so much, I didn't take time to actually test it... (I mean, it doesn't crash, but I haven't tested with phpMyAdmin around.)

Been procrastinating a bit regarding Wedge lately... Got hooked on Misfits (UK show). Misfits is to Heroes what Skins was to 90210 & co. (Well, except I liked the first few episodes of Heroes better than the first season of Misfits. But then again, they should have made Heroes focus on Hiro and last only one season... Instant cult show.)
Posted: October 6th, 2011, 02:57 PM
Quote from Arantor on October 4th, 2011, 11:47 PM
Something about pretty URLs causes redirectexit() - no parameters - to fail. In the spirit of interest, while already logged in, head over to action=login and see what happens. If that fails the same way (which I expect it to), there's your culprit.
Nope..... :(
No error.
7542
Features / Re: New revs
« on October 6th, 2011, 02:49 PM »
rev 1060
(5 files, 8kb)

+ Temp query to update children's parent IDs when deleting a post. To do: also deal with topic splitting... (RemoveTopic.php)

* Updated top menu arrow with a version that's more in line with the current menu colors. (menurow.gif)

* Using :only-child instead of :first-child:last-child where possible. A better solution in this case would be to modify all templates to use 'centertext' in the owner div, and get rid of the p tags. If you don't understand, that's okay, just like I'm not asking you how to forge a +5 fire sword. To each their own. (index.css, index.ie8.css)

* French translation. (ManageSettings.french.php)
7543
Off-topic / Re: RIP Steve Jobs
« on October 6th, 2011, 12:46 PM »
It's very sad. :(
7544
And people disabling smileys?
7545
Off-topic / Re: Repurposing WP, or not.
« on October 6th, 2011, 12:51 AM »
Roles are okay as long as the software tells me what their permissions are exactly. Wp doesn't.