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
8267
The Pub / [Archive] Re: Logo Madness
« on August 3rd, 2011, 12:18 AM »
Let me think... Something like this maybe.
Hmm... Well, 90% of all corporate logos are made of two things: a small graphical logo, and the company name in a distinctive font. I don't know about the font, I just 'like' Helvetica-style these days (hence why Arial 14pt is everywhere in Wedge itself). Here's another try with PT Sans Bold.
Hmm... Well, 90% of all corporate logos are made of two things: a small graphical logo, and the company name in a distinctive font. I don't know about the font, I just 'like' Helvetica-style these days (hence why Arial 14pt is everywhere in Wedge itself). Here's another try with PT Sans Bold.
8268
The Pub / [Archive] Re: Logo Madness
« on August 2nd, 2011, 07:32 PM »
Don't focus on the wedge, focus on the text!
8269
Off-topic / Re: Kudos for Nao & Arantor
« on August 2nd, 2011, 07:09 PM »
Thanks ;)
We'll have alpha and beta sessions for Wedge, the alpha will hopefully start in September.
We'll have alpha and beta sessions for Wedge, the alpha will hopefully start in September.
8270
The Pub / [Archive] Re: Logo Madness
« on August 2nd, 2011, 07:05 PM »
How about this? And that.
8271
Features / Re: New revs - Public comments
« on August 2nd, 2011, 01:12 PM »At the time I thought it would make it easier to internationalise through using LC_ALL since I couldn't see a good reason not
to but you've found an excellent reason not to.
Still, we're in a situation that reminds us that, sometimes, the amount of servers and configurations makes it hard to make software work everywhere without tweaking. Somehow it reminds me of my 'terrific' days of debugging Direct3D code to make it work on both ATI and NVIDIA cards... Ahhhh.
Considering also that the number format is not managed through the locale anyway, the only reason remaining that actually matters is the possible incompatibility - but even then... it hasn't bothered SMF that I could find, so run with LC_TIME.
Posted: August 2nd, 2011, 01:06 PM
Okay, with rev 904 I added the template hooks. They probably won't work out of the box though, but I figured if I didn't add them, we'd forget about them eventually. We can always remove them later. The point here is: how do we make it as easy as possible for modders and themers to add these template hooks? Should we have 'proper' functions in a separate file, should we load a file actually...?
Here's how I'm considering the approach:
- mod adds an add_hook('some_source_hook', my_function, my_file)
- in my_file, mod adds a template_something_subtemplate_before function that executes before template_something_subtemplate
- after executing some_source_hook, Wedge proceeds to load Something.template.php and execute the subtemplate, and then call the _before hook that's precisely in the my_file file.
Does it make sense, or should it be made easier?
8272
Features / Re: New revs
« on August 2nd, 2011, 01:02 PM »
rev 904
(6 files +2, 18kb)
* Changed wedge_type field name to board_type. At this point I'm unsure we'll keep the 'wedge' terminology for boards and blogs, so there's no point in adding more confusion. (install.sql, Load.php, RemoveTopic.php)
+ Re: my post 257238 at the forum, implementing 'before', 'after' and 'override' generic hooks for all template functions. The total overhead is no more than a millisecond per page. Needs more work. (Load.php)
! Resetting global locale scope to LC_TIME instead of LC_ALL, to avoid issues in the CSS parser. Although we could have fixed that directly in the parser, we're never far away from meeting more issues, so for now we'd rather remain compatible with the SMF method. (Load.php)
+ Added index.php dummy files for a couple of folders that missed them. (images/fields, images/theme)
! Typonazi. (Install.french.php)
(6 files +2, 18kb)
* Changed wedge_type field name to board_type. At this point I'm unsure we'll keep the 'wedge' terminology for boards and blogs, so there's no point in adding more confusion. (install.sql, Load.php, RemoveTopic.php)
+ Re: my post 257238 at the forum, implementing 'before', 'after' and 'override' generic hooks for all template functions. The total overhead is no more than a millisecond per page. Needs more work. (Load.php)
! Resetting global locale scope to LC_TIME instead of LC_ALL, to avoid issues in the CSS parser. Although we could have fixed that directly in the parser, we're never far away from meeting more issues, so for now we'd rather remain compatible with the SMF method. (Load.php)
+ Added index.php dummy files for a couple of folders that missed them. (images/fields, images/theme)
! Typonazi. (Install.french.php)
8273
Features / Re: New revs - Public comments
« on August 2nd, 2011, 10:33 AM »Yes: some versions of the locales database don't set everything properly when using just LC_TIME, going off the comments in the setLocale manual page. http://www.php.net/manual/en/function.setlocale.php#77795 mentions it for example.
Windows aside, which is buggy anyway and I wouldn't expect serious users to be running PHP on Windows as a consequence, setLocale is threaded, meaning that there are no outbound consequences for doing the switch as suggested; once it enters the CSS parser, it's going to remain there until it's done.
I'm happy to try it as suggested,
(I'm really pro-LC_TIME here. I don't see why we should deviate from the SMF implementation, apart from the fact that we're only executing setlocale once per page call now.)
especially since now I read up on it again, I don't see how we can make use of LC_COLLATE or LC_CTYPE because that has implications for users migrating from other systems (since those affect how strtolower is done and how string comparisons may be made, though equivalence checks shouldn't be affected) though some things like LC_MONETARY might be useful in places.
8274
The Pub / [Archive] Re: Logo Madness
« on August 2nd, 2011, 09:09 AM »
That was the idea.
Unfortunately, as I said, this (beautiful) logo has three drawbacks, which I pointed out on the previous page. If you have any solutions...
Unfortunately, as I said, this (beautiful) logo has three drawbacks, which I pointed out on the previous page. If you have any solutions...
8275
Off-topic / Re: Dial Up BBS
« on August 2nd, 2011, 09:08 AM »On the other end of the scales, I'm 27 and Nao's a few years older than me...
8276
Other software / Re: "Paid for" shit.
« on August 2nd, 2011, 08:49 AM »
Yes.
But they're easy to guess.
Heck, they would have been my first guesses. After all, they're the ones who fucked with me over and over last year... And one of the two was 'sorry' about the post-ban, but could actually lift it and never did -- heck, he actually did worse over time.
No wonder he would abuse his rights to censor the only place where I can speak freely at simplemachines.org........
Name your thoughts now :lol:
But they're easy to guess.
Heck, they would have been my first guesses. After all, they're the ones who fucked with me over and over last year... And one of the two was 'sorry' about the post-ban, but could actually lift it and never did -- heck, he actually did worse over time.
No wonder he would abuse his rights to censor the only place where I can speak freely at simplemachines.org........
Name your thoughts now :lol:
8277
Features / Re: New revs - Public comments
« on August 2nd, 2011, 08:45 AM »It's almost certainly the setLocale call that's been made which uses LC_ALL from what I remember, which means numbers will be formatted to the locale specified if possible.
Not sure how to fix that other than temporarily resetting the locale to the English default when entering the parser and resetting it back to the normal language on exit.
This changed was applied in rev 750. You added a centralized setlocale(LC_ALL) call (which includes LC_NUMERIC for the decimal separator), and removed the setlocale(LC_TIME) calls in Load.php and Subs-Media.php. So this basically breaks the 'normal' SMF behavior for localization.
I'm the first surprised because this didn't happen to me at all on the demo site. It only started happening on my second demo site, which I installed yesterday to test the importer. It's on the same server...!
So, I guess there are two possible solutions:
- setlocale(LC_TIME) in Load.php, instead of setlocale(LC_ALL). Or setlocale(LC_ALL & ~LC_NUMERIC) if that's even possible (I'm not sure LC_* is a bitwise thing.) I'd rather we use this one because at least it's going to be prooftested through SMF.
- $ex_locale = setlocale(LC_ALL, 0); setlocale(LC_ALL, 'en_US.utf8'); do our stuff; setlocale(LC_ALL, $ex_locale). That's what you suggest but I'm not sure it'll work flawlessly. It may break on some server types, etc... And it doesn't ensure it'll work in non-Subs-Cache pages.
8278
Other software / Re: "Paid for" shit.
« on August 2nd, 2011, 07:46 AM »
So. Anyone interested in knowing the names of the cowards who censored the AeMe page and won't even admit it?
8279
Features / Re: New revs - Public comments
« on August 2nd, 2011, 07:25 AM »
There are dozens of topics like this one in private :P
I find myself a bit antisocial these days, especially on this topic. Meh. (Sorry Pete. bit ashamed.)
I find myself a bit antisocial these days, especially on this topic. Meh. (Sorry Pete. bit ashamed.)