P.S. e-mail me some github usernames, and I can give you guys permission to push to the fork.
On Thu, Jun 23, 2011 at 9:16 AM, Joe Dallago <[email protected]> wrote: > I would like to help with this, if you guys start a project. I would > say the best way to do it would be to alter deform to accept multiple > template rendering engines stored within deform itself. The actual > translating part would not be hard at all, as I have already converted > a few of them myself. Pretty sure the i18n stuff is not dependent on > chameleon in any way, but I'll have to take a look. Honestly, I'm > pretty sure that all we would have to do is convert all of the > templates to Mako, put them in a separate directory, and create a > configuration option of some sort to change between different template > renderers, while keeping the ability to set your own template > directory. Shouldn't be too time consuming, it just hasn't been done > yet. We would also have to change the docs to match our changes, > create a few tests to make sure you can switch between renderers, and > possibly change the demo up a bit? Not sure about that last one. So > I just did some hardcore forking action on deform, I will add some of > my Mako templates at the end of the day. You can find it here > https://github.com/jayd3e/deform. I like the idea of having a dir > structure like this(may seem obvious, but thought I should vocalize > it): > --deform-- > | > --templates-- > | > --chameleon-- > | > --readonly > *templates* > | > --mako-- > | > --readonly > *templates* > > On Thu, Jun 23, 2011 at 4:15 AM, Robert Forkel <[email protected]> > wrote: >> Hi Matt, >> i'm in the same boat - liking deform mostly, but being a bit afraid of >> layout requirements i will get, which turn out to require something on >> the order of custom widgets in deform. configurable html ids and class >> attributes on all generated elements might be good enough, but >> configurable templates per schema-node might be good, too. I'd also >> like deform templates with mako, but haven't done any work on this, >> partly because i18n is important for me, and I'm not really sure, how >> easy it would be to replicate the zpt renderer machinery for mako. >> so anyway, hoping we'll find the community project. >> best, >> robert >> >> On Wed, Jun 22, 2011 at 6:42 PM, Matt Feifarek <[email protected]> >> wrote: >>> Is there a community project to "port" the templates in Deform to Mako? If >>> so, is there a repo anywhere, and maybe I can help? >>> I'm liking deform mostly, but I know that I will need to customize some of >>> the layout a bit... and I'm a mako guy. It seems that if you're in for a >>> penny, you're in for a pound on the template switch... >>> ... so, is anybody already ¾ of the way there? >>> This work by Mike Bayer for Pylons might be a good place to start: >>> http://techspot.zzzeek.org/2008/07/01/better-form-generation-with-mako-and-pylons/ >>> Failing all that, how have people's experiences been trying to do gross >>> layout with forms with only CSS? The generated code from peppercorn is kinda >>> crufty, so it might be rough. I'm going to give it a whack today, but >>> was just wondering... >>> -- Matt >>> >>> >>> -- >>> 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?hl=en. >>> >> >> -- >> 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?hl=en. >> >> > -- 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?hl=en.
