Ah, ok. I havent got that much experience with python/turbogears, but that makes sense. Would putting the form/grid into the controller itself as a static help?
On 12 Okt., 18:35, "Diez B. Roggisch" <[email protected]> wrote: > On Monday 12 October 2009 18:12:15 Daishy wrote: > > > > > > > Hi, > > thanks for the answers so far. > > The lambda-thing works for me to, but unfortunately i guess this must > > be supported by the widget. The forms support this, but i got several > > other widgets that dont (some selfmades i dont want to rewrite for > > that) > > Regarding the app.get(/)-tipp: I read that tip before and inserted > > that into my wsgi-file, but it doesnt change anything :/ > > The way to pass urls during display() sounds a bit complicated. I > > pasted a bit of my code: > > >http://paste.turbogears.org/paste/122962 > > > I got several of these grids and to pass several urls for several > > columns is kinda against the idea of keeping it simple. > > > I think i will override the url-function and use some sort of static > > prefix (stored in the settings) to append to each url (since i already > > use absolute urls this isnt that much work). Either i have missed some > > important point or this is kinda unhandy ^^ > > The problem is that you have to distinguish between module import time (which > happens early), and application-setup (which happens later). > > This conundrum faces every application, and unless you hardcode something > (which you seem to want), you will have to have a lazy mechanizm, as the > lambda-stuff. > > Diez --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
