Source Browser ?

1\usemodule[present-stepwise,present-bars,abr-01]
2
3\startdocument
4  [title=After the cleanup,
5   color=darkred]
6
7\StartSteps
8
9\startsubject[title=The update]
10
11    \startitemize[packed]
12
13        \startitem The move to \MKIV\ is more than supporting an engine. \stopitem \FlushStep
14        \startitem It is a complete rewrite (pruning, extending, cleaning). \stopitem \FlushStep
15        \startitem Although somewhat crippled by the fact that we want to remain compatible. \stopitem \FlushStep
16        \startitem But sometimes we sacrifice compatibility by getting rid of old stuff. \stopitem \FlushStep
17
18    \stopitemize
19
20\stopsubject
21
22\startsubject[title=The current state]
23
24    \startitemize[packed]
25
26        \startitem A lot of work, more than I had thought, so it takes longer. \stopitem \FlushStep
27        \startitem Most \TEX\ code is done (some structure and column code left). \stopitem \FlushStep
28        \startitem New namespaces and helpers mostly done, but will be checked for constency. \stopitem \FlushStep
29
30    \stopitemize
31
32\stopsubject
33
34\StopSteps
35
36\page
37
38\StartSteps
39
40\startsubject[title=What is there todo]
41
42    \startitemize[packed]
43
44        \startitem Some code might become generalized (also depends on others). \stopitem \FlushStep
45        \startitem Layer and positioning code might get a more extensive \LUA\ and \XML\ interface. \stopitem \FlushStep
46        \startitem Structure related code will support setups (some already in place). \stopitem \FlushStep
47        \startitem New page builder variants will be explored (anyway more column support and floats). \stopitem \FlushStep
48        \startitem Math domains cq.\ dictionaries (basics already in place, just needs time). \stopitem \FlushStep
49        \startitem Math list optimization (pet project). \stopitem \FlushStep
50        \startitem Generate dependecy trees (easier now) and more consistent code loading order. \stopitem \FlushStep
51        \startitem All error messages needs checking (some gone, some not yet translated). \stopitem \FlushStep
52        \startitem Update all xml definitions (work in progress, also relates to wiki). \stopitem \FlushStep
53        \startitem Optimize positioning system (a bit more powerful now, but also more resources). \stopitem \FlushStep
54        \startitem More support for css like styling (makes it easier to share code). \stopitem \FlushStep
55        \startitem Modules (especially those for tracing) need to be normalized. \stopitem \FlushStep
56        \startitem Some styles (mostly private presentation styles) needs to be fixed. \stopitem \FlushStep
57        \startitem Pick up the \quote {lean and mean} \CONTEXT\ variant project. \stopitem \FlushStep
58        \startitem Now that we have more code isolated, we can define an api. \stopitem \FlushStep
59        \startitem Some manuals need to be updated (most still applies). \stopitem \FlushStep
60
61    \stopitemize
62
63\stopsubject
64
65\StopSteps
66
67\page
68
69\StartSteps
70
71\startsubject[title=What I have to keep in mind]
72
73    \startitemize[packed]
74
75        \startitem What is handy for me is not always handy for all users. \stopitem \FlushStep
76
77    \stopitemize
78
79\stopsubject
80
81\startsubject[title=But nevertheless there will be new things]
82
83    \startitemize[packed]
84
85        \startitem Elements of our processing framework will show up in the distribution. \stopitem \FlushStep
86        \startitem It's just more convenient to have one installation for related things. \stopitem \FlushStep
87        \startitem This is also why support for databases has been added recently. \stopitem \FlushStep
88        \startitem Running (blocking) \TEX\ jobs needs special treatment (ticket management). \stopitem \FlushStep
89        \startitem It makes sense to use the well developed \TDS\ infrastructure. \stopitem \FlushStep
90
91    \stopitemize
92
93\stopsubject
94
95\StopSteps
96
97\page
98
99\StartSteps
100
101\startsubject[title=Keep an eye on updates]
102
103    \startitemize[packed]
104
105        \startitem Rewriting the code base leads to bugs but these are often resolved quickly
106                   (indeed by Wolfgang). \stopitem \FlushStep
107        \startitem Following the mailing list helps and nowadays the wiki is adapted close to
108                   realtime (coordinated by Sietse). \stopitem \FlushStep
109        \startitem Changes in standards and related tools are supported and followed by those who
110                   depend on them (ask Peter). \stopitem \FlushStep
111        \startitem Sometimes users have demands and these end up as extensions to existing
112                   mechanisms (Aditya's elastic modules). \stopitem \FlushStep
113        \startitem Issues with platforms are often quickly dealt with (if Luigi doesn't know it
114                   \unknown). \stopitem \FlushStep
115        \startitem And of course I add new things driven by projects, challenges (and an occasional
116                   stack of new \CD's). \stopitem \FlushStep
117        \startitem New releases (and betas) are checked against a growing set of test files (Lukas
118                   mails a report after each update). \stopitem \FlushStep
119    \stopitemize
120
121\stopsubject
122
123\StopSteps
124
125\page
126
127\StartSteps
128
129\startsubject[title=Just ask]
130
131    \startitemize[packed]
132
133        \startitem We started long ago with what ended up as \MKII\ and \MPII. \stopitem \FlushStep
134        \startitem We currently have \MKIV\ and \MPIV. \stopitem \FlushStep
135        \startitem It has some features that we tag as \MKVI. \stopitem \FlushStep
136        \startitem Recently \MKIX\ and \MKXI\ were introduced. \stopitem \FlushStep
137        \blank
138        \startitem Examples: \MKIV, \MKVI, \MKIX, \MKXI \stopitem \FlushStep
139        \blank
140        \startitem So, what should \MKIC\ provide \stopitem \FlushStep
141
142    \stopitemize
143
144\stopsubject
145
146\startsubject[title=What I'm working on]
147
148    \startitemize[packed]
149
150        \startitem Proper dependency chain so that we can make small dedicated formats. \stopitem \FlushStep
151        \startitem Support for typesetting from databases (text, graphics). \stopitem \FlushStep
152        \startitem Next iteration if (job) tickets processing system cq. framework. \stopitem \FlushStep
153
154    \stopitemize
155
156\stopsubject
157
158\StopSteps
159
160% show latest manuals
161
162\stopdocument
163