Re: [Gzz] Agora next thursday inbct seminar presentations

[Alatalo Toni]

On Fri, 21 Mar 2003, Asko Soukka wrote:

> I guess, that navidoc is less important to the project's
> oweners/financiers, but it's the only project I know enough to talk about

AFAIK they are very dependent on efficient software development processes
(or in other words: they suffer constantly from the lack of it).

Navidoc is a potentially very useful tool that is already usable in
practice. Yet, there are "deep theoretical underpinnings (pönkkiä) and
endless future possibilities" (sorry for this awful market lang :), I mean

a) the hypertext research on interlinking and navigation maps can be seen
as underlying the construct (as you probably elaborate in the submitted
publication i haven't really read recently..)

b) as discussed on (then-)#gzz when you were writing the article, these
can be seen as first steps towards someting that may eventually be
implemented with Fenfire (then gzz) itself, with additional benefits ..
back then we talked how it would be easier to get the occurrences of an
item/element/object/(what?) if could just check for them along d.clone
etc. or is this thinking different (now?), i.e. the goal is not to bring
everything into 'the system' but to develope useful features outside it,
too? something Benja said recently has kept me thinking this, but that's
probably another discussion.

just thinking, perhaps self-evident things to you

~Toni

(keeping the tail to inform my prof. on this 'samalla vaivalla' (lazy me)
.. his doctoral thesis addresses adding hypertext funtionality to
software engineering tools and was partly made there in Jyväskylä, BTW,
see e.g. Flexible CASE and hypertext, ACM Computing Surveys (CSUR), v.31
n.4es, Dec. 1999 from http://portal.acm.org/citation.cfm?doid=345966.345985)

> - navidoc as byproduct of our project
>   + components/features added, when needed
>   + built primarly for this project, currently
>     being moved to independent project, "easily"
>     used also elsewhere
>   + independent from the other project
>   + paper submitted to HT03
> - lightweight freesoftware tools/toolchains to
>   support our documentation (and therefore development)
>   + focusing to navidoc itself
>     - lexical UML written within other documentation (ReST)
>     - linking different documentations using UML diagrams
>     - himalia
>   + pegboard could be mentioned
>  (+ out version of docutils latex writer)
>  (+ also homepage tools, i.e. navbar, will be part of navidoc)
>
> Should we have those abstracts soon for advertisement?
>
> "Navidoc is a collection of lightweight tools built to support our
> project's documentation. Navidoc provides readily-authored language to
> describe UML diagrams lexically within design documentation. Navidoc could
> also expand diagrams to work as multi-ended links, to
> hypertextually connect design documentation to Javadoc generated
> documentation. The example of Navidoc enhanced documentation could be
> found at http://himalia.it.jyu.fi/gzzdoc/";
>
> --
> Asko Soukka <address@hidden>
> <http://www.iki.fi/asko.soukka/>