>One altertative to your proposal that Adrian and I tossed around at >one point was to alias certain "normal" modules into a set of >"tasks." That way writing a view would become::
+1 from me - that would allow to provide "simplified" namespaces by still keeping the basic structure in place (as the tasks could just be importing modules without their own code). Especially this would give a good way to have only high level interfaces in those tasks and keeping low-level stuff for advanced usage in their original places - and therefore would be a good starting point for a API documentation in two (or more) layers (having a simplified-but-powerful base API and an advanced-usage API could make some stuff much easier to learn). bye, Georg
