5/17/2023 0 Comments Switchup clone![]() ![]() An existing file can be browsed to and opened, in the style of an Open dialogue.This is a different convention used by some editors where it makes sense. Is this an export action, wherein a new copy is saved but the old copy is kept open? Is this something where a new duplicate document is opened (without saving)? Is this an in-place clone action, where you're cloning something within the record? An alternate pattern: "Create new from existing file" The idea of "Clone" and "Create Copy" is pretty clear - it's just unclear what will happen with the copy/clone. If you use it, you're communicating to your users exactly what's going on unambiguously. That is exactly what the Save As feature is expected to do. The process in using this feature sounds like it is to: ![]() (* the wording/label should probably be improved) Create new record (with sample data and detailed help) *.That way you know when a field is really meant to be filled-in. And you could also provide a warning for required fields that are not filled in.Īn alternative could be to optionally start with a record containing example data, or, maybe even better, a form with more detailed help/examples and placeholders. If the fields were empty from the start, the fields the user doesn’t want to edit stay empty (instead of filled in with wrong data). Users might forget (or don’t bother) to edit all fields, which would result in falsified data. In a database context, it could be used to export/save a specific record in a file.īut I think in general (→ there might be cases where this doesn’t apply) it’s not a good idea to clone an existing record to add a new one. I wouldn’t use this term for a database record which (probably) is only part of a file. I think that Save as … should always have a file as result. It looks like we will allow users to modify some of the values as part of creating the new record. That will decide which answer gets accepted. When I hear "save as", I think of documents, not database records. I'm leaning toward "Clone", but I don't have a reason other than it 'feels' more right to me than "Save As". What do you think would be the best label for this button, and why? ![]() In general, it is not appropriate for there to be two identical records in the database.īut we are not sure how to label the button for doing this. The main purpose of creating a copy is to use the original record as a starting point for a different record. We are now developing a feature whereby a user can create a record that is a copy of another. The main purpose of the GUI is for creating and editing these records. We have a system where a user can view database records in a GUI application. ![]()
0 Comments
Leave a Reply. |