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
3856
Features / Re: New revs
« on January 23rd, 2013, 12:33 PM »
rev 1868
(9 files, 6kb)
+ New linktree for Warm skin. This is located somewhere between the sobriety of Weaving and extravagance of Wuthering. Not 100% happy with it. I think that design is better suited to Weaving than Warm, but we're trying to keep Weaving simple. Suggestions welcome. (Warm/extra.css)
* Also decided to go for Open Sans font in Warm, instead of Tahoma. What do you know, it's a warmer font after all. Needs adjustments. (Warm/extra.css, Warm/skin.xml)
! Fixed a DOM validation error. (Search.template.php)
! Safari 5 doesn't seem to like text-indent. Found an alternative hack for it... If you find the reason why the original doesn't work, please contact me. (index.css)
* %1$s isn't a string that JavaScriptEscape needs to modify. :) (Boards.template.php)
* Cleaned up comments. (index.template.php, ManagePlugins.template.php, Warm/skin.xml)
* Gzinazi. That means I'm saving bytes. (Wuthering/extra.css)
* Translation. (ManagePlugins.french.php)
(9 files, 6kb)
+ New linktree for Warm skin. This is located somewhere between the sobriety of Weaving and extravagance of Wuthering. Not 100% happy with it. I think that design is better suited to Weaving than Warm, but we're trying to keep Weaving simple. Suggestions welcome. (Warm/extra.css)
* Also decided to go for Open Sans font in Warm, instead of Tahoma. What do you know, it's a warmer font after all. Needs adjustments. (Warm/extra.css, Warm/skin.xml)
! Fixed a DOM validation error. (Search.template.php)
! Safari 5 doesn't seem to like text-indent. Found an alternative hack for it... If you find the reason why the original doesn't work, please contact me. (index.css)
* %1$s isn't a string that JavaScriptEscape needs to modify. :) (Boards.template.php)
* Cleaned up comments. (index.template.php, ManagePlugins.template.php, Warm/skin.xml)
* Gzinazi. That means I'm saving bytes. (Wuthering/extra.css)
* Translation. (ManagePlugins.french.php)
3857
Archived fixes / Re: Linktree
« on January 22nd, 2013, 07:27 PM »
Thing is, one of my plans is to separate Wine from the rest, i.e. move Warm and Wuthering to be direct children of Weaving. So... Warm for now, I guess?
3858
Archived fixes / Re: Linktree
« on January 22nd, 2013, 07:05 PM »
The circles are here to stay. They're in Wuthering, which isn't the default skin.
Weaving, however, has the difficult task of trying to please everyone, and also staying a 'bare' skin that can easily be modified to your own taste. Wuthering is a child of Weaving and as such I can try to be as inventive as possible, because it's not going to be the default.
So...
- Weaving: boring linktree
- Wine and Warm: inherit linktree from Weaving
- Wuthering: has its own cool linktree
What I'm trying to do is change the boring Weaving linktree to the arrow version you see above. I'm trying to determine if it's "neutral" enough to be used in default skins. If yes, then it might be worth including.
After all, technically Wess has a nice little feature called 'reset' which allows you to entirely rewrite a selector without having to 'cancel' its current definition manually... And although I'd rather not encourage users to do that for anything, I'm trying to determine if it's okay for the linktree.
(Oh, and I also tried to move the Wuthering linktree to Weaving... It still looks great, but it's too "in your face". It tends to draw your attention, a bit too much. If I make it flat, though, it's better, but it looks a bit weird.)
Weaving, however, has the difficult task of trying to please everyone, and also staying a 'bare' skin that can easily be modified to your own taste. Wuthering is a child of Weaving and as such I can try to be as inventive as possible, because it's not going to be the default.
So...
- Weaving: boring linktree
- Wine and Warm: inherit linktree from Weaving
- Wuthering: has its own cool linktree
What I'm trying to do is change the boring Weaving linktree to the arrow version you see above. I'm trying to determine if it's "neutral" enough to be used in default skins. If yes, then it might be worth including.
After all, technically Wess has a nice little feature called 'reset' which allows you to entirely rewrite a selector without having to 'cancel' its current definition manually... And although I'd rather not encourage users to do that for anything, I'm trying to determine if it's okay for the linktree.
(Oh, and I also tried to move the Wuthering linktree to Weaving... It still looks great, but it's too "in your face". It tends to draw your attention, a bit too much. If I make it flat, though, it's better, but it looks a bit weird.)
3859
Archived fixes / Re: Linktree
« on January 22nd, 2013, 06:20 PM »
So... For those curious, here's a screenshot of the tentative linktree for Weaving.
It's using an arrow instead of a circle, the CSS is a bit shorter but not that much.
There aren't any pretty animations or anything, it's just what you can see below.
Is it worth committing, or should we stick to the default Weaving one..?
It's using an arrow instead of a circle, the CSS is a bit shorter but not that much.
There aren't any pretty animations or anything, it's just what you can see below.
Is it worth committing, or should we stick to the default Weaving one..?
3860
Archived fixes / Re: Why does Wedge look different for me?
« on January 22nd, 2013, 05:19 PM »
Hmm... Maybe I should just delete these lines then.
Actually my own copy is an empty file...
Actually my own copy is an empty file...
3861
Archived fixes / Re: Why does Wedge look different for me?
« on January 22nd, 2013, 04:42 PM »
(What is it with Home.english?)
3862
Features / Re: New revs
« on January 21st, 2013, 11:53 PM »
rev 1864 -- Wysiwyg gets some love!! Until Pete decides to ditch it :P
(18 files, 11kb)
+ Bringing proper Wysiwyg support for iOS and Android (stock and whatever), as long as they're not ancient versions. Only Firefox <3.5 and Opera Mini are not compatible. Also removed the fallback to contenteditable, because really, if you use a browser that's too old for that trick, you don't even know what 'Wysiwyg' means. You probably don't even know that you can register on forums and post messages, not just read them. (Class-Editor.php, editor.js)
! Fixed smiley and link insertion regression in Wysiwyg mode, due to an oversight (I didn't immediately see that iMoveCursorBack could have a value of zero. If you're not following, don't worry, it's intentional.) (Class-Editor.php)
* Simplified Wysiwyg processing. If your browser doesn't support it, you won't get an error message -- Wedge will simply no longer show the switcher icon. Also, if BBC is disabled, Wysiwyg is now disabled directly from within the editor code, rather than external files. (Class-Editor.php, PersonalMessage.php, Post.php, editor.js, LANGUAGE: index, Post)
* Rewrote Wysiwyg CSS handling. Finally, clicking at the bottom of the pseudo-textarea will properly move the cursor to the end of the text! Things like that... Also shortened and simplified many variable names, for logic reasons (isWysiwyg and canWysiwyg come to mind) and better compression overall. (Class-Editor.php, editor-func.js, editor.js, post.js, topic.js)
* Simplified editor CSS. Most notably, I replaced the browser-based variable declarations with @if's. It isn't any faster or more efficient or whatever -- it's just easier to understand. Originally I mostly used these variables to show that they can be used not only as values, but also as property-value pairs. (editor.css, extra.ie6.css, extra.ie7.css, extra.ie8.css, index.member.css)
* Language! (index.french.php, Post.french.php, Errors.french.php)
* Some breathing space. (Post.template.php)
(18 files, 11kb)
+ Bringing proper Wysiwyg support for iOS and Android (stock and whatever), as long as they're not ancient versions. Only Firefox <3.5 and Opera Mini are not compatible. Also removed the fallback to contenteditable, because really, if you use a browser that's too old for that trick, you don't even know what 'Wysiwyg' means. You probably don't even know that you can register on forums and post messages, not just read them. (Class-Editor.php, editor.js)
! Fixed smiley and link insertion regression in Wysiwyg mode, due to an oversight (I didn't immediately see that iMoveCursorBack could have a value of zero. If you're not following, don't worry, it's intentional.) (Class-Editor.php)
* Simplified Wysiwyg processing. If your browser doesn't support it, you won't get an error message -- Wedge will simply no longer show the switcher icon. Also, if BBC is disabled, Wysiwyg is now disabled directly from within the editor code, rather than external files. (Class-Editor.php, PersonalMessage.php, Post.php, editor.js, LANGUAGE: index, Post)
* Rewrote Wysiwyg CSS handling. Finally, clicking at the bottom of the pseudo-textarea will properly move the cursor to the end of the text! Things like that... Also shortened and simplified many variable names, for logic reasons (isWysiwyg and canWysiwyg come to mind) and better compression overall. (Class-Editor.php, editor-func.js, editor.js, post.js, topic.js)
* Simplified editor CSS. Most notably, I replaced the browser-based variable declarations with @if's. It isn't any faster or more efficient or whatever -- it's just easier to understand. Originally I mostly used these variables to show that they can be used not only as values, but also as property-value pairs. (editor.css, extra.ie6.css, extra.ie7.css, extra.ie8.css, index.member.css)
* Language! (index.french.php, Post.french.php, Errors.french.php)
* Some breathing space. (Post.template.php)
3863
Other software / Re: Discussing Elkarte on wedge.org
« on January 21st, 2013, 12:08 PM »They've made a TV series about nerds and how wonderful they are. Ladies of all types simply drooling over the prospect they may get noticed by one of these heavily prized creatures.
Never really watched the programme as it wasn't my cup of tea. Nonetheless it was aired suggesting nerds were on their way up in the world. Cant remember the name of the show. From that I made the general observation that nerds were popular. Doesn't matter merely a bit of goss.
The simple fact is, technology is now an important part of everyone's life. But just because you use the Internet doesn't make you a geek. However, using the Internet might *reveal* your geeky tendencies. So I guess there are more and more self-proclaimed geeks like ourselves, and with market shares comes power. There you go, TV starts trying to hide their Jerry-from-Parker-Lewis characters (whatever geek you could find in a TV show), and show instead 'cool' geeks.
Effectively, one thing I like about TBBT is that its geeks are not exactly likeable. Especially not Sheldon...
OTOH, I love The IT Crowd because Maurice Moss is so likeable :lol:
Bartender???/ sounds like Ted Danson and show Cheers just a bunch of broken down has been's frequenting their regular watering hole. Wouldn't exactly categorize them as nerds if that's what you were suggesting.
Unfamiliar with The Book of Mormon really.
Basically, he's the triumphant hero.
Then again, the BOM was written by a band of nerds who wouldn't admit it... (See Avenue Q for one, and South Park: You Have Zero Friend for the other group...)
3864
Off-topic / Re: I sympathise with this guy
« on January 21st, 2013, 11:59 AM »
Meh............ Seen way worse.
3865
Plugins / Re: PM Flash
« on January 21st, 2013, 07:17 AM »
Bat's arse != rat's arse?
First heard in Red Dwarf 8x01, personally... the Starbug actually went into a rat's ass.
First heard in Red Dwarf 8x01, personally... the Starbug actually went into a rat's ass.
3866
Features / Re: New revs
« on January 20th, 2013, 07:38 PM »
rev 1861 -- "a byte is a byte is a byte."
(3 files, 3kb)
+ Added two preg_replaces to the output buffer manager, that will remove the protocol and/or the domain name of any link that don't require it (i.e. they either share the same protocol as the current web page being viewed, or even its domain name.) It saves about 150 gzipped bytes on a regular full topic page (it all depends on the number of links), which is not much, but it also doesn't use more than a few milliseconds of CPU time, so it's a fair trade I'd say. Hasn't been 100% tested but should work. It can always be reversed later, or an admin setting can be set, too. Whatever. (Subs-Template.php)
! Fixed URL shortening when entities were found in them. This also saves an additional 5 gzipped bytes... Yeah, I know, it's boring innit? (script.js)
* Saved about 20 bytes in the editor by using php_unhtmlspecialchars() properly instead of a custom replacement, and removing a code block that did absolutely nothing. I'm annoyed by the useless var declarations in the spellcheck code by the way, but stripping them out actually adds 3 bytes. The joys of gzipping magic... (editor.js)
(3 files, 3kb)
+ Added two preg_replaces to the output buffer manager, that will remove the protocol and/or the domain name of any link that don't require it (i.e. they either share the same protocol as the current web page being viewed, or even its domain name.) It saves about 150 gzipped bytes on a regular full topic page (it all depends on the number of links), which is not much, but it also doesn't use more than a few milliseconds of CPU time, so it's a fair trade I'd say. Hasn't been 100% tested but should work. It can always be reversed later, or an admin setting can be set, too. Whatever. (Subs-Template.php)
! Fixed URL shortening when entities were found in them. This also saves an additional 5 gzipped bytes... Yeah, I know, it's boring innit? (script.js)
* Saved about 20 bytes in the editor by using php_unhtmlspecialchars() properly instead of a custom replacement, and removing a code block that did absolutely nothing. I'm annoyed by the useless var declarations in the spellcheck code by the way, but stripping them out actually adds 3 bytes. The joys of gzipping magic... (editor.js)
3867
Off-topic / Re: Post count fever
« on January 20th, 2013, 04:13 PM »
rev 1860+
(2 files, 21.542KB)
! Fixed this obvious bug where Pete appeared to have less posts than mine. (Dignity.php)
! Wedge should now properly increase Pete's postcount at a higher rate than mine. (Pragmatism.php)
(2 files, 21.542KB)
! Fixed this obvious bug where Pete appeared to have less posts than mine. (Dignity.php)
! Wedge should now properly increase Pete's postcount at a higher rate than mine. (Pragmatism.php)
3868
Archived fixes / Re: Previous/next topics don't work properly
« on January 20th, 2013, 04:09 PM »
I think I'm the one who rewrote the Previous/Next feature a year ago or so. Was very proud of it. I also think that it took pinned topics into accounts...
Where exactly do you think you'd broken it...? I haven't looked at your latest commits yet.
Where exactly do you think you'd broken it...? I haven't looked at your latest commits yet.
3869
Other software / Re: Discussing Elkarte on wedge.org
« on January 20th, 2013, 04:07 PM »
Oracle, I don't know where you've heard of that... Not everything in life happens like in The Book of Arnold Mormon... Geeks, and let's not even talk about nerds, tends to annoy girls in general. Not everyone wants to watch a romcom and be told about the entire fascinating filmography of this guy who plays the bartender in that scene. :whistle:
ema, I would heartfully agree with you, in that I tend to avoid looking at SMF/Elkarte codebases because they're confusing for someone like me who hasn't touched $smcFunc or $modSettings or $user_info in weeks, months or sometimes years. However, sharing ideas could be for the better of all projects. Maybe we should do something like that... We don't have to share implémentations, since they'll likely differ anyway. Sharing ideas sounds nice to me. Or bug fixes, like the many 'SMF bug' mentions I made in the Wedge changelog. ;)
ema, I would heartfully agree with you, in that I tend to avoid looking at SMF/Elkarte codebases because they're confusing for someone like me who hasn't touched $smcFunc or $modSettings or $user_info in weeks, months or sometimes years. However, sharing ideas could be for the better of all projects. Maybe we should do something like that... We don't have to share implémentations, since they'll likely differ anyway. Sharing ideas sounds nice to me. Or bug fixes, like the many 'SMF bug' mentions I made in the Wedge changelog. ;)
3870
Features / Re: New revs
« on January 20th, 2013, 01:24 AM »
rev 1860 -- fixing bugs, and again, and again! Plenty this time.
(5 files, 3kb)
! Finished a fix that was started last October and that I thought was already done... Hopefully it'll work fine now. This is about Wess's mixin feature. Some complex classes destined to be used as mixins would be broken when including them through a 'mixin:' property, rather than the 'mixes' keyword. (Class-CSS.php)
! Switching to Wysiwyg mode could have unwanted effects on whitespace inside quotes. (Subs-BBC.php)
! Changing one's language in the profile would generate an error due to a last remaining $context['user']. (Profile-Modify.php)
! IE7 in Wuthering STILL wasn't working properly... This was because of Microsoft (who else?). For a reason I ignore, when I try to view the page in IE10 using IE7 mode, it still gives me 'IE10 standards mode', instead of IE7 standards mode. And it just so happens that the 'filter' property isn't recognized in IE10 standards mode... (Wuthering/extra.css)
* Modified un_htmlspecialchars() to use htmlspecialchars_decode() for simplicity. (Subs.php)
(5 files, 3kb)
! Finished a fix that was started last October and that I thought was already done... Hopefully it'll work fine now. This is about Wess's mixin feature. Some complex classes destined to be used as mixins would be broken when including them through a 'mixin:' property, rather than the 'mixes' keyword. (Class-CSS.php)
! Switching to Wysiwyg mode could have unwanted effects on whitespace inside quotes. (Subs-BBC.php)
! Changing one's language in the profile would generate an error due to a last remaining $context['user']. (Profile-Modify.php)
! IE7 in Wuthering STILL wasn't working properly... This was because of Microsoft (who else?). For a reason I ignore, when I try to view the page in IE10 using IE7 mode, it still gives me 'IE10 standards mode', instead of IE7 standards mode. And it just so happens that the 'filter' property isn't recognized in IE10 standards mode... (Wuthering/extra.css)
* Modified un_htmlspecialchars() to use htmlspecialchars_decode() for simplicity. (Subs.php)