Hi Azeez, >> >> The reason why a dashboard was added to DSS was to have some server >> related statistics as gadgets. But by the time it was released, these >> gadgets were not ready, but the samples were. So product was released with >> the samples for gadgets only. > > Rather than release it in a half baked state with an irrelevant view, it > would have been better to remove the dashboard. Nobody would have complained > about it :)
Now, the idea I was having for having the dashboard is for the user to write his own gadgets. Which is, not to just look at the gadgets that's there and forget about the dashboard, rather to use it as a means of customising the dashboard. As I see, in a dashboard like ESBs, it is simply duplicating the statistics information that is anyway available in the statistics under the Monitor section. And personally I think the non-gadget statistics is more nicer :) .. And so if you look at it, it is not specifically related to the ESB, but just general server information. So IMHO, simply having a data services related gadget sample seemed more suitable. Cheers, Anjana. > >> >> But having dashboard to show of the samples is wrong. But gadget component >> was lacking the functionality of dynamically adding/removing dashboards. >> Hence we could not add a dashboard when only samples are being added. >> BTW, this discussion on not deploying samples with a products was >> discussed on a different thread sometime ago & now most of the products do >> not deploy samples by default. >> /sumedha >> > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Anjana Fernando Software Engineer WSO2, Inc.; http://wso2.com lean.enterprise.middleware _______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
