On Tue, Jan 25, 2011 at 1:56 PM, Afkham Azeez <az...@wso2.com> wrote:
> > > On Tue, Jan 25, 2011 at 12:19 AM, Anjana Fernando <anj...@wso2.com> wrote: > >> 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 >> > > Yes, I also think the non-gadget view was much nicer and much more > readable. The thing is, the gadget UIs were simply added to these management > console just for the sake of having a Gadget based UI, not because of any > real requirement. > Yes , We have decided to remove Gadget UI from upcoming ESB release because of this reason. Plan is to make it a optional feature. In a real deployment ESB dashboard becomes really annoying for users because it takes ages to load gadgets and UI is stucked until that. > > >> 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 >> > Carbon-dev@wso2.org >> > 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 >> Carbon-dev@wso2.org >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > > -- > *Afkham Azeez* > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > * > * > *Member; Apache Software Foundation; > **http://www.apache.org/*<http://www.apache.org/> > * > email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Thanks, Miyuru
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
