> > > 3) What is the TG2 "API"?... other than @expose and returning the dict > > () from a controller, how can/should I interact with the TurgoGears > > stack from my code? > > This is a common mistake people do between api and framework. you CALL > a library, you work with a framework. as you said asp and php tend to > use the 'calling' more, but others like 'java' and 'python' framework > work more in the 'invoke' mode (the framework 'calls' your objects). > > So the proper answer here is you don't, you simply make your code look > like what TG is expecting and it will call you. HINT: a controller > subclass and @expose to indicate it's a "over the web callable" >
Sorry for the inexact wording. Though, I hope you understood my main point. Regardless of who is doing the invoking, I want to know how to interact with the TG stack. (Or more precisely, how to be "interacted with") Since Python lacks strict Java-esqe "interfaces", outside of the docs, there is is no particularity easy to know of all the functionality my code can supply and/or interact with. > > 4) Need a TG2 specific tutorial that covers basic genshi template > > building "from scratch". Those coming from a ASP/PHP background will > > be very lost when trying to look at the quickstart'ed template files. > > There is nothing TG specific about this. Remember part of the goals of > TG is to reuse components, the genshi docs are great so why reinvent > them? They have a whole website dedicated to it!http://genshi.edgewall.org/ > Right. And if TG's target market is already proficient Python web- programmers, why reinvent the wheel. But, we are talking about introductory documentation. For many new users, TG is their first serious Python web programming experience. (Perhaps coming from Java, .net, or PHP) Just writing a simple introduction as part of TG's "new-users-should- read-this" documentation is all that is needed. Actually there is already something like this, but it could cleaned up and linked to earlier on. See: http://turbogears.org/2.0/docs/main/Genshi.html > > > 2) Why upgrade warning for virtualenv install? It's certainly a new > > install, as this is a tutorial. (Perhaps re-word.) > > huh? you mean the warning > herehttp://www.turbogears.org/2.0/docs/main/DownloadInstall.html#install-... > > 1- this is not supposed to be a new install it's for all installs the > fact that it's new for you the first time doesn't means it's new for > everyone > 2- the warning is there because I (yes I did it) was totally tired of > replying the same question in the ML, irc, etc. > 3- most people think that install will upgrade TGs dependencies when > it will not so it's better to introduce the -U flag to everyone the > sooner the better. > 4- Due to the way easy_install works running those instructions in two > different time frames will render two potentially different sets of > dependencies (new releases) therefore the -U is needed on the old > venv. > Perhaps I am not clear on how virtualenv works, but if the user is following the tutorial, he will have just created an empty virtualenv, so there is no way this could be an upgrade. That is why i suggested rewording the warning to indicate that if the user is not strictly following the tutorial, and is working in an existing virtual env, he should use the -U option. > > > 3) When installing pysqlite, the user must have the sqlite3 dev files > > installed, as well. (sqlite3-dev package on Ubuntu) > > This is no longer needed as pysqlite site gives the instructions but > you should be using the ubuntu package (instead of easy_install > pysqlite) > Hmm... but the OS level install is for the systems "site-packages", right? That will not be in our virtualenv, right? If those dev files are still needed, it should be noted in the Ubuntu section of our docs as well. > > 4) Suggest, as an option, ipython. Since paster shell can use it. > > this was there some time ago and was deleted because people though it > was required. Install docs should have the least optional components > IMO. > I hear your point. Perhaps it should just be mentioned in passing. > So yea, thanks for the feedback even though I had most of it covered, > in a couple of minutes we'll have the new version up :) > Glad to (try) to help.... I'll take a look at the new version too. :) --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
