Sorry I got lost on this discussion, I'd be happy to help document with example PayPal to start with. As for document formats, I have never used scribus. I am ok, with LaTex, and Beamer and Sphinx.
However, I think a little structure would be needed on the format this documents would be shared, and reviewed (which I think is vital), as the way they may be produced may vary depending on how and where they will be shown. So, I do think a bit of consensus should be reached before commiting to writing documentation. Cheers, Benigno. On Jul 21, 6:35 am, Yarko Tymciurak <yark...@gmail.com> wrote: > anyway, since I'm Scribus-ing other things, I'll go with you on that here... > perhaps we can share master pages, etc. so the slew of stuff (eventually) > has some "common"-ish look to it. > > On Mon, Jul 20, 2009 at 11:34 PM, Yarko Tymciurak <yark...@gmail.com> wrote: > > (and yes, on looking again, sure: reST doesn't address the 1st 2, nor does > > (if I'm getting you) LaTex (by itself, nor TeX in general), troff, or any of > > the wiki markups, nor XML-ish stuff.... > > > On Mon, Jul 20, 2009 at 11:31 PM, Yarko Tymciurak <yark...@gmail.com>wrote: > > >> :-) Ahh, mercy at last! ;-) > > >> On Mon, Jul 20, 2009 at 11:27 PM, JohnMc <maruadventu...@gmail.com>wrote: > > >>> Yarko, > > >>> I could go into a long histronic on document systems and disparate > >>> roles for each but I will pass. I'll just close with the comment that > >>> the four roles are distinct and not to be merged. Learned that at > >>> Xerox. > > >>> JohnMc > > >>> On Jul 20, 10:49 pm, Yarko Tymciurak <yark...@gmail.com> wrote: > >>> > On Mon, Jul 20, 2009 at 4:41 PM, JohnMc <maruadventu...@gmail.com> > >>> wrote: > > >>> > > Yarko, > > >>> > > Understand your viewpoint as well. Documentation is a 4 part process > >>> - > >>> > > create, edit, format, distribute. reST is excellent on the last 2 > >>> > > points and bordering on sad on the first two. > > >>> > BTW - didn't mean to sound harsh, but this mis-info, topic is wearing > >>> on > >>> > me... > > >>> > From a strictly structural analysis of your argument, you seem to want > >>> to > >>> > INTEGRATE in stead of separate the 4 processes you describe (want them > >>> > coupled). For Scriptus, I've seen create/edit tool lists that are > >>> > bafflingly rich and long. Editing text is... editing text; With > >>> Scribus > >>> > you can insert a layout box, and put in it the output of LaTex > >>> (processed), > >>> > or reST. so the editing is still separate. > > >>> > It seems to me the argument you are making is one of workflow, and > >>> prefering > >>> > not to deal w/ markup languages (of any kind) if at all necessary, and > >>> I > >>> > don't know that I disagree with you.... it's just that I don't find > >>> markup > >>> > languages all that troubling (heck , used nroff and troff for years - > >>> was > >>> > the best way to self generate a book / paper, well before "Word" ... or > >>> even > >>> > Microsoft! existed). > > >>> > But I'm just toying with you - I don't mean to dismiss you, merely show > >>> the > >>> > circularness of these arguments. There's nothing wrong with Sphinx. > >>> Theres > >>> > nothing wrong with LaTex; there's nothing wrong with Scribus. All > >>> require > >>> > some learning (now, if you want to mush it all together, let's just > >>> use > >>> > open office and be done). > > >>> > Kindly, > >>> > Yarko --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
