> Thanks a lot for all this notes, most of us have look at them too much > to find this kind of info :)
No problem, :)... thats what my friend told me too > I think we should add a section to http://docs.turbogears.org/1.0 with > the default components maybe even move this image to the frontpage > http://docs.turbogears.org/1.0/GettingStarted/BigPicture I freely admit that I am very lazy when it comes to reading and looking at charts so this images probably wouldn't help me because I would just blatantly skip over it (bad engineering habit). But others probably don't think the same way as me. > > * in case people dont want to try it out themselves, it might be > > helpful to include screenshots or perhaps a working tutorial site of > > what the page would look like after each addition in the written 20-min > > wiki tutorial (because the screencast would take too long to see)... > > for example, after watching the screencast, i now look at the written > > tutorial, but i dont want to actually program it, so screenshots would > > have been useful for me > send them to me :) I would, but I was lazy and I didn't actually do the tutorial, :)... if I have some free time, I may go back and do it to extract the screenshots. > > * the written example explained a bit more of what publish_parts > > was but the explanation itself was difficult to find... also, it still > > doesnt explain exactly what it does and why we need it to grab html > > data from the database > yes that's true but remenber the idea of the wiki tutorial is to get > you hook in, not to be extensive, most TG apps don't even use > publish_parts this was just a clever way to get that bit out of the > way and focus on how great tg is. That is true, and I think I was using the tutorial to also see what Python coding should look like (I suspect that my coding still looks like Java). > I believe that one was there. it probably got lots on the transition > to the new docs site. I have the old one on my disk (0.8a2 required :) > we'll need to upload the newest zip. I think I found it on the last page of the 20min WIki, but it would be better on the first page, in my opinion (so that people can download and see how it should work as an end product). I don't remember it existing for Brian's tutorial though. > One thing that you should note is that most php hostings out there are > bad so the actual number is not that different. > > On the other hand python hosting is not something lots of companies do. > > last but not least WebFaction service is great it's worth the money > even for non-tg projects. Yes, but sometimes I just want a web server to play with (when I want to do more than just localhost) so I don't want to pay too much. But I suppose the price is still pretty decent. I just thought I'd point that out because PHP is awful but is popular because of its hosting options. > > Continuing the last point in "Overall"... in the > > http://www.turbogears.org/docs/deployment/hosting.html page, under > > WestHost... it says that TurboGears can be run under "straight > > proxying". What does that mean? > > > umm good question I don't know what's the westhost setup, my guess is > that they have an apache server that uses mod_proxy to send your CP > server the requests. Is it possible to have a step-by-step installation guide or something? > now let me ask you something > > Did you like TG so far? Yes, I really like it. So far, I haven't done anything complicated so I can't comment too much about performance or power, but everything I've seen I like. And I think the general consensus outside is that it's well built. For me, the learning curve was not steep... around 2 hours to understand what it's supposed to do and how to do some of the main things (via the tutorials) and then a few more hours to actually program my own web app. Add to the fact that I had only learnt Python basics the day before, and I don't think that's too bad at all. I think the learning curve is a bit steeper than it would have been just because we need to learn CherryPy, MochiKit, Kid, and SQLObject before we can really get into it (perhaps with the exception of MochiKit). Not that I object to that. I think the learning time would be even faster with better docs because much of my time was spent on perusing Google and finding examples and docs (for the 3rd party components mostly). That was hard because there weren't many. It mostly wasn't the TurboGears docs that slowed me down, but there were times when I didn't know who's docs to look in to find something, so I guess by association, TurboGears had a slower learning process than had the external docs been good. I heard rumors that TurboGears could switch from SQLObject to SQLAlchemy. Any truth in that? One thing that I hope is that all changes to components are made sooner rather than later because to alter existing code to match changes continuously would be annoying. But I have heard that SQLAlchemy runs better than SQLObject and I'm not totally pleased with SQLObject... so since I haven't gotten too far, I don't mind, ;) One thing that I found to be missing was a tutorial on sessions and user authentication. I just designed a simple web app that includes that but it took me half an hour just to find how to delete a session (for logout). CherryPy docs are not very good, :)... then I found the answer on a forum... I don't know if it's the proper way to do it but it works: del cherrypy.session['User'] Before that, I tried things like delete(), expire(), etc. but with no success. It's funny how the only doc for session authentication that I found on CherryPy docs was to increment a counter. But I suppose that's really all you need, considering that I was able to extrapolate it into a user authentication system. So... to summarize, I'm going to keep using it, :) -Frank --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
