I am not sure I fully understand the reason for these suggestions. You seem to need access to the Wiki object in more then one controller. Why? I can see why one may want to define the wiki outside of an action to benefit from the menu (if you delete models/menu.py) all actions will have the wiki menu but only one action should actually expose the menu. Perhaps I misunderstood.
massimo On Monday, 27 August 2012 06:06:00 UTC-5, Alan Etkin wrote: > > I'be been testing the wiki for a while and have some random comments. > > -I created .wiki() in the model and used it in a given function, but it > doesn't add by default the menu entries > -Doing auth.wiki() in any function is not apt for lazyness. i'd add the > option to decorate them: > > @auth.wikify() > def afunction(): > ... > return dict() > > -And also a app-wide command to make any action a wiki would be cool > -I think that the scaffolding layout should have a wiki block or similar > to automagically put the wiki contents > -There's need for sort of a request arguments handling, to support using > the wiki with other objects in the view. For instance: > If you create the wiki in the model to allow crud with appadmin, > insert/select/... commands fail for wiki rewrites the request > I managed to filter the appadmin controller in the wiki code so it > prevents it, but it will fail with other features like custom .grid objects > arguments exposed in the same view > > Current auth.wiki rocks, but with those enhancements, I think it would be > even better. > > --
