> It certainly communicates that you are slightly struggling Yes! Indeed I'm struggling! :) TG seems very cool but I haven't got the right way of using it I guess but that's okay every tool has a learning curve. Thanks to this list with TG it's not that bad actually :)
> 1) The GET/POST variables arrive at your method as parameters (no > decorator involved for the most part). You may want to employ a > varargs strategy in some places. Yes, this is clear. > 2) The username of a logged in user is directly available as a > variable within TG. Clear too. > 3) The last time I put the same call in to every method; I was trying > to construct a bread crumb trail and I since discovered a much better > way of doing that which is covered here: > http://www.nabble.com/-n00b--headers-footers-t3935734.html Oh yes, I forgot about your example mainly because when I looked at it last time it was too complicated. Now it's much clearer, thanks. > 4) It puzzles me that you appear to "setup" each transaction when you > have a long running server process to hand. The kind of setup I'm thinking of is for example this: if I have a book shop app I would like to display at the top of each page the total number of books and the total number of authors. This should appear on every page so I was forced to fetch these two numbers from the db and put the corresponding function call at the beginning of each method. > You might find it helpful to work through a small application from the > cogbin. Yes, that is exactly what I'm doing! > Regards > A Thanks so much for the help! Daniel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
