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
2566
The Pub / Re: Font size in Chrome Android
« on August 29th, 2013, 10:27 AM »
Okay, back on my PC...
The good news is that I found a nand backup lying around on my external SD Card, dated August 14, I'd forgotten I'd done it at all, so in the span of 10 minutes, I was all good -- back with a 15-day old copy of my S3. It's not as good as a 1-day old copy, but hey, I can't ask for too much, I guess... At least I won't have to spend another 2 days reinstalling all of this shit.
And the correct font sizes are back in my Chrome, phew...!
So, I've been having a closer look at your screenshots guys, and they seem quite all right to me. It really was FoxHound 4.2.2's fault that the font sizes were screwed up -- not FoxHound 4.1.2's. There are font size differences between browsers, but they're all within acceptable range, and I'm not going to restart from scratch just for that, eh.
Now, I'll just need to deal with iOS. For this, I only have my iPod Touch 4 with iOS 5.1.2 or something, and it's okay, but I remember Pete mentioned problems with his iPad devices. It'll be some time before I can access an iPad again, so I suppose it'll have to wait, for now!
The good news is that I found a nand backup lying around on my external SD Card, dated August 14, I'd forgotten I'd done it at all, so in the span of 10 minutes, I was all good -- back with a 15-day old copy of my S3. It's not as good as a 1-day old copy, but hey, I can't ask for too much, I guess... At least I won't have to spend another 2 days reinstalling all of this shit.
And the correct font sizes are back in my Chrome, phew...!
So, I've been having a closer look at your screenshots guys, and they seem quite all right to me. It really was FoxHound 4.2.2's fault that the font sizes were screwed up -- not FoxHound 4.1.2's. There are font size differences between browsers, but they're all within acceptable range, and I'm not going to restart from scratch just for that, eh.
Now, I'll just need to deal with iOS. For this, I only have my iPod Touch 4 with iOS 5.1.2 or something, and it's okay, but I remember Pete mentioned problems with his iPad devices. It'll be some time before I can access an iPad again, so I suppose it'll have to wait, for now!
2567
The Pub / Re: Font size in Chrome Android
« on August 29th, 2013, 09:03 AM »
Devices, guys...?
And skins, I'm afraid. Well, i can recognize them myself, but really I'm only interested in Wireless shots ;)
And skins, I'm afraid. Well, i can recognize them myself, but really I'm only interested in Wireless shots ;)
2568
Features / Re: New revs
« on August 29th, 2013, 12:24 AM »
rev 2232
(8 files, 3kb)
* Three more strings that weren't used in the index language files. (index.language.php, Post.language.php)
- Removed some duplicate PM strings. (PersonalMessage.language.php, Profile.language.php)
(8 files, 3kb)
* Three more strings that weren't used in the index language files. (index.language.php, Post.language.php)
- Removed some duplicate PM strings. (PersonalMessage.language.php, Profile.language.php)
2569
Features / Re: New revs
« on August 29th, 2013, 12:23 AM »
rev 2231
(5 files, 2kb)
! PM blocking system wasn't working. Hopefully should work now... (Subs-Post.php)
! Stop forcing user boxes to 'position-fix' themselves if they're as tall as their parent message in the first place. Hmm, my math is a bit strange here... I think it works, though. (topic.js)
! Ouch, my eyes! An actual 'or' instead of '||', the folly! (MessageIndex.template.php)
! SPOILERS! Forgot to hide them. Which is the basic idea behind a spoiler box, right..? (index.css)
! PM preferences should load the PM language files, even if in the profile area. Cleaner. (Profile-Modify.php)
(5 files, 2kb)
! PM blocking system wasn't working. Hopefully should work now... (Subs-Post.php)
! Stop forcing user boxes to 'position-fix' themselves if they're as tall as their parent message in the first place. Hmm, my math is a bit strange here... I think it works, though. (topic.js)
! Ouch, my eyes! An actual 'or' instead of '||', the folly! (MessageIndex.template.php)
! SPOILERS! Forgot to hide them. Which is the basic idea behind a spoiler box, right..? (index.css)
! PM preferences should load the PM language files, even if in the profile area. Cleaner. (Profile-Modify.php)
2570
Archived fixes / User box screwing up post height in quick edit mode
« on August 28th, 2013, 11:18 PM »
This is a downside of the nice user box code... If you quick edit a long post, the post won't resize to adjust to the textarea. This is because the user box area is 'fixed' in height.
Can be solved in at least two ways...
- Temporarily un-fixing the user box when editing a post. Downside: if the user box is position:fixed at that exact moment, it will potentially overflow to the next post.
- Adjusting the textarea height to the current post height (with a set minimum). This seems to make more sense, but if the post is more than one page tall, it's obviously not going to work... So, it's even worse.
I guess I can't expect anyone to know my code well enough to offer a third suggestion, but just in case... Please let me know ;)
Can be solved in at least two ways...
- Temporarily un-fixing the user box when editing a post. Downside: if the user box is position:fixed at that exact moment, it will potentially overflow to the next post.
- Adjusting the textarea height to the current post height (with a set minimum). This seems to make more sense, but if the post is more than one page tall, it's obviously not going to work... So, it's even worse.
I guess I can't expect anyone to know my code well enough to offer a third suggestion, but just in case... Please let me know ;)
2571
The Pub / Font size in Chrome Android
« on August 28th, 2013, 11:12 PM »
Story of my life...
(click to show/hide)
As a result, the wedge.org homepage shows much smaller characters to me in Chrome for Android, and it's like I have to restart from scratch... Obviously, I don't want to play the 'guess' game, and I'd like to ask you guys to... post a screenshot of your wedge.org page being rendered in your mobile device.
- You can either choose the wedge.org homepage, or this very post. It would make more sense to choose this post, as you can take a screenshot right now... ;)
- You can use Chrome for Android, or the stock browser on your device. Not anything else, please. You can do both, if you want.
- If you have the same results as someone else with the same setup who posted a screenshot before you, please don't post your screenshot, just confirm or like their post.
- On Android, the screenshot shortcut is usually Power + Volume Down. On some devices, you need to swipe your entire hand (the pinky should pretty much touch the screen, and the hand should be perpendicular to the screen), from left to right, to generate a screenshot.
- On iOS, it's Power + Home.
- Just attach the screenshot in your post.
- Indicate: your OS and OS version, your browser name and version, and any changes you may have applied to your setup (e.g. whether it's a custom ROM, or you did something to change the font face, or size, etc.)
This should, hopefully, help me determine what's the 'correct' size right now, and what I should be aiming for.
I've been having some quite *shitty* week, so far.... After my very bad news from last week; after Pete calling it quits; now I've got a friend who came to visit, and showed me his CloudMobile (which I recommended to him, although I'd never seen it in action, and wanted to), and I wanted to show him a 'bare' Android install and installed CyanogenMod on my second ROM, and then it turned out that it was the first ROM and the stupid device had wiped my entire data set... GREAT!!!
So, if I have to reinstall, I thought, I'll install Android 4.2.2 (instead of 4.1.2), and on my S3 it's not an official ROM, it's basically a leak from Samsung, and there are many things missing, in addition to the, err, additions. Mostly, I think I preferred my old ROM, so I'll probably take another few hours to reinstall it (boo hoo...), but in the meantime:
- It has no Helvetica S (ouch), although it has a very interesting Samsung Sans font,
- Its Roboto is horrible. The font size is much smaller than on my previous ROM. I don't know if it's due to being 4.2.2, or the custom ROM I used being too... bold.
As a result, the wedge.org homepage shows much smaller characters to me in Chrome for Android, and it's like I have to restart from scratch... Obviously, I don't want to play the 'guess' game, and I'd like to ask you guys to... post a screenshot of your wedge.org page being rendered in your mobile device.
- You can either choose the wedge.org homepage, or this very post. It would make more sense to choose this post, as you can take a screenshot right now... ;)
- You can use Chrome for Android, or the stock browser on your device. Not anything else, please. You can do both, if you want.
- If you have the same results as someone else with the same setup who posted a screenshot before you, please don't post your screenshot, just confirm or like their post.
- On Android, the screenshot shortcut is usually Power + Volume Down. On some devices, you need to swipe your entire hand (the pinky should pretty much touch the screen, and the hand should be perpendicular to the screen), from left to right, to generate a screenshot.
- On iOS, it's Power + Home.
- Just attach the screenshot in your post.
- Indicate: your OS and OS version, your browser name and version, and any changes you may have applied to your setup (e.g. whether it's a custom ROM, or you did something to change the font face, or size, etc.)
This should, hopefully, help me determine what's the 'correct' size right now, and what I should be aiming for.
2572
Features / Re: New revs
« on August 28th, 2013, 09:53 AM »
rev 2230
(8 files, 3kb)
* Using HTML5 instead of a div tag soup on spoiler tags.
(click to show/hide) (install.sql, index.css)
! border-box divs are nice, but adding a margin to these increases their width above 100% and kinda misses the original purpose... Doesn't it? (sections.css)
! Signatures need some extra horizontal padding in Wireless. (Wireless/extra.css)
- Removed two language strings that were no longer in use, and moved another to a more specific file. (index.language.php, PersonalMessage.language.php)
- Removing tags column from topics for now. These aren't used, and I might as well try and put them to a different table, it'd probably be better for performance. (install.sql)
* Added UptimeRobot to the bot list; it's probably a wedge.org thing only, but it's not like it's going to change anything if I add it or not, so might as well add it. (install.sql)
@ Note: forgot to add 'mixes .hide' to .spoiler blockquote, will do on next commit, do it yourself if needed ;) Did it here.
(8 files, 3kb)
* Using HTML5 instead of a div tag soup on spoiler tags.
The main advantage is that it allows them to act like quote tags when it comes to keeping footnotes inside them[1].
1. Ring any bell, Pete? ;)
! border-box divs are nice, but adding a margin to these increases their width above 100% and kinda misses the original purpose... Doesn't it? (sections.css)
! Signatures need some extra horizontal padding in Wireless. (Wireless/extra.css)
- Removed two language strings that were no longer in use, and moved another to a more specific file. (index.language.php, PersonalMessage.language.php)
- Removing tags column from topics for now. These aren't used, and I might as well try and put them to a different table, it'd probably be better for performance. (install.sql)
* Added UptimeRobot to the bot list; it's probably a wedge.org thing only, but it's not like it's going to change anything if I add it or not, so might as well add it. (install.sql)
@ Note: forgot to add 'mixes .hide' to .spoiler blockquote, will do on next commit, do it yourself if needed ;) Did it here.
2573
Features / Re: New revs
« on August 26th, 2013, 06:24 PM »
rev 2229 -- back to work after this, err... Interesting detour..?
(12 files, 4kb)
+ Added a new note class, notevoid, which is meant to be neutral, so it has a grey background. Used in notifications. (index.template.php, script.js, index.css)
* Moved notification block creation to the skeleton file itself. Effectively, this means that skins can choose to hide it, and while I don't see *why* they would want to, it's still okay to do it in my opinion. People aren't forced to use your skins. (Notifications.php, index.template.php, skeleton.xml, Warm/skeleton.xml)
* Just like CSS files, people shouldn't be able to view skin XML files from within their browser. (skins/.htaccess * 5)
! most_online param was inverted when it came to Ajax loading of monthly stats. (Stats.template.php)
(12 files, 4kb)
+ Added a new note class, notevoid, which is meant to be neutral, so it has a grey background. Used in notifications. (index.template.php, script.js, index.css)
* Moved notification block creation to the skeleton file itself. Effectively, this means that skins can choose to hide it, and while I don't see *why* they would want to, it's still okay to do it in my opinion. People aren't forced to use your skins. (Notifications.php, index.template.php, skeleton.xml, Warm/skeleton.xml)
* Just like CSS files, people shouldn't be able to view skin XML files from within their browser. (skins/.htaccess * 5)
! most_online param was inverted when it came to Ajax loading of monthly stats. (Stats.template.php)
2574
Features / Re: New revs
« on August 24th, 2013, 04:22 PM »
rev 2228
(2 files, 1kb)
! The recent Wireless tweaks apparently broke the notification popup width. Hopefully this should fix it. (script.js, Wireless/extra.css)
(2 files, 1kb)
! The recent Wireless tweaks apparently broke the notification popup width. Hopefully this should fix it. (script.js, Wireless/extra.css)
2576
Bug reports / Re: req_win bug
« on August 24th, 2013, 10:07 AM »
Last time I tried to use reqWin for something a bit more complex (just loading an image with no HTML), I ended up adding 200+ bytes of code to it, and felt it was overkill for an admin area feature, and reverted my changes. I guess it influenced my post above, and yes, it's still possible to do great things with it.
If you have any suggestions...
If you have any suggestions...
2577
Archived fixes / Re: Outgoing emails aren't passed through the rewriter
« on August 24th, 2013, 10:05 AM »
It is, as far as I can remember.
2578
Features / Re: New revs
« on August 24th, 2013, 12:47 AM »
rev 2227
(8 files, 19kb)
! Tweaked PM notifications to use different text strings, allowing for the French version (and any other complicated language) to fit into the smaller width, because we're worth it... Also restored the Settings icon. Dunno if it not being there was as desired, uh..? (PersonalMessage.template.php, Notifications.language.php, PersonalMessage.english.php)
! PM notification update code was incorrectly using the 'count' variable, instead of items[1]. Also reworked code flow to save a few bytes, e.g. pmload() is never used outside of script.js, and thus can be declared as a local function. (script.js)
- Removed the PM icons from the menu sprite. Saves 220+ bytes of CSS, yay. (index.css, images/sprite-menu-32bit.png, images/icons/sprite.png)
(8 files, 19kb)
! Tweaked PM notifications to use different text strings, allowing for the French version (and any other complicated language) to fit into the smaller width, because we're worth it... Also restored the Settings icon. Dunno if it not being there was as desired, uh..? (PersonalMessage.template.php, Notifications.language.php, PersonalMessage.english.php)
! PM notification update code was incorrectly using the 'count' variable, instead of items[1]. Also reworked code flow to save a few bytes, e.g. pmload() is never used outside of script.js, and thus can be declared as a local function. (script.js)
- Removed the PM icons from the menu sprite. Saves 220+ bytes of CSS, yay. (index.css, images/sprite-menu-32bit.png, images/icons/sprite.png)
2579
The Pub / Re: PM popup
« on August 24th, 2013, 12:01 AM »
Yes, I don't see any problem in removing it; but that's mainly because I always found this to be overkill...
Amusingly, I had the same idea when studying the patch file; but I figured you would disagree with me. I was wrong, I guess ;)
BTW, while on the subject...
I rewrote the JS PM notif code to save about 80 gzipped bytes; it's not MUCH indeed, but it's better than nothing.
However, my rewrite consists in making a 'generic' object to handle any kind of notification popup, but I have two problems:
- I hardly see any reason for a plugin to add another type of notification...?! They would probably add themselves to the generic notifications, no..?
- I'm having trouble with the auto_update, ah ah... Because getting both notification numbers from the same request implies calling handlers from within a higher scope, so it's... Quite a bit fucked up.
I'm probably gonna give up on this, but I have to admit, I'm not thrilled with having so much repeated code in script.js, although it DOES compress very well, compared to the amount of code, so...
Amusingly, I had the same idea when studying the patch file; but I figured you would disagree with me. I was wrong, I guess ;)
BTW, while on the subject...
I rewrote the JS PM notif code to save about 80 gzipped bytes; it's not MUCH indeed, but it's better than nothing.
However, my rewrite consists in making a 'generic' object to handle any kind of notification popup, but I have two problems:
- I hardly see any reason for a plugin to add another type of notification...?! They would probably add themselves to the generic notifications, no..?
- I'm having trouble with the auto_update, ah ah... Because getting both notification numbers from the same request implies calling handlers from within a higher scope, so it's... Quite a bit fucked up.
I'm probably gonna give up on this, but I have to admit, I'm not thrilled with having so much repeated code in script.js, although it DOES compress very well, compared to the amount of code, so...
2580
Bug reports / Re: req_win bug
« on August 23rd, 2013, 08:35 PM »
It'd be a bad idea, basically.
I did my best to code something that was both modal and with nice effects. It was a bit... unrealistic, to think I could come up with it, but I did. I sort of regret it now, because ask/say functions are still a bit limited in what you can do with them, but still, I don't think I could have stopped myself from using them, ah ah...
Anyway, if you want to do some kind of form popup, you should rely on an actual popup, it's probably safer. <sigh>
Unless you have workarounds, of course...
I did my best to code something that was both modal and with nice effects. It was a bit... unrealistic, to think I could come up with it, but I did. I sort of regret it now, because ask/say functions are still a bit limited in what you can do with them, but still, I don't think I could have stopped myself from using them, ah ah...
Anyway, if you want to do some kind of form popup, you should rely on an actual popup, it's probably safer. <sigh>
Unless you have workarounds, of course...