Edit Mode
Printed From: IdeaBlade
Category: Cocktail
Forum Name: Community Forum
Forum Discription: A professional application framework using Caliburn.Micro and DevForce
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=3982
Printed Date: 28-Apr-2025 at 12:28pm
Topic: Edit Mode
Posted By: gregweb
Subject: Edit Mode
Date Posted: 06-Feb-2013 at 6:08am
One thing I notice about TempHire is that it uses an Edit mode, ie, the user is required to click the Edit button before Edits.
I have seen this a lot in the past, and especially on web based interfaces, but it seems the client based apps are leaning towards always being in edit mode.
The one clear advantage to edit mode is when permissions are involved. So if the user is not authorized to make changes to a record, then they are not permitted to go into Edit mode.
But other than that, I tend to go with always being in Edit mode. Just wondering what your thoughts are on the matter.
Greg
|
Replies:
Posted By: mgood
Date Posted: 06-Feb-2013 at 6:22am
|
TempHire initially didn't have an explicit edit mode. I added this later because I see a lot of our customers doing it this way and yes it's primarly so they can permission the edit mode. I personally favor to not having an actual edit button and instead drive the edit mode off of the user's permission. So if the user has write permission, the screen is automatically activated in edit mode and if they don't have write permission it's activated in read mode. Since TempHire doesn't use permissions at the moment, the edit button will have to do. Some prefer to show the user a disabled edit button if they don't have the necessary permissions. It's really all a matter of the user experience you want to give.
|
Posted By: gregweb
Date Posted: 06-Feb-2013 at 7:22am
OK, thanks, good data!
Greg
|
|