On Thu, Oct 15, 2009 at 09:23:05AM -0000, Julian Edwards wrote:
> Okay.
>
> The thing that triggered me to file this bug (after talking to Gary) is the
> +ppas search form. It's a regular LaunchpadView, not a LaunchpadFormView.
> I'm not sure it makes sense to have a search form as LFV but I don't have much
> experience in doing these so I'd be happy to convert it if that's what is
> normally done. But it would mean making an interface for a non-model object
> right?
It certainly does make sense to use LFV for a search page, but you don't
need to convert it. You can use self.request.form_ng.getOne() in any
view.
But yes, if you do want to convert the view, the easiest way is to
create an interface for the view. But it's also possible to create the
fields in the view itself.
On Thu, Oct 15, 2009 at 09:23:05AM -0000, Julian Edwards wrote:
> Okay.
>
> The thing that triggered me to file this bug (after talking to Gary) is the
> +ppas search form. It's a regular LaunchpadView, not a LaunchpadFormView.
> I'm not sure it makes sense to have a search form as LFV but I don't have much
> experience in doing these so I'd be happy to convert it if that's what is
> normally done. But it would mean making an interface for a non-model object
> right?
It certainly does make sense to use LFV for a search page, but you don't form_ng. getOne( ) in any
need to convert it. You can use self.request.
view.
But yes, if you do want to convert the view, the easiest way is to
create an interface for the view. But it's also possible to create the
fields in the view itself.