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
7726
The Pub / Re: Copyrights
« on September 20th, 2011, 08:28 AM »
They still insist on copyright notices.
I don't see ourselves retaining the notice in all files -- I mean, some files are new like Subs-Cache.php and have a couple of SMF functions in them -- it doesn't guarantee to me that they should have a "based on" copyright line -- that would imply they created the file in the first place. Meh...
I'm so annoyed, I'm actually tempted to leave the headers as is (just because we can if they're a basic BSD license), and remove the credits for SMF in the credits page to show them who's in charge -- just retain the link to sm.org, the mention that it's based on SMF etc because I'm cool, but remove the list of credits. And if this bothers those of us in the team/friends who are ex-SMF devs, I don't mind crediting them in the Wedge credits section.
I don't see ourselves retaining the notice in all files -- I mean, some files are new like Subs-Cache.php and have a couple of SMF functions in them -- it doesn't guarantee to me that they should have a "based on" copyright line -- that would imply they created the file in the first place. Meh...
I'm so annoyed, I'm actually tempted to leave the headers as is (just because we can if they're a basic BSD license), and remove the credits for SMF in the credits page to show them who's in charge -- just retain the link to sm.org, the mention that it's based on SMF etc because I'm cool, but remove the list of credits. And if this bothers those of us in the team/friends who are ex-SMF devs, I don't mind crediting them in the Wedge credits section.
7727
Off-topic / Re: I am looking for a favour
« on September 20th, 2011, 08:16 AM »
Because Latin is in your culture. Too easy for Italians. Greek is what they use to fuck with your mind ;)
Romani ite domini! Or something.
Romani ite domini! Or something.
7728
Off-topic / Re: The Oatmeal
« on September 20th, 2011, 08:13 AM »
I thought netflix was like a paid YouTube?
7729
Features / Re: New revs
« on September 19th, 2011, 11:54 PM »
rev 1013
(18 files, 22kb)
* Category URLs now use "?category=", and also have their own pretty URL. (index.php, Boards.php, Load.php, PrettyUrls-Filters.php, QueryString.php, Recent.php, Search2.php, Subs-BoardIndex.php, Subs-Template.php, Unread.php, UnreadReplies.php, ModerationCenter.template.php)
! IE9 doesn't support -ms-border-radius, only the prefix-free version, and as a result it didn't show any rounded corners. So, fixed that. (Subs-Cache.php)
+ Added support for notifications in non-main menus. (Subs-Menu.php, GenericMenu.template.php)
! Fixed main menu layout breaking when menu was split into several lines, especially with notifications shown. (index.css)
* The Media menu item now uses menu notifications for its number of unseen items. (Subs.php)
* Code cleanup. (PrettyUrls-Filters.php)
@ Funny note: notifications in non-main menus work in IE6, 7 and 8... But not in IE9 or IE10! Ahah. Well, the layout is broken but it's still usable. Whatever.
@ Also, used 'category' instead of 'cat' because 'cat' is being reserved for blog categories, potentially. Well, it's a weak reason... Feel free to change it.
(18 files, 22kb)
* Category URLs now use "?category=", and also have their own pretty URL. (index.php, Boards.php, Load.php, PrettyUrls-Filters.php, QueryString.php, Recent.php, Search2.php, Subs-BoardIndex.php, Subs-Template.php, Unread.php, UnreadReplies.php, ModerationCenter.template.php)
! IE9 doesn't support -ms-border-radius, only the prefix-free version, and as a result it didn't show any rounded corners. So, fixed that. (Subs-Cache.php)
+ Added support for notifications in non-main menus. (Subs-Menu.php, GenericMenu.template.php)
! Fixed main menu layout breaking when menu was split into several lines, especially with notifications shown. (index.css)
* The Media menu item now uses menu notifications for its number of unseen items. (Subs.php)
* Code cleanup. (PrettyUrls-Filters.php)
@ Funny note: notifications in non-main menus work in IE6, 7 and 8... But not in IE9 or IE10! Ahah. Well, the layout is broken but it's still usable. Whatever.
@ Also, used 'category' instead of 'cat' because 'cat' is being reserved for blog categories, potentially. Well, it's a weak reason... Feel free to change it.
7730
Off-topic / Re: The Oatmeal
« on September 19th, 2011, 11:23 PM »
I was reading a similarly themed joke earlier today...
http://bradcolbow.com/archive/view/the_brads_-_how_netflix_is_getting_easier/
Dunno what 'Qwickster' is, though. I barely heard of Netflix at all... Not available in France AFAIK. Not that I care.
http://bradcolbow.com/archive/view/the_brads_-_how_netflix_is_getting_easier/
Dunno what 'Qwickster' is, though. I barely heard of Netflix at all... Not available in France AFAIK. Not that I care.
7731
Off-topic / Re: I am looking for a favour
« on September 19th, 2011, 08:09 PM »
The Romans invented Latin so that the Pythons could send them home :eheh:
7732
Features / Re: New revs - Public comments
« on September 19th, 2011, 05:30 PM »
I've decided that I'll use ?cat= for consistency, as you suggested.
Also, I won't make a PURL rule for it -- unless you definitely want to, but right now I'm thinking, the PURL rule is only for consistency, and it really doesn't matter that much -- ?cat is only going to be used in the linktree and a couple other links, and it's very short anyway... It's not like it hurts my eyes to see that.
Having problems with the padding BTW. I noticed that with a notification there, a menu entry will be 1 pixel taller, meaning that if the entire menu wraps (smaller window), second-line items are shown horizontally after the item that has the notification. Yikes.
So I turned them into inline-blocks and it works, but then I remembered that inline-blocks take whitespace into account, ah ah... Well, there are hacks to prevent that anyway.
Re: layers, well, do you think I should set $where to a different default depending on the target layer...? $target = context, $where = replace by default. $target != context, $where = add by default. It would allow us to remove the $where param from pretty much all loadBlock calls, but it's really not exactly 'obvious'.
Oh, and I think I have a couple of questions/concerns in the New Revs topic that you didn't comment on. If you don't mind.
Oh crap, I have so many things left to reply/comment, myself... :(
Also, I won't make a PURL rule for it -- unless you definitely want to, but right now I'm thinking, the PURL rule is only for consistency, and it really doesn't matter that much -- ?cat is only going to be used in the linktree and a couple other links, and it's very short anyway... It's not like it hurts my eyes to see that.
Having problems with the padding BTW. I noticed that with a notification there, a menu entry will be 1 pixel taller, meaning that if the entire menu wraps (smaller window), second-line items are shown horizontally after the item that has the notification. Yikes.
So I turned them into inline-blocks and it works, but then I remembered that inline-blocks take whitespace into account, ah ah... Well, there are hacks to prevent that anyway.
Re: layers, well, do you think I should set $where to a different default depending on the target layer...? $target = context, $where = replace by default. $target != context, $where = add by default. It would allow us to remove the $where param from pretty much all loadBlock calls, but it's really not exactly 'obvious'.
Oh, and I think I have a couple of questions/concerns in the New Revs topic that you didn't comment on. If you don't mind.
Oh crap, I have so many things left to reply/comment, myself... :(
7733
Off-topic / Re: PC hotline
« on September 19th, 2011, 02:25 PM »
@Pete> I don't have any viruses. I have the MS antivirus running in active mode, so it basically checks all of my files for viruses when I launch them (I enabled it because, well, it's the first time this doesn't slow down my PC at all...), but even if I disable it, it stays the same.
@Shitiz> I don't think it'd change anything to disable HT. I'd just see a usage peak of 25% (it's really the case, even with HT on...), and that's all. As for core affinity, it's reset once I quit the program so it's not going to be helpful when launching it... :(
As an ex-Win32 developer, I remember that it wasn't possible to choose a core to work with -- you just created your thread and Windows would pick the core for you. I don't know if this has changed, though.
PS: why did I say 12.66% in my previous post when it was 12.5%? :^^;:
@Shitiz> I don't think it'd change anything to disable HT. I'd just see a usage peak of 25% (it's really the case, even with HT on...), and that's all. As for core affinity, it's reset once I quit the program so it's not going to be helpful when launching it... :(
As an ex-Win32 developer, I remember that it wasn't possible to choose a core to work with -- you just created your thread and Windows would pick the core for you. I don't know if this has changed, though.
PS: why did I say 12.66% in my previous post when it was 12.5%? :^^;:
7734
Features / Re: New revs
« on September 19th, 2011, 11:18 AM »
rev 1012
(13 files, 16kb)
+ Added removeBlock() and removeLayer() shortcuts. removeLayer() protects all of the context's direct parents, so you can't remove the main layer through this. (Subs-Template.php)
! loadBlock shouldn't be replacing sidebar blocks, only adding to them. I still don't know if I should make it the default for non-context blocks, but it might confuse themers and modders... (Admin.php, Boards.php, Calendar.php, Display.php, Aeva-Gallery.php, MessageIndex.php, Profile.php, Unread.php, UnreadReplies.php)
! Don't set a block to use a layer that was removed, even if its hint is still there. (Subs-Template.php)
* Changed the way Wedge deals with non-existing target layers in loadBlock(). Mods will now have to specify a fallback layer (logically, 'context') if it's vital for their block to be shown, as 'context' is the only layer that's guaranteed to be shown. Unless some other mod played with unset($context['layers']['context']) like crazy, ah ah. Well, shoot them on sight. (Subs-Template.php)
* If the skeleton array doesn't have at least the context layer, launch a fatal error because an add-on is screwing up. (Subs-Template.php)
! I'm not exactly sure why I used to prevent layer functions (above and below) from being overloaded or overridden... This is fixed now. You can create your template_layer_above_after functions all you want. Well, I think. (Subs-Template.php)
! Menu removal code was still using the old layer system. (Subs-Menu.php)
* Random weak translation. (Help.french.php)
* Pete likes having space in his notifications. (index.css)
@ Need to write a multi-language error for the context layer error... Would you care to write it, Pete? I lack inspiration to do something that can be understood by normal users and not overly dramatic at the same time :P
(13 files, 16kb)
+ Added removeBlock() and removeLayer() shortcuts. removeLayer() protects all of the context's direct parents, so you can't remove the main layer through this. (Subs-Template.php)
! loadBlock shouldn't be replacing sidebar blocks, only adding to them. I still don't know if I should make it the default for non-context blocks, but it might confuse themers and modders... (Admin.php, Boards.php, Calendar.php, Display.php, Aeva-Gallery.php, MessageIndex.php, Profile.php, Unread.php, UnreadReplies.php)
! Don't set a block to use a layer that was removed, even if its hint is still there. (Subs-Template.php)
* Changed the way Wedge deals with non-existing target layers in loadBlock(). Mods will now have to specify a fallback layer (logically, 'context') if it's vital for their block to be shown, as 'context' is the only layer that's guaranteed to be shown. Unless some other mod played with unset($context['layers']['context']) like crazy, ah ah. Well, shoot them on sight. (Subs-Template.php)
* If the skeleton array doesn't have at least the context layer, launch a fatal error because an add-on is screwing up. (Subs-Template.php)
! I'm not exactly sure why I used to prevent layer functions (above and below) from being overloaded or overridden... This is fixed now. You can create your template_layer_above_after functions all you want. Well, I think. (Subs-Template.php)
! Menu removal code was still using the old layer system. (Subs-Menu.php)
* Random weak translation. (Help.french.php)
* Pete likes having space in his notifications. (index.css)
@ Need to write a multi-language error for the context layer error... Would you care to write it, Pete? I lack inspiration to do something that can be understood by normal users and not overly dramatic at the same time :P
7735
Features / Re: New revs - Public comments
« on September 19th, 2011, 11:05 AM »
Re: cat, I suppose nobody has an opinion on this... Not even us :( Argh.
Re: add-on manager, most likely at the end of the process?
Re: layers, yes indeed, I forgot to add hidden chromes to the list of exceptions. Which made me realize my process is really flawed in that respect... So I changed it and now, all blocks will be refused if their target layer doesn't exist. If a block is vital, then the modder should add a context fallback to it. I'm also adding code to prevent mods from removing said context layer...
Re: I did a lot of tweaking for the menu padding before, and, err... What can I say -- 6px is a bit much for me. 5px is fine however. It's a good compromise :lol:
Re: add-on manager, most likely at the end of the process?
Re: layers, yes indeed, I forgot to add hidden chromes to the list of exceptions. Which made me realize my process is really flawed in that respect... So I changed it and now, all blocks will be refused if their target layer doesn't exist. If a block is vital, then the modder should add a context fallback to it. I'm also adding code to prevent mods from removing said context layer...
Re: I did a lot of tweaking for the menu padding before, and, err... What can I say -- 6px is a bit much for me. 5px is fine however. It's a good compromise :lol:
7736
Off-topic / Re: PC hotline
« on September 19th, 2011, 10:57 AM »I haven't experienced that, but I don't have that many cores, or hyperthreading, and I turn my PC off at the end of the day.
How do you keep track of your logo history, do you save every single version of the logo after you made a change? Oh no you're not dealing with the logo :P (And I'm not done with it... :lol:)
How do you keep track of your Notepad2 windows? Oh now you're using Notepad++ for that :P
Well I have too many tools I like that don't really appreciate being turned off... So basically I'm a bit stuck, unless I change my tools to things that are less... volatile. Not going to happen for now.
I'm guessing it's related to having a lot of uptime
I regularly had 1-month uptimes for my XP, one time I think I even spent 2 or 3 months without rebooting... And that was even before I had my UPS :P
I should think that Win7 improves on uptime, instead of the opposite...
and something leaking memory causing Windows to thrash and have to swap.
For instance, Opera uses its file cache a lot. Never have a problem...
7737
Off-topic / Re: PC hotline
« on September 19th, 2011, 10:03 AM »
I have something of a problem that is having a definite impact on Wedge...
As a reminder: I have Windows 7 Ultimate on a brand new PC, Core i7 (4 cores + hyper-threading so that's 8), 8GB Ram, SSD HD, and so on.
When a core is running 100% CPU time, that's 100/8 = 12.66% = 13% in my task manager. So when a program is running a thread at 100%, there's a 13% for it in the task manager. Meaning there are still 7 cores available and under-used. All right?
Enter a recent issue. Well, about a few weeks ago I think...
When I boot my PC and use it, for the first day it'll be okay.
Then after some time, it'll develop a problem. On SOME actions, not ALL of them, the current program will suddenly jump to 13%, for a few seconds. It's not that important, but what matters to me is that it *effectively* slows down the entire computer, most notably the mouse cursor gets jerky, sometimes VERY jerky (i.e. it's only updated a few times every second.)
This happens systematically in these cases for instance:
- clicking the Start button (well, what replaced it...) -- not severe, though. But I see it's jerky for half a second.
- launching a program (whether it's stored on my SSD or regular HD...)
- launching my diff tool from within TortoiseSVN (which is pretty much needed for writing my changelog...) will take about 2 to 4 seconds with a jerky mouse, while when I first launch my PC, it takes much less than a second.
- sometimes -- just opening a *window* from inside a program (like the Settings window) will be jerky (like in my diff tool) or not (like in Opera). It's not related to Aero (I tried disabling it). The jerkiness appears during the time between my menu mouse click and the moment the window animation starts (i.e. the animation itself is very smooth and the mouse is only jerky before that).
All in all, with these, it feels a bit like my computer is slower than my old PC (XP + 2GB ram)...
Last time I rebooted, my problems were fixed but they started again the following day. I tried hibernating (= saving memory state and rebooting), and the problems were still there, so I'd like to suspect it's not a hardware problem, but...? What could it be! Everytime I search about this online, I find people saying to "upgrade video card drivers" (first thing I did of course...), or similar. Like, "upgrade your mouse drivers", lol. That one's funny.
I figured maybe someone around here already had a similar problem and they managed to fix it...? It's really making my changelogging life a hell right now!
As a reminder: I have Windows 7 Ultimate on a brand new PC, Core i7 (4 cores + hyper-threading so that's 8), 8GB Ram, SSD HD, and so on.
When a core is running 100% CPU time, that's 100/8 = 12.66% = 13% in my task manager. So when a program is running a thread at 100%, there's a 13% for it in the task manager. Meaning there are still 7 cores available and under-used. All right?
Enter a recent issue. Well, about a few weeks ago I think...
When I boot my PC and use it, for the first day it'll be okay.
Then after some time, it'll develop a problem. On SOME actions, not ALL of them, the current program will suddenly jump to 13%, for a few seconds. It's not that important, but what matters to me is that it *effectively* slows down the entire computer, most notably the mouse cursor gets jerky, sometimes VERY jerky (i.e. it's only updated a few times every second.)
This happens systematically in these cases for instance:
- clicking the Start button (well, what replaced it...) -- not severe, though. But I see it's jerky for half a second.
- launching a program (whether it's stored on my SSD or regular HD...)
- launching my diff tool from within TortoiseSVN (which is pretty much needed for writing my changelog...) will take about 2 to 4 seconds with a jerky mouse, while when I first launch my PC, it takes much less than a second.
- sometimes -- just opening a *window* from inside a program (like the Settings window) will be jerky (like in my diff tool) or not (like in Opera). It's not related to Aero (I tried disabling it). The jerkiness appears during the time between my menu mouse click and the moment the window animation starts (i.e. the animation itself is very smooth and the mouse is only jerky before that).
All in all, with these, it feels a bit like my computer is slower than my old PC (XP + 2GB ram)...
Last time I rebooted, my problems were fixed but they started again the following day. I tried hibernating (= saving memory state and rebooting), and the problems were still there, so I'd like to suspect it's not a hardware problem, but...? What could it be! Everytime I search about this online, I find people saying to "upgrade video card drivers" (first thing I did of course...), or similar. Like, "upgrade your mouse drivers", lol. That one's funny.
I figured maybe someone around here already had a similar problem and they managed to fix it...? It's really making my changelogging life a hell right now!
7738
Features / Re: New revs
« on September 18th, 2011, 11:55 PM »
rev 1010
(20 files, 15kb)
* Replaced WIRELESS_PROTOCOL with the 'wap2' string. I don't see us supporting any other wireless protocol in the future. (index.php, Boards.php, Display.php, Errors.php, FindMember.php, Load.php, Login.php, Login2.php, ManageBans.php, MessageIndex.php, PersonalMessage.php, Post.php, Profile.php, Security.php, Post.php, Profile.php, Security.php, Subs.php, Unread.php, UnreadReplies.php)
! Fixed menu layout in IE6 and IE7. Still glitchy, but more usable. (GenericMenu.template.php, index.ie6/ie7.css)
(20 files, 15kb)
* Replaced WIRELESS_PROTOCOL with the 'wap2' string. I don't see us supporting any other wireless protocol in the future. (index.php, Boards.php, Display.php, Errors.php, FindMember.php, Load.php, Login.php, Login2.php, ManageBans.php, MessageIndex.php, PersonalMessage.php, Post.php, Profile.php, Security.php, Post.php, Profile.php, Security.php, Subs.php, Unread.php, UnreadReplies.php)
! Fixed menu layout in IE6 and IE7. Still glitchy, but more usable. (GenericMenu.template.php, index.ie6/ie7.css)
7739
Features / Re: New revs
« on September 18th, 2011, 11:13 PM »
rev 1009
(11 files, 11kb)
+ Added the 'c' query string variable to action=boards, allowing to specify a single category that should be shown in the board list (à la Noisen). Considering changing it to '?cat=' later, for consistency, although it'll require updating pretty URLs as well. (Boards.php, Load.php, MessageIndex.php, Subs-BoardIndex.php, Recent.php, Search2.php, Unread.php, UnreadReplies.php, ModerationCenter.template.php, Xml.template.php)
* Category collapse action should redirect to the board list instead of reloading it silently from the collapse action URL. (Collapse.php)
(11 files, 11kb)
+ Added the 'c' query string variable to action=boards, allowing to specify a single category that should be shown in the board list (à la Noisen). Considering changing it to '?cat=' later, for consistency, although it'll require updating pretty URLs as well. (Boards.php, Load.php, MessageIndex.php, Subs-BoardIndex.php, Recent.php, Search2.php, Unread.php, UnreadReplies.php, ModerationCenter.template.php, Xml.template.php)
* Category collapse action should redirect to the board list instead of reloading it silently from the collapse action URL. (Collapse.php)
7740
Features / Re: New revs - Public comments
« on September 18th, 2011, 10:36 PM »
Adding cat as a top level var means adding a pretty URL rule for it. I'm not fond of the idea... But one pro is that it allows us to link to the URL even if boardindex is the default. Hmm.