I realize I am a little late to this discussion but after reviewing a lot of the messages in the group, searching the web resources (purchased manual, cookbook slides, alterego, etc.) and playing around with the framework for a few weeks at work in my spare time, I have some observations:
- Documentation should be the number one priority. I realize there is movement on this but I am not clear on the specifics other than Sphinx being mentioned, which is really good to hear. - Building out the resources for prospective web2py developers should take precedence over anything like CMS or eStore (though I personally would benefit from both of those). Things like http://www.djangosnippets.org/ for web2py would go a long way to spreading the gains from any/all projects around to the larger community. Something like Railscasts would also be a good example of something that could be both a project and service to newcomers. I think the idea of cleaning up the appliance app is a good idea and inline with the above. I am still trying to make myself fluent with web2py and even though it is a lot simpler to pick up than Django, for example, I felt a lot more secure in the Djangoverse because of the kick-ass documentation and community support. Whatever else you want to say about the Django folks, they are definitely organized and they serve up some nice things to their community. A laundry list of complaints would sound like nitpicking but little things can really annoy... like when i am copying/pasting code form the how-to section of the web page and all of the string quotes come over like `some string` so I have to manually edit every string I just pasted. Thank you to everyone for their hard work on web2py, especially Massimo. I really like the concept. The completeness of it all as a package.. the practically zero configuration factor and many other niceties put it in a class alone among the many web frameworks out there right now. -- KW On Jul 11, 12:08 pm, Yarko Tymciurak <yark...@gmail.com> wrote: > ... I personally don't want to start w/ CMS or eStore. > > I'm already uncomfortable with the immediate jump to solution; an immediate > "here's how you can do it!", without allowing for the necessary and normal > process of "what do we want this to do?" followed by "what are the ways > this can be done?"... and the choice to "let's do it this way...").... > > I continue to think sometihing more focused, narrower in scope is a better > first target. > > On Sat, Jul 11, 2009 at 11: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-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 -~----------~----~----~----~------~----~------~--~---
