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
3196
Archived fixes / Re: Plugin execution
« on April 15th, 2013, 05:17 PM »
Did you quick-edit the post above..? Because I got the 'New' icon another time after I pressed Refresh. Also, that refresh caused rev 2051 not to show up. I made a dozen more refreshes, and it didn't happen again, but I guess it means it's not due to the wrong caching level, or somethin'.
I don't know why the index language is reloaded. I find it even weirder, that the SkinSelector language file was loaded in one instance, and not in the other...
I don't know why the index language is reloaded. I find it even weirder, that the SkinSelector language file was loaded in one instance, and not in the other...
3197
Archived fixes / Re: Something is screwy with the main menu
« on April 15th, 2013, 05:12 PM »
The reason cache level 2 was activated is, I guess, because this morning I tried to flush the non-file cache (mentioned that in the thoughts area), and I figured it might work if I switched to level 2 and then back to level 1... I guess either there's a bug with switching between levels, or I simply forgot to switch back to level 1.
Anyway, if level 2 is broken... It should be fixed, I guess ;)
Switched back to level 1 for now...
Anyway, if level 2 is broken... It should be fixed, I guess ;)
Switched back to level 1 for now...
3198
Archived fixes / Re: Plugin execution
« on April 15th, 2013, 05:08 PM »
See differences... The buggy version, has 3 extra files loaded (2 cached, one uncached -- the plugin one.)
3199
Archived fixes / Re: Plugin execution
« on April 15th, 2013, 04:56 PM »
Merged the topics...
As far as I can say, this used to be a problem, and I fixed it, re:Quote If it no longer works, then it's probably due to language caching, since this was implemented by Pete only recently. It's expected to have bugs with it, considering it also saves much processing time on each page. However, I'm afraid I can't reproduce the bug here... Really, it always shows me the rev number. Maybe it's for a specific language, I don't know..?
:edit: Reproduced with English UK... Happens about 1 out of 5 times.
As far as I can say, this used to be a problem, and I fixed it, re:
Instead of reloading the index language a last time, I just saved $txt before that, and restored $txt immediately after... It should also be much faster, eh!
:edit: Reproduced with English UK... Happens about 1 out of 5 times.
3200
Archived fixes / Re: Flexbox bug
« on April 15th, 2013, 03:39 PM »
Bump for above...?
Also, Chrome is really starting to get on my nerves...
I double-checked the :hover/:focus bug that broke Wedge in Chrome 26, a few months ago... If you'll remember, just setting a border on hover for a textarea or text input would quite simply prevent entering text in them. So I disabled it... Today (an hour ago), I decided to re-enable it, because apparently it's been fixed. Good, good...
Only, on the very same day, i.e. a few minutes ago, I found another silly bug in Chrome 28...
Are you ready?
Set position: relative on an object.
Set position: absolute on a child, and top: 0px.
Animate (through jQuery) to top: 100% on that child.
Element goes right below parent, as expected.
All right..?
Now, set said element's top: 100% to be animated to top: 0px. Which will do the exact reverse... Okay?
Well, it doesn't. It resets its starting position to 100% of the total window height... Fun!
I tested in earlier versions, and the bug isn't there.
Thankfully, I found a workaround, which costs 5 bytes, but whatever... Just set the target to '0%', rather than just 0.
Ah, well... That's the fun of using cutting-edge jQuery along with cutting-edge Chrome...!
I don't know if it's a Chrome or jQuery 2.0 beta 3 bug, so I'll let it slide for now.
:edit: Actually, it's a free fix. I forgot to remove my debug code before comparing... ;)
Also, Chrome is really starting to get on my nerves...
I double-checked the :hover/:focus bug that broke Wedge in Chrome 26, a few months ago... If you'll remember, just setting a border on hover for a textarea or text input would quite simply prevent entering text in them. So I disabled it... Today (an hour ago), I decided to re-enable it, because apparently it's been fixed. Good, good...
Only, on the very same day, i.e. a few minutes ago, I found another silly bug in Chrome 28...
Are you ready?
Set position: relative on an object.
Set position: absolute on a child, and top: 0px.
Animate (through jQuery) to top: 100% on that child.
Element goes right below parent, as expected.
All right..?
Now, set said element's top: 100% to be animated to top: 0px. Which will do the exact reverse... Okay?
Well, it doesn't. It resets its starting position to 100% of the total window height... Fun!
I tested in earlier versions, and the bug isn't there.
Thankfully, I found a workaround, which costs 5 bytes, but whatever... Just set the target to '0%', rather than just 0.
Ah, well... That's the fun of using cutting-edge jQuery along with cutting-edge Chrome...!
I don't know if it's a Chrome or jQuery 2.0 beta 3 bug, so I'll let it slide for now.
:edit: Actually, it's a free fix. I forgot to remove my debug code before comparing... ;)
3201
The Pub / Re: Logo Madness
« on April 15th, 2013, 11:59 AM »
@Oracle> I also played with the fact that 'W' and 'E' are similar in shape, but the results weren't particularly interesting. Well, I've made plenty of logos I find better than the current one, but that's the thing, it's something so frontal, it needs to be liked by most.
@agent47> Aller Display, Segoe UI, Helvetica (various types, such as LT or Neue...), and Sansation. I think these are all the ones used in the logos in the poll. Lato, Lobster, Meta, TheSans, Tin Doghouse, theeeese are a few of my faaaaavorite thiiiings... Errr, a few of my 'sanctioned' fonts, for attempts at doing a Wedge logo.
Not that you can't use another font... It's just that I've always wanted a 'professional' looking font.
I haven't worked on the logo for the last few months though. I lost interest, I guess, mostly after everyone else did the same... ;)
@agent47> Aller Display, Segoe UI, Helvetica (various types, such as LT or Neue...), and Sansation. I think these are all the ones used in the logos in the poll. Lato, Lobster, Meta, TheSans, Tin Doghouse, theeeese are a few of my faaaaavorite thiiiings... Errr, a few of my 'sanctioned' fonts, for attempts at doing a Wedge logo.
Not that you can't use another font... It's just that I've always wanted a 'professional' looking font.
I haven't worked on the logo for the last few months though. I lost interest, I guess, mostly after everyone else did the same... ;)
3202
Features / Re: New revs
« on April 15th, 2013, 11:48 AM »
rev 2058
(3 files -1, 5kb)
* Simplified CSS button extends, removing per-button :hover declarations (replaced them with a similar but shorter and cooler solution), opting for a mixin instead of a base, and saving a hundred bytes in the process. Never underestimate the power of refactoring. (common.css, index.css)
* Moved all of extra.webkit.css's hacks to the main files. Yet another proof that while maintaining separate files is cleaner, sometimes it creates bugs due to oversights when removing features. (Plus, grouping items thematically compresses better, as always.) (extra.webkit.css, index.css, sections.css)
(3 files -1, 5kb)
* Simplified CSS button extends, removing per-button :hover declarations (replaced them with a similar but shorter and cooler solution), opting for a mixin instead of a base, and saving a hundred bytes in the process. Never underestimate the power of refactoring. (common.css, index.css)
* Moved all of extra.webkit.css's hacks to the main files. Yet another proof that while maintaining separate files is cleaner, sometimes it creates bugs due to oversights when removing features. (Plus, grouping items thematically compresses better, as always.) (extra.webkit.css, index.css, sections.css)
3203
Features / Re: New revs
« on April 15th, 2013, 11:40 AM »
rev 2057 -- SSI and XML fixes. Or breaking more things, maybe ;)
(4 files, 2kb)
! ssi_examples was horribly broken... Well, maybe not horribly, but it needed fixin'. (root/ssi_examples.php)
- Forgot to remove a Xml template call. Seems harmless, but broke all thoughts and board selector... Oops. (Ajax.php)
* Search2 no longer replies to AJAX calls, AFAIK, so it was needlessly calling a template block for it. (Search2.php)
! ssi_quickSearch was broken due to a very, very old change. I'm using the opportunity to add our output buffer handler to SSI, which is probably going to be controversial, so I'm repeating in case it's unclear or we need to revert: from now on, any calls to SSI will call pretty URLs, <URL> and other things on your page. Understood..? (SSI.php)
(4 files, 2kb)
! ssi_examples was horribly broken... Well, maybe not horribly, but it needed fixin'. (root/ssi_examples.php)
- Forgot to remove a Xml template call. Seems harmless, but broke all thoughts and board selector... Oops. (Ajax.php)
* Search2 no longer replies to AJAX calls, AFAIK, so it was needlessly calling a template block for it. (Search2.php)
! ssi_quickSearch was broken due to a very, very old change. I'm using the opportunity to add our output buffer handler to SSI, which is probably going to be controversial, so I'm repeating in case it's unclear or we need to revert: from now on, any calls to SSI will call pretty URLs, <URL> and other things on your page. Understood..? (SSI.php)
3204
The Pub / Re: Logo Madness
« on April 15th, 2013, 08:01 AM »
Nice logo! The font not my cup of tea though.
Nevertheless, I doubt this will gather enough interest compared to the consensual current default so I won't add it to the poll.
Nevertheless, I doubt this will gather enough interest compared to the consensual current default so I won't add it to the poll.
3205
Features / Re: CSS inheritance issue
« on April 15th, 2013, 07:54 AM »
Yes. Do you want me to quickly re-explain what keywords do what..?
3206
Features / Re: CSS inheritance issue
« on April 15th, 2013, 12:12 AM »
Add a 'final' keyword to all of these windowbg-related selectors, and please tell me how many bytes this saves in your gzipped CSS, if any ;)
That's because with your CSS, any classes that inherit from windowbg will also be applied to this. ^^
That's because with your CSS, any classes that inherit from windowbg will also be applied to this. ^^
3207
Features / Re: CSS inheritance issue
« on April 15th, 2013, 12:03 AM »
Lol... ;)
Anyway... To answer your question, the main thing with my rewrite is that you no longer have to provide a :hover with a new color. All buttons are now properly 'lighted' when hovering them, with a specific box-shadow setting.
I'll try to commit these things tomorrow. Along with a host of other changes to CSS... Don't worry though, nothing potentially game-breaking for you.
Anyway... To answer your question, the main thing with my rewrite is that you no longer have to provide a :hover with a new color. All buttons are now properly 'lighted' when hovering them, with a specific box-shadow setting.
I'll try to commit these things tomorrow. Along with a host of other changes to CSS... Don't worry though, nothing potentially game-breaking for you.
3208
Features / Re: CSS inheritance issue
« on April 14th, 2013, 08:19 PM »
So... Right now, in order to have a working button, you just need to do this.
Code: [Select]
This new method saves about 60 bytes in the regular gzipped file. It actually moves the :hover stuff to the basic button styling, and uses a box-shadow trick to reproduce the hover effect. It's not exactly the same, but it's similar.
(Using 'extends' instead of 'mixes' is possible, but saves 11 bytes from what I could see in my implementation... Goes to show how important repetition is, for gzip ;))
input.new mixes .button-padding
background: url($images/buttons/new.png) 5px center no-repeat
background-color: #e0eaf6This new method saves about 60 bytes in the regular gzipped file. It actually moves the :hover stuff to the basic button styling, and uses a box-shadow trick to reproduce the hover effect. It's not exactly the same, but it's similar.
(Using 'extends' instead of 'mixes' is possible, but saves 11 bytes from what I could see in my implementation... Goes to show how important repetition is, for gzip ;))
3209
Features / Re: CSS inheritance issue
« on April 14th, 2013, 05:02 PM »
I'm probably going to go for the background shorthand route when it comes to declaring input.submit (including position and background-color), and remove the background-position declaration that was a bit below... I'll need some testing though, because it all doesn't make sense, and I want to ensure I didn't do that because of a special issue.
3210
Plugins / [Plugin] Re: Notifications system (1.0)
« on April 14th, 2013, 04:48 PM »
It'll soon be WebKit AND Blink only... :P
That is, enough to warrant standardization. Which, BTW, is underway... :)
Anyway.
A few issues I'm having with notification emails...
- I noticed that Notifications.php calls sendmail() with $send_html set to true. So, it does intend to transmit links, but unfortunately all I'm receiving is raw HTML, i.e. tags show up in the mail... (That's with gmail, I should add.)
- Even if we managed to have e-mails sent through HTML, there's the tiny problem of membergroups... Ever since rev 2031, member colors are no longer stored, rather groups, which is fine by me, be in an e-mail, you don't have access to the website's CSS, so these class names just return nothing. Is it worth including a link to our CSS files in the e-mails...? Hmm... I dunno...
That is, enough to warrant standardization. Which, BTW, is underway... :)
Anyway.
A few issues I'm having with notification emails...
- I noticed that Notifications.php calls sendmail() with $send_html set to true. So, it does intend to transmit links, but unfortunately all I'm receiving is raw HTML, i.e. tags show up in the mail... (That's with gmail, I should add.)
- Even if we managed to have e-mails sent through HTML, there's the tiny problem of membergroups... Ever since rev 2031, member colors are no longer stored, rather groups, which is fine by me, be in an e-mail, you don't have access to the website's CSS, so these class names just return nothing. Is it worth including a link to our CSS files in the e-mails...? Hmm... I dunno...