If I understand the more effective way is to use session that store info about master app so that util-app can access layout and other static resources and so on, returning some result. The only shared information is the database position or address, and this can be a constant for the two applications. Well, i will try it. Thanks for your kindness -leone
On Sep 25, 8:46 pm, mdipierro <[email protected]> wrote: > On Sep 25, 1:21 pm, leone <[email protected]> wrote: > > > Someone knows what is the better way to resolve this scenario with > > web2py? > > 1) I have an application populated with useful pages linked and used > > from other application. These utility-pages must be inizialized with > > some values. What is the better way to pass values between the two > > applications (not by GET, please)? The utility page not knows who is > > the caller. > > It really depends on the type of information. Applications can share > database and sessions. > > > 2) each utility-page must have the layout of the caller page. > > I have read about exec-environment and sessions but I am confused > > about the cleaner approach and I need some examples. > > in {{extend layout}} layout can be a string or a variable. If it is a > variable it can be a string pointing to a layout in another app > layout='../../otherapp/views/layout.html' > > This works assuming the two apps are not bytecode compiled and > assuming the otherapp/views/layout finds the variables it needs to > render. > > Anyway, perhaps if you tell is what is the bigger picture there is a > better way. > > > Thanks on advance > > -leone --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
