-1 to increasing the distribution size. Big -1 to this addition. Adding
everything to carbon core violates the component model.

----
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/>
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to