form "list", "edit" and why not "view" ?

thread: 2 messages  |  last: about 3 years ago  |  started: wednesday, march 26, 2008, 6:04 pm pdt


#1  |  rsantos (Rio de Janeiro, RJ) Brazil
Wednesday, March 26, 2008, 6:04 PM PDT

QCodo is a fantastic framework, but I fell like it lacks a “view” form.

What is a “view” form ?
Simply a “view” form would be a form that at first shows all the details of an item selected from the “list” form.

Why have a “view” form ? What are the benefits ?
- it lets you show information that is not displayed in the list
- it lets you display information without the need of editing it
- it lets you display information that is not editable in “edit” form
- it lets you interact with other tables and show related information to the selected item that comes from other tables
- it lets you deal better with displaying additional information on N-N table relationships

Many systems projects that I have been part of had this necessity, that's one of the motives why I am bringing this scenario up.

I would be glad to hear opinions from everyone on this topic.

#2  |  VexedPanda (Calgary, AB) Canada
Thursday, March 27, 2008, 3:09 PM PDT

We let our edit form double as view, but ideally you're right, it would be nice to “toggle” each control to/from “readonly” mode, where it's shown as a label/other uneditable control.

I have not done it myself, but I don't believe that tweaking the templates yourself to accomplish this (or creating a new set of templates for a separate view page) would be very time consuming.

If you do make some, be sure to post them back here so that everyone can take advantage of them. :)



Copyright © 2005 - 2012, Quasidea Development, LLC
This open-source framework for PHP is released under the terms of The MIT License.