231 |
============================= |
============================= |
232 |
|
|
233 |
Navidoc is as a light-weight tool built on top of several existing |
Navidoc is as a light-weight tool built on top of several existing |
234 |
Free Software [fsf02categories]_ tools. |
Free Software tools. |
235 |
|
|
236 |
|
.. The main existing components are Docutils [goodger02docutils]_, |
237 |
|
|
238 |
|
|
239 |
|
.. we can only have very few references [fsf02categories]_ |
240 |
|
|
241 |
- main parts: Docutils [goodger02docutils]_, lexical UML language |
- main parts: Docutils [goodger02docutils]_, lexical UML language |
242 |
|
|
243 |
Navidoc uses several free utilies to convert each |
Navidoc uses several free utilies to convert each |
244 |
lexical UML diagram description into final *Portable Network Graphics* |
textual UML diagram description into a set of imagemaps --- one |
245 |
(PNG) diagram files. Such utilies are *MetaPost* [hobby89metapost]_ |
for each target document since the current document is highlighted |
246 |
(mpost), which implements a language for picture drawing, and Netpbm |
in the images. |
247 |
image file manipulation toolkit. |
|
248 |
|
.. No space for this, I wager |
249 |
|
|
250 |
|
Such utilies are *MetaPost* [hobby89metapost]_ |
251 |
|
(mpost), which implements a language for picture drawing, and Netpbm |
252 |
|
image file manipulation toolkit. |
253 |
|
|
254 |
- why lexical UML language: |
- why lexical UML language: |
255 |
|
|
293 |
|
|
294 |
* separated as navidoc |
* separated as navidoc |
295 |
|
|
296 |
Usage |
Experiences |
297 |
===== |
=========== |
298 |
|
|
299 |
- does it really work |
- does it really work |
300 |
|
|
304 |
|
|
305 |
* what does the previous prove? |
* what does the previous prove? |
306 |
|
|
307 |
|
* anecdotes - has someone used it? |
308 |
|
|
309 |
Conclusion |
Conclusion |
310 |
========== |
========== |
311 |
|
|