sevenseeker wrote: > This is in reference to a problem described in > http://trac.turbogears.org/ticket/1457 > > There should be the Elixir classes and instead you get the vanilla > SQLAlchemy table functions. > > The patch in ticket 1457 does not apply cleanly to 1.0.4b2. > > Is anyone here aware of this problem and do they have a workaround > handy?
As a workaround, you can use the current head of the 1.0 branch and the patch I added to the ticket. But Chris Arndt is right in his comment that a better solution would be to refactor the template inheritance so that view and model files are not mixed in one template (TurbogearsTemplate in this case). This would allow us to choose individual combinations of ORM and templating language when creating projects. We could also provide quickstart templates for other templating languages like Mako. Also, the choice of names for the templates, packages and directories is very inconsistent and obscuring the connections between them: tgbase = BaseTemplate = qsbase turbogears = TurbogearsTemplate = quickstart tgbig = TGBig = quickstartbig tgwidget = TGWidgetTemplate = widget My suggestion is to refactor this in branches/1.1 before the release: - create a better quickstart template hierarchy separating model, view and controller files - use consistent names for these templates - use Tempita instead of Cheetah in all quickstart template -- Christoph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
