I am considering posting most of the book on line in HTML. This may be possible with a disclaimer about "do not reproduce in print". The main issue is that the book is in latex and not easy to convert.
On Feb 8, 10:18 am, Jonathan Lundell <[email protected]> wrote: > On Feb 8, 2010, at 2:46 AM, Beerc wrote: > > > I ***LOVE*** the tight integration of web2py components. > > > I ***LOVE*** the compactness of web2py. > > These are by far the two biggest reasons I started using web2py, mainly over > Django and its kin. > > Now that I have a little more experience, I'd add this mailing list to my > list of reasons. > > My biggest complaint is what has been referred to as "magic" behavior, and in > particular the relative opaqueness of some of that magic. Documentation could > help there by making more clear what's going on inside; there's a little too > much "do this and it just works" right now. But that's true of (say) RoR, > too, so web2py isn't alone. > > I like the idea of a wiki that parallels the structure of the book. I'd also > like to see a page each for all (or at least the important) classes, linked > to their mentions in the mainline docs, where among other things magic > behavior is explained. -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
