Thursday, December 15, 2005

Proposal: Blinking Cursors and Other Delights

S-Killed.—Chronos

Adminned at 16 Dec 2005 05:52:09 UTC

Modify 2.3.1 Definitions in the list after “The following list of definitions applies only to text on the Threads page, excluding headings”.

*A Thread is a collection of Moves, with a possible Intro. Threads may be created by direct Proposal or as dictated by a Rule or Rules. Threads may begin with either a Prompt or a Result. Threads may not contain any text that is not a Prompt, a Command, or a Result. (Results may begin a Thread for the purpose of providing introductory text. They may be thought of as the result of starting a game.)

to:

*A Thread is a collection of Moves, with a possible Intro. Threads may be created by direct Proposal or as dictated by a Rule or Rules. Threads may begin with either a Prompt or a Result. Threads may not contain any text that is not an Element (a Prompt, a Command, or a Result). (Results may begin a Thread for the purpose of providing introductory text. They may be thought of as the result of starting a game.) The last Element in a Thread is considered to be followed by nothing, even if there are other Threads beyond it. The last Element in a Thread is known as the End of a Thread.
*An Element is an object which takes the form of a Prompt, a Command, or a Result.

This is mainly to make it so I don’t have to say Prompt, Command, and Result a million times. It also helps a little with defining the end of a Thread.

Create a new rule subsection of ‘‘Narrative’‘


====Cursors====
After every Prompt which is at the End of a Thread, a blinking text insertion Cursor must be placed due to the coolness of how it looks. A Cursor may not be created anywhere else. A Cursor may exist anywhere the following Rules allow for it. Multiple cursors are allowed to exist within a single Thread. Cursors are not allowed to exist outside of Threads.

A Cursor must be located between two characters of any sort and must be preceeded by an Element. If a Cursor is directly preceeded by or followed by another Cursor, then they must be merged into a single Cursor. When adding text, it must be added directly at a Cursor. Deletions at a Cursor function as a backspace only. Text before (but not after!) a Cursor can be deleted as part of an action containing the Cursor. A Cursor must be deleted when any action involving it occurs unless the Cursor involved in the action is specifically spared by another section of this or any other Rule.

If any number of Elements preceeding a Cursor are deleted, the Cursor is located directly before the deleted section. If there are no Elements or the Element the Cursor follows is not a Prompt or Command, the Cursor shall be deleted.

If anything is added to the Element preceeding a Cursor, the Cursor is moved depending on the preceeding Element. If it is a Prompt, the addition is made before the Cursor location. Otherwise, the addition is made after the Cursor location. The Cursor is then removed unless it satisfies one and only one of the following conditions:
*The preceeding Element is a Prompt or Command.

A single image or textual representation shall be used to represent the Cursor. The image or textual representation must be updated with the color scheme so that a high-contrast blinking Cursor is maintained. If the Protagonist who changes the color scheme does not update the Cursor appropriately, e shall have to incorporate the word “blink” into five unique comments / posts, i.e. any number of “blink"s per post counts as a single “blink”. Alternate forms of “blink” such as “to blink” are acceptable. A similar punishment applies to those who do not correctly use the Cursors within Threads. They must incorporate one of the words “left”, “right”, “up”, or “down” in Dice5 comments / posts.

This is a baseline image I rather like. It’s made for the Wiki rather than this page, but oh well.

In section 2.3.2 “Mechanics” of “Narrative”, change

*one Command and the following Result.

to:

*one Command and the following Result, OR
*a single word at any Cursor.

under things the Protagonist add each day.

In section 2.3.2 “Mechanics” of “Narrative”, change

*the last complete Move.

to:

*the last complete Move, OR
*Any number of characters up to and including the previous 3 Elements from before a Cursor, OR
*Any single Cursor.

under things the Protagonist may delete each week.

The thing I find most interesting is that everything must still conform to everything set forth in the Mechanics. I’m using bolding here to indicate new or changed text. Use of italics within the new text is to be considered as bolding.

Comments

Salamander:

15-12-2005 10:31:23 UTC

First point: looks like this was long enough to dissuade the rest of the nomic from reading it. lol.

Second point: Saurik’s new post walkes us through 2 example applications of his laws in flavor text form. This makes it Seriously easier to understand. I’m going to vote for, but will vote against if you don’t give me a couple examples :)

Third point: It would be nice if you provided a penalty for Protagonists that do thigns like

Elias IX:

15-12-2005 12:52:39 UTC

against coolness would have to be defined.

Salamander:

15-12-2005 13:46:33 UTC

Elias IX: LMOL

Cayvie:

15-12-2005 15:35:41 UTC

against

Hix:

15-12-2005 17:47:05 UTC

against

Seventy-Fifth Trombone:

15-12-2005 20:58:44 UTC

against

I understand the desire to abstract objects and actions to this degree—I suppress that desire constantly (with varying amounts of success).  This is much too far past that line.

Also, frivolity is good, but the characters:significance ratio of this Proposal is way, way too large.

Salamander, your vote on this Proposal is currently AGAINST, because that icon occurred last in your post.

AgentHH:

15-12-2005 21:04:56 UTC

I agree that it’s way too much verbiage for such little functionality. Self-kill against

I do however like some of the mechanics implemented by this, and I will be drafting a new Proposal based on them.

Excalabur:

16-12-2005 04:10:23 UTC

Excellent.