On 21-5-2014 10:28, japples wrote:
Martin, to put it more simply, you prefer to post the styles /
definitions of a document as a cheat sheet rather than see the code in
real time and where located in your document (reveal codes). Very
inefficient to take eyes off of the document to search for "style
definitions" then go back to document to "fix" the problem and
possibly create a clash with imported document or another style
definition.
To be honest, I don't prefer anything, because I believe I master
Styles. All I tried to address is that we should not be blind for
requirements of others and see if we can come up with a solution to
assist users who have problems with Styles.
A more efficient way would be to have the codes seen where they are in
document and make corrections on the spot. Also, using this type of
reveal code window eliminates the possibility of creating a
conflicting style definition.
This whole thing reminds me of when I started writing web pages. In
short order I began to see how limiting wysiwyg (ie, styles) was yet I
was unable to move to a more efficient method until that mindset
changed. If the mind is closed, nothing can be accomplished.
Opening a Reveal Codes window to correct document is more efficient
and less problematic than working with styles. Per your description,
a list of styles can be opened to identify what part of the rule is
creating the problem. Reveal Codes allows to see the code causing
the problem plus eliminates guessing related to conflicting styles.
Perhaps when all the mindsets are put into neutral, an option that is
intuitive, efficient, has low risk of creating other document
problems, will come to light.
Another comparison of styles vs reveal codes is the automobile
transmissions. The manual is similar to working with style
definitions while the automatic is more like working with reveal codes.
The above is not saying adding "reveal codes" to OO is the thing to
do; however, those with open minds seem to be projecting a more
efficient way to handle documents.
Nor is it saying anyone understanding the value of reveal codes and
capable of the work required to add it to OO, won't be driven to drink
or start staring at spinning spiral disks in a room of alternating
color spotlights highlighting the pink spotted elephant chorus line.
Jack
Doug Johnson wrote:
And your not even involving columns and tables, etc., yet!
A page can get very complex.
On Sun, May 18, 2014 at 8:06 AM, Martin Groenescheij <
mar...@groenescheij.com> wrote:
For me personally I worked with Styles for about three decades and find
this the best way to control my documents.
Nevertheless we should not be blind for the needs of others, managing
Styles has a long learning curve and someone can make many mistakes
before
he master Styles.
Where someone can fall into the trap is the complexity of inherited
properties from parent Styles.
Even if you are an expert in Style formats you come into problems
when you
have to combine documents which are originated from different persons.
Users tend to ask for something they are familiar with instead of
expressing their problem, they ask for "Reveal Codes" but what they
need is
something like "Reveal my Mistakes with Styles" or better "Help me
to Avoid
Making Mistakes".
One of the simple things that could help users is information of each
property within a Style that shows from which Style
the property is inherited e.g. Heading 1 inherit properties from Style
Heading and Style Heading inherit properties from
Style Default. Displaying this information either in the Style and
Formatting Toolbar or in the Sidebar will help to analyze
the formatting issues.
Heading 1
Font
Font Inherited from Heading
Typeface Bold
Size 115%
Language Inherited from Default
Font Effects
Font Color Inherited from Default
Effects Inherited from Default
Relief Inherited from Default
Outline Inherited from Default
Shadow Inherited from Default
Blinking Inherited from Default
Hidden Inherited from Default
Overlining Inherited from Default
Striketrough Inherited from Default
Underlining Inherited from Default
Alignment
Left Inherited from Default
Right Inherited from Default
Center Inherited from Default
Justified Inherited from Default
Indent and Spacing
Before Text 0.76
After Text Inherited from Default
First Line -0.76
Automatic Inherited from Default
Above paragraph Inherited from Heading
Below paragraph Inherited from Heading
Line Spacing Inherited from Default
Active Inherited from Default
On 13-5-2014 11:06, Sarala Lee wrote:
Sir / Madam,
For many years I used WordPerfect as my Word Processor and
Desktop Publisher to produce a 12 page newsletter. I have never
found a
better program. As I now have iMac I use Openoffice and have found
that
satisfies most of my requirements.
However there is one very important property (if that's the
right
word) that WP had that is missing from all the Word Processors that
I have
used. That is what WP called "Reveal Codes", where every change
that was
made in the document was shown by a particular code. e.g.: Hard
return was
"HRT". If this was not what was wanted then you could make the
change you
required. Or as sometimes happens in OpenOffice, something happens
which I
don't understand, I have no way of finding out why.
Would it be possible to incorporate this feature in
OpenOffice?
It would enhance this program's appeal to me and, I'm sure to many
others
who still hanker for the user friendliness of WP.
Gordon Lee.
-------------------------------------------
List Conduct Guidelines:
http://openoffice.apache.org/list-conduct.html
To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
For additional commands, e-mail: users-h...@openoffice.apache.org
-------------------------------------------
List Conduct Guidelines: http://openoffice.apache.org/list-conduct.html
To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
For additional commands, e-mail: users-h...@openoffice.apache.org
