+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 explain the overall effort required to port these gadgets? What needs to be done? Thanks. On Fri, Feb 26, 2016 at 12:42 PM, Lochana Ranaweera <[email protected]> wrote: > Hi all, > > This is regarding the HTTP Monitoring Dashboard for AS 6.0.0. It is to be > deployed as a collection of user preferred set of gadgets in the Dashboard > Server. > As of now, I have ported the* basic* HTTP monitoring functionality as > separate gadgets for DS. > > A typical HTTP monitoring gadget has the following structure: > > gadget-name > ├── css > ├── js > ├── fonts > ├── images > ├── index.xml > └── gadget.json > > What will be the best structure to version control thus created gadgets in > the given branch <https://github.com/wso2/product-as/tree/wso2as-6.0.0> > of AS 6.0.0? > Should it be in modules or should it be inside contents directory in the > distribution module? > The directory structure of the build for new AS 6.0.0 is given below: > > > > Appreciate your suggestions on this matter. > > Thanks and Regards, > -- > Lochana Ranaweera > Intern Software Engineer > WSO2 Inc: http://wso2.com > Blog: https://lochanaranaweera.wordpress.com/ > Mobile: +94716487055 <http://tel%2B716487055> > > -- *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
