|
[
Permalink
| « Hide
]
Eloy Lafuente (stronk7) added a comment - 02/Nov/08 08:14 PM
Assigning to Martin for his consideration. Sounds like a good feature for me (to control which tabs are available). +1
Ralf - I am trying to imagine a scenario where not providing the option for single or list views would be helpful. Can you give me specific scenario that demonstrates how the hiding option would be actually useful. My gut tells me this might be a slight feature bloat but I am certainly open to your experience and ideas. Peace - Anthony
Hi Anthony,
I'm thinking mostly about very small databases like file upload, bibliography or a web link list. In this cases often you have only 2 or 3 fields in the database and you can show all elements in the list view. The single view needs additional editings by the teacher and thats not so easy. Actually they have to understand the HTML-concept of creating tables. A standard teacher can't do this. But this is a usabilty problem. If you have two tabs with the same content it may be confusing for students. The option for list view and single view is sensefull if you have lots of fields in the database, longer texts or pictures. But its not sensefull if you have only a few fields. Ralf Ralf - Thanks for the explanation as it makes sense. I agree that the whole template structure is not simple enough for teachers but that is another issue. I think we would need to study how folks are using it. The nice thing about the HTML is that it does give a pretty good deal of flexibility and control to the user which we will not want to give up but if we can simultaneously make it more automated to setup that would be a good thing. In any case, just to play a little devil's advocate, even on databases with only a few fields the list and single templates could be made the same so that the student's do not see a difference.This might be a useful comment in Docs (i.e. something along the lines of - "For databases with only a few fields, the entire record is viewable from the list view. In such cases, in order to avoid confusion for the student the teacher may find it helpful to make the list view and the single (detail) view appear identically. That way visually the student will not think they are look at or need to do something different." One simple way of implementing this would be to add a capability (or capabilities) View List, View Single and that way it could be handled with a role assignment. By default both would be on; however, a teacher could create an override and prevent that capability for a particular database. This is how the add entry is handled so it could easily enough be replicated to function with the other tabs. Peace - Anthony
Hi Anthony,
you are playing devils advocat. Thought you came from the other side To show two times the same thing doesn't make sense for me. And for this teacher have to create the list view and to create a copy of html code to create three different parts and to add them in the other windows. No thats not a solution. I also disagree to handle the visibility of the tabs by capabilities. It should be much easier to handle for a teacher in the database settings. By default teachers don't have the capability to overwrite roles in courses. While reading your text I got a new idea how to handle the list view much better. The teacher gets a list of the elements in the database and can tick and order them how they should be visible in a list. Not ticked elements are not visible in the list view. Ordering can be done in a similar way like in test module for questions. After saving this settings moodle creates automatically the HTML code for the list. Interested teachers can then go to the code and add additional functions via CSS. If we think more about this it should be possible to create a better model for the single view also. Ralf - Well I may have started trying to be devil's advocate but felt myself being converted in the process
 Thinking about it further, I also agree that capabilities is not the way to go as we want it to be simple for the teachers. Let's keep kicking it around and see what ideas come forth. Peace - Anthony Added this as being related to usability and would be interested in Olli's input on this and how it relates to the usability guidelines. Peace - Anthony
Thanks, Anthony. Did not get into this much detail in the UI guidelines/consistency project of 2009 though. Hopefully in a later project!
Thank Olli! As I think about this more, we are really talking about limiting functionality that in most cases is useful. On the conceptual level you want to be able to view either a single entry or multiple entries. Even though setting up is not as simple as it could be and we can work on improving that I am back to thinking that this might not be a good idea. My concern would be that the option to hide either single or list only complicates the interface and will then lead to confusion as to why someone cannot view it. My gut is back to telling me that this may not be a good idea but I would be willing to be convinced. Also, developing a patch should not be that difficult either. I would probably recommend adding a field to the data table - perhaps something like hidetab that would default to 0. When set to 1 it would hide the single view and when set to 2 it would hide the list view. Then we only need to check for $data->hidetab before displaying. Ralf, does that sound along the lines of what you might hope for? Peace - Anthony
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
New Feature
Open
Major
Add an option to show/hide list/single view
 |
|
