Charlotte Foust
charlotte.foust at gmail.com
Sat Sep 8 12:48:17 CDT 2012
I've used it when I need a quickie menu for apps that aren't deployed, i.e. for my own use. And I used it in the applications I've built under my latest contract, since they were never intended to be long-lived, but were transitional between old and new systems. I prefer to build my own menu forms, and I'd like to see yours. Charlotte On Sat, Sep 8, 2012 at 10:25 AM, Arthur Fuller <fuller.artful at gmail.com>wrote: > That's most interesting. Can you describe one of your own? How do you lay > out the, for want of a better word, tree? Do you begin with an equivalent > of the switchboard, or start with the most likely place to visit (such as > "Things to Attend To Today", whatever that might entail? > > I'm seriously curious about how you and others on this list open the given > app. I once presented an opening screen that paid attention to projects > marked "Incomplete", and my user objected vociferously, saying "I don't > want anyone to see what jobs I haven't completed!" An interesting take, > which I absorbed, and hence tailored the opening form to show clients and > jobs and let her decide. > > The switchboard is admittedly an easy way to provide a front end, but is > also so generic as to be somewhat pointless, in its generality. Who has a > better idea (and portable from app to app)? > > A. > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > > > Website: http://www.databaseadvisors.com > > >