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
6571
Features / Re: New revs
« on January 28th, 2012, 04:09 PM »
rev 1280
(10 files, 4kb)
+ Implemented sidebar positioning through skin settings, i.e. <sidebar>. (Load.php, Aeva-Gallery.php, Subs-Cache.php, skin.xml, Warm/skin.xml)
* Replaced $context['post_position'] with $context['sidebar_position'] in topic pages, and inverted their logic obviously. (Display.php, Display.template.php)
* wetem::parent() is a much more elegant way of determining whether the current block is executed in the default layer or in the sidebar... (Media.template.php)
* Micro-styling. (admin.css, media.css)
(10 files, 4kb)
+ Implemented sidebar positioning through skin settings, i.e. <sidebar>. (Load.php, Aeva-Gallery.php, Subs-Cache.php, skin.xml, Warm/skin.xml)
* Replaced $context['post_position'] with $context['sidebar_position'] in topic pages, and inverted their logic obviously. (Display.php, Display.template.php)
* wetem::parent() is a much more elegant way of determining whether the current block is executed in the default layer or in the sidebar... (Media.template.php)
* Micro-styling. (admin.css, media.css)
6572
Features / Re: New revs
« on January 27th, 2012, 09:07 PM »
rev 1279
(10 files, 4kb)
* Harmonized block headers in the sidebar. Some were using we:title, others were using we:title2, now they're all using we:title. (Display.template.php, GenericMenu.template.php, MessageIndex.template.php)
* Started harmonizing font sizes in the sidebar. Right now it'll look ugly on a stock install, but that's because I'm doing the styling in the new skin, which has yet to be committed. Trust me, it's looking good. (GenericMenu.template.php, InfoCenter.template.php)
- Removed info center's toggler button, because it's of absolutely no use, and a waste of bandwidth. If you want it, you can always, I don't know, get a life. (Boards.php, Welcome.php, InfoCenter.template.php, Welcome.template.php, index.rtl.css, sections.css, Warm/index.css)
(10 files, 4kb)
* Harmonized block headers in the sidebar. Some were using we:title, others were using we:title2, now they're all using we:title. (Display.template.php, GenericMenu.template.php, MessageIndex.template.php)
* Started harmonizing font sizes in the sidebar. Right now it'll look ugly on a stock install, but that's because I'm doing the styling in the new skin, which has yet to be committed. Trust me, it's looking good. (GenericMenu.template.php, InfoCenter.template.php)
- Removed info center's toggler button, because it's of absolutely no use, and a waste of bandwidth. If you want it, you can always, I don't know, get a life. (Boards.php, Welcome.php, InfoCenter.template.php, Welcome.template.php, index.rtl.css, sections.css, Warm/index.css)
6573
Off-topic / Re: Google Code-in
« on January 27th, 2012, 06:37 PM »
I should add it's well deserved -- you can glance at his work when following links, there are some impressive things. Including some assembler code! :lol:
(My little finger is telling me that Google Code-In becomes much easier to handle by using the Google search engine, just like any sane person would do... :P)
(My little finger is telling me that Google Code-In becomes much easier to handle by using the Google search engine, just like any sane person would do... :P)
6574
Features / Re: New revs
« on January 27th, 2012, 06:34 PM »
rev 1278 -- another set of features I'd been meaning to add from day one!
(4 files, 5kb)
+ Added number of new posts available per topic in the Unread Topics and Unread Replies pages. Another proud feature from Noisen/Wedge.org! And yes, I know, it's a bit of a slow query... But I think it could be worse. And it never killed my forums, after years of use. (Unread.php, UnreadReplies.php, Recent.template.php)
* Remove the thoughts block if no thoughts are found at all. (Welcome.php)
(4 files, 5kb)
+ Added number of new posts available per topic in the Unread Topics and Unread Replies pages. Another proud feature from Noisen/Wedge.org! And yes, I know, it's a bit of a slow query... But I think it could be worse. And it never killed my forums, after years of use. (Unread.php, UnreadReplies.php, Recent.template.php)
* Remove the thoughts block if no thoughts are found at all. (Welcome.php)
6575
Features / Re: New revs
« on January 27th, 2012, 04:56 PM »
rev 1277
(25 files, 4kb)
* Renamed constructPageIndex() to template_page_index(), in keeping with the index template's naming guidelines. (index.template.php, 24 files in Sources)
(25 files, 4kb)
* Renamed constructPageIndex() to template_page_index(), in keeping with the index template's naming guidelines. (index.template.php, 24 files in Sources)
6576
Features / Re: New revs
« on January 27th, 2012, 04:45 PM »
rev 1276
(5 files, 3kb)
+ Just like at Wedge.org, Wedge will now add a New icon next to the page index if there are more unread topic pages available to you. Although it's not as important as back in the day when SMF was buggy and marked an entire topic as read even with more pages unread, it's still nice to easily spot whether there are more pages to go through. (index.template.php)
+ Show a New icon next to the first unread post in topic pages. Wedge.org does it differently (it adds a New icon next to all unread posts), but I felt this might be a bit overwhelming in a generic forum system. (Display.php, Display.template.php)
* Optimized the 'new' icon's size. Didn't expect to save anything, but there you go, a few less bytes. (images/language/new.gif)
(5 files, 3kb)
+ Just like at Wedge.org, Wedge will now add a New icon next to the page index if there are more unread topic pages available to you. Although it's not as important as back in the day when SMF was buggy and marked an entire topic as read even with more pages unread, it's still nice to easily spot whether there are more pages to go through. (index.template.php)
+ Show a New icon next to the first unread post in topic pages. Wedge.org does it differently (it adds a New icon next to all unread posts), but I felt this might be a bit overwhelming in a generic forum system. (Display.php, Display.template.php)
* Optimized the 'new' icon's size. Didn't expect to save anything, but there you go, a few less bytes. (images/language/new.gif)
6577
Features / Re: New revs
« on January 27th, 2012, 03:04 PM »
rev 1275
(3 files, 9kb)
+ Added support for transparency in attachments and avatars. Transparency is only calculated when showing an attachment in a topic (loadAttachmentContext), when showing an avatar in the sidebar (loadUserSettings, setupThemeContext), and when loading avatars for other members (loadMemberContext). Calculations are done using the code I wrote for Aeva Media 2.x. Non-transparent avatars get an 'opaque' class, while nothing special is done for attachments right now. Maybe we'll do something later, but I'm lacking inspiration. (Display.php, Load.php, Subs.php)
(3 files, 9kb)
+ Added support for transparency in attachments and avatars. Transparency is only calculated when showing an attachment in a topic (loadAttachmentContext), when showing an avatar in the sidebar (loadUserSettings, setupThemeContext), and when loading avatars for other members (loadMemberContext). Calculations are done using the code I wrote for Aeva Media 2.x. Non-transparent avatars get an 'opaque' class, while nothing special is done for attachments right now. Maybe we'll do something later, but I'm lacking inspiration. (Display.php, Load.php, Subs.php)
6578
Off-topic / Re: Google Code-in
« on January 27th, 2012, 12:39 PM »
Congratulations are in order, then!! :)
Why didn't you mention it before?
Why didn't you mention it before?
6579
Features / Re: New revs
« on January 27th, 2012, 12:38 PM »
rev 1274
(1 file, 2kb)
+ Added a transparency flag to attachments. Yep. You know what I'm gonna do. I just need a couple of hours to grab a snack and check my implementation's elegance. (install.sql)
! Turning BBC size 1-7 to use the equivalent point size instead of em's, to match whatever's in the Wysiwyg editor. (install.sql)
(Next commit will be a bit bigger.)
(1 file, 2kb)
+ Added a transparency flag to attachments. Yep. You know what I'm gonna do. I just need a couple of hours to grab a snack and check my implementation's elegance. (install.sql)
! Turning BBC size 1-7 to use the equivalent point size instead of em's, to match whatever's in the Wysiwyg editor. (install.sql)
(Next commit will be a bit bigger.)
6580
Features / Re: New revs
« on January 27th, 2012, 12:35 PM »
1273
(5 files, 1kb)
- Removed a few unused global declarations of $user_settings. (ManageServer.php, PersonalMessage.php, Profile.php, Security.php, Subs-Auth.php)
(5 files, 1kb)
- Removed a few unused global declarations of $user_settings. (ManageServer.php, PersonalMessage.php, Profile.php, Security.php, Subs-Auth.php)
6581
Off-topic / Re: Google Code-in
« on January 27th, 2012, 12:22 PM »
So, Dragooon! Google Code-In is complete, and you're still first (by a large margin!).
Does this mean you won the competition? :D
Does this mean you won the competition? :D
6582
Features / Re: New revs
« on January 27th, 2012, 10:46 AM »
rev 1272
(3 files, 9kb)
* WYSIWYG: Rewrote a lot of the updateEditorControls code to work properly across all browsers I could test against. (editor.js)
+ WYSIWYG: Added an .insertStyle(object) function to the editor object, where you specify a key/value object similar to .css(object) to add specific styles to the selection. Note: if using styleWithCSS, we'd also have to match span[style*="xxx-large"]. Thankfully I removed that one. Also, it could be interesting to actually re-use this code to replace most of the complex insertions like insertCustomHTML... (editor.js)
! WYSIWYG: Only update select boxes if their contents were actually changed. It's not a free process, you know. (post.js)
! WYSIWYG: Ensure select boxes don't try to select an invalid value. (post.js)
* Harmonized editor's textarea and iframe to have the same sizes and appearances. (Well, internal iframe padding is off by a pixel in some browsers but it's the best I could do.) The main trick was to actually set their display to block, as odd as it may sound. (editor.js, editor.css)
:edit: Updated rev 1270's changelog with an item I forgot to document.
(3 files, 9kb)
* WYSIWYG: Rewrote a lot of the updateEditorControls code to work properly across all browsers I could test against. (editor.js)
+ WYSIWYG: Added an .insertStyle(object) function to the editor object, where you specify a key/value object similar to .css(object) to add specific styles to the selection. Note: if using styleWithCSS, we'd also have to match span[style*="xxx-large"]. Thankfully I removed that one. Also, it could be interesting to actually re-use this code to replace most of the complex insertions like insertCustomHTML... (editor.js)
! WYSIWYG: Only update select boxes if their contents were actually changed. It's not a free process, you know. (post.js)
! WYSIWYG: Ensure select boxes don't try to select an invalid value. (post.js)
* Harmonized editor's textarea and iframe to have the same sizes and appearances. (Well, internal iframe padding is off by a pixel in some browsers but it's the best I could do.) The main trick was to actually set their display to block, as odd as it may sound. (editor.js, editor.css)
:edit: Updated rev 1270's changelog with an item I forgot to document.
6583
Features / Re: New revs
« on January 26th, 2012, 12:48 AM »
rev 1271
(3 files, 14kb)
* Dozens of extra size optimizations on the Wysiwyg editor, most notably all for () loops were replaced with my beloved $.each() call. That was NOT easy, though, especially in post.js... Still, over one kilobyte saved on the gzipped minified file? Not something to complain about! (editor.js, post.js)
* I try to avoid code evaluation when possible, such as in setInterval calls. (post.js)
! Chrome didn't correctly retrieve the current font face when navigating the Wysywig editor. Seems to be working for all three font parameters in IE, Chrome, Firefox and Opera. Last time I checked, it wasn't the case... Let's not ask too many questions. (editor.js)
! updateEditorControls()'s breadcrumb builder would actually execute way too much code in one of its loops, as most of it only needed to be called once. (editor.js)
! Fixed a bug in rev 1270 where I wrote some JavaScript when I meant to be using PHP. Perhaps I was *too* thrilled I'd fixed that bug... (Class-Editor.php)
(3 files, 14kb)
* Dozens of extra size optimizations on the Wysiwyg editor, most notably all for () loops were replaced with my beloved $.each() call. That was NOT easy, though, especially in post.js... Still, over one kilobyte saved on the gzipped minified file? Not something to complain about! (editor.js, post.js)
* I try to avoid code evaluation when possible, such as in setInterval calls. (post.js)
! Chrome didn't correctly retrieve the current font face when navigating the Wysywig editor. Seems to be working for all three font parameters in IE, Chrome, Firefox and Opera. Last time I checked, it wasn't the case... Let's not ask too many questions. (editor.js)
! updateEditorControls()'s breadcrumb builder would actually execute way too much code in one of its loops, as most of it only needed to be called once. (editor.js)
! Fixed a bug in rev 1270 where I wrote some JavaScript when I meant to be using PHP. Perhaps I was *too* thrilled I'd fixed that bug... (Class-Editor.php)
6584
Features / Re: New revs
« on January 25th, 2012, 11:38 PM »
rev 1270
(5 files, 4kb)
! Fixed this most *annoying* IE 6-10 bug that took me over a week to find and neutralize, where the cursor position was reset to the message's beginning when clicking a smiley or button in Wysiwyg mode. Note for anyone at SMF tempted to use sprites for buttons in the editor: don't even think of getting rid of the img tag. Or at least, just having an empty div will break your stuff. Trust me, you don't wanna waste a week debugging this. (Class-Editor.php)
! Fixed another IE bug where it didn't correctly convert smileys from Wysiwyg to non-Wysiwyg mode. This is because it seems to reorder img tag parameters instead of using whatever was requested originally. Bad IE. (Class-Editor.php)
! Fixed installer's first page: CSS cache generation was broken (resulting in unstyled HTML), and the language select box wouldn't show up. (other/install.php, install.css)
* Moved New/Modify links in the Thought editor to inside the block, rather than in the block header. I'd say I should avoid putting links in short headers, because it can break the overall layout easily. (index.template.php)
* Forgot to document the 'include' keyword for code tags in skin files. (Warm/skin.xml)
:edit: - Removed Arial Black font from font list. Latest versions of Firefox, due to their font engine rewrite, will now ignore a simple "font-family: Arial Black" and instead expect "font-family: Arial; font-weight: 800" to show it. This is too complicated to implement with regards to the limited interest of that font face.
(5 files, 4kb)
! Fixed this most *annoying* IE 6-10 bug that took me over a week to find and neutralize, where the cursor position was reset to the message's beginning when clicking a smiley or button in Wysiwyg mode. Note for anyone at SMF tempted to use sprites for buttons in the editor: don't even think of getting rid of the img tag. Or at least, just having an empty div will break your stuff. Trust me, you don't wanna waste a week debugging this. (Class-Editor.php)
! Fixed another IE bug where it didn't correctly convert smileys from Wysiwyg to non-Wysiwyg mode. This is because it seems to reorder img tag parameters instead of using whatever was requested originally. Bad IE. (Class-Editor.php)
! Fixed installer's first page: CSS cache generation was broken (resulting in unstyled HTML), and the language select box wouldn't show up. (other/install.php, install.css)
* Moved New/Modify links in the Thought editor to inside the block, rather than in the block header. I'd say I should avoid putting links in short headers, because it can break the overall layout easily. (index.template.php)
* Forgot to document the 'include' keyword for code tags in skin files. (Warm/skin.xml)
:edit: - Removed Arial Black font from font list. Latest versions of Firefox, due to their font engine rewrite, will now ignore a simple "font-family: Arial Black" and instead expect "font-family: Arial; font-weight: 800" to show it. This is too complicated to implement with regards to the limited interest of that font face.
6585
Off-topic / Re: Customer Care
« on January 25th, 2012, 08:05 PM »
How cute.
(But her daddy should be ashamed that he can't remove a backslash from his mails.. :P)
(But her daddy should be ashamed that he can't remove a backslash from his mails.. :P)