<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><blockquote type="cite">I assume that you want to keep the number of visible buttons to a minimum otherwise there is no point of hiding 'delete' button if the form is dirty. I.e., if you want to delete the record, you don't care about the unsaved changes you already made.<br></blockquote><div><div>Yes, Petr, I want to reduce the information load. The Delete button calls a lot of attention (more than the save button actually) and I don’t want to make him think (see image below). We are assuming that after the user start to edit, he is more likely to save or clear his changes than deleting the artefact. That’s why we hide the button.</div><div><br></div><div><img apple-inline="yes" id="66ADECF3-A606-4294-8C4B-2A3611D95426" height="57" width="268" apple-width="yes" apple-height="yes" src="cid:56488FCD-0EC7-4510-A20F-167813B4F8BF"></div><div><br></div></div><blockquote type="cite">We have similar buttons in FreeIPA just with different names:<br>- 'Refresh' reload from server - always enabled<br>- 'Reset' undo changes - enabled if form is dirty<br>- 'Update' save changes - enabled if form is dirty<br><br>We also have 'undo' next to each form control. It's visible only when the item is dirty.<br></blockquote><div>Thanks for sharing!</div><div><br></div><div><blockquote type="cite">These are good questions that you raise. Not sure about Scenario 02 either. In other places I have seen a "Revert" button that I think does the same thing you are proposing for "Clear Changes". Not Sure what "Delete" is doing in this context. I'm generally not a big fan of buttons appearing and disappearing or changing names.<br></blockquote><div>Matt, we need somehow to allow the user to delete the artefact. I’ll take the Push page as example. We don’t have a list of Push resources, so the only place where the user can delete a push is inside the Push page. This page illustrates the scenario 02:</div><div><br></div><div>- Initial state (not modified)</div><div><br></div><div><img apple-inline="yes" id="D9C040CD-DA91-4278-A6FF-D3CCD97CEC02" height="359" width="768" apple-width="yes" apple-height="yes" src="cid:B22F642A-F302-49EC-ACFD-EEB752071607"></div><div><br></div><div>- After making changes</div><div><br></div><div><img apple-inline="yes" id="62107183-A798-43C0-B016-8D366BCBEC29" height="183" width="771" apple-width="yes" apple-height="yes" src="cid:4CBCFFFC-4C90-4345-AB6A-E07F9043AF3B"></div><div><br></div><div>I’m not a big fan of dancing buttons as well, but I think this is better than the three buttons side by side (like above). What do you think?</div><div><br></div><div>And finally, that will be the initial state for the scenario 01:</div><div><br></div><div><img apple-inline="yes" id="3FB8B234-05FA-40F7-A74D-5E37C1903AC6" height="445" width="766" apple-width="yes" apple-height="yes" src="cid:CC2D2A30-4DE3-4399-9E3A-FD7F2A64A9CE"></div><div><br></div><div>Thanks,</div><div><br></div><div>Gabriel</div></div></div><br><div> <div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>---</div><div>Gabriel Cardoso</div><div>User Experience Designer @ Red Hat</div></div> </div> <br></body></html>