Re: [Architecture] [Dev] Creating Gadgets for Web Application Statistics Monitoring Dashboard - Application Server 6.0.0

2016-03-02 Thread Udara Rathnayake
Hi All, Try to stick to the existing libraries within platform as much as possible(d3,vega,viz etc..). These are proven to provide all necessary functionalities to render gadget UIs. Regards, UdaraR On Wed, Mar 2, 2016 at 7:15 AM, Lochana Ranaweera wrote: > Hi Tharik, > >

Re: [Architecture] [Dev] Creating Gadgets for Web Application Statistics Monitoring Dashboard - Application Server 6.0.0

2016-02-29 Thread KasunG Gajasinghe
It seems these gadgets should directly call the DAS analytics API to get the summarized info. For the folder structure, may be we can create a top-level module called webapp-analytics and create the CApp there. If there are other artifacts other than the CApp, then we'll have to add the capp as a

Re: [Architecture] [Dev] Creating Gadgets for Web Application Statistics Monitoring Dashboard - Application Server 6.0.0

2016-02-26 Thread Tharik Kanaka
Hi Lochana, Are you going to use existing analytics API used in DAS? Apart from that what are the javascript chart libraries are you going to use for these gadgets? Regards, On Fri, Feb 26, 2016 at 3:46 PM, Lochana Ranaweera wrote: > > Hi KasunG, > > The final deliverable

Re: [Architecture] [Dev] Creating Gadgets for Web Application Statistics Monitoring Dashboard - Application Server 6.0.0

2016-02-26 Thread Lochana Ranaweera
Hi KasunG, The final deliverable of the dashboard will be a set of gadgets that can be deployed in the DS separately. It was suggested that ideally with the AS build the gadgets could be packed as a car file. As of now, the gadgets are working along with an API that provides the gadgets with

Re: [Architecture] [Dev] Creating Gadgets for Web Application Statistics Monitoring Dashboard - Application Server 6.0.0

2016-02-26 Thread KasunG Gajasinghe
+architecture Hi Lochana, Can you describe what is the final deliverable of the dashboard? Also, please explain briefly how the users are going to use these gadgets as well as all other dependencies these need. Based on that, we can figure out how the folder structure should be. Btw, can you