How2Py, was getting a little long. The previous discussion seems to
have brought out a couple principles --

* More emphasis on content than form to get the pump primed.
* Nobody said it but I seem to sense that more people would be
comfortable with the idea that source type (pdf, rst, doc, odt) not be
an issue for submitting How2To's.

* Finally Alex F recommended that the source code be provided in
a .zip/.w2p format.

Did I miss anything? That brings up additional items, of various time
scales --

1) Where to host the submissions? Open to recommendations. Possibly
dirt simple on a temporary basis.

2) Develop a midterm goal of a submission and catalog system with
search for How2Py.

3) A little more ambitious and Alex F deserves the credit based on the
last bullet above. Provide a copy of the code with the article. Why
not turn that around a bit -- provide the code with the article
inside? Any How2Py document is an application. The article(s) would be
housed in ../static. The lead article would have an agreed to standard
name. The extension of which would be any agreed to set of file types
(eg. .doc, .rst,.odt, .htm, etc). There is a How2Py controller that
looks for that standard name, determines the extension and brings to
bear the OS or How2Py resources to read the document. The associated
code for the article is contained in a MVC layout that the author sees
fit to offer.

Couple of advantages to this. File type concerns are reduced. Code is
ready to run. Tools for making HowTo's easier to create could be
provided. Once the document is written it can utilize the Web2Py
packaging in preparation for distribution.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to