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
2326
Features / Re: On Mobile Theme...
« on November 9th, 2013, 11:21 PM »
Oops. I made a wrong manipulation on my Wireless file, and reverted it to the 'original'. I'm hoping the Wilderless works for both of you, and it's not just Wireless that worked, although I don't think it'd be too hard reproducing the float layout I'd made for it... :^^;:
Really, though, Wilderless is the way I'd like to fix it, including in Wireless, so hopefully it'll be the right one, eh..?
Hmm, one thing I'd like to try, though, is reverting Wilderless back to use display: inline instead of display: inline-block, so that I don't have to add a hack for it on older browsers, but then again... It's only for IE6 and IE7. I'm sure they've got a ridiculous user base, by now...
Really, though, Wilderless is the way I'd like to fix it, including in Wireless, so hopefully it'll be the right one, eh..?
Hmm, one thing I'd like to try, though, is reverting Wilderless back to use display: inline instead of display: inline-block, so that I don't have to add a hack for it on older browsers, but then again... It's only for IE6 and IE7. I'm sure they've got a ridiculous user base, by now...
2327
Features / Re: On Mobile Theme...
« on November 9th, 2013, 10:39 PM »
On both skins? Which platform already?
2328
Features / Re: On Mobile Theme...
« on November 9th, 2013, 06:33 PM »
Hoping for this one to be the last... :^^;:
Changed Wireless to use floats instead. Seriously-- this one should work.
Changed Wilderless to use inline-blocks. I also tweaked the CSS to correctly align the elements vertically along the same line.
Please test both! Anyone who's got access to iOS, really.
Changed Wireless to use floats instead. Seriously-- this one should work.
Changed Wilderless to use inline-blocks. I also tweaked the CSS to correctly align the elements vertically along the same line.
Please test both! Anyone who's got access to iOS, really.
2329
Features / Re: On Mobile Theme...
« on November 9th, 2013, 11:35 AM »
Oh, bugger...
How 'bout now?
I insist, these tests must be done on Wireless, not Wilderless. Wilderless is the current 'default' mobile skin, so you have to consciously switch to it. If you didn't do it, then the previous test was for nothing.
If the current test works for you, then it means the profile mini-menus have to go from Wireless, at least in that position.
Posted: November 9th, 2013, 11:33 AM
How 'bout now?
I insist, these tests must be done on Wireless, not Wilderless. Wilderless is the current 'default' mobile skin, so you have to consciously switch to it. If you didn't do it, then the previous test was for nothing.
If the current test works for you, then it means the profile mini-menus have to go from Wireless, at least in that position.
2330
Features / Re: On Mobile Theme...
« on November 9th, 2013, 12:56 AM »
What about now?
(In Wireless; not in Wilderless.)
(In Wireless; not in Wilderless.)
2331
Features / Re: New revs
« on November 9th, 2013, 12:47 AM »
rev 2312
2 files changed, 2 insertions(+), 2 deletions(-), 903 bytes
! Spoiler tags didn't accept spaces in their descriptions, and as an indirect cause, made quick edit fail through some complicated crap in strip_tags(). Definitely NOT a fun thing to debug, really. (install.sql)
! JavaScript doesn't like receiving malformed XML CDATA strings. In some rare situations (pasting some code, maybe?), it would simply freeze at parse time. (Subs.php)
@ Note for those who already have Wedge installed somewhere: either repopulate your bbcode table with the updated version, or ignore the fix, or edit it. You just need to add two double quotes, no biggie.
2 files changed, 2 insertions(+), 2 deletions(-), 903 bytes
! Spoiler tags didn't accept spaces in their descriptions, and as an indirect cause, made quick edit fail through some complicated crap in strip_tags(). Definitely NOT a fun thing to debug, really. (install.sql)
! JavaScript doesn't like receiving malformed XML CDATA strings. In some rare situations (pasting some code, maybe?), it would simply freeze at parse time. (Subs.php)
@ Note for those who already have Wedge installed somewhere: either repopulate your bbcode table with the updated version, or ignore the fix, or edit it. You just need to add two double quotes, no biggie.
2332
Features / Re: New revs
« on November 8th, 2013, 10:10 PM »
rev 2311
7 files changed, 49 insertions(+), 40 deletions(-), 2.24 KiB
* As Wess doesn't do anything interesting with array variables, let's at least return the size of them, allowing you to test for empty (or non-existent) arrays. Should account for 90% of all use cases. Using that for language flags. (Subs-Cache.php, index.css)
* Like buttons in posts should have the same opacity effect as other action elements. (sections.css)
! Wrong font variable name. (index.css, sections.css, Wireless/extra.css)
! Overflow problem. Again. (Wireless/extra.css)
! Was this an unfinished language string? It certainly didn't mean anyth (Admin.language.php)
! When a post had an attachment, clicking its icon would result in a broken icon list. (topic.js)
! Hadn't committed my local changes to quick edit, regarding the new tags for last modified date. (topic.js)
! follow_me() fixes. (topic.js)
* Very minor rewrites. (topic.js)
7 files changed, 49 insertions(+), 40 deletions(-), 2.24 KiB
* As Wess doesn't do anything interesting with array variables, let's at least return the size of them, allowing you to test for empty (or non-existent) arrays. Should account for 90% of all use cases. Using that for language flags. (Subs-Cache.php, index.css)
* Like buttons in posts should have the same opacity effect as other action elements. (sections.css)
! Wrong font variable name. (index.css, sections.css, Wireless/extra.css)
! Overflow problem. Again. (Wireless/extra.css)
! Was this an unfinished language string? It certainly didn't mean anyth (Admin.language.php)
! When a post had an attachment, clicking its icon would result in a broken icon list. (topic.js)
! Hadn't committed my local changes to quick edit, regarding the new tags for last modified date. (topic.js)
! follow_me() fixes. (topic.js)
* Very minor rewrites. (topic.js)
2333
Features / Re: On Mobile Theme...
« on November 8th, 2013, 05:11 PM »
Well, at least I can get rid of that ugly fix I made yesterday... :^^;:
I'm afraid it's due to the position: relative I have in the user name, then... Which means, it's pretty much impossible to fix it without rewriting the mini-menu layout system, and I'm, err... Not a fan of the idea. While getting the menu out of that particular DOM node (sorry for talking rubbish :P) would help with some earlier z-index issues (I already apologized!), it also means that any changes to the page dimensions would need to be passed on to the mini-menu manually, and... Well, it sucks.
I'm afraid it's due to the position: relative I have in the user name, then... Which means, it's pretty much impossible to fix it without rewriting the mini-menu layout system, and I'm, err... Not a fan of the idea. While getting the menu out of that particular DOM node (sorry for talking rubbish :P) would help with some earlier z-index issues (I already apologized!), it also means that any changes to the page dimensions would need to be passed on to the mini-menu manually, and... Well, it sucks.
2334
Off-topic / Re: Bitcointalk.org $11k bounty for new forum software
« on November 8th, 2013, 05:08 PM »
At least 5500 zeroes today I believe. But tomorrow, the value will be divided by 10^5600, so hurry up!
2335
Off-topic / Re: feline hiccups
« on November 8th, 2013, 05:00 PM »
If I had a hammer... ♫Quote from Wanchope on November 2nd, 2013, 03:38 AM There's nothing to add. His departure was unexpected, uncalled for, and regretted by most everyone here. It was, however, his right to do it. Nothing forced him to work on Wedge for his entire life. (I'm just not sure why he seems to see jumping to a lifetime of working on SMF as an improvement over this, but...)
Heck, even I am not forced to do that. It's just that, unlike Pete, I've always enjoyed doing it, and that I never cared about what others thought of my work. It's what a fork is for, after all.Quote Or she's just a nice running joke to pass the time!
4 pages redirected fromTerminatorArantor back toMachinesSimple machines and Feline was the reason. Two things
* You guys are moving on from Arantor here so fast which is a kind of sad
Heck, even I am not forced to do that. It's just that, unlike Pete, I've always enjoyed doing it, and that I never cared about what others thought of my work. It's what a fork is for, after all.
* You guys like Feline more than you realizes
2336
Other software / Re: Arantor back on SMF Team!
« on November 8th, 2013, 04:57 PM »
A line had to be drawn... :P
2337
Features / Re: New revs
« on November 8th, 2013, 04:31 PM »
rev 2310
5 files changed, 30 insertions(+), 25 deletions(-), 1.66 KiB
! Page header was incorrectly sized in responsive mode (with 1.5 pixel density or higher, which I rarely test on desktop.) (sections.css)
! Post avatars were incorrectly aligned in responsive mode. (sections.css)
! ins tag styling fixes. (extra.rtl.css, sections.css)
* Pixel-perfect news in the admin sidebar. The jury's still out on whether I'll use that area at all, though... (mana.css)
* Intermediate work on font types. Seriously, more to come. I just need to see it in action on a live site. (common.css, index.css, sections.css)
:edit: Forgot to document (why is TortoiseGit missing the ability to edit the latest changelog, when even TortoiseSVN allows it..?!): disabled flexbox on iOS 6, because it's obviously not working between us.
5 files changed, 30 insertions(+), 25 deletions(-), 1.66 KiB
! Page header was incorrectly sized in responsive mode (with 1.5 pixel density or higher, which I rarely test on desktop.) (sections.css)
! Post avatars were incorrectly aligned in responsive mode. (sections.css)
! ins tag styling fixes. (extra.rtl.css, sections.css)
* Pixel-perfect news in the admin sidebar. The jury's still out on whether I'll use that area at all, though... (mana.css)
* Intermediate work on font types. Seriously, more to come. I just need to see it in action on a live site. (common.css, index.css, sections.css)
:edit: Forgot to document (why is TortoiseGit missing the ability to edit the latest changelog, when even TortoiseSVN allows it..?!): disabled flexbox on iOS 6, because it's obviously not working between us.
2338
Features / Re: New revs
« on November 8th, 2013, 04:12 PM »
rev 2309
3 files changed, 23 insertions(+), 14 deletions(-), 1.34 KiB (same size for much less code? Doesn't seem too trustworthy to me, then...)
+ News feature (Random news and newsfader) will now only output and cache their CSS if they're enabled in the first place, and yes, it's a nice thing to have, and even if it serves as an example of what plugins should be able to do in the future, I'm glad I can save these bytes, eh. (ManageNews.php, index.css, sections.css)
! The $view_junk variable definition needed double double quotes (not a typo!), in order for the test to understand its values as strings, not constants. Silly me. (index.css)
3 files changed, 23 insertions(+), 14 deletions(-), 1.34 KiB (same size for much less code? Doesn't seem too trustworthy to me, then...)
+ News feature (Random news and newsfader) will now only output and cache their CSS if they're enabled in the first place, and yes, it's a nice thing to have, and even if it serves as an example of what plugins should be able to do in the future, I'm glad I can save these bytes, eh. (ManageNews.php, index.css, sections.css)
! The $view_junk variable definition needed double double quotes (not a typo!), in order for the test to understand its values as strings, not constants. Silly me. (index.css)
2339
Features / Re: New revs
« on November 8th, 2013, 04:05 PM »
rev 2308
1 file changed, 58 insertions(+), 40 deletions(-), 1.37 KiB
* Rewrote the we::is parser for sanity. (Class-System.php)
+ Adds support for operator-less variable testing (i.e. != "").
* Deals with bracket grouping in a better and more readable way. Finally, I get to remove a dirty hack!
! Fixes problems with variable testing, notably with loose checks, and variables like 'admin' being parsed as the admin constant.
! Also fixes negative tests. Up until now, "!$var == true" was seen as "!($var == true)", now it's "(!$var) == true", which is 95% the same, but at least it's more logical.
1 file changed, 58 insertions(+), 40 deletions(-), 1.37 KiB
* Rewrote the we::is parser for sanity. (Class-System.php)
+ Adds support for operator-less variable testing (i.e. != "").
* Deals with bracket grouping in a better and more readable way. Finally, I get to remove a dirty hack!
! Fixes problems with variable testing, notably with loose checks, and variables like 'admin' being parsed as the admin constant.
! Also fixes negative tests. Up until now, "!$var == true" was seen as "!($var == true)", now it's "(!$var) == true", which is 95% the same, but at least it's more logical.
2340
Features / Re: New revs
« on November 8th, 2013, 03:37 PM »
rev 2307
2 files changed, 9 insertions(+), 10 deletions(-), , 1.05 KiB
* ! $context tests in Wess weren't ready yet. Well, now they are. (Subs-Cache.php)
! Variable tests in Wess would be added to a variable stored in the database settings. No need to pollute it with these, as well as the 'true' keyword, so I made sure to strip them off. Or out? What's the correct English word for that? Anyway, it also saves a couple of extra mandatory we::is tests per page load, even when everything is cached. (Subs-Cache.php)
! Tested Wedge in the latest Maxthon, using Chrome 26, and it still doesn't accept unprefixed CSS like gradients etc, so I thought a bit about it, and decided to simply up the minimum version for unprefixing to 27, to give forks some time to sort out their stuff. Or off. Nah, must be out. Not a big deal, since v26 is long past for mainline Chrome users anyway. The only thing that bothers me is that the comments are now incorrect, but whatever, I'm sure I'm the only one who checks out prefix usage at caniuse.com anyway. (Class-CSS.php)
2 files changed, 9 insertions(+), 10 deletions(-), , 1.05 KiB
* ! $context tests in Wess weren't ready yet. Well, now they are. (Subs-Cache.php)
! Variable tests in Wess would be added to a variable stored in the database settings. No need to pollute it with these, as well as the 'true' keyword, so I made sure to strip them off. Or out? What's the correct English word for that? Anyway, it also saves a couple of extra mandatory we::is tests per page load, even when everything is cached. (Subs-Cache.php)
! Tested Wedge in the latest Maxthon, using Chrome 26, and it still doesn't accept unprefixed CSS like gradients etc, so I thought a bit about it, and decided to simply up the minimum version for unprefixing to 27, to give forks some time to sort out their stuff. Or off. Nah, must be out. Not a big deal, since v26 is long past for mainline Chrome users anyway. The only thing that bothers me is that the comments are now incorrect, but whatever, I'm sure I'm the only one who checks out prefix usage at caniuse.com anyway. (Class-CSS.php)