Pretty cool except for the part where I was really terrified and now my knees are all dizzy.

Willow ,'Never Leave Me'


Buffistas Building a Better Board  

Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.

To-do list


msbelle - Oct 18, 2004 2:23:20 pm PDT #8404 of 10000
I remember the crazy days. 500 posts an hour. Nubmer! Natgbsb

mark a post, jump to end, post, go to bookmarks and pick back with the marked post.

It's not a pretty solution, but as someone who did not understand message center for the first few months of PF, or was it TT?, I know it works.


Wolfram - Oct 18, 2004 2:28:02 pm PDT #8405 of 10000
Visilurking

Thanks msbelle, that sounds like a good idea. And I think I started using Message Center about 6 months (or later) after I started posting. Now I can't navigate the site without it.


tommyrot - Oct 19, 2004 8:14:10 am PDT #8406 of 10000
Sir, it's not an offence to let your cat eat your bacon. Okay? And we don't arrest cats, I'm very sorry.

When trying to get to message_center.php:

Parse error: parse error, unexpected T_LIST, expecting T_STRING in /home/httpd/vhosts/buffistas.org/httpdocs/classes/quote.php on line 87


§ ita § - Oct 19, 2004 11:46:21 am PDT #8407 of 10000
Well not canonically, no, but this is transformative fiction.

Thanks. It was a side effect of file-copying to generate the list of quotes. Gone now!

Jon, I have a for-now theoretical question:

If we were to automate the vote system, what functionality would we need? There already is polling code written, but I'm pretty sure that it's not complex enough to handle the votes we've been doing.

I'm thinking there are three units:

A ballot is made up of one or more questions, which has two or more possible answers.

Ballots can be created, edited, opened, deleted or closed. No editing after opening.

Questions can be created, edited, deleted, and answered. No creating, editing or deleting after the ballot is opened. No answering until the ballot is opened. No answering after the ballot is closed.

Answers can be created, edited, deleted and chosen. No creating, editing or deleting after the ballot is opened. No choosing until the ballot is opened. No choosing after the ballot is closed.

Questions must have at least one required answer, maybe more, and some of them may be written in.

A ballot may be informal (and show results before it has been closed) or formal, and results aren't available until closing.

I'm also thinking that once the ballot is closed, the specifics of who voted for what can be purged, but the totals should be kept. No one will be able to vote twice, or if we choose to make that an option, the second vote overwrites the first.

Does that cover the cases you've coded for so far?


Jon B. - Oct 19, 2004 12:04:50 pm PDT #8408 of 10000
A turkey in every toilet -- only in America!

I'm about to head home. I'll think on it, and get back to you.


DCJensen - Oct 19, 2004 2:32:59 pm PDT #8409 of 10000
All is well that ends in pizza.

ETA: told you I always get the wrong thread.


§ ita § - Oct 19, 2004 2:36:31 pm PDT #8410 of 10000
Well not canonically, no, but this is transformative fiction.

Wrong thread, DCJ.


§ ita § - Oct 19, 2004 6:07:55 pm PDT #8411 of 10000
Well not canonically, no, but this is transformative fiction.

Have we had write-ins for actual votes? That's be a pisser to automate. But if it's for something more informal, not such a big deal.


Jon B. - Oct 19, 2004 7:19:01 pm PDT #8412 of 10000
A turkey in every toilet -- only in America!

No, the first time a write-in was used was in last week's informal poll.


§ ita § - Oct 19, 2004 7:34:10 pm PDT #8413 of 10000
Well not canonically, no, but this is transformative fiction.

Okay, cool. I'm toying with the data model, and that doesn't fit properly right yet.