To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=3395





------- Additional comments from [EMAIL PROTECTED] Sun Oct 28 03:47:36 +0000 
2007 -------
I'm very sad to see that this feature is not receiving the attention that it
deserves.

There is a HUGE falacy of composition in the threads/arguments above.  The
argument runs something like this -- because styles are styles, therefore all
understanding of the code that frames the layout and changes the format is 
useless.

Styles are styles.  They are a great convenience, but they have NOTHING
WHATSOEVER to do with the justification of Reveal Codes as a valuable feature. 
Neither one can act as a substitute for, or reason for the extermination of, the
other.  They are unrelated featers.  (The efficiency and long-lasting impacts of
the Madison Avenue brainwashing job that MS underwrote for competition purposes,
to trick people into believing that because theiz have "da Styles" dherefores
theiz dussunt need "da Codes," when the two features are totally unrelated,
still amazes me.)

A coder writing php and html gets to see his code (doh!).  Why does he need to
see his code -- he is writing for one of the most forgiving of display-delivery
devices, the monitor.  An author using Writer is preparing to send a high
precision document to a high precision printer, which is by comparison several
orders of magnitude less forgiving than a monitor.

Imagine an author using a TeX editor (TeX uses styles!) but his TeX editor
refuses to allow him to see the codes which control the layout of his or her
document.  Two authors, one using MS Word and the other using a TeX variant, are
sending their documents to similar printers, and both should have equal access
to the layout structure for their documents.  One cannot proofread a precise
document and rely on "styles" and a WYTYSINWYG monitor.  Having sexy styles, or
not having sexy styles, will not change that.  **Nor will Reveal Codes -- until
the inevitalbe problems show up.  When there are problems with a PRECISION
document (not a Post-It note) at the printing phase, Reveal Codes is the only
feature that will help cure the problem.  That's part of the learning curve, and
that when the author realizes that having access to Reveal Codes helps him or
her keep the problems out of the code in the first place, so my sentense at **
above was an intentional lie.  Reveal Codes flattens the learning curve and that
increases the precision and control.

IMHO, Writer should be not be marketed as, or known as, a "Post-It Note"
scribbler like MS Word. (And that is just exactly what Word is, with its 10,000
styles and its totally blindfolded authors.)  Marketing staff for OpenOffice
should "shape" the ooWriter produce so that it develops a reputation as a
**precision document** program -- a program that offers the author precise qand
full control over placement of all format changes and layout changes.  Thus,
when an author needs more control than offered by a "Styles-and-Blindfolds"
product like MS Word, but doesn't want the learning curve and hassles of TeX,
then in the marketplace, then the first product that springs into their minds
should be ooWriter.

"ooWriter ... the powers of TeX, without the hassles ..."  (Of course, everyone
realizes that power, without control, is just plain dangerous, wasteful and 
stupid.)

That will require that programmers understand that Styles and Reveal Codes are
completely unrelated features.  (If they are related, they are only in the sense
that each feature augments the powers of the other feature.)  And yes, TeX uses
styles.  But, just because TeX has styles, it's programmers understood MS-BS was
not sufficient reason to then hide the code.

OpenOffice Writer ... the powers of TeX without the hassles ...


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to