Joe, I have to disagree again. We have a lot of developers, more than a dozen. Here they are:
http://web2py.com/examples/default/who.html and a log of the people who contributed are very skilled in web2py. The wiki did not was very well but that is not a concern of mine. As far as I am concerned the book is the source of documentation. You are confusing experimental stuff with web2py. T2 and T3 are poorly documented by they are not and never were part of web2py. T2 was deprecated long ago. T3 was an experiment. One day it will be rewritten and better, perhaps integrated with jpolite and/or kpax. The "official" Authentication method is very well described in the new book and the chapter I posted here. The only feature of web2py that is not documented well are web services. I will finish this missing chapter by the end of the month. AlterEgo is a place for me (and you) to post brief articles. Some are current, some are obsolete, but they all talk about recipes that work. I just reviewed all of them and I found that only a dozen of them describe recipes that are not discussed in the book. I will include them in the second edition. Massimo On Jul 11, 7:32 pm, Joe Barnhart <joe.barnh...@gmail.com> wrote: > OK Massimo -- > > I'm not going to beat my drum to death, but your new book is not what > I meant by documentation. We have AlterEgo, the book, the examples, > this forum, "web2pyslices", etc. etc. etc. Each occupies a tiny space > in the totality of documenting web2py. We decided a wiki could > subsume pretty much all of the "unofficial" sources of documentation > and provide a more focused place to learn and share w2p information. > > The wiki was a failure in that it never attracted developers to fix > its shortcomings and thus never attracted anyone to use it for docs. > The wiki was not deemed a very complicated project, yet as a group we > did not succeed in creating a wiki. (The wiki itself was deemed to be > "strategic" enough that it was important not to use someone else's > wiki but rather show we could do it in web2py.) > > Now I read that we want to start more ambitious projects for a > storefront and a content management system to back it up. What's > wrong with this picture? > > The people who are actively participating in web2py are about a dozen > developers (or fewer) and they're doing all the work on web2py as well > as all the apps. Many (perhaps most) of the thousand plus "signups" > on the forum represent people who came here, got discouraged, and > wandered off to solve their problem some other way. Or, like me, > landed here in purgatory never quite making it to software heaven but > seeing the promise of those pearly gates and refusing to leave. > > I've been working on a project on and off (as my day job permits) but > I have to say it is very difficult going because there are too many > scattered sources of information. And the information comes from > different "epochs" of web2py which provides conflicting ways to > accomplish a task (e.g. T2, T3, auth, crud, etc. all have many > variations). All of those variations show up when you search for a > phrase to find out how to do something. It is very slow going. > > If the slow learners (like me) were ahead of the power curve instead > of always chasing it, you would have many more than a dozen active > developers on web2py. That's all I'm saying. Build the base, then > the code will flow. > > -- Joe B. > > On Jul 11, 9:57 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > I disagree Joe. > > > The new book is coming out in less than one month. It will cover all > > the new features. I have posted some of the chapters already. > > > Massimo > > > On Jul 11, 11:34 am, Joe Barnhart <joe.barnh...@gmail.com> wrote: > > > > I think its a complete diversion of effort and a waste of time. > > > > The reason we don't have meaningful apps on web2py is because nobody > > > can figure out how to use it. The documentation SUCKS. Hello??!? > > > Haven't we had this discussion endless times already? > > > > We are the same group who couldn't create our own WIKI in web2py so we > > > could have a PLACE for documentation. Instead of fixing the wiki > > > we're going to hike the banners and storm the walls of other platforms > > > by doing our own CMS? > > > > We need cohesive documentation so we can grow the pool of web2py > > > users. Useful meaningful applications will come if we have a user > > > community with depth. Which we DON'T at present. > > > > -- Joe Barnhart > > > > On Jul 10, 1:32 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > > I think we need to build two task forces. > > > > > 1) to build a CMS > > > > > 2) to build a eStore > > > > > the more overlap the better. We need two project leaders and > > > > volunteers. I also suggest starting by creating google docs to gather > > > > requirements. > > > > > Lots of people needs these, including me. > > > > > Massimo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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 -~----------~----~----~----~------~----~------~--~---
