Alex,

Certainly can, and will.

Fact it brings up yet another 'opportunity' for consideration.
Hopefully the How2Pys will include the sample code run ready. If that
is the case why not just put the documentation in /static? (or
someplace better?) That way it is totally contained in the .zip/.w2p
application.

Thoughts?

JohnMc

On Jul 20, 5:51 pm, Alex Fanjul <alex.fan...@gmail.com> wrote:
> Wow!! impressive John...!
> Could you provide us with an example zip application ready to install in
> web2py?
>
> thanks in advance!!
> alex f
>
> El 20/07/2009 23:12, JohnMc escribió:
>
>
>
> > Ok, here is a draft of the article 
> > --http://76.185.48.154/images/web2pyart1.pdf.
>
> > Have not applied a great deal off formatting. Looking for input as to
> > preferences in that regard.
>
> > JohnMc
>
> > On Jul 19, 10:13 pm, Yarko Tymciurak<yark...@gmail.com>  wrote:
>
> >> On Sun, Jul 19, 2009 at 7:49 PM, Tim Michelsen
> >> <timmichel...@gmx-topmail.de>wrote:
>
> >>>> A directed question if I may. What tools do you use to create the rest
> >>>> doc that goes into Sphinx.
>
> >>> I tried to show some here:
>
> >>>http://bazaar.launchpad.net/~timmie/web2py/web2py-appdocu/annotate/he...<http://bazaar.launchpad.net/%7Etimmie/web2py/web2py-appdocu/annotate/...>
>
> >> This was Timmies patch for web2py documenting - and his proposal to follow
> >> numpy standards (a good starting point, I thought, and continue to think,
> >> but too detailed for web2py sources). I got partway thru parsing this down
> >> to what I thought would be useful essentials for web2py;  I need to send
> >> this to Massimo.  In the end, too many people working at once, and no
> >> coherent direction, so this confused the issue / task (too many / no 
> >> chiefs;
> >> incongruent effort), and I just dropped it until this aspect cooled 
> >> (anyway,
> >> other things in my life took priority at the time).
>
> >> I haven't tried prettytable (write python code to generate ascii table; but
> >> could be useful to dump existing data).
>
> >> The shell scripts for making web2py specific sphinx docs I don't think 
> >> apply
> >> to your question of what tools do I use to create rest (that is, the
> >> structured format of the content).
>
> >> But bottom line is still - you can easily just use a normal text editor....
>
> >> To get a feel for this - to convince yourself that as a edit / contributor
> >> this is "sane", just look at one of the "show source" links on any of the
> >> sphinx docs
> >> e.g.http://sphinx.pocoo.org/_sources/intro.txtofhttp://sphinx.pocoo.org/intro.html;
> >> other sphinx docs listed here:http://sphinx.pocoo.org/examples.html
>
> >> - Yarko
>
> >>> you can use a simple editor that involves good syntax highlighting. Like
> >>> HTML...
>
> >>> Or see the post on Lyx.
>
> --
> Alejandro Fanjul Fdez.
> alex.fan...@gmail.comwww.mhproject.org
--~--~---------~--~----~------------~-------~--~----~
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