LOL. Good points.

At 9:43 PM -0700 on 12/11/99, Rob Cozens wrote:


>"Since I built the engine, I'll design the drive train, suspension, and
>wheels", said Anthony.  And the group said, "Go for it, Anthony!"

I think Uli may be building the wheels (XBF) <g>.

>"OK", said Alain.  "Lets all meet here in three months to assemble
>FreeRx...and don't forget: each of us must write one or more chapters for
>the owners manual."

Yes, that's the problem: The 'let's all meet in three months'. We must stay
in touch, and agree on common interfaces.

For the UI, we've done this: right now, it's to be designed in pictures.
For programming, we'll have to do it sometime. XBF has designed the
low-level file system. Interpreter will define the entire scripting system.

If we build the modular, it won't matter that different people wrote them.
Properly written modular code is plug-and-play (the Mac way, not the
Windoze way).


>Anthony thought, "We don't want to be constrained by the RX7's 115kg
>maximum passenger size; so I am going to build 4WD, high ground clearence,
>and all terain wheels."  And Anthony did an excellent job.

Uli had better be building all terain wheels :)

>
>Adrian thought,  "The essence of the RX7 is its sleek, low styling; so I'm
>going to make the FreeRx body sleeker and lower and in translucent bondi &
>tangerine."  And Adrian did an excellent job.

We'd have to call it the iMazda...

>Our intreped fivesome meet three months later to assemble their creation.
>Write your own ending ...

Hmmm... A lot of duct take should fix the situation <veg>.

>
>                                  ###
>
>For a real world example of FreeRx, pick up the Bourn Shell manual that
>came with Berkeley Unix in the mid 1980s.  One only needs to thumb through
>three or four pages to realize each command in this UI was written totally
>without regard to the rest of the commands.  The commands were presented in
>different formats and writing styles.  Much worse, a modifyer for one
>command (eg: "/A") would mean one thing for one command and something else
>for another command.  Commands would often use the same modifier for
>different purposes or different modifiers for the same purpose.

We definitely need to agree on documentation styles and interfaces styles.

Reply via email to