<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Gadgets and Widgets as an alternative to Portlets</title>
	<atom:link href="http://apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/feed/" rel="self" type="application/rss+xml" />
	<link>http://apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/</link>
	<description>Random Thoughts</description>
	<lastBuildDate>Mon, 05 Dec 2011 13:29:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Ariel Roberge</title>
		<link>http://apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/#comment-4459</link>
		<dc:creator><![CDATA[Ariel Roberge]]></dc:creator>
		<pubDate>Wed, 18 Feb 2009 15:01:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/#comment-4459</guid>
		<description><![CDATA[Lars,

If my reading of the standard is right JSR268 adresses the inter portlet communications issues. This is an interesting advantage in favore of portlets to build more interactive portal apps in the near future bases on real standards, I for one believe portlets and Widgets/Gadgets can co-exits. It is a question of using the right tool for the job.]]></description>
		<content:encoded><![CDATA[<p>Lars,</p>
<p>If my reading of the standard is right JSR268 adresses the inter portlet communications issues. This is an interesting advantage in favore of portlets to build more interactive portal apps in the near future bases on real standards, I for one believe portlets and Widgets/Gadgets can co-exits. It is a question of using the right tool for the job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PCM.Blog &#187; Goodbye 2008, Welcome 2009</title>
		<link>http://apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/#comment-4458</link>
		<dc:creator><![CDATA[PCM.Blog &#187; Goodbye 2008, Welcome 2009]]></dc:creator>
		<pubDate>Tue, 30 Dec 2008 13:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/#comment-4458</guid>
		<description><![CDATA[[...] Widgets and Gadgets have been popular for quite sometime.&#160;Some products&#160;had gadgets much before portlet spec.&#160;I am sure many people have seen examples of counters, ad banners etc which are essentially widgets only. However, there is a considerable interest now in using these within the enterprises for more sophisticated portal like applications. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Widgets and Gadgets have been popular for quite sometime.&nbsp;Some products&nbsp;had gadgets much before portlet spec.&nbsp;I am sure many people have seen examples of counters, ad banners etc which are essentially widgets only. However, there is a considerable interest now in using these within the enterprises for more sophisticated portal like applications. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karthick</title>
		<link>http://apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/#comment-4457</link>
		<dc:creator><![CDATA[Karthick]]></dc:creator>
		<pubDate>Mon, 15 Dec 2008 15:06:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/#comment-4457</guid>
		<description><![CDATA[Apoorv,

Will Gadgets and Widgets be a boon for start-up firms who don&#039;t have enough capital ? Just to see the market response a startup firm can build a quick portal * like * applications. And based on the response they can go for a full fledged portal implementation. This way a firm need not invest more on the Portals when they are skeptical about the responses which they get from the market.

Here is one article on building cost effective websites using blogs and widgets

http://blogsbyshyam.blogspot.com/2008/04/cost-effective-website-using-blogs-and.html

And below is a start-up&#039;s website which is built with widgets.

http://www.360Inn.com

Regards
Karthick]]></description>
		<content:encoded><![CDATA[<p>Apoorv,</p>
<p>Will Gadgets and Widgets be a boon for start-up firms who don&#8217;t have enough capital ? Just to see the market response a startup firm can build a quick portal * like * applications. And based on the response they can go for a full fledged portal implementation. This way a firm need not invest more on the Portals when they are skeptical about the responses which they get from the market.</p>
<p>Here is one article on building cost effective websites using blogs and widgets</p>
<p><a href="http://blogsbyshyam.blogspot.com/2008/04/cost-effective-website-using-blogs-and.html" rel="nofollow">http://blogsbyshyam.blogspot.com/2008/04/cost-effective-website-using-blogs-and.html</a></p>
<p>And below is a start-up&#8217;s website which is built with widgets.</p>
<p><a href="http://www.360Inn.com" rel="nofollow">http://www.360Inn.com</a></p>
<p>Regards<br />
Karthick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apoorv</title>
		<link>http://apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/#comment-4456</link>
		<dc:creator><![CDATA[Apoorv]]></dc:creator>
		<pubDate>Sat, 13 Dec 2008 09:12:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/#comment-4456</guid>
		<description><![CDATA[Thanks Lars and Kingshuk for dropping by. You bring in some important points.]]></description>
		<content:encoded><![CDATA[<p>Thanks Lars and Kingshuk for dropping by. You bring in some important points.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kingshuk</title>
		<link>http://apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/#comment-4455</link>
		<dc:creator><![CDATA[Kingshuk]]></dc:creator>
		<pubDate>Mon, 08 Dec 2008 05:04:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/#comment-4455</guid>
		<description><![CDATA[Apoorv, I mostly agree with what you say except for the fact that I am more excited about the gadget world - pretty much like Lars. I like the Gadget world more because of the relative ease in pulling together a decentalized architecture involving Gadgets.  While WSRPv2 affords some of that in the conventional Portlet world, we have spent quite a bit of time making that work while experimenting with leading Portal servers of today. In contrast, we liked our experience with Apache Shindig server while creating Wipro Web2Works. If you build your own Gadget Manager, Layout Manager and Security Manager on top of Shindig, you can have a Gadget container that can truly match any good Portal server. That said, you are so correct that gadget world lacks maturity. Security could be its Achilles heel - especially when you are trying to mashup Gadgets hosted on servers spread around the world. Gadget certification itself can be an interesting service area. On the problem of Inter-Gadget/Portlet  communication, I think that the solution is not easily forthcoming, if are focusing on visually mashup of  presentation nuggets - all on a browser, WYSIWIG. Firstly we need to evolve a metadata representation framework (may be some semantic agent) that can introspect a Gadget and discover the Mashable parts.Secondly we need to think of a visual interface that allows those Mashable parts of different Gadgets come together based on simple user intent. It is the constraint of human imagination that impedes us most in Visual Mashup interface construction.]]></description>
		<content:encoded><![CDATA[<p>Apoorv, I mostly agree with what you say except for the fact that I am more excited about the gadget world &#8211; pretty much like Lars. I like the Gadget world more because of the relative ease in pulling together a decentalized architecture involving Gadgets.  While WSRPv2 affords some of that in the conventional Portlet world, we have spent quite a bit of time making that work while experimenting with leading Portal servers of today. In contrast, we liked our experience with Apache Shindig server while creating Wipro Web2Works. If you build your own Gadget Manager, Layout Manager and Security Manager on top of Shindig, you can have a Gadget container that can truly match any good Portal server. That said, you are so correct that gadget world lacks maturity. Security could be its Achilles heel &#8211; especially when you are trying to mashup Gadgets hosted on servers spread around the world. Gadget certification itself can be an interesting service area. On the problem of Inter-Gadget/Portlet  communication, I think that the solution is not easily forthcoming, if are focusing on visually mashup of  presentation nuggets &#8211; all on a browser, WYSIWIG. Firstly we need to evolve a metadata representation framework (may be some semantic agent) that can introspect a Gadget and discover the Mashable parts.Secondly we need to think of a visual interface that allows those Mashable parts of different Gadgets come together based on simple user intent. It is the constraint of human imagination that impedes us most in Visual Mashup interface construction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars Trieloff</title>
		<link>http://apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/#comment-4454</link>
		<dc:creator><![CDATA[Lars Trieloff]]></dc:creator>
		<pubDate>Fri, 05 Dec 2008 22:56:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2008/12/05/gadgets-and-widgets-as-an-alternative-to-portlets/#comment-4454</guid>
		<description><![CDATA[I am much more optimistic that gadgets will replace portlets in most scenarios. On the one hand, with OpenSocial there is a gagdet standard that is getting traction, which makes it an attractive development platform, on the other hand does Apache Shindig provide a low-cost way of integrating this feature in your application, which means gadget containers will start popping up where portlet containers would be way to heavyweight. As for the missing inter-gadget communication: this is something that is also missing from portlet standards and we have found ways to cope with it.]]></description>
		<content:encoded><![CDATA[<p>I am much more optimistic that gadgets will replace portlets in most scenarios. On the one hand, with OpenSocial there is a gagdet standard that is getting traction, which makes it an attractive development platform, on the other hand does Apache Shindig provide a low-cost way of integrating this feature in your application, which means gadget containers will start popping up where portlet containers would be way to heavyweight. As for the missing inter-gadget communication: this is something that is also missing from portlet standards and we have found ways to cope with it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

