So my +1 was for this feature (note the comments). Not the inclusion of this to core UI. That was probably miscommunicated. I'm also -1 for including this in the core.
Well, right now only BAM has heavy use of gadgets, with around 40+ gadgets. So, until gadgets are used heavily inside of all products, this should not be included by default. And still, it can be in every product profile, outside of core. On Sat, Sep 17, 2011 at 6:26 AM, Nuwan Bandara <[email protected]> wrote: > Hi Tharindu, > > On Sat, Sep 17, 2011 at 2:12 AM, Tharindu Mathew <[email protected]>wrote: > >> Nuwan, can we make this available to whoever has the dashboard feature >> without increasing the core size? > > > Can be done, but not sure if that actually achieve our objective. my-idea > was to push this feature for platform wide UI, so developers can create > gadget with their own UI components and have them inside the JSPs across > other components. > > Regards, > /Nuwan > > >> >> >> On Friday, September 16, 2011, Afkham Azeez <[email protected]> wrote: >> > Please note that I would like to see some other modules which are in >> carbon core also moved out. So, please don't add anything new. >> > >> > ---- >> > Sent from my phone >> > >> > On Sep 16, 2011 11:51 PM, [email protected] wrote: >> >> We will have to think about how to properly implement this, but I'm >> sure it >> >> can be done. >> >> >> >> ---- >> >> Sent from my phone >> >> On Sep 16, 2011 10:13 PM, "Nuwan Bandara" <[email protected]> wrote: >> >>> Hi Azeez, >> >>> >> >>> On Fri, Sep 16, 2011 at 8:13 PM, Afkham Azeez <[email protected]> wrote: >> >>> >> >>>> -1 to increasing the distribution size. Big -1 to this addition. >> Adding >> >>>> everything to carbon core violates the component model. >> >>>> >> >>> I agree the bundle is bulky in Size, and doing our best to reduce its >> size >> >>> (discussion on* [carbon-dev]Shindig upgrading effort*) it was 20MB >> before >> >>> and we have managed to reduce it to 12MB. >> >>> >> >>> About the component model; is there another mechanism you suggest to >> have >> >>> this feature to be integrated with the carbon-core ui, the objective >> of >> >> this >> >>> feature is, that any UI component developer can add a gadget simply >> from a >> >>> tag, like we add properties etc. if we make this a separate component >> IMO >> >> we >> >>> cannot get the model working. >> >>> >> >>> Can you suggest the correct way in doing this if it violates the >> component >> >>> model. >> >>> >> >>> Regards, >> >>> /nuwan >> >>> >> >>>> ---- >> >>>> Sent from my phone >> >>>> On Sep 16, 2011 4:19 PM, "Nuwan Bandara" <[email protected]> wrote: >> >>>> > Hi All, >> >>>> > >> >>>> > We have done some work around gadget rendering, and we have >> developed a >> >>>> new >> >>>> > feature so that if you need a gadget in you page you do not need >> the >> >>>> > dashboard to show them. You can simply create a tag and add the >> gadget >> >>>> URL >> >>>> > and the UI part will be available in ur page. an example would be >> >>>> > >> >>>> > <c:gadget url="/foo.xml" height="100" width="100" >> class="gadget-style" >> >> /> >> >>>> > >> >>>> > once you add above tag you can place the gadget where ever you want >> in >> >>>> your >> >>>> > page. >> >>>> > >> >>>> > This feature can come in handy in many ways where you want to mix >> >> static >> >>>> and >> >>>> > dynamic information. We are working on revamping the system >> statistics >> >>>> page >> >>>> > with this new method just to demonstrate as a POC. >> >>>> > >> >>>> > However in-order to make this available we will have to add shindig >> a >> >>>> part >> >>>> > of carbon-core. Shindig is at the moment is 14.3MB and it will go >> down >> >>>> for >> >>>> > about 12MB with fixes to bundle plugin, hence this will increase >> the >> >> size >> >>>> of >> >>>> > the distribution in 12MBs. >> >>>> > >> >>>> > However I believe there are many advantages in having this as part >> of >> >> our >> >>>> > core UI framework. for an example Google it self is pushing this >> model >> >> in >> >>>> > almost all the pages they published recently [1]. I believe this >> >> feature >> >>>> can >> >>>> > be quite helpful for products like BPS, GREG and BAM directly. By >> >> having >> >>>> > this you can have functionalities like intercommunication between >> UI >> >>>> parts, >> >>>> > unified way to show analytics/statistics and any other dynamic >> content. >> >>>> > >> >>>> > comments and ideas welcome. >> >>>> > >> >>>> > [1] http://code.google.com/apis/opensocial/ >> >>>> > >> >>>> > -- >> >>>> > *Thanks & Regards, >> >>>> > >> >>>> > Nuwan Bandara >> >>>> > Senior Software Engineer >> >>>> > WSO2 Inc. | http://wso2.com >> >>>> > lean . enterprise . middleware >> >>>> > >> >>>> > http://nuwan.bandara.co >> >>>> > * >> >>>> > <http://www.nuwanbando.com/> >> >>>> >> >>>> _______________________________________________ >> >>> >> >> -- >> Regards, >> >> Tharindu >> >> blog: http://mackiemathew.com/ >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Thanks & Regards, > > Nuwan Bandara > Senior Software Engineer > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > > http://nuwan.bandara.co > * > <http://www.nuwanbando.com/> > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Regards, Tharindu blog: http://mackiemathew.com/
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
