> On Jan 28, 2025, at 2:07 PM, Richard Gaskin via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Bob Sneidar wrote: >> I want to present the client user with a list of the names of those profiles. >> If the user does not select a profile, either by clicking off the menu I pop >> up, or by hitting the escape key, then I notify the user that they must >> choose a profile. > > Have you considered a list in modal dialog? I have issues troubleshooting modal stacks so I avoid them if I can. > > This would allow a more spacious display for the list and the prompt, > prohibit proceeding without the necessary selection, make that necessity > clear in its prompt and initially-disabled confirmation button, and offer the > option of being entirely keyboard-navigable. Good points, and the keyboard navigation part is tempting. > > > But I'm also curious: > > What information does the user need to consider to make that choice, and what > would their decision tree look like? Service technicians would store two types of documents: Data files (text files, address book backups, clone data etc.) and Forms (PDFs of service forms presented to the customer.)
But this is the foundation to a more sophisticated document management system, where these storage profiles will be linked to document workflows. Things like Purchase Orders. AP and AR invoices, Sales Orders etc. The solution we currently use, Docuware that was supposed to supplant DocRecord is completely cloud based, and incredibly expensive, especially when we add the storage and extra user licenses we will need for all of our salespersons and accounting and executive staff. My ambitious goal is to create a system we control, and then if the company adopts it I can justify the licensing for the new LC product LC Create. But if I cannot demonstrate a viable product, I do not think I can sell the powers that be on the new licensing model. > > And are some choices better than others? Are there any that would be a > "wrong" choice? Any that would be a "best" choice? What are the > implications to the system when a suboptimal choice is made? The only suboptimal choice would be no choice. There has to be some indication of where the file needs to be stored on the server end. I don’t want to define a default because if you leave it up to end users to change the location profile from the default, the untrained and the unconcerned alike are just going to leave defaults as they are. There will be a point at which the user can cancel the file transfer before the payload gets sent. That being said, I will have to develop a mode to reassign a document in case of an error, and especially when the workflows begin to take shape. > > -- > Richard Gaskin > FourthWorld.com > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
