I think I understand a bit what you mean about not feeling like you understand the "guts" of web2py at first. The book wants to walk you through app-building before introducing you to much of the core, even conceptually. I think this is actually a good pedagogical move for lots of people, but for those of us who are used to understanding our tools before we use them it can feel awkward. Because the web2py community is younger (and so smaller) there aren't the variety of solid books that take slightly different approaches. So far Massimo's tome has to try to be all things to all people. I think that situation is already changing but I'd encourage you not to let it influence your choice of framework too much.
If I were starting web2py over again, I would actually start with the chapter on the "core" and then read the chapter on the DAL. But I'm finding that the elegance and completeness of web2py makes it well worth the effort. And the community here on the Google group (Massimo included) is so responsive that I've never been stuck for long. On the sluggishness issue, I also find the web-ide pretty unresponsive. I've used pyCharm happily for a while with web2py, although it doesn't mesh quite as easily as WingIDE does. At the moment I'm just using favourite text editor (Sublime Text 2 because I'm a sucker for aesthetics, Geany when my open-source conscience wins out). But having the web-ide available has sometimes been helpful in emergencies or for small experiments. Cheers, Ian On Friday, March 23, 2012 12:15:27 AM UTC-4, SeamusJP wrote: > > Hi, > I am developing a new project, new to python. Project is mainly for CRUD, > display data on website, and easy management of back end. I started > Djangobook and finished it, I felt like it was great and I could go in to > eclipse, create my models, validate, and then make my forms on site..pretty > simple (Although I am sure I am missing something). > Then I came to find Web2py, initially, I am super stoked about it, > however I can't seem to mesh with the documentation very well. Maybe I am > missing something. I feel like djangobook held my hand and spoke about the > main concepts of django, but in web2py, it jumps right into these super > long pages , and don't really explain whats happening in the back. Also, I > am running web2py on my machine, ubuntu, as well as another win7 machine. > It feels sluggish. Anyone else experience this? Is this whe web based IDE > causing it? Its difficult to switch through browser tabs / windows to make > changes to things, validate errors, read the book..It just felt like django > + eclipse + djangobook + terminalx was easier to manipulate. I could use > terminal to quickly validate things and find errors, which djangobook > explained thouroughly. > I recently went on to IRC and was told to look at the Vimeo videos. The > first one just jumped into features, and did not seem like a in depth > tutorial. I really want to use Web2py, I think it will make my life easier > when deploying apps, creating forms quickly, etc, but it just doesnt feel > streamlined, I feel like alt tabbing and inputting code makes me wait > longer than I had to in eclipse. I am having these weird issues getting it > going. Anyone experience anything like this? Should I just push through it > ? >
