Source Browser ?

1% \enablemode[paper]
2
3\usemodule[present-stepwise,present-wobbling,abr-02]
4% \usemodule[present-wobbling,abr-02]
5
6\setuppapersize[S6][S6] \setupbodyfont[10pt] \def\METAPOST{MetaPost}
7
8% \StartText{...}{...}
9
10\startdocument
11  [title={\TEX\ and Reality\crlf Clashing Mindsets?},
12   topic={Bacho\TEX, May 1, 2010}]
13
14\StartItems{Some reasons to use \TEX}
15    \StartItem
16        There can be several reasons for using \TEX. Some are subjective.
17    \StopItem
18    \StartItem
19        You like the way it works: you edit a document using a simple editor,
20        add a couple of directives and delay rendering. It's the content and
21        structure that matter.
22    \StopItem
23    \StartItem
24        You need it for instance because you have to typeset math and you believe that
25        no other tool can do a better job on that.
26    \StopItem
27    \StartItem
28        You found out that it can save time because it is programmable and after all,
29        programming is a nice distraction from writing.
30    \StopItem
31    \StartItem
32        You don't want to change a 20 year old habit and why quit using something that
33        you know well by now.
34    \StopItem
35    \StartItem
36        You like an occasional fight with a batch oriented system and updating (sometimes to
37        the extend of compiling) can be done while watching a movie.
38    \StopItem
39    \StartItem
40        You dislike learning a new program every 5 years. Of course it would be different
41        if we'd live for 500 years.
42    \StopItem
43\StopItems
44
45\StartItems{My reasons to use \TEX}
46    \StartItem
47        I've always used \TEX\ and can do what I need to do with it. I like to
48        focus on what can be done instead of what can't.
49    \StopItem
50    \StartItem
51        I don't like disposable tools and am quite lucky that \TEX\ still
52        can adapt to my needs.
53    \StopItem
54    \StartItem
55        I like my job but only when using the current tools and cooking up
56        reuseable solutions.
57    \StopItem
58    \StartItem
59        I need it for rendering (often educational) content and also use it
60        for fun.
61    \StopItem
62    \StartItem
63        In the process I need to implement styles based on designs provided by
64        designers, most probably only know click and point tools but some of them
65        can think outside that box.
66    \StopItem
67\StopItems
68
69
70\StartItems{Using \TEX\ in projects}
71    \StartItem
72        Each project has at least a few challenges, the input,
73        the design, graphics, the boundary conditions, interfaces, etc.
74    \StopItem
75    \StartItem
76        In quite some cases a printed product is an afterthought and coding is
77        driven by viewing on the web.
78    \StopItem
79    \StartItem
80        Most time goes into mapping structure. Coding is done in \XML\ because
81        we can then manipulate content and publishers can reuse it.
82    \StopItem
83    \StartItem
84        Publishers often use a preselected designer and ask him/her to come
85        up with a design.
86    \StopItem
87    \StartItem
88        Chapter openings and title pages take some effort as well, especially
89        if the implementation has to be exact. For some reason design comes before
90        content so the designer has to guess.
91    \StopItem
92    \StartItem
93        Although one can try to catch bordercases it hardly pays off as the eventual
94        solutions are not that logic. Simplification is preferred over heuristics.
95    \StopItem
96    \StartItem
97        Unfortunately designers never use the fact that we can program variations and
98        and flexible solutions. On the other hand in a later stage we can quite conveniently
99        provide solutions for problems resulting in the editorial workflow.
100    \StopItem
101\StopItems
102
103\StartItems{Struggling with structure}
104    \StartItem
105        Structure in regular \TEX\ documents assumes a proper nesting of chapters,
106        sections, subsections etc.
107    \StopItem
108    \StartItem
109        In \CONTEXT\ we can clone heads and configure them independently. Often we end up with
110        tens of variants.
111    \StopItem
112    \StartItem
113        In practice numberings can intermix, for instance subsections can be numbered
114        per chapter instead of per subsection.
115    \StopItem
116    \StartItem
117        Numbers seldom run like 1 \unknown\ 1.1 \unknown\ 1.1.1 and individual components can be omitted and can
118        have different properties (font, color). This quickly becomes messy as more (unexpected)
119        structure is added.
120    \StopItem
121    \StartItem
122        It's for this reason that we now have a more complex model of resetting and synchronization
123        of states in \CONTEXT. Actually we keep adding more structure support.
124    \StopItem
125    \StartItem
126        Additional information that is used in a chapter sometimes is also used elsewhere, as
127        in tables of contents (for instance icons). Therefore in \CONTEXT\ \MKIV\ we now have
128        the possibility to let userdata travel around.
129    \StopItem
130\StopItems
131
132\StartItems{Bringing system in color}
133    \StartItem
134        When making a product line it helps if there is some systematic
135        approach in defining colors but it does not work out that way.
136    \StopItem
137    \StartItem
138        Unfortunately we can never use the colorpalet and colorgroup features
139        that have been present in \CONTEXT\ from the start.
140    \StopItem
141    \StartItem
142        Spotcolors are nice as they enforce a more systematic approach than
143        process colors. In such cases there is often some system.
144    \StopItem
145    \StartItem
146        With processcolors we often have to fight the \quotation {on my screen 0.01
147        \letterpercent\ makes a big difference} dilemma.
148    \StopItem
149    \StartItem
150        Automatically converting graphics to such color spaces can save a lot of time and
151        money.
152    \StopItem
153\StopItems
154
155\StartItems{Relations between fonts}
156    \StartItem
157        Although there is some fashion in using fonts most designs use at least
158        a few different ones.
159    \StopItem
160    \StartItem
161        Not all fonts are equally well equipped and one cannot rely too much on
162        features without testing them first. Although \OPENTYPE\ makes things
163        easier it also introduces problems due to incomplete features.
164    \StopItem
165    \StartItem
166        A macro package assumes some logic in sizes and relations but this is of no
167        use in practice. Most if the font mechanism is simply not used.
168    \StopItem
169    \StartItem
170        The same is true for interline spacing. Often some standard latin quote and
171        title is used to determine the spec. Not seldom most spacing is inconsistent.
172    \StopItem
173    \StartItem
174        It looks like justification is not wanted that much, let alone advanced features
175        like protrusion and expansion. Inter|-|character spacing is sometimes requested.
176    \StopItem
177\StopItems
178
179\StartItems{Why I still use \TEX}
180    \StartItem
181        We started making \CONTEXT\ for our own use, especially complex and demanding
182        educational documents.
183    \StopItem
184    \StartItem
185        Nowadays we stick to typesetting and as we specialize in automated processing
186        we have to operate within strict bounds.
187    \StopItem
188    \StartItem
189        We use not that many handy features as there is hardly any structure in the designs
190        we have to implement.
191    \StopItem
192    \StartItem
193        But we use quite some of the manipulative power of \CONTEXT. Also, we are able to
194        fulfil even the most extreme demands.
195    \StopItem
196    \StartItem
197        It's user demand that is the driving force behind most new features. Users typically
198        use \CONTEXT\ in a different way than we do.
199    \StopItem
200    \StartItem
201        And \unknown\ some things can probably only be done with \TEX, especially in automated
202        workflows.
203    \StopItem
204\StopItems
205
206\StartItems{Suggestions for designers}
207    \StartItem
208        Talk to those implementing the design, let them show you what can be done. Stick to
209        general designs and don't go into much detail. It's the look and feel that matters.
210    \StopItem
211    \StartItem
212        Think in systematic solutions. Lack of freedom in interactive placement of graphics can
213        be compensated by other variations.
214    \StopItem
215    \StartItem
216        Think outside the box. Use the fact that the system is programmable and can adapt. And it
217        probably goes beyond what you can think of.
218    \StopItem
219    \StartItem
220        Try to make a design extensible. There will always be more structure. Some components
221        will have less text that expected. Titles can be very short or quite long. Keep in mind
222        that you cannot tweak.
223    \StopItem
224    \StartItem
225        Try to see a pattern in structure and provide escapes for strange cases. Give the implementor
226        some freedom.
227    \StopItem
228\StopItems
229
230\stopdocument
231
232% \StopText
233