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.
8281
Off-topic / Re: Dial Up BBS
« on August 2nd, 2011, 07:06 AM »
Rory is older post DW5.
And Jack Harkness post TW2.
And Jack Harkness post TW2.
8282
Features / Re: New revs - Public comments
« on August 2nd, 2011, 07:04 AM »
Oh.
But this means there will be bugs in plenty other areas to come.
Are you sure that's necessary?
But this means there will be bugs in plenty other areas to come.
Are you sure that's necessary?
8283
Features / Re: New revs - Public comments
« on August 2nd, 2011, 01:13 AM »
That's why I said the status field didn't have to just have two values -- unapproved and approved.
0: unapproved, unmoderated
1: approved
2: deleted (recycled)
3: postponed for later?
Hmm, I've noticed a strange behavior on the demo site that isn't on my local site.
When doing floating point manipulations in the wecss class, any floating point number is stored internally as "1,23" instead of "1.23". It always retains that comma.
I have to go, but maybe someone can tell me what's happening? I suspect it's somewhere in the setlocale stuff, but I don't know how to fix for now. The problem is that I'm relying on the periods as they're compatible with the CSS syntax, unlike the commas.
0: unapproved, unmoderated
1: approved
2: deleted (recycled)
3: postponed for later?
Posted: August 2nd, 2011, 12:33 AM
Hmm, I've noticed a strange behavior on the demo site that isn't on my local site.
When doing floating point manipulations in the wecss class, any floating point number is stored internally as "1,23" instead of "1.23". It always retains that comma.
I have to go, but maybe someone can tell me what's happening? I suspect it's somewhere in the setlocale stuff, but I don't know how to fix for now. The problem is that I'm relying on the periods as they're compatible with the CSS syntax, unlike the commas.
8284
The Pub / [Archive] Re: Logo Madness
« on August 2nd, 2011, 01:02 AM »
You mean its position?
Something like this?
Posted: August 2nd, 2011, 12:51 AM
Something like this?
8285
Features / Re: New revs - Public comments
« on August 2nd, 2011, 12:00 AM »
Pseudo-deleted doesn't have to have the same internal status id as not-yet-approved.
I don't really see how it could hurt performance as long as we have a serious index on the status field...?
I don't really see how it could hurt performance as long as we have a serious index on the status field...?
8286
Features / Re: New revs - Public comments
« on August 1st, 2011, 11:42 PM »
We obviously rename that 'delete'.
8287
Features / Re: New revs - Public comments
« on August 1st, 2011, 11:11 PM »*facepalm* Yes, good plan.Quote The only point is to have only two strings for the day list, as opposed to a dozen
That wasn't the plan from what I remember;
we didn't really get into any conclusion as to what we wanted to do, just getting rid of the existing bin setup for something cleaner.
8288
The Pub / [Archive] Re: Logo Madness
« on August 1st, 2011, 11:03 PM »
Nah, I made many tries you know :)
The w being separate from the edge has to be very subtle, in order to keep some balance between the text and the logo behind it. The more detail you add, the less you'll see the logo as 'natural' in the end. I always had this problem with the old logo: it had *one* detail too many (the horizontal line on the 'we'). And it wasn't graphic enough. I started making tests with the wedge logo next to the text, but it was a bit dull. Fine for corporate use, but I'm not that dull myself.
I've made yet another attempt. It's directly in use at the top of this page. Tell me what you think, guys... (I know, the difference is barely noticeable.)
As for the Segoe UI Light logo: well, I wouldn't say it's 70s, to me it's 2010s, it's the kind of font that tends to have a growing success these days. It looks nice, clean and stylish. Microsoft had some flair when they decided to use it on their marketing material for Windows 8 really.
My problems with that logo: (1) you're never sure whether the logo behind is a ship, a paper plane or a wedge, (2) monochromatic. Too much brown. Lacks a complementary color. (3) At small sizes, the 'wedge' text is barely readable.
Right now, I think the current test logo tends to be a solution to all of these.
The w being separate from the edge has to be very subtle, in order to keep some balance between the text and the logo behind it. The more detail you add, the less you'll see the logo as 'natural' in the end. I always had this problem with the old logo: it had *one* detail too many (the horizontal line on the 'we'). And it wasn't graphic enough. I started making tests with the wedge logo next to the text, but it was a bit dull. Fine for corporate use, but I'm not that dull myself.
I've made yet another attempt. It's directly in use at the top of this page. Tell me what you think, guys... (I know, the difference is barely noticeable.)
As for the Segoe UI Light logo: well, I wouldn't say it's 70s, to me it's 2010s, it's the kind of font that tends to have a growing success these days. It looks nice, clean and stylish. Microsoft had some flair when they decided to use it on their marketing material for Windows 8 really.
My problems with that logo: (1) you're never sure whether the logo behind is a ship, a paper plane or a wedge, (2) monochromatic. Too much brown. Lacks a complementary color. (3) At small sizes, the 'wedge' text is barely readable.
Right now, I think the current test logo tends to be a solution to all of these.
8289
Features / Re: New revs - Public comments
« on August 1st, 2011, 10:34 PM »I was in two minds about that. I basically stole the code from my own mod there for that part, didn't see too much point reinventing the wheel.
Re: recycle bin, I thought we'd agreed (although it was long ago...) that we ccould simply do it like here: a Hide (Unapprove) button that would set posts to status!=1 or something... Then if you hide a post, you get the ability to either restore it (Publish), or restore it and set its posting date to the current time (Publish to date). Which is practical on a blog when you want to publish in intervals. (Only works if nothing was posted after the message.)
8290
Features / Re: New revs
« on August 1st, 2011, 10:13 PM »
rev 903
(9 files, 11kb)
* Don't show a submenu on mail settings (admin area) if the mail queue is disabled. (Admin.php)
! Fixed accidental revert from the last timezone commit. (ManageSettings.php)
* Changed 'Mail' label to 'Email Settings' in the Server & Maintenance admin menu. (Admin.language.php)
* I thought it would be amusing if the redirection topic strings actually used number_context()... (index.language.php, MoveTopic.template.php)
* Very minor fixes/changes. (ManageMedia.template.php, sections.css)
* French translation. (index.french.php)
(9 files, 11kb)
* Don't show a submenu on mail settings (admin area) if the mail queue is disabled. (Admin.php)
! Fixed accidental revert from the last timezone commit. (ManageSettings.php)
* Changed 'Mail' label to 'Email Settings' in the Server & Maintenance admin menu. (Admin.language.php)
* I thought it would be amusing if the redirection topic strings actually used number_context()... (index.language.php, MoveTopic.template.php)
* Very minor fixes/changes. (ManageMedia.template.php, sections.css)
* French translation. (index.french.php)
8291
Off-topic / Re: Dial Up BBS
« on August 1st, 2011, 08:28 PM »
I'd be curious to know the average age of future Wedge users. I'd bet it'll be higher than Smf's Eheh. Even Dragooon can't change that!
8292
Features / Re: New revs - Public comments
« on August 1st, 2011, 08:13 PM »
Arent we gonna remove the recycle bin at one point anyway?
8293
Features / Re: New revs - Public comments
« on August 1st, 2011, 05:36 PM »
We could store an id_previous_board for each topic.
8294
Development blog / Re: Now with 97% more visuals!
« on August 1st, 2011, 04:54 PM »Actually, none of your stuff seems to have contrast in the areas that typical colour blindness would have a problem with.
8295
Features / Re: New revs - Public comments
« on August 1st, 2011, 04:54 PM »No... the original code had an in_array to select only the regions of interest, and IIRC there was an isset for something else at the end before actually adding it to the loop but off hand I can't remember what.
Right now am dealing with the fact that the imperative scheduled system is completely broken (and in fact I'm dubious about how it ever worked when I tested it originally because it shouldn't have done),
will commit that when I've fixed it and finished the feature that actually uses it.