[as2api-dev] as2lib to as2api

[martin heidegger]

> On Thu, Aug 25, 2005 at 10:15:06PM +0200, martin heidegger wrote:
> > we from the as2lib are just discussing about changing from visdoc to
> > as2api because its rather problematic to argue with some developers:
> > go get a mac to work with us, and there are some questions open:
> >
> > * Is it possible to integrate overloading or a different kind of
> > eventhandling (would be some kind of important)?
> 
> I've not put any real thought into overloading support.  How should the
> @overload tag (that I can see used in as2lib source) be presented in the
> documentation?  What are you referring to by "a different kind of event
> handling"?

Visdoc implemented overloading like a box of links, nothing special @
all... but it could perhaps be implemented in a better way. @overload
#methodSpecial in #method marks that if you use arguments like for
#methodSpecial then #method will redirect the arguments to
#methodSpecial, or lets say: It will act like #methodSpecial.

> > * How is the current state for a different output template. How
> > complex is it to write such or template or are you planning to update
> > your template. We would invest some time for this...
> 
> The HTML produced by the current templates should be very amenable to
> control by CSS.  If there are aspects of the formatting which it's
> difficult or impossible to change by supplying custom CSS, then I'd
> consider that a bug which needs fixing.
> 
> If you need to actually change the content which the templates produce,
> some minor refactoring of as2api's internals would be required to
> simplify the process of plugging in your custom code.
> 
> Roughly, what changes are you considering?

Two frame - frameset and a dhtml tree, that is based on xhtml ... 

> > * How fast is the generation of the as2lib documentation with as2api
> > (i know i could find that out for myself, but i thought you've already
> > done that)
> 
> On the 1.6GHz IBM ThinkPad R51 I'm using (because my little HP died last
> week), the simplest resonable set of options gives...
> 
>   time ./as2api.rb --classpath \
>     eg/as2lib_0.9.2_with_dependencies/src:eg/flash_mx_2004_7.2/Classes \
>     org.as2lib.* main
> ...
>   real    0m32.930s
>   user    0m22.994s
>   sys     0m1.841s
> 
> Adding in the --draw-diagrams and --sources options pushes that from
> just over 30 seconds to just under 60.

Sounds really great! ... Visdoc takes awful much time ...  uncomparable ...