On Mon, Sep 19, 2011 at 2:47 PM, Nuwan Bandara <[email protected]> wrote:

>
>> I think the problems are really clear and crystal. The biggest is the
>> devlopment effort. Then I get this question of why does it need to go though
>> a server side component at all for many cases, where the browser can do it
>> completely and cleanly with JS. And with the second point, again comes the
>> ease of development, all that you want is to Google, and there is enough
>> support around on how to write with JQuery. So what does it give me as added
>> advantage to use Shinding here and why is it better? Gadget repo? Gadget
>> communication? Gadget security?
>>
>
> I get your point :) but I believe a person who is willing to google a bit
> and find some nice jquery plugins/mechanisms wont find any difference in
> writing a gadget. It is no deference in writing a webpage with javascript
> and writing a gadget. you can simply ignor all the features that a gadget
> offer and simply write the web page as a gadget.
>
> So IMO a gadget is something that gives more than some web content. It is
> dynamic, portable, and give other benefits as you specified. So I see no
> defferent in using a different dashboard solution for other products when
> you can do the same thing with an equal effort.
>

+1 - there's no work difference between writing a gadget and a writing a
pure JS UI bit: The gadget code can simply do exactly that.

The advantage is that the gadget is reusable (by design), is a standard, can
be part of a repo of gadgets to be shared in other places etc. etc.. The
main reason we're not seeing those benefits right now is because our gadgets
are not cool enough :). Too much flash will do that to you.

Sanjiva.
-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/

Lean . Enterprise . Middleware
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to