On Thu, Feb 11, 2010 at 11:05 AM, Vladimir Dronnikov <[email protected]> wrote:
> Right! I am the user and I speak for formalchemy. I'm not sure what you mean when you say "speak for formalchemy". > I'm inclined to do so, but still as the user I want related stuff be > visible on parent view. May be partially, but visible. You can still make it visible, but not editable. Just do it in the templates. I don't see why you need to make a "read-only renderer" to do this instead of just doing the rendering directly in a template, perhaps using a helper function for stuff such as rendering dates/times or slightly more complex HTML. For forms, I can understand using something like a form library to help with rendering as you want to make sure you have a simple way to serialize the form results into an entity. But for strictly read-only text or other HTML that isn't fields on a form, I'd just keep that to the template. > > Exactly. Suppose I want to CRUD images related to an object. The > situation is hardened here since images (along with other uploaded > stuff), as indirectly accessed objects, should in addition be provided > with interface to upload them. How would you do that? > I am not understanding you fully. My main worry is that you're trying to take DRY too far, which is a problem that that I know hounded me for awhile, and still sneaks into my thought process. But I guess it would be helpful to know your use case a little better. -- 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.
