On 10/30/07, Alberto Valverde <[EMAIL PROTECTED]> wrote:
> > 1. middleware configuration step could be optional, since I believe you
> > could do the same with some magic tweaking of .ini file.
>
> This could be done, TW even exposes a paste.app_filter entrypoint but I
> don't think it is a good idea to configure TW this way since it's not a
> configuration option users should be able to modify, let alone disable.
> It's more or less the same reason why you shouldn't configure Routes'
> middleware using the .ini file.
Settings that must be a certain way in order for the app to function
belong in the app. Settings that can be changed by the user to
reflect different deployment scenarios belong in the configuration
file. Also, in the application you have more flexibility to set
non-string values, put middleware in precise locations, etc.
I assume Alberto is talking about the configuration's "filter-with"
key, which can wrap a middleware around an
application-with-other-middlewares. But (1) outermost is not
necessarily the best location for this middleware, (2) the config file
is not the easiest way to configure this, and (3) the user should not
be able to disable TW or the application will crash. So TW does not
belong in the config file.
> > 6. I'd really like to see docs that tell how to control layout of the
> > HTML code produced. You see, I have a great HTML/CSS guy in my team and
> > he is responsible for all HTML/CSS produced by our app. Hence he wants
> > to be in control and b able to easily tweak it. As it is, Python code
> > essentially obscures what's going on underneath. He even objects to
> > web_helpers and so I think twForms magic may be too much to ask. ;)
>
> If he objects to python functions in templates like webhelpers' then I
> don't think he'd like twForms at all either since fields are rendered
> this way: ${display_child('name')}.
>
> In this scenario twForms might not be a good solution.
This is an important point. There's a tradeoff between generated
forms vs modifying a static form in $GRAPHICAL_HTML_EDITOR. In my
office we also have another person who tweaks the HTML and CSS, so I
have not decided whether WebHelpers and/or ToscaWidgets will be worth
it. It partly depends on which forms the client is willing to accept
a "standard" form look for, vs which forms they'll insist on moving
individual controls anywhere, changing the label position, adding text
in various spots, etc.
--
Mike Orr <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
