<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Matt,<div class=""><br class=""></div><div class="">I don’t have this in any of the applications I work on, but I’m sending as reference the way iTunes does it, which I find very interesting.</div><div class=""><br class=""></div><div class="">1) Original state</div><div class=""><br class=""></div><div class=""><img apple-inline="yes" id="89C09BD8-5458-4547-A252-CBD2E3ED8D82" height="512" width="465" apple-width="yes" apple-height="yes" src="cid:1BE33FF5-7114-4A42-AD19-6B3C21BB0A52" class=""></div><div class=""><br class=""></div><div class="">2) The use puts the mouse over the “artist” information</div><div class=""><br class=""></div><div class=""><img apple-inline="yes" id="11165C7F-E118-43CC-BCDA-4CA94263CC30" height="512" width="464" apple-width="yes" apple-height="yes" src="cid:2A440FF9-2240-48DB-8C4B-3AFE312EC017" class=""></div><div class=""><br class=""></div><div class="">3) It becomes an input by clicking on it</div><div class=""><br class=""></div><div class=""><img apple-inline="yes" id="EA554A46-16FC-42A1-864F-BA6238317D48" height="514" width="465" apple-width="yes" apple-height="yes" src="cid:D793772C-77F5-4867-9529-A4ABAE7F1A84" class=""></div><div class=""><br class=""></div><div class="">The tab also works for navigation :)</div><div class=""><br class=""></div><div class="">With this approach we avoid the Edit/stop editing buttons</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Gabriel</div><div class=""><br class=""></div><div class="">15, at 7:53 PM, Matt Carrano <<a href="mailto:mcarrano@redhat.com" class="">mcarrano@redhat.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class="">Hi All,<br class=""><br class="">I am currently working on a design where I need an editable form and wanted to see what examples or patterns may already exist for this. Our current Forms pattern does not currently address this use case, but probably should. The requirement I have is that some users will only be able to view information on the form and others can view or edit, so there may be a need to switch between modes. I know this is a scenario that is fairly common, so wondering how you may be handling this in your applications.<br class=""><br class="">Thanks in advance for your feedback.<br class=""><br class="">Regards,<br class=""><br class="">Matt<br class=""><br class="">_______________________________________________<br class="">Patternfly mailing list<br class=""><a href="mailto:Patternfly@redhat.com" class="">Patternfly@redhat.com</a><br class="">https://www.redhat.com/mailman/listinfo/patternfly<br class=""></div></blockquote></div><br class=""><div class=""> <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;" class=""><div class="">---</div><div class="">Gabriel Cardoso</div><div class="">User Experience Designer @ Red Hat</div></div> </div> <br class=""></div></body></html>