Re: [pylons-discuss] deform lipstick

2015-09-21 Thread Kurt Bendl 
Just as a follow-up to close the loop on this...

Thanks for the info, guys. The retail form example link totally got me 
started. That, and the docs at: 

   http://deform.readthedocs.org/en/latest/retail.html  

that chameleon-ish (Gah! How'd I miss that!) have me blissfully making form 
love.

Thanks, again!

  -Kurt

On Friday, August 28, 2015 at 6:34:09 PM UTC-6, cguardia wrote:
>
> This might at least give you some ideas:
>
>
> https://github.com/ericrasmussen/deform_retail_demo/blob/master/deformretail/templates/home.mako
>
> Carlos de la Guardia
>
> On Fri, Aug 28, 2015 at 6:21 PM, Kurt Bendl  > wrote:
>
>> Hola, 
>>
>> I've been using deform and colander to render forms for internal apps 
>> here at work for the past couple of years. It works just fine for the 
>> utility apps I've been doing in-house. The pre-registration form I'm 
>> pulling together has about 40 fields that I want to break up into 6 
>> sections. I'm thinking I want to group the fields in fieldsets, although 
>> idea is half-baked at the moment. 
>>
>> I really dig all the deform widget magic and building custom colander 
>> validators is pretty simple. Although the deform-rendered forms are simple 
>> and functional, they're also kind of horse-faced by default (apologies to 
>> any horses out there.) While it's been fine for our internal applications, 
>> these apps I'm working on now are going to be public-facing, and I know I'm 
>> going to need a bit more control of the layout. 
>>
>> I keep getting pulled into project management stuff, and I'm lucky these 
>> days if I get to code for any length of time. If someone has examples of 
>> how I might get better renders via deform, or maybe some example of using 
>> some hand-built forms but still use the deform/colander validation and 
>> error responses, or an entirely different approach that I should be using 
>> instead, I'd be grateful. I'm open to just about anything at this point.
>>
>> Lurking on this list the past few years, I really appreciate your ideas 
>> or opinions.
>>
>> Thanks,
>>Kurt
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "pylons-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to pylons-discus...@googlegroups.com .
>> To post to this group, send email to pylons-...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/pylons-discuss.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-discuss] deform lipstick

2015-08-31 Thread Torsten Irländer 
On Fri, Aug 28, 2015 at 04:21:32PM -0700, Kurt Bendl wrote:

Hi Kurt,

> I keep getting pulled into project management stuff, and I'm lucky these 
> days if I get to code for any length of time. If someone has examples of 
> how I might get better renders via deform, or maybe some example of using 
> some hand-built forms but still use the deform/colander validation and 
> error responses, or an entirely different approach that I should be using 
> instead, I'd be grateful. I'm open to just about anything at this point.
> 
> Lurking on this list the past few years, I really appreciate your ideas or 
> opinions.

Here a entirely different approach:

I'am doing a lot of form rendering and validation here at work too and we are
using formbar[0] as validation and rendring library for our forms. The forms
are quite big (30-400 Fields) and we were seeking for more control on the
layout and form logic too.

Formbar uses a very different approach to the most form libraries I know. I
uses a XML file to define the formlogic, rendering and other things. The
library isn't by far not as polished as deform/colander or other more known
libraries but it helps us a lot managing larger forms.

Maybe this is of some value for you.

[0] http://formbar.readthedocs.org/en/latest/start.html

Torsten

-- 
Torsten Irländer  |  ++49-541-335 08 30  |  http://www.intevation.de/
Intevation GmbH, 49074 Osnabrück, DE | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.

Re: [pylons-discuss] deform lipstick

2015-08-28 Thread Carlos de la Guardia 
This might at least give you some ideas:

https://github.com/ericrasmussen/deform_retail_demo/blob/master/deformretail/templates/home.mako

Carlos de la Guardia

On Fri, Aug 28, 2015 at 6:21 PM, Kurt Bendl kurtbe...@gmail.com wrote:

 Hola,

 I've been using deform and colander to render forms for internal apps here
 at work for the past couple of years. It works just fine for the utility
 apps I've been doing in-house. The pre-registration form I'm pulling
 together has about 40 fields that I want to break up into 6 sections. I'm
 thinking I want to group the fields in fieldsets, although idea is
 half-baked at the moment.

 I really dig all the deform widget magic and building custom colander
 validators is pretty simple. Although the deform-rendered forms are simple
 and functional, they're also kind of horse-faced by default (apologies to
 any horses out there.) While it's been fine for our internal applications,
 these apps I'm working on now are going to be public-facing, and I know I'm
 going to need a bit more control of the layout.

 I keep getting pulled into project management stuff, and I'm lucky these
 days if I get to code for any length of time. If someone has examples of
 how I might get better renders via deform, or maybe some example of using
 some hand-built forms but still use the deform/colander validation and
 error responses, or an entirely different approach that I should be using
 instead, I'd be grateful. I'm open to just about anything at this point.

 Lurking on this list the past few years, I really appreciate your ideas or
 opinions.

 Thanks,
Kurt

 --
 You received this message because you are subscribed to the Google Groups
 pylons-discuss group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to pylons-discuss+unsubscr...@googlegroups.com.
 To post to this group, send email to pylons-discuss@googlegroups.com.
 Visit this group at http://groups.google.com/group/pylons-discuss.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
pylons-discuss group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.