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
4621
The Pub / Re: Print Page
« on August 22nd, 2012, 03:06 PM »Then the check that normally sets robot_no_index should be modified.
The usual rule is that if there is random stuff in $_GET (i.e. other than topic) and/or if $_REQUEST['start'] is non-numeric (which is set up with msgXXXX for linking to specific posts, new for new items and is numeric if you're using conventional pagination)
robot_no_indexed makes sense in Wedge (overall), and in this situation it does, too. It's about saving users from having to download two extra lines of HTML they don't care about, and will only be useful to search bots...
I forgot to specify that I changed prev/next meta to link to prev/next pages back when I was reading the Google blog, and they published an article about how they were changing their logic to use prev/next links for topic pages so that they can be seen as a single page in the engine. Well, so far I ain't seen that happen... (Not that I'm testing a lot, though.)
Just like when they announced they'd use microformats or microdata or whatever, the schema.org thing, to show clean breadcrumbs in their result pages... Well, the result is that many bare SMF sites have their breadcrumb at google, and Wedge hasn't -- even though SMF doesn't use schema.org breadcrumbs and Wedge does. Thank you very much for the time loss, Google...
I seem to recall it's pretty much only Opera that does with gestures on the browser side.
No. What it means is that it is indexed, but no PR is brought from the main site to the printable version.
Then again, if (and only if) Google's handling of prev/next works as expected on Wedge, then I suppose we can expect it not to need a printpage for that...
Print page actually works, but I dread to think what the memory limit is set to.
I'd say, if mod_gzip and PHP are smart enough to catch the output buffer and gzip parts of it (I believe gzip is suited for chunk transmissions?), then it's not worth worrying too much about memory...
Then again, I'm not exactly a server/Apache/PHP internals specialist, and I probably said something silly.
Oh, and of course, another good way to limit the filesize (and thus bandwidth requirements) is to just strip any whitespace around posts, and/or start optimizing the actual HTML like crazy... For instance, here we have a class for author and for body, with two different tags. It may be smarter to just use a class on top of both of them (in the DOM), and just use class-free tags after it...
I'm still not entirely convinced this needs to stay in the core - other than archiving threads to send to people, I've never used the damn thing.
Possibly, what we could do is, instead of directly showing the printpage version, we could hmm... Show a choice to the user: either print the current page, or print the entire topic, or show an archive of the topic for safe-keeping. Then we could handle all of them differently...
4622
The Pub / Re: Print Page
« on August 22nd, 2012, 01:06 PM »SMF has it, however it uses it to point to previous/next topic, not pages within a multi-page topic (and I can't remember if that's the correct use or not actually)Quote But I think that Google & co know better when it comes to a topic page - especially with the 'next' and 'previous' (prev?) meta keywords in it to indicate that it's a multi-page topic.
So I double-checked my code, and indeed I implemented it into Wedge -- but with a caveat: robot_no_index has to be set to off. So there are many reasons why the meta links wouldn't show up: either there's only one page in the topic (duh!), or it was access through a msgXXX or #new link, things like that...
And what matters is obviously bots only, here. I don't think that accessibility gurus would even kill anyone for not providing these meta links, because seriously... Who ever uses those?! Your browser has to support them, you have to show a special toolbar that takes room in the UI, etc...
Except that it isn't. It's been marked as nofollow for some time, even in SMF, which means search engines are not supposed to consider it for ranking purposes - but they will still frequently index it anyway.
Also note that there are cases where you can screw things up because of the way print page works. For example, try to get the print page of the Aeva topic on SMF, it's likely going to fail hard when it runs out of memory.
The main display staggers it - it pulls one post, processes it, displays it. Print page gets *everything* in one go and then hands it all to the template. For larger topics, doubly so on low-memory configurations, it's going to go splat.
I used to do that precisely on sm.org topics back in the day.
4623
Features / Re: New revs
« on August 22nd, 2012, 10:54 AM »
rev 1668
(9 files, 2kb)
! The Opera hack for keyboard handling in select boxes no longer works in v12.5 because they rewrote and fixed their keyboard event code. Meaning I have to hack even more into it, ah ah... (sbox.js)
* I'm not sure why I kept using .filter(':first') instead of .first() in some place... The latter is faster, simpler and cleaner. Same for .last() and even .children(':first') is better off as .children().first(), thank-you-very-much. (sbox.js)
* Fixed a couple of remaining list() calls into list (), because of its non-function nature. (Class-UnitTest.php, Like.php, getid3)
* Translation. (Admin.french.php, ManageSettings.french.php)
(9 files, 2kb)
! The Opera hack for keyboard handling in select boxes no longer works in v12.5 because they rewrote and fixed their keyboard event code. Meaning I have to hack even more into it, ah ah... (sbox.js)
* I'm not sure why I kept using .filter(':first') instead of .first() in some place... The latter is faster, simpler and cleaner. Same for .last() and even .children(':first') is better off as .children().first(), thank-you-very-much. (sbox.js)
* Fixed a couple of remaining list() calls into list (), because of its non-function nature. (Class-UnitTest.php, Like.php, getid3)
* Translation. (Admin.french.php, ManageSettings.french.php)
4624
Features / Re: New revs
« on August 22nd, 2012, 10:02 AM »
rev 1667
(2 files, 3kb)
! Fixed some specific cases of cascaded selector inheritance (CSI?!) that simply failed. This was a purely logic error and one that took days to spot, and a few lines to fix. As usual with my bugs. The good news is, this should also speed up the extension code by a fair margin, as it reduces the size of the base list, and also drastically shortens the code path for deep inheritors. It's good now. Look at me I'm all weepy. (Class-CSS.php)
- Removed a few pass-by-reference optimizations that were only there for performance, when really with the copy-on-write mechanism it's more likely to make processing slower. By a nanosecond, of course. (Class-CSS.php)
- WeCSS no longer needs to look for prefixes in keyframes when it parses them. This is unrelated to the auto-prefix code itself. (Class-CSS.php)
! Forgot to commit my index CSS from a few commits ago. (index.css)
(2 files, 3kb)
! Fixed some specific cases of cascaded selector inheritance (CSI?!) that simply failed. This was a purely logic error and one that took days to spot, and a few lines to fix. As usual with my bugs. The good news is, this should also speed up the extension code by a fair margin, as it reduces the size of the base list, and also drastically shortens the code path for deep inheritors. It's good now. Look at me I'm all weepy. (Class-CSS.php)
- Removed a few pass-by-reference optimizations that were only there for performance, when really with the copy-on-write mechanism it's more likely to make processing slower. By a nanosecond, of course. (Class-CSS.php)
- WeCSS no longer needs to look for prefixes in keyframes when it parses them. This is unrelated to the auto-prefix code itself. (Class-CSS.php)
! Forgot to commit my index CSS from a few commits ago. (index.css)
4625
Features / Re: New revs
« on August 20th, 2012, 06:49 PM »
rev 1664 (one left to commit -- the JavaScript stuff -- probably not coming immediately though.)
(2 files, 7kb)
* Simplified, strengthened and sped up the hasBrowser function, by a very decent factor! So, now you can use index.ie6,ie7.css if you want, or index.ie[6-7].css, or index.ie[-7].css. Or even index.ie6,firefox[-15],safari[5-].css or whatever you want, really. I'm not going to judge you. I have issues of my own. (Load.php, Subs-Cache.php)
* Reworked detectBrowser() in a similar fashion. Chromium always provides a Chrome version number so we don't need the Chromium detection. Chrome for iOS, however, provides CriOS instead of Version, so I'm now accounting for that. Version numbers are now simplified to the first significant sub-version. For instance, v2.01 would be recorded as '2', v2.1.7 as '2.1' and v2.50.3 as '2.5'. If browser makers don't start screwing up with version numbers, everybody should be happy. Especially me. (Load.php, Subs-Cache.php)
(2 files, 7kb)
* Simplified, strengthened and sped up the hasBrowser function, by a very decent factor! So, now you can use index.ie6,ie7.css if you want, or index.ie[6-7].css, or index.ie[-7].css. Or even index.ie6,firefox[-15],safari[5-].css or whatever you want, really. I'm not going to judge you. I have issues of my own. (Load.php, Subs-Cache.php)
* Reworked detectBrowser() in a similar fashion. Chromium always provides a Chrome version number so we don't need the Chromium detection. Chrome for iOS, however, provides CriOS instead of Version, so I'm now accounting for that. Version numbers are now simplified to the first significant sub-version. For instance, v2.01 would be recorded as '2', v2.1.7 as '2.1' and v2.50.3 as '2.5'. If browser makers don't start screwing up with version numbers, everybody should be happy. Especially me. (Load.php, Subs-Cache.php)
4626
Features / Re: New revs
« on August 20th, 2012, 06:48 PM »
rev 1663 -- and a couple more are coming, as always it's sorted thematically...
(5 files +10-10, 10kb)
* Removed fallback gradient from the index CSS file (as allowed by the previous commit), and optimized/fixed a couple of other gradients. (index.css)
* Renamed all *.ie[6].css (or other versions) to *.ie6.css, because on a philosophical level, the brackets should really only be used for providing ranges. (*.css, skin.xml)
! Fixed inverted gradient in Zoomedia. (zoom.css)
(5 files +10-10, 10kb)
* Removed fallback gradient from the index CSS file (as allowed by the previous commit), and optimized/fixed a couple of other gradients. (index.css)
* Renamed all *.ie[6].css (or other versions) to *.ie6.css, because on a philosophical level, the brackets should really only be used for providing ranges. (*.css, skin.xml)
! Fixed inverted gradient in Zoomedia. (zoom.css)
4627
Features / Re: New revs
« on August 20th, 2012, 06:43 PM »
rev 1662 -- a couple more are coming up.
(1 file, 1kb)
! Undefined variable in keyframes fixer. Woops. (Class-CSS.php)
+ Added support for fallback conversion from standard to prefixed syntax in radial gradients, allowing you to provide only the 'at' syntax. (Class-CSS.php)
! CSS transitions are not limited to the 'transition' keyword. (Class-CSS.php)
(1 file, 1kb)
! Undefined variable in keyframes fixer. Woops. (Class-CSS.php)
+ Added support for fallback conversion from standard to prefixed syntax in radial gradients, allowing you to provide only the 'at' syntax. (Class-CSS.php)
! CSS transitions are not limited to the 'transition' keyword. (Class-CSS.php)
4628
The Pub / Re: Print Page
« on August 20th, 2012, 11:04 AM »1) It could be a plugin rather than a core feature. The savings for the bulk of forums would be quite significant since robots do often follow nofollow links, they just don't carry link juice through. So removing it entirely would actually save quite a bit of bandwidth in the long run.
OTOH, one of the good points of printpage is that it gets you more chances to have multiple keywords stuffed in it. But I think that Google & co know better when it comes to a topic page - especially with the 'next' and 'previous' (prev?) meta keywords in it to indicate that it's a multi-page topic.
Which I just realized is NOT in Wedge..?! I thought I'd implemented that long ago... :-/
2) If it's not made a plugin, it could have permissions attached, e.g. default to be not visible to guests.
4629
Other software / Re: More thoughts on SMF 2.1
« on August 18th, 2012, 05:14 PM »*shrug* Moving on from Curve had to happen sooner or later.
(Not saying that Weaving is modern... It just is a bit more.)
Well, a mini-menu for actions is definitely an improvement, and I'm not in the slightest surprised that things are going both ways. In some ways I'm actually kind of pleased because what it means is there is less hostility going on and more that everyone's doing what's best for the software and community.
Oh, and I knew I'd already seen this button style before... It's the Youtube interface, actually!
It's popular, available easily and looks good. Hardly surprising more people are using it.
Well, as I said, these days my local install varies between Segoe UI and Calibri, and since I never found out what I'll be using for the final official version, I'm sticking to Arial for now... Heck, I might even go back to Verdana if I'm sufficiently bored... :lol:
The main issue with Calibri is its odd x-height. Yesterday I finally found a Google webfont that has the same dimensions -- Source Sans Pro, the 'first open source font by Adobe'. Sure. But it's a Calibri rip-off, or replacement if you will :P
So now I'm tending towards using Calibri, with a Source Sans fallback (it has the disadvantage of being rather heavy, although not as much as PT Sans for instance. The solution is to just keep to non-bold non-italic versions, and basically have Wedge treat it like a Tahoma when it comes to using bold and italics... I know, it sucks!)
Or I could stick to Open Sans, too... I like it and it's lightweight :lol:
But it's a matter for another topic I guess...
4630
The Pub / Getting ready for an alpha release...
« on August 18th, 2012, 12:24 PM »
So... I'm looking into making this August 25 date a reality, right...? :edit: Obviously at a later date, now...
In order to achieve such a close release date, I needed to decide that some of the features I want for 1.0 will have to go through an upgrade script of my own. I hate the idea, but I'd rather postpone 20% of my features (and a stable release), than have Wedge remain vaporware forever... Plus, the interest we might generate could help get more developers onboard.
So, there are places in the code where "I'm not too sure" about what I've been doing, and here's what I'll do: I'll simply post patches and ask for feedback... This is better than withholding commits until I'm sure of what I'm actually doing.
Could you guys review the first patch? It's a simple one really -- it's something we discussed before, the default lengths for various database columns. I tend to forget what we talked about, especially when it comes to MySQL, so I don't know what is "right" and what isn't. And because we're going to have an upgrade script eventually, it also means we can safely change these field lengths later in the process, so I'm not even sure this patch needs applying at all.
Yet, there might be a few fields that warrant shortening or lengthening. You tell me. Thanks.
:edit: Removed attachment to make it possible to have the topic in public...
In order to achieve such a close release date, I needed to decide that some of the features I want for 1.0 will have to go through an upgrade script of my own. I hate the idea, but I'd rather postpone 20% of my features (and a stable release), than have Wedge remain vaporware forever... Plus, the interest we might generate could help get more developers onboard.
So, there are places in the code where "I'm not too sure" about what I've been doing, and here's what I'll do: I'll simply post patches and ask for feedback... This is better than withholding commits until I'm sure of what I'm actually doing.
Could you guys review the first patch? It's a simple one really -- it's something we discussed before, the default lengths for various database columns. I tend to forget what we talked about, especially when it comes to MySQL, so I don't know what is "right" and what isn't. And because we're going to have an upgrade script eventually, it also means we can safely change these field lengths later in the process, so I'm not even sure this patch needs applying at all.
Yet, there might be a few fields that warrant shortening or lengthening. You tell me. Thanks.
:edit: Removed attachment to make it possible to have the topic in public...
4631
Features / Re: New revs
« on August 18th, 2012, 10:05 AM »
rev 1661
(3 files, 3kb)
! Fixed handling of @keyframes in WeCSS. (Class-CSS.php)
! Fixed a bug in surroundText() that made it fail when called with an empty selection (e.g. smart quote splitter.) (editor.js)
! And fixed another bug in surroundText() that made the focus go to the end of the post because of a last-minute pre-commit optimization -- you know, my biggest flaw. At least I'm aware of it. (editor.js)
! Bytesizenazi. (editor-func.js)
(3 files, 3kb)
! Fixed handling of @keyframes in WeCSS. (Class-CSS.php)
! Fixed a bug in surroundText() that made it fail when called with an empty selection (e.g. smart quote splitter.) (editor.js)
! And fixed another bug in surroundText() that made the focus go to the end of the post because of a last-minute pre-commit optimization -- you know, my biggest flaw. At least I'm aware of it. (editor.js)
! Bytesizenazi. (editor-func.js)
4632
Off-topic / Re: Randomly I wish I worked in an office
« on August 18th, 2012, 09:34 AM »I'll certainly try and take a look.
I'm not sure what I should do then... Try to reproduce, or add a failsafe to the JS, or just ignore it?
4633
Off-topic / Re: Nexus 7
« on August 18th, 2012, 12:07 AM »I never really liked Opera Mini, will maybe at first since it compresses and down scales everything, but that was when most data packages where slow. Every site is going to have a problem with Mini because how the Opera server mangles everything when it compresses it to send it to the users device
.
Now I use Opera Mobile which is a more fuller web browser that doesn't query the Opera server for compressed or lower quality data.
However I rather browse with the browser set as "Desktop" so every website I view thinks it is a desktop and not mobile. When I took the screen shot I let the site detect it as mobile, but I rather not browse in that format if you know what I mean.
Can you get Opera Mobile on your device? Opera Mini just is blah.
So, basically, Apple is abusing their monopoly...
PS: oh crap, another bug... Looks like the smart quote splitter is broken in Opera. Even in older versions..?! And even when manually rewriting surroundText() to avoid going though the Opera path... :-/
Posted: August 17th, 2012, 11:07 PM
Uhoh... Broken in Firefox 16 just the same. Not broken in IE though... Go figure!
Posted: August 17th, 2012, 11:16 PM
PS: oh crap, another bug... Looks like the smart quote splitter is broken in Opera. Even in older versions..?! And even when manually rewriting surroundText() to avoid going though the Opera path... :-/
4634
Other software / Re: More thoughts on SMF 2.1
« on August 17th, 2012, 11:23 PM »
So... Today I was bored, and while spending time reinstalling my music library on my iPod (I'm faaaar from being finished, to think that I could have just kept the backup I made earlier today! >_<), I also installed SMF 2.1 for the first time on my computer...
Well, it seems (from what I see in the changelogs) that they replaced the default theme with Penguin this week, so I was right on time or something.
And it's looking pretty good. Not Wedge-good I'm afraid, but good enough that there are a couple of details I might as well steal from them (the conveniently located Unread links for boards perhaps, the fine yet still sober buttons which really make me think I should reuse my own button stylings for topic buttons), and good enough that I'm amused (rather than upset) that they took ideas from Wedge... Again ;)
Among more minor things, the more noticeable is that they now use a mini-menu for post actions, just like Wedge.
I just have to ask though... What is it with everyone going for Segoe UI these days? I'm actually considering just staying with Arial 14px because there are so many Segoe UI forums these days :lol:
Oh, if someone at SMF is reading... I only had a very quick look at the source code, but even in less than a minute I managed to stumble upon a typo in a variable name :P 'bbcode_handling' is written as 'bbcode_hanlding'... Several times ;)
Well, it seems (from what I see in the changelogs) that they replaced the default theme with Penguin this week, so I was right on time or something.
And it's looking pretty good. Not Wedge-good I'm afraid, but good enough that there are a couple of details I might as well steal from them (the conveniently located Unread links for boards perhaps, the fine yet still sober buttons which really make me think I should reuse my own button stylings for topic buttons), and good enough that I'm amused (rather than upset) that they took ideas from Wedge... Again ;)
Among more minor things, the more noticeable is that they now use a mini-menu for post actions, just like Wedge.
I just have to ask though... What is it with everyone going for Segoe UI these days? I'm actually considering just staying with Arial 14px because there are so many Segoe UI forums these days :lol:
Oh, if someone at SMF is reading... I only had a very quick look at the source code, but even in less than a minute I managed to stumble upon a typo in a variable name :P 'bbcode_handling' is written as 'bbcode_hanlding'... Several times ;)
4635
Off-topic / Re: Nexus 7
« on August 17th, 2012, 06:14 PM »
Good news: I'm now running iOS 5.1.1... (unjailbroken. Will have to do that later...) And the update went without having to go back to an unjailbroken version, so it was easy.
Bad news: I made a backup of my music folder (20GB) into my hard drive (30GB free). Then launched the update. It told me there wasn't enough space to back up my media, so I figured okay it's going to back it all up so let's let it do it by itself... I proceeded to remove my backup folder, and launched the upgrade. When I came back an hour later, I had an error message saying there was a synchronization problem. Okay... I rebooted my iPod, it was upgraded to iOS 5, yay, and then I noticed the music folder was empty. Then I looked into my hard drive, and it had 30GB of free data, meaning that none of my music folders had been backed up!
Thank you, Apple..!!!
The music library is still 'backed up' as a text file in iTunes, so I'm going to have to find every CD again on my hard drive and copy it manually... About 200 albums. Again, thank you.
Additionally, iTunes 10.6 is extremely slow to sync. Heck, I started this post after launching a copy request, and it's still frozen. Thank you very, very much Apple. I know what I'll be doing when I consider buying an iPhone... I'll do something else with my money.
Also, Opera too can be an ass...
Opera Mini 7.0.x gives a user agent string that basically identifies it as Opera 11.10. Fine by me. However, Mini doesn't support gradients -- while 11.10 desktop does!
And I don't really see myself going through detectBrowser to add a special case... Or even adding mandatory fallbacks before the linear-gradient line when the browser itself is saying it supports gradients... -_-
Bad news: I made a backup of my music folder (20GB) into my hard drive (30GB free). Then launched the update. It told me there wasn't enough space to back up my media, so I figured okay it's going to back it all up so let's let it do it by itself... I proceeded to remove my backup folder, and launched the upgrade. When I came back an hour later, I had an error message saying there was a synchronization problem. Okay... I rebooted my iPod, it was upgraded to iOS 5, yay, and then I noticed the music folder was empty. Then I looked into my hard drive, and it had 30GB of free data, meaning that none of my music folders had been backed up!
Thank you, Apple..!!!
The music library is still 'backed up' as a text file in iTunes, so I'm going to have to find every CD again on my hard drive and copy it manually... About 200 albums. Again, thank you.
Additionally, iTunes 10.6 is extremely slow to sync. Heck, I started this post after launching a copy request, and it's still frozen. Thank you very, very much Apple. I know what I'll be doing when I consider buying an iPhone... I'll do something else with my money.
Posted: August 17th, 2012, 05:56 PM
Also, Opera too can be an ass...
Opera Mini 7.0.x gives a user agent string that basically identifies it as Opera 11.10. Fine by me. However, Mini doesn't support gradients -- while 11.10 desktop does!
And I don't really see myself going through detectBrowser to add a special case... Or even adding mandatory fallbacks before the linear-gradient line when the browser itself is saying it supports gradients... -_-