On 2/2/06, Martina Oefelein <[EMAIL PROTECTED]> wrote:
> One should keep in mind that this isn't quite MVC anymore, as the
> model now decides over its representation (i.e. view). Of course, if
> you consider FastData a tool to create a quick&dirty CRUD interface,
> and not the main user interface of your application that's probably OK.
The idea (and this is the difference between fastdata and CatWalk) is
that it starts off quick&dirty but should be able to work up into a
usable interface. It's not there, yet, though.
> What would be the "proper" MVC way? In TG, the (kid) templates play
> the role of the view, so we would need a way for the app to specify a
> template that renders the object as an xhtml fragment. There could
> still be a default template, e.g. just "<span xmlns:py='...">$
> {object_instance}</span>" would be a good default that happens to
> give the same result as the current implementation.
It's quite likely that you'd want different appearances for the same
object in different places. That was why I was saying that some third
party object is the more likely candidate to handle this. It could be
as simple as a template. Or it could be a widget, which would allow
for more customized behavior than a template might comfortably do.
Kevin
