Hi,
>>"Wichert" == Wichert Akkerman <[EMAIL PROTECTED]> writes:
Wichert> [1 <text/plain; us-ascii (quoted-printable)>]
Wichert> Previously Antti-Juhani Kaijanaho wrote:
>> No. Let the frontend define everything about presentation - including
>> order - as it sees fit. If a package _really_ needs a given order, it
>> should use a command that the language provides for that purpose. You
>> refer to SGML and LaTeX in another post - this will make it even more
>> LaTeXish and SGMLish. Content shouldn't control presentation where it
>> doesn't need to.
Wichert> Interesting idea. How about adding commands to define a beginning and
Wichert> an end for a block, within which the frontend is not allowed to change
Wichert> the order, but may freely change the order of blocks and seperate
Wichert> items?
Since I am on an heirarchical kick today, if things were done
in an heirarchical fashion, variables at the same level could be
presented in any order, as long as the children come first (or
last). So you could do depth first or breadth first presentation,
with sibling occuring in random order.
manoj
--
It is good to restrain one's mind, uncontrollable, fast moving, and
following its own desires as it is. A disciplined mind leads to
happiness. 35
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
