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
1156
Features / Re: Plugin revs
« on March 11th, 2014, 07:47 PM »
[Commit revision ca8653a]
Author: Nao (Signed-off)
Date: Tue, 11 Mar 2014 19:47:15 +0100
Stats: 1 file changed; +1 (insertion), -1 (deletion)

  • Minor validation error. (skin_selector/SkinSelector.php)
1157
Features / Re: New revs
« on March 11th, 2014, 04:35 PM »
[Commit revision 2b8ffa8]
Author: Nao
Date: Mon, 10 Mar 2014 20:12:36 +0100
Stats: 1 file changed; +12 (insertions), -5 (deletions)

  • A bit of love for iOS. Well, really, I don't like it anymore, but that's no reason not to commit the iOS-specific font stack I'd been using locally before I switched to a proper mobile OS. (common.css)
  • Also gathered big font definitions under a common font stack. Don't bother. (common.css)
  • Re-adding support for flexbox for Opera 12.1. Whoever's still using it will be glad. Vive la Résistance ! Technically, the only 'difference' is that I checked my code again under the browser, and it worked just fine, so I'm assuming a recent change fixed it. (common.css)
  • Re-adding support for flexbox for iOS 7+, but since I'm unable to test it, I'm doing this in the blind. Technically, though, it doesn't matter because touch-friendly devices all default to a mobile skin by default, and mobile skins don't really make use of flexboxes, so... (common.css)

[Commit revision 0bce09e]
Author: Nao
Date: Mon, 10 Mar 2014 21:47:47 +0100
Stats: 1 file changed; +1 (insertion), -1 (deletion)

  • Making the IE6/IE7 warning message a bit less intrusive, in case the guest user really has no way to upgrade. (Errors.template.php)

[Commit revision ec1a335]
Author: Nao
Date: Tue, 11 Mar 2014 14:24:29 +0100
Stats: 1 file changed; +0 (insertion), -1 (deletion)

  • Commenazi. (common.css)

[Commit revision 9ac659a]
Author: Nao
Date: Tue, 11 Mar 2014 14:27:01 +0100
Stats: 1 file changed; +2 (insertions), -2 (deletions)

  • Shorter opacity animation times in menus, should help make them closer in spirit to the old code. (index.css)

[Commit revision 7732394]
Author: Nao
Date: Tue, 11 Mar 2014 14:30:11 +0100
Stats: 1 file changed; +4 (insertions), -1 (deletion)

  • Fixing height problems on img tags when only a height was set. Well, it's complicated... It won't solve situations where you'd want to resize an image and not respect its aspect ratio, but... Why would you want to do that, exactly..? (index.css)

[Commit revision 56b79ca]
Author: Nao
Date: Tue, 11 Mar 2014 14:36:43 +0100
Stats: 1 file changed; +13 (insertions), -16 (deletions)

  • Separated all category classes (cat, title and title2) into classes all derived from catbase, instead of title2 extending on title extending on cat extending on catbase. This should make it MUCH easier to rewrite either of these, without having to rely on unextends or reset tricks. (index.css)

[Commit revision a8d3e5a]
Author: Nao
Date: Tue, 11 Mar 2014 16:02:39 +0100
Stats: 1 file changed; +7 (insertions), -6 (deletions)

  • And now for a, hopefully, more responsive footer... The logo never should get in the way again if you don't have screen estate to spare. (index.css)

[Commit revision 00ef483]
Author: Nao
Date: Tue, 11 Mar 2014 16:22:46 +0100
Stats: 1 file changed; +5 (insertions), -5 (deletions)

  • Trying to zoom into a chart from the right of its last available date would show 'undefined' date ranges instead of the last date. (wraph.js)
  • Err... Why did I put a Math.max between 0 and a number I know will be positive..? (wraph.js)

[Commit revision 8ac388d]
Author: Nao
Date: Tue, 11 Mar 2014 16:33:02 +0100
Stats: 1 file changed; +18 (insertions), -3 (deletions)

  • Adding styling for the homepage's topic list. Can you imagine I didn't notice this was in my custom.css file until now, and therefore not committed..? (sections.css)
1158
Features / Re: Plugin revs
« on March 11th, 2014, 03:51 PM »
[Commit revision 4aab840]
Author: Nao (Signed-off)
Date: Tue, 11 Mar 2014 15:40:39 +0100
Stats: 1 file changed; +24 (insertions), -24 (deletions)

  • Renaming some variables to make them easier to understand. And following naming guidelines, basically. (mass_attach/attachui.js)

[Commit revision eec7300]
Author: Nao (Signed-off)
Date: Tue, 11 Mar 2014 15:41:23 +0100
Stats: 1 file changed; +1 (insertion), -1 (deletion)

  • A span works just as well to maintain the absolute position for an image. (we_pinterest/We-Pinterest-Main.php)

[Commit revision 78d11ec]
Author: Nao (Signed-off)
Date: Tue, 11 Mar 2014 15:42:16 +0100
Stats: 1 file changed; +1 (insertion), -1 (deletion)

  • WedgeDesk, still the untested beast, has the one remaining add_css_file call I had to simplify. (wedgedesk/src/WedgeDesk-AdminMaint.php)
1159
Features / Re: Language revs
« on March 11th, 2014, 03:48 PM »
[Commit revision ed39e30]
Author: Nao (Signed-off)
Date: Tue, 11 Mar 2014 15:45:11 +0100
Stats: 7 files changed; +8 (insertions), -8 (deletions)

  • Bad Behavior link update. (Security)
  • At install time, half-width non-breakable spaces won't be turned into mobile-friendly characters, so let's just forget this one. (Install.french.php)
  • A couple of Farjo updates that he forgot to carry over to his recent commit. (Help.english-uk.php)
  • Keeping names before nicknames. (Who.english-uk.php)
1160
Bug reports / Re: New board error
« on March 11th, 2014, 07:26 AM »
Okay, too much data here...

I'll keep it simple. If you're giving the same pretty URL to both boards, of course it's going to complain.
Maybe Wedge then decides to add a random number to the pretty URL to make it work and be unique. There's no bug here AFAIK.
1161
Bug reports / [Posting] Re: Wrong attachment is uploaded
« on March 11th, 2014, 07:21 AM »
Also, I should mention that since Wedge has a drop in fallback for JSON, there's no reason for it not to work without the instruction above...
1162
Bug reports / [Posting] Re: Wrong attachment is uploaded
« on March 10th, 2014, 10:35 PM »
Quote from Pandos on March 10th, 2014, 09:15 PM
Dig a bit deeper in it and found out that json_encode() was removed from PHP core in 5.5 due to a licensing problem.

Will install it and see if it is working :)
Ubuntu only.

Do this:
apt-get install php5-json
1163
Plugins / Re: Facebook plugin, language issue?
« on March 10th, 2014, 03:53 PM »
I hadn't noticed. Thanks ;)
1164
Features / Re: Poll: changing paths
« on March 10th, 2014, 03:53 PM »
So, path customization will be removed soon. The people have spoken. :)

I'll work on this, hmm... As soon as I'm done with the banner rewrite! And the final South Park dungeon. :P
1165
Features / Re: Poll: dropping oldIE
« on March 10th, 2014, 03:51 PM »
Quote from Bunstonious on March 10th, 2014, 09:20 AM
I guess it comes to a point where you decide what you want the project to be (and draw a line in the sand).
There's always a flag to restore old OSes... Just add 'allow_jurassic_crap' to the settings table, and set it to 1.
I could also (1) make it not hidden, and (2) make it enabled by default, but I don't know to which extent people are interested in keeping support for OSes that haven't been patched for security in at least 8 years (for Windows 2000), more for the others...
Quote
Cutting Edge and Nimble or Encumbered by hacks for old browsers.
Oh, there are still plenty of hacks for old browsers...
For a hack to make it into Wedge, it has:
- To mean that I actually use the browser in my test suite. I dropped IE6 from said suite last week, so it will no longer be getting new hacks. I still have IE7 in my suite, but I really don't care about it. Its market share is even less than IE6's...
- Not to be cumbersome to other browsers. That is, if a hack forces me to make a chance for other browsers, or if it adds bytes for all browsers (which it never will, thanks to Wess!), then it's a no-go for me.
Quote
I can definitely understand that, although I am the opposite, I usually end up reinstalling my OS every 6 - 12 because I either break it or get the shits with it's performance.
I know I took a couple of days with Win7 to customize it so that it acts more like XP... (XP's Taskbar and Explorer, more precisely. I have no qualms with the rest.)
Basically, I use Classic Shell, it does 95% of the job. :P
1166
Features / Re: Plugin revs
« on March 10th, 2014, 03:42 PM »
[Commit revision 6e4476a]
Author: Pandos (Signed-off)
Date: Sat, 01 Mar 2014 08:42:38 +0100
Stats: 1 file changed; +29 (insertions), -0 (deletion)

  • German translation for facebook plugin.

[Commit revision 59e58a7]
Author: Nao
Date: Mon, 10 Mar 2014 15:42:41 +0100
Stats: 1 file changed; +29 (insertions), -0 (deletion)

  • Merge pull request #24 from Pandos/master
  • German translation for facebook plugin.
1167
Quote from Farjo on March 4th, 2014, 12:15 AM
Yes I think that has fixed everything. It now works, albeit in a different way, as SMF does. Which is thus:
What is SMF's way? This way, or something else?
Quote from Farjo on March 4th, 2014, 12:15 AM
If a member has not yet set any options then he will get the default option i.e. what is set "For guests/new members". The "For existing members" dropdown will not change these members' options.

If a member has saved any setting on his Look & Layout, Notifications or Personal Messaging screens then that screen's options are now saved in the database and will be changed by the "For existing members" dropdown but not "For guests/new members".
And it makes sense. If you change a setting in your profile page, there's no way to know if you didn't change the other settings because you agreed with them (therefore, you want them to stay that way), or you didn't bother (therefore, they should remain 'default'.)
The only fix for that would be to replace checkboxes with select boxes that say "Default (Yes)" (or "Default (No)"), "Yes", and "No". To me, it's... Less usable, I'd say.
1168
Importing into Wedge / Re: SMF 2 to Wedge importer errors
« on March 10th, 2014, 03:32 PM »
Bump for @TE! ;)
1169
Plugins / Re: Facebook plugin, language issue?
« on March 10th, 2014, 03:31 PM »
Still here or not..?
1170
Features / Re: Poll: dropping oldIE
« on March 10th, 2014, 08:22 AM »
Quote from Bunstonious on March 9th, 2014, 11:33 PM
I don't think it should be blocked, just include a banner saying its unsupported, then remove the hacks to make it work.
You're mixing things up.
IE 6-IE 7 = unsupported. They currently look bad. But any good looking modern website will break horribly on them.
Old Windows = blocked. Not blocked "because they're unsupported"... Blocked because approximately 0.01% web visitors are actually using one of these, and a MUCH higher number of web visitors using this are actually spam bots.

I personally stayed with Win XP until my PC broke down a couple of years ago and I was forced to reinstall everything anyway.
I tend to tweak my OSes a lot, so I like keeping them that way. I have the same problem with my Galaxy S3 right now, ahah, can't upgrade to KitKat...

Anyway. WordPress blogs using BB will actually block any requests coming from Windows 2000 and below. What else?