How would you prefer to keep the screen elements which are rarely useful in the modules/applications/screens?
Edit Delete Ban
Most of the time while working with heavy data intensive application I have encountered that there is 20 to 30% of the modules/webparts/portlates/functionality are rarely useful for the end-users in most of the applications for example elements like News, Article, Record Summery, Archive Records, User Summery, Report Summery, etc..
They are defiantly useful for the user to make some business decision while accessing that module or page but they still occupying area on screens and therefore designer end-up compromising business critical data/fields on the screen for the information which is rarely or occasionally useful for end-users.
I have my way to handle this situation but I want to understand how are you handling this, let me evaluate your methods with mine and I am sure I will improve a lot.
Thank you very much for your suggestions well in advance.
Erniwati Fordham
0 Reputation points
Posted 2009/12/02 @ 06:47AM with
Dock-able panels work ok for me, I stole the idea from Adobe, its the way Photoshop arranges all the extra panels/windows. such as history or layers. Panels can be stacked, minimized or hidden according to your needs
Gilbert Midonnet
3 Reputation points
Posted 2010/03/08 @ 09:08AM with
Dock-able panels are good for expert users, people who are repeat users, such as in an intranet. I found that confused many users.
I worked on several real estate sites that had much rarely-used-but-important information which were satisfied by “more” links.
I would need more information from the OP to give a better explanation else all I could say are generic, not very useful answers such as: “place the info in the footer.”