Sure, go to it. Feel free to use any or all of the anatomy paper. It
would probably make sense to chop it into sections so it can be more
easily expanded and edited.
If there's something that's not clear, or you add something you aren't
entirely sure of, just put a note by it and someone'll add to it or
fix it as they notice it. Such is the Wiki way.
Edmund Lian <elian@...> wrote:
> I think we need more documentation about Webware internals, perhaps on the
> Wiki? For example, Ian's anatomy paper could perhaps be linked or contained
> on the Wiki. And perhaps someone could give an overview of how to go about
> writing kits and plug-ins for Webware.
> For example, I don't mind taking a stab at packaging Ken's database pooling
> modes to Application.py as a kit or plug-in, but it would be better if I
> had a guide rather than read the source code alone. Yeah, I know I need to
> read the source anyway, but it would be better if I already had a mental
> picture of how all the bits and pieces fit together...
> Webware-devel mailing list