Daniel Peter Lepage on Mon, 26 Jul 2004 13:49:31 -0500 (CDT)


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [spoon-discuss] Renumbering CFIs


Damn webmail forms... can't figure out a stupid reply-to header...

This message was aimed at s-d and went to Zarpint instead. Here it is in the right direction, now:

-----Original Message-----

> Date: Mon Jul 26 14:00:23 EDT 2004
> From: athena@xxxxxxxxxxxxxxx
> Subject: Re: Re: [spoon-discuss] Re: [Spoon-business] Renumbering CFIs
> To: spoon-discuss@xxxxxxxxx
>
> To do special things when respect props pass, we'd need to put the
> Roster in a database. Then the props could just tell the database to
> increment a certain field by 1, or change one text field to another.

To make a 'voting results' printout that includes 'Rob gains 1 respect' wouldn't require a Roster database. Likewise, such a printout could adjust the "points gained" at the end of the voting results automatically to account for the fact that Respect props don't earn their authors points, etc.

Not that having a Roster db would be hard - until you took it over on the wiki, that's how the Roster was stored, in a MySQL database on Dave's server.

If you want automated Roster updating, we'll need a standard language for changing dimensions, something like
<action type="dimension">
Rob::Respect::+1
</action>

Of course, then we'd have to move the Roster stuff from the Wiki back to the database, and either I'd have to update it all myself, or I'd have to write a bunch of nifty access scripts to let other people log in and edit it, and I don't really have time to do either...

> We could make changes in the Ruleset that way if the Ruleset were a
> database, also.

The Ruleset still is in a database. If a proposal contained
<rule chutzpah=12>
<title> No Win for U! </title>
<keywords> Names, Winning </keywords>
Players whose names contain the letter 'U' may not win.
</rule>
I could parse it fairly easily and automate the rule-changing procedure.

Of course, most of our props are much more complex than this, things like, "If pXXXX/X passed, and pYYYY/Y failed or was shelved, but the scoring gremlin still exists, do A. Otherwise, create rule B, unless there's no such thing as a Flying Spleen of Apparent Dyslexia, in which case alter rule C, if it exists, and create rule D otherwise."

> Am I right in thinking that the Wiki can't handle PHP and MySQL? Is
> there some way to access the database with Python?

The Wiki can handle anything that Python can, and Python can talk to MySQL easily. Not so easily right now, though, because the wiki's on nomic.net and the database is on bnomic.org.

I think I've got a new installation of MoinMoin working at bnomic.org/Bwiki, but I didn't copy over everything yet so it's not yet a viable replacement for the current wiki.

Once I've got that working, I can start writing interface scripts that work through the wiki (i.e., using its login stuff, etc.)

-- 
Wonko

_______________________________________________
spoon-discuss mailing list
spoon-discuss@xxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/spoon-discuss