...is to predict the future. Which I think I did fairly well, when I began - some 5 years ago - talking about the ideas of Alan Kay as extremely relevant to the business of edu-sig.
What I seem to have gotten wrong is the fact that giving forum to those ideas; praise, implicit and explicit of those ideas; encouragement to the Python community to embrace those ideas is what is relevant. Critique of those ideas, encouragement of the Python community to resist them and to work to create a viable alternative to them is what is not. My bad. My effort at creating , informed by an alternative world view, is progressing. Many of the suggestions that Andre had given me when I asked for some feedback here earlier have been implemented. Lot's of hard work. Including extending/abusing the framework of the pudge automated documentation generation tool to, I think, pretty good effect. See http://pudge.lesscode.org/ for the tool: and http://pygeo.sourceforge.net/docs/module-base.geometry_real.html for example output. I have worked out one thing that was bothering me, i.e. lack of control on the ordering of modules in index documentation and such, but have not put up the new output as of yet. Beyond the auto-generated docs, a Overview document has been written that is an effort to express PyGeo's vision of itself. http://pygeo.sourceforge.net/docs/Overview.html as well as a document in progress on approaching the PyGeo application code as a readable document, geared toward those without prior experience in undertaking such an effort. http://pygeo.sourceforge.net/docs/codeanatomy.html PyGeo is what it is, but it is at this point hard to take seriously not taking it seriously. Andre's feedback had in fact been very helpful to me in getting to this stage. I am still a little bit away from a new release and an announcement. Any feedback in the meantime is relevant and welcome. Art _______________________________________________ Edu-sig mailing list [email protected] http://mail.python.org/mailman/listinfo/edu-sig
