Most websites that allow editing also do the following:
When a post is edited, add (edited x <timespan> ago) to the end of the post.
An option to view past version(s) of the post is made available
A "history" link, or making (edited x <timespan> ago) clickable
The ability to "flag" posts as inappropriate/dishonest
An approach like this, while ...
The absolute vote count should always be left alone. Reddit's masking of the true up/down vote count was a controversial matter due to the lack of transparency around how much activity constituted 'hot'.
I proposed (elsewhere) that the upvote counter should have a detail-panel (on hover) that depicts the percent of current content that was voted on.
How to Switch between View and Modify Modes
To answer your explicit questions, it’s acceptable to have a single command button toggle between View and Modify. This can be effected by changing the caption of the button between “View” and “Modify”, or you can have a toggling “Modify” command button. When pressed “in,” the page is in Modify mode. Click again ...
For editing values in a text field, it depends where you edit them, and what other fields are in its context:
if the layout stays data-table-like, and the cell simply becomes editable, then I agree with @Erisu's answer, to conform to excel-like solution.
if the text field is in a form, it is better to be consistent across fields, to prevent user having to ...
Looking at Excel as an example, when a cell becomes a numeric value, the numbers are right aligned. When double clicking into the cell to edit, they maintain the content right aligned.
As people are accustom to Excel, it might be sound to follow the same flow?
My opinion is that the text must be saved to be 'part' of searchable data. That is a standard approach. If for some reason, there is a requirement for you to be able to search unsaved text also, then its a different thing.
On search focus, you can 'auto save' or 'prompt-save' or just plain ignore the unsaved changes in your search results. But searching ...
Show everything right away. You shouldn't hide new functions behind an edit. Editing implies you already finished the process, but want to alter a few minor things. So, if you edit an activity, all the options available were there when you created it. Hence, the editing aspect.
Hiding available functions behind an edit is kind of counter-intuitive. Users ...
Set expectations up front, and provide clear feedback upon submission. Prevent errors (and more support tickets) after submission by disabling the approval fields.
I'm not familiar with your domain, but you could split the form into simple changes that users can make immediately, and be clear with changes that will require an approval ...
In most cases I know, changing the upvotes or likes to an item seems not to be the solution to your problem. It rather causes confusion and probably frustration. In general, you always have to regard the intention of the upvote counter, if there is a public edit history and/or if votes are directly linked to a specific version of the upvoted item.
E.g. if ...
This is a bit of a made-up question. Who asks this sort of stuff?
Who should be president?
However on this site at least, I think if you had an answer which got a lot of up-votes, and subsequently the answer was changed to something completely different then someone could flag it for moderator attention.
The moderator could then revert the answer, and ...
The click-to-edit pattern you describe is very common for enterprise applications.
Given (a) the 75% view / 25% edit ratio you describe and (b) the moderate to high cost of accidental edits, I would definitely recommend this pattern for you.
Click to edit provides a positive affirmation of intent...given the cost of errors it helps to erect a ...
You can add a button on the bottom of the search result, so that if the college or school is not available the user can add it by directly clicking the "Add missing School/College" button. It would be a better user experience in my perspective.
Hope this helps..
I strongly hold the opinion that pop-ups are almost never the best UX for CRUD operations. I would recommend looking into some of the following components:
Slide in panels
These scale well for mobile contexts, and allow for scrolling on larger forms without "leaving" the context of the current page/action
Show more than one line of ...
For both the scenarios, pressing back should take the user to the list of homework.
The Edit action should only be accessible by the Edit button
When the user clicks on the Back button, he/she expects to go back a step in the workflow (which is the Homework list screen in your case) rather than going back to the previous screen.
I'd suggest to follow each platform's conventions, that way the iOS user will know how it works, and same for your Android users.
Also want to mention that if you are using a pre-existing framework such as Google's Material Design, then follow Material Design guidelines suggestions.
Since time is such a core component of Gantt charts, including both the time and the offset might suit this use case best, in order to have both absolute clarity and relative perspective of the change.
Something like the following might work:
This slightly larger tooltip is explicit about the previous time, new proposed time, and the offset, in a still ...
You might want to look at how Google's Material design solves this with its concept of chips.
So in your case once the user links to a person, it is displayed on the screen as a chip. The user can could then remove the chip (unlink) or add a new chip (link a different person).
Here's a link to the design guide on chips:
Google Material Design Chip ...
Wizards are useful for stepping the user through a sequence of steps to accomplish a goal. They are sequential by nature.
Mostly useful for breaking down complex operations in simple steps where efficiency(how fast can the users perform a certain task) is not too important.
Refer to this link : for more on when to use Wizards:
Actually, there's two questions in here, one regarding the master-detail navigation, the other regarding accordion vs. tabs.
Master-detail can be realized on one screen, like here, or with a two-step navigation from the list to a complete screen of details. For me, the decision between these two relies on the following:
How many detail is needed to ...
For bimodal I like a simple checkbox
With a toggle button is it not clear if the toggle represents the current mode or the mode you would toggle to
In the app this is used in even in view mode (not edit) the users still want to be able to select text for copy and they like an explicit view (read only) mode so they know they can't accidentally change ...
Text boxes are great in simpler layouts, where the primary use of the element is editing. In a grid where the control is repeated indefinitely, they (like buttons or other controls) will increase visual clutter. This is a problem since one of the reasons we use grids is to provide us with overview.
I really like designs where editable fields are very ...
There are a couple of aspects to this. One is adding a list item, other is editing a list item.
If you are adding a list item, once it is added it is saved. Now that item can be searched for.
If you are editing, let there be an edit view where the search field will display results for all the editable and non-editable item(s).
Prompting to save the ...
Per-line Edit Button makes sense when
When all the attributes of a row are shown,
and Editing is happening inline.
Otherwise per-line edit button doesn't make sense.
Similarly, Per-line Delete Button (whether it is a button or a cross mark) makes sense when
A row (record) is either too trivial to ask for a confirmation. For example, removing a ...
I think the other answers are misinterpreting the question as 'where should new posts be placed'. I believe the question is about editing the initial forum/blog post or article after new information came in to view.
Is it being updated live?
If you're covering an event realtime (ish), like a political debate, or CES presentations, people are likely to stay ...
If the individual tickets are visible but you want to be able to modify them as a group, you could keep your checkbox representation of true/false and introduce a set of controls. These wouldn't represent the current state but rather work as actions to modify all the tickets (and you can see from looking at the individual tickets what the current states are)....
You can use inline editing.
See this example: Simple inline editing.
It is for a table, but the functionality can be implemented with others libraries too (like this).
Another option can be a tooltip. See this library.
As per my view point, Use inline edit to edit single cell and if column contains multiple fields to select like a dropdown checkbox then show respective controls over the cell when user click the cell to edit. For an example : If column is for age then show calender on edit, if it is either or option then show dropdown.
download bmml ...
Basically you need a design for CRUD operations for addresses and emails.
actually you can accommodate both email and addresses in one screen.
For adding new items(email/address) you can follow google's material design
For listing, editing, deleting you can try below design.
This is the very simple design you can start with. then as your app ...