Forum OpenACS Development: Re: forms as columns of template::list

Collapse
2: Re: forms as columns of template::list (response to 1)
Posted by Emmanuelle Raffenne on 12/16/08 08:50 AM
Hi Luis,

I would recommend to avoid including forms in a table as much as possible. That's why IMO it doesn't make sense to provide this functionality in template::list.

I can't think of any better way to include a form than using display_template. But is including the form in the table the only solution for your user interface?

Collapse
3: Re: Res: Re: forms as columns of template::list (response to 2)
Posted by Luis de la Fuente on 12/16/08 09:16 AM
Well, I have to present several parameters of a (maybe)large number of users. I think a table with template::list fits for this situation.

The special requirement appears because some of these parameters may be writable, so I put a form there.

If your recommendation is to avoid forms in a table, I will explore other alternatives. Do you have any suggestion?

Anyway, I'm not pretty sure about what kind of accesibility problem appears when you include forms in a table. Just for understanding, could you tell me more about it?

Collapse
4: Re: Res: Re: forms as columns of template::list (response to 3)
Posted by Emmanuelle Raffenne on 12/16/08 11:17 AM
Hi Luis,

Without seeing the interface or a clear picture of it, it's not easy to imagine or to have an opinion. On the other hand, I don't know what problem you're trying to address with this table and forms.

Anyhow, it's not really an accessibility issue but more an usability one (these are very related anyway). The purpose of a table is to display data, changing the data would be a separated action the user would decide to do (by pressing a "edit" button for example). Also, if you expect to have a large number of users on this table, you may want to consider pagination.