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
8446
Features / Re: New revs
« on July 15th, 2011, 09:31 AM »
rev 869
(8 files +3-3, 18kb)
! Never noticed that before, but the main content was misaligned in floating sidebar mode. (index.css)
* Don't show « » in Last edit, and show it in italics only through CSS. (Display.template.php, sections.css)
* Say "Last edited" instead of "Last edit", since it's followed with "today", "yesterday" or "on Date". (index.english.php)
* Renamed some bigicons to keep underscore consistency. (ban_list.png, media_settings.png, server_settings.png, Admin.php)
* The admin area's placeholder icon should be at the same size as the rest... (Admin.template.php)
* Translation, or lack thereof. (Who.french.php)
(8 files +3-3, 18kb)
! Never noticed that before, but the main content was misaligned in floating sidebar mode. (index.css)
* Don't show « » in Last edit, and show it in italics only through CSS. (Display.template.php, sections.css)
* Say "Last edited" instead of "Last edit", since it's followed with "today", "yesterday" or "on Date". (index.english.php)
* Renamed some bigicons to keep underscore consistency. (ban_list.png, media_settings.png, server_settings.png, Admin.php)
* The admin area's placeholder icon should be at the same size as the rest... (Admin.template.php)
* Translation, or lack thereof. (Who.french.php)
8447
Off-topic / Re: Doctor Who
« on July 15th, 2011, 08:49 AM »AGMGTW answers the question, of *who* River Song is, but doesn't explain much more than that.
It doesn't, for example, explain who the good man that she murdered is (and was subsequently sent to Stormcage for).
It doesn't explain how she was subsequently pardoned because she has been by the time of the events of Silence in the Library.
It also does not explain - and this is the most intricate detail - the military insignias. The military insignias shown on the uniforms in AGMGTW match the military insignias on the uniforms of the troops in The Time of Angels.
And if that's not enough, the insignia is... potentially... from a very old enemy of the Doctor.
As for TW, it isn't the same show as DW so it will appeal to some more than others. Though I'd argue that TW is no more a thrillerish show than DW itself is.
What I like in DW is precisely the opposite of what most RD episodes did: the intimate moments, the slow moments, the moments where story matters most than the thrills. That's why I hate cliffhangers: they're supposed to make you excited for the follow up. But I'm not excited for the follow up! I'm excited for what I'm seeing right now! I don't spend hours discussing theories on the next DW! (Well, happened to me, but mainly to play along, not for the sheer enjoyment of it :P)
8448
The Pub / Re: Menu hover concerns
« on July 15th, 2011, 08:38 AM »
Re: menu delay, I'm afraid there's no delay when opening it. There is a delay -- but it is before *closing* it.
I could add a very, very short delay before opening it, but I didn't. (So far, at least.)
Since I wrote the damn thing, let me explain my point of view.
When you open a menu, you want reactivity. The first thing I always do when reinstalling Windows, is getting rid of the stupid hover delay on menus. I suppose people are used to it.
Now, when it comes to Windows, once a menu is opened and you've hovered somewhere else, it stays open until you click something, so I can understand the logic behind it. But in a web page, the menu will auto-close when hovering away. So there's really no loss in usability, just a minor issue with things showing up unexpectedly because you're aiming for a toolbar button.
All right.
Now, the thing that may bother you in SMF menus may not bother you as much in a Wedge menu, because it's a much more evolved menu system. I thought I'd described it in the Features area, but only wrote these two lines:
"- New menu system. Looks great, plays great, uses CSS3 but works in IE6, uses JavaScript but works when JS is disabled. Supports separators. Icons based on the Diagona set."
Okay, so here's what happens who you hover a menu: it starts opening, yes -- but with a fade in, and an animation. The animation isn't of concern here. What matters is the quick fade in. Because it shows up smoothly, it doesn't jump at you, and you don't get the same feeling as you'd get when opening a menu by mistake in SMF.
It may sound silly, but I literally refined my menu tech for years. I spent something like two weeks working on it for Wedge last year, to make it the best I could. I made tries with opening delays, but I found they bothered me when I actually wanted to open a menu item.
So, I guess you'll have to take my word for it, or wait a few more weeks until we make the demo site public.
But it's all thoroughly thought out really. I'm very serious about menus. I even considered using mega-menus at some point, for usability geeks. Tried it all, kept what worked for me.Quote from Arantor on July 15th, 2011, 07:53 AM It does, as explained in the feature description. Another thing that I spent a lot of time on ;)
JavaScript is only used for a few things in the menu:
- setting up closing delays (to allow for a user's mouse pointer to hover outside the menu area, then quickly come back in, without having the entire menu get closed),
- specifying the position of submenu items (relative to their owner item),
- adding a shim for IE6 (in order to prevent form elements from being shown on top of the menu items),
- applying a special class to hovered items, so that I can keep a consistent trail of selected elements in the nested levels, i.e. if I'm highlighting an option in submenu level 3, the parent option in level 2 stays highlighted, and in level 1 as well. This can be done in CSS (IIRC, I actually gave SMF the technique to do that, I don't remember whether they implemented it or not, or whether I implemented it myself during my stint in their dev team), but it has limits and I don't like limitations.
So, until the menu JS code is loaded, it works perfectly well, in CSS mode. When JS is loaded, the CSS mode is disabled and we play with the big boys.Quote Well, it does benefit from it ;)Quote Completely agreed.
I could add a very, very short delay before opening it, but I didn't. (So far, at least.)
Since I wrote the damn thing, let me explain my point of view.
When you open a menu, you want reactivity. The first thing I always do when reinstalling Windows, is getting rid of the stupid hover delay on menus. I suppose people are used to it.
Now, when it comes to Windows, once a menu is opened and you've hovered somewhere else, it stays open until you click something, so I can understand the logic behind it. But in a web page, the menu will auto-close when hovering away. So there's really no loss in usability, just a minor issue with things showing up unexpectedly because you're aiming for a toolbar button.
All right.
Now, the thing that may bother you in SMF menus may not bother you as much in a Wedge menu, because it's a much more evolved menu system. I thought I'd described it in the Features area, but only wrote these two lines:
"- New menu system. Looks great, plays great, uses CSS3 but works in IE6, uses JavaScript but works when JS is disabled. Supports separators. Icons based on the Diagona set."
Okay, so here's what happens who you hover a menu: it starts opening, yes -- but with a fade in, and an animation. The animation isn't of concern here. What matters is the quick fade in. Because it shows up smoothly, it doesn't jump at you, and you don't get the same feeling as you'd get when opening a menu by mistake in SMF.
It may sound silly, but I literally refined my menu tech for years. I spent something like two weeks working on it for Wedge last year, to make it the best I could. I made tries with opening delays, but I found they bothered me when I actually wanted to open a menu item.
So, I guess you'll have to take my word for it, or wait a few more weeks until we make the demo site public.
But it's all thoroughly thought out really. I'm very serious about menus. I even considered using mega-menus at some point, for usability geeks. Tried it all, kept what worked for me.
I have a feeling it does,
JavaScript is only used for a few things in the menu:
- setting up closing delays (to allow for a user's mouse pointer to hover outside the menu area, then quickly come back in, without having the entire menu get closed),
- specifying the position of submenu items (relative to their owner item),
- adding a shim for IE6 (in order to prevent form elements from being shown on top of the menu items),
- applying a special class to hovered items, so that I can keep a consistent trail of selected elements in the nested levels, i.e. if I'm highlighting an option in submenu level 3, the parent option in level 2 stays highlighted, and in level 1 as well. This can be done in CSS (IIRC, I actually gave SMF the technique to do that, I don't remember whether they implemented it or not, or whether I implemented it myself during my stint in their dev team), but it has limits and I don't like limitations.
So, until the menu JS code is loaded, it works perfectly well, in CSS mode. When JS is loaded, the CSS mode is disabled and we play with the big boys.
but honestly, the admin panel is somewhere we're likely to be expanding the use of JavaScript in (there is one place I know right now that *needs* JavaScript because of its current implementation) - it's not as if the general forum absolutely requires JS at the moment.
The admin panel does have a much lower access rate and can afford to make more demands.
8449
Development blog / Re: Now with 97% more visuals!
« on July 15th, 2011, 06:54 AM »
The admin panel show how the sidebar can be useful (you don't actually have to visit the homepage again to view all of these details from within an admin area.)
Oh, I did the redesign for the fieldset, too. I felt I had to do it because Pete is so much in love with fieldsets and likes using them everywhere. Now with good reason :D (This is all part of the 'work in progress', as we have yet to see whether we'll use fieldsets a lot or just on the odd page.)
Oh, I did the redesign for the fieldset, too. I felt I had to do it because Pete is so much in love with fieldsets and likes using them everywhere. Now with good reason :D (This is all part of the 'work in progress', as we have yet to see whether we'll use fieldsets a lot or just on the odd page.)
8450
Off-topic / Re: Doctor Who
« on July 15th, 2011, 01:22 AM »
Thanks. I'll be waiting then.
Oh and I like dark. Just not the American way. With big sfx and cliffhangers. Meh.
Oh and I like dark. Just not the American way. With big sfx and cliffhangers. Meh.
8451
Off-topic / Re: Doctor Who
« on July 15th, 2011, 01:12 AM »
So. Was Torchwood any good?
Loved s2, wasn't thrilled with s3. Just for reference.
Oh. And tomorrow a big French channel is showing Sherlock at 20:35. Can't believe Moffat will finally be getting some deserved exposure here!
Loved s2, wasn't thrilled with s3. Just for reference.
Oh. And tomorrow a big French channel is showing Sherlock at 20:35. Can't believe Moffat will finally be getting some deserved exposure here!
8452
Development blog / Re: Now with 97% more visuals!
« on July 15th, 2011, 12:50 AM »
I wanted to publish the version with userbox on the right, but figured there was already enough to analyze for newcomers ;)
Oh, and I translated everything on the page but somehow managed to miss the second post's title, lol. Time for bed anyway!
Oh, and I translated everything on the page but somehow managed to miss the second post's title, lol. Time for bed anyway!
8453
Development blog / Now with 97% more visuals!
« on July 15th, 2011, 12:35 AM »
8454
Features / Re: New revs
« on July 14th, 2011, 11:45 PM »
rev 867
(6 files +1, 11kb)
* More changes to the topic view. Both Report to Moderator links are now in the user box, with the main one getting its own (temp) icon. And it no longer shows on user's own posts (which always baffled me because sometimes they'd use this as a way to draw attention on their own posts.) Also reworded 'Report to moderator' to 'Report this message to a moderator', because hover titles can be longer, right? (Display.template.php, report.gif, index.language.php, sections.css)
* Nothing interesting. (PersonalMessage.english.php, ManageNews.template.php)
(6 files +1, 11kb)
* More changes to the topic view. Both Report to Moderator links are now in the user box, with the main one getting its own (temp) icon. And it no longer shows on user's own posts (which always baffled me because sometimes they'd use this as a way to draw attention on their own posts.) Also reworded 'Report to moderator' to 'Report this message to a moderator', because hover titles can be longer, right? (Display.template.php, report.gif, index.language.php, sections.css)
* Nothing interesting. (PersonalMessage.english.php, ManageNews.template.php)
8455
Features / Re: New revs
« on July 14th, 2011, 09:28 PM »
rev 866 (another big commit... U mad bro?)
(16 files, 27kb)
* Moved user box template to its own function. (Display.template.php)
* Subtle changes to the post box to please Pete, err, to make it less crowded. (sections.css)
* Boldly attempting to remove the border around fieldsets in the admin homepage. Only there, eh. Makes the page less... crowded, you got it. (index.css)
! Media embedder still had a deprecated table align. Ouch. (Subs-Media.php)
! In some situations (namely Wedge rewriting the tab_data stuff with its own data to finetune tab positions), Wedge would fail noticing that it shouldn't be trying to show a context menu item. (GenericMenu.template.php)
- As far as I know, $txt['attachment_log'] is not used anywhere. (Admin.language.php)
* Ugly warning in Attachment/Avatar admin area. (ManageAttachments.php, Admin.language.php)
* Log pruning area has long descriptions in French, so I added bold tags around the actual names of the logs. (ManageSettings.french.php)
* Indenazi. (Subs-Menu.php)
* Large cleanup in the Log admin area. spider logs lost their plural, all log menu entries are now repeated (once for their in-context menu entry, once for the Log menu area, enabling to drop the 'log' part of the name and keep the context menu on a single line in French and other long languages), renamed pruning_title to log_pruning, etc. (Admin.php, ManageSearchEngines.php, ManageSettings.php, Admin.language.php, Search.language.php, ManageSearch.template.php)
(16 files, 27kb)
* Moved user box template to its own function. (Display.template.php)
* Subtle changes to the post box to please Pete, err, to make it less crowded. (sections.css)
* Boldly attempting to remove the border around fieldsets in the admin homepage. Only there, eh. Makes the page less... crowded, you got it. (index.css)
! Media embedder still had a deprecated table align. Ouch. (Subs-Media.php)
! In some situations (namely Wedge rewriting the tab_data stuff with its own data to finetune tab positions), Wedge would fail noticing that it shouldn't be trying to show a context menu item. (GenericMenu.template.php)
- As far as I know, $txt['attachment_log'] is not used anywhere. (Admin.language.php)
* Ugly warning in Attachment/Avatar admin area. (ManageAttachments.php, Admin.language.php)
* Log pruning area has long descriptions in French, so I added bold tags around the actual names of the logs. (ManageSettings.french.php)
* Indenazi. (Subs-Menu.php)
* Large cleanup in the Log admin area. spider logs lost their plural, all log menu entries are now repeated (once for their in-context menu entry, once for the Log menu area, enabling to drop the 'log' part of the name and keep the context menu on a single line in French and other long languages), renamed pruning_title to log_pruning, etc. (Admin.php, ManageSearchEngines.php, ManageSettings.php, Admin.language.php, Search.language.php, ManageSearch.template.php)
8456
Features / Re: New revs
« on July 14th, 2011, 06:40 PM »
rev 864 (another big one!)
(36 files, 37kb)
* Rewrote the post layout for topic views. Ohhhh yeah. Now using display: table and sporting more freedom. Will fix IE6 and IE7 later. If they're nice enough. Also, section.css could probably use some cleaning up. (Display.template.php, sections.css)
* Rewrote JavaScriptEscape() to avoid escaping tabs and newlines. Also gave up on escaping tag closers, as I couldn't find any single reason for doing so. And using shorter hacks for script, href and scripturl situations. (Subs.php)
* Renamed global smf_* Js variables to we_*, and smf_scripturl to we_script, as it's used more often, so might as well have it shorter. (various other/* files, editor.js, mediadmin.js, register.js, script.js, stats.js, suggest.js, topic.js, up.js, Admin.php, TEMPLATES: index, ManageMembergroups, Packages, Post, SplitTopics, Themes)
* Moved registration center next to the member list in the admin menu, as semantically it's closer to that, than to the permission/ban stuff. (Admin.php)
! Avoid duplicates in closed tag list when doing the split quote thing. Needs a rewrite though. (Class-Editor.php)
* Indenazi, Pretty URL replace buffer cleanup and other useless changes. (Subs.php, ManageMedia.english.php, post.js, index.css)
! Event delayer was systematically doing a failed bind() for each and every event in the page. Oops, my bad. (Subs.php)
- sScriptUrl and sImagesUrl are never used (or never useful) in a couple of JS objects. (Display.template.php, Media.template.php, topic.js)
* Renamed admin menu entry 'Reports' to 'Detailed Reports'. I think it should help differentiate it from moderator reports. I always get confused by this. (Admin.language.php)
* Updated French translation. (Admin.french.php, ManageMedia.french.php)
! It's Rank images, not Stars. (ManageMembers.language.php, Reports.language.php)
! Fixed toggler in the email settings page. Note: we need to turn this into a PROPER Wedge toggler... (ManageNews.template.php)
* Various script.js changes that may or may not be reverted later: a semi-fix for reqWin title retrieval (doesn't actually work on text nodes, uh...), and a hack to prevent Firefox from fixing the reqWin event. (script.js)
! Apparently, Firefox 5 (and earlier?) doesn't like when jQuery creates a hidden input and adds a name param separately. Fixed by putting the name into the tag string itself. (suggest.js, topic.js)
rev 865
! Typo crash. (Admin.php)
(36 files, 37kb)
* Rewrote the post layout for topic views. Ohhhh yeah. Now using display: table and sporting more freedom. Will fix IE6 and IE7 later. If they're nice enough. Also, section.css could probably use some cleaning up. (Display.template.php, sections.css)
* Rewrote JavaScriptEscape() to avoid escaping tabs and newlines. Also gave up on escaping tag closers, as I couldn't find any single reason for doing so. And using shorter hacks for script, href and scripturl situations. (Subs.php)
* Renamed global smf_* Js variables to we_*, and smf_scripturl to we_script, as it's used more often, so might as well have it shorter. (various other/* files, editor.js, mediadmin.js, register.js, script.js, stats.js, suggest.js, topic.js, up.js, Admin.php, TEMPLATES: index, ManageMembergroups, Packages, Post, SplitTopics, Themes)
* Moved registration center next to the member list in the admin menu, as semantically it's closer to that, than to the permission/ban stuff. (Admin.php)
! Avoid duplicates in closed tag list when doing the split quote thing. Needs a rewrite though. (Class-Editor.php)
* Indenazi, Pretty URL replace buffer cleanup and other useless changes. (Subs.php, ManageMedia.english.php, post.js, index.css)
! Event delayer was systematically doing a failed bind() for each and every event in the page. Oops, my bad. (Subs.php)
- sScriptUrl and sImagesUrl are never used (or never useful) in a couple of JS objects. (Display.template.php, Media.template.php, topic.js)
* Renamed admin menu entry 'Reports' to 'Detailed Reports'. I think it should help differentiate it from moderator reports. I always get confused by this. (Admin.language.php)
* Updated French translation. (Admin.french.php, ManageMedia.french.php)
! It's Rank images, not Stars. (ManageMembers.language.php, Reports.language.php)
! Fixed toggler in the email settings page. Note: we need to turn this into a PROPER Wedge toggler... (ManageNews.template.php)
* Various script.js changes that may or may not be reverted later: a semi-fix for reqWin title retrieval (doesn't actually work on text nodes, uh...), and a hack to prevent Firefox from fixing the reqWin event. (script.js)
! Apparently, Firefox 5 (and earlier?) doesn't like when jQuery creates a hidden input and adds a name param separately. Fixed by putting the name into the tag string itself. (suggest.js, topic.js)
Posted: July 14th, 2011, 05:09 PM
rev 865
! Typo crash. (Admin.php)
8457
Features / Re: New revs
« on July 14th, 2011, 12:57 AM »
rev 863
(5 files, 11kb)
* Rewrote uuid code in Atom feeds to instead use a tag URI (RFC 4151), in the form "tag:domain.com,2011-07-01:msg-7". It may not be the definitive code, but it's better than a UUID. Also removed the last compatibility code block. Really no need for that... (Feed.php, QueryString.php)
! Typo. (Help.french.php)
* In a world where war rages on every day, I believe it's important to say 'Hello' rather than 'Hi'. Who is Wedge to say you want to say Hi when you may not even know who you're talking to? (ManageSettings.language.php)
@ Note: totally unrelated... It appears that not many people tested the automatic quote splitter :P It fails badly when pressing Enter after a self-closed tag such as more, media etc. Also fails horribly when splitting URL tags. Okay, is anyone ever testing my crappy code? :P
(5 files, 11kb)
* Rewrote uuid code in Atom feeds to instead use a tag URI (RFC 4151), in the form "tag:domain.com,2011-07-01:msg-7". It may not be the definitive code, but it's better than a UUID. Also removed the last compatibility code block. Really no need for that... (Feed.php, QueryString.php)
! Typo. (Help.french.php)
* In a world where war rages on every day, I believe it's important to say 'Hello' rather than 'Hi'. Who is Wedge to say you want to say Hi when you may not even know who you're talking to? (ManageSettings.language.php)
@ Note: totally unrelated... It appears that not many people tested the automatic quote splitter :P It fails badly when pressing Enter after a self-closed tag such as more, media etc. Also fails horribly when splitting URL tags. Okay, is anyone ever testing my crappy code? :P
8458
Features / Re: New revs
« on July 13th, 2011, 07:20 PM »
rev 862
(6 files, 9kb)
* Minor details and fixes for the separator code. (Admin.php, GenericMenu.template.php)
- Why are we adding a class for something that's not even useful? (Admin.template.php, admin.css)
! Just because I spent months on that silly translation already, doesn't mean I don't have to keep improving it. (Help.french.php, Profile.french.php)
(6 files, 9kb)
* Minor details and fixes for the separator code. (Admin.php, GenericMenu.template.php)
- Why are we adding a class for something that's not even useful? (Admin.template.php, admin.css)
! Just because I spent months on that silly translation already, doesn't mean I don't have to keep improving it. (Help.french.php, Profile.french.php)
8459
Features / Re: New revs
« on July 13th, 2011, 06:14 PM »
rev 861
(8 files, 20kb)
+ Added separators to submenu items, slightly reordered a few entries, and fixed a logic issue in the menu cleanup code. (Admin.php, Subs-Menu.php, GenericMenu.template.php)
! Information box was too small. (ManagePaid.php)
* Added rounded corners to the admin homepage fieldsets, but it doesn't work well in Opera... Ah well, if it's an Opera bug, I'm not gonna prevent other browsers from showing these. (Admin.template.php)
* Refined Pretty URLs admin area. Made it clearer what the cache option is for (until now, it wasn't even obvious that disabling it would still keep PURLs enabled.) (Admin.template.php, Admin.language.php, admin.css)
* French translation fixes in the admin area. It had a tendency to use words like 'Réglages' a bit too much where 'Paramètres' made more sense. Also, the 'Forum' menu area is called 'layout' internally, so the French translation had 'Apparence'. Since Pete moved the Theme options to another menu area, it was time to reflect the change in the French version as well... (Admin.french.php)
(8 files, 20kb)
+ Added separators to submenu items, slightly reordered a few entries, and fixed a logic issue in the menu cleanup code. (Admin.php, Subs-Menu.php, GenericMenu.template.php)
! Information box was too small. (ManagePaid.php)
* Added rounded corners to the admin homepage fieldsets, but it doesn't work well in Opera... Ah well, if it's an Opera bug, I'm not gonna prevent other browsers from showing these. (Admin.template.php)
* Refined Pretty URLs admin area. Made it clearer what the cache option is for (until now, it wasn't even obvious that disabling it would still keep PURLs enabled.) (Admin.template.php, Admin.language.php, admin.css)
* French translation fixes in the admin area. It had a tendency to use words like 'Réglages' a bit too much where 'Paramètres' made more sense. Also, the 'Forum' menu area is called 'layout' internally, so the French translation had 'Apparence'. Since Pete moved the Theme options to another menu area, it was time to reflect the change in the French version as well... (Admin.french.php)
8460
Plugins / [Naming poll] Re: Packages
« on July 13th, 2011, 02:28 PM »
Let me guess, you're Colin and you like being surrounded by beautiful women :P
As for add-on, I wouldn't dare to criticize the word itself. It just doesn't sound right to me to start using a word that will eventually end up like 'package', i.e. not used at all in favor of 'mod' or 'plugin', but maybe that's just me.
At any rate, I launched this poll to gauge the public opinion on the matter. The numbers tell me to leave it be and not change anything (as everything is already an 'add-on' internally), but since half of our visitors disagree, I'll just... Leave the poll on until we reconsider the question (if we ever do.)
As for add-on, I wouldn't dare to criticize the word itself. It just doesn't sound right to me to start using a word that will eventually end up like 'package', i.e. not used at all in favor of 'mod' or 'plugin', but maybe that's just me.
At any rate, I launched this poll to gauge the public opinion on the matter. The numbers tell me to leave it be and not change anything (as everything is already an 'add-on' internally), but since half of our visitors disagree, I'll just... Leave the poll on until we reconsider the question (if we ever do.)