I believe for this example app either approach is fine for passing vars to the template; the way you mention is more Myghty/Mason-ish, while attaching vars to c (short for "context" I think?) is similar to Rails (as of late, many other frameworks before Rails).
In this case either works, but one example where it's nice to stick the vars onto 'c' is if you're inheriting from a base controller in which you override methods but still call the methods in the parent class -- this way the vars are "magically" present in the template after the parent class calls m.subexec(). And I think it's maybe a bit more explicit and avoids big long param lists on the subexec call but that's of course debatable and aesthetic. Future releases of Pylons (current?) using Buffet and other templating libs might require one approach or the other -- I dunno though. Oh and of course someone correct me if I'm getting this all wrong! _TG --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss -~----------~----~----~----~------~----~------~--~---
