There is an existing set but it takes a lot of time to get loaded so I just thought to first understand the base rule while selecting the components like -
There are 3 Tabs in the dashboard. While I click on the first tab, some graphs appears and on second tab, some different … As of now I can see 3 Tab sets are used, so is there correct? Or we can select something else which can take less time while loading it?
One Push button is there, when we click on it 1 drop down list and 2 Calendars comes to select the values. Is this correct? Or can we have better choice for this?
3 scoreboards are inserted with 3 labels. So whatever values are selected in the point 2, appears on these labels.
Point 2 and Point 3 are put in one rectangle.
Again in each tab, 6 scorecards are used and I can see for 2 tabs, the TEXT is same in scorecards, so can we use instead of having 18, can we have 12 scoreboards serving the purpose. Also do I need scorecards as they just haev headings for graphs…
These are some basic dashboard design components so I Just thought to get some idea about the components. It would really be great if someone can please guide me ?
Also help me in finding the documentation where I can read about the dashboard components?
There’s very little that is correct or incorrect - too many factors for somebody else to determine if there are better ways of doing what you do.
In your case, I’d get back to the users and get some basic requirements and priorities. Then I’d rebuild according to those, using what you have as a guideline. I’ve always found it’s better to start again than to change what you have, as xcelsius doesn’t like change and has a tendency to sulk in the corner!
Tabs are rumoured to be memory-hungry though I’ve not had problems with them myself.
However, as a gut check, I’d say you have too many components going on. And probably a few components that are not being used appropriately (am I understanding that you are using scorecards to effectively generate chart titles?). If I walked in and saw that, my first step as developer would be to look for ways to simplify the model.
It ultimately comes down to two things, though. One, is performance acceptable? Two, is the client satisfied that the requirements have been met? If you nail both of those, then the rest is just striving for perfection.
(BOB member since 2007-10-05)