Stop it StopIt *StopIt* *STOP*IT*  **STOP** **IT**!!!!!!  ENOUGH WITH
THE MANUAL NAMES, ALREADY!

"Extended" is for extending and customizing LyX?!  WHAT THE H*** ARE
YOU PEOPLE THINKING?!  WHY WOULD WE HAVE A "Customization" IF THAT
WERE TRUE?!

<pant> <pant> <pant> <pant> <pant>

Okay... I'm trying to calm down... I'm trying to calm down...

On Thu, Oct 14, 1999 at 11:51:07AM -0700, [EMAIL PROTECTED] wrote:
>
> We beat the naming issue to death about a year ago. I think "Extended" was
> the compromise that caused the fewest vegetables to be thrown.

AGREED!  The names of the manuals are an ABBREVIATED SUMMARY OF
CONTENT, not the end-all be-all.  We went through this already, and
settled on what we felt was the best choice.

Since I began the whole doc-reorganization 4 years ago, and began the
DocTeam, period, and laid out the current design of the new documents,
what I hereby say is The Final Word:

The documents are organized based on *reading* *order*, and nothing
more.  You need to read Intro before you can read any of the others.
Some people need to read the Tutorial before moving on.  Some don't.
The User's Guide assumes you're read the first two, and covers the
most-frequently used subset of LyX features.  Extended is basically an
extension of the UG.  It contains less-frequently used features.
Using EF impiles that you have read the UG.  Customization and
Reference are last in the sequence.  

>From time-to-time, things may migrate from EF to UG or vice versa, as
we fine-tune the organization.  But my description of the purpose of
the manuals --- WHICH IS ALSO IN "Intro," if y'all had bothered to
read it --- is sacrosanct and must never be violated!

If y'all don't cut it out, I will go and rename the manuals to:

Stage 1
Stage 2
Stage 3
Stage 4
Stage 5
Stage 6

... thereby forcing you to read them, instead of just looking at the
titles.

(And if I start feeling *really* malicious, I'll give 'em names like
"Eqiv L1," "Eqiv L2," "Eqiv L3," so that you'll *really* have to read
them.  ;)

Your former Doc-Editor-In-Chief/Tyrrant,

-- 
John Weiss

Reply via email to