Here are a few things I'm looking into...
- Looks like passing an %e to strftime() will return " 1" in case you're on the first of a month, instead of "1". I have no idea why PHP is adding the leading space. It's okay in most cases, but in French the number comes first, so if you show the date (like this), you will get ( 1 avril) instead of (1 avril). (Well, actually it should say "(1er avril)" to be proper French, and that's actually in the Noisen codebase, but I never got around to find a *QUICK* way to do it that would also be usable by other languages, rather than just French....)
- Speaking of timeformat(), it's called every time a date is calculated on the page. Meaning it's called a lot on most pages...
I was thinking, wouldn't there be a way to simply cache *for the duration of the page load* (e.g. a static variable) as much data as we can...? Because redoing the calculations is a bit silly if you ask me. Heck, we could even store the last calculated date, determine whether it has the same characteristics, and refuse its time format...
- Generally speaking, timeformat() is a real mess to begin with. It has so much code... I'm pretty sure there are simpler ways to implement this.
- Pete, what about your changes to the admin area...? I've been postponing the moving of admin files to their own folders because you told me you had something on the backburner... (Not that it's urgent or anything, though.)
- Looks like passing an %e to strftime() will return " 1" in case you're on the first of a month, instead of "1". I have no idea why PHP is adding the leading space. It's okay in most cases, but in French the number comes first, so if you show the date (like this), you will get ( 1 avril) instead of (1 avril). (Well, actually it should say "(1er avril)" to be proper French, and that's actually in the Noisen codebase, but I never got around to find a *QUICK* way to do it that would also be usable by other languages, rather than just French....)
- Speaking of timeformat(), it's called every time a date is calculated on the page. Meaning it's called a lot on most pages...
I was thinking, wouldn't there be a way to simply cache *for the duration of the page load* (e.g. a static variable) as much data as we can...? Because redoing the calculations is a bit silly if you ask me. Heck, we could even store the last calculated date, determine whether it has the same characteristics, and refuse its time format...
- Generally speaking, timeformat() is a real mess to begin with. It has so much code... I'm pretty sure there are simpler ways to implement this.
- Pete, what about your changes to the admin area...? I've been postponing the moving of admin files to their own folders because you told me you had something on the backburner... (Not that it's urgent or anything, though.)




