You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@shindig.apache.org by Jordan Zimmerman <jo...@shop.com> on 2009/04/07 01:19:23 UTC

RE: http://cwiki.apache.org/SHINDIGxSITE/how-to-support-features-that-depend-on-gadgetsrpc.html

FYI - gadgets.window.setTitle() works without the gadget containing the
setRelayUrl() call. Is this expected? I was surprised by this. I haven't
tried other calls.

Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com 

SHOP*COMTM
Shop Smart, Save Big(tm)
www.shop.com

This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this 
message
immediately if this is an electronic communication.

Thank you.

Re: http://cwiki.apache.org/SHINDIGxSITE/how-to-support-features-that-depend-on-gadgetsrpc.html

Posted by Kevin Brown <et...@google.com>.

On Wed, Apr 8, 2009 at 10:52 AM, Jordan Zimmerman <jo...@shop.com> wrote:

> The spec is very thin on what the signature of the handler is:
> http://code.google.com/apis/opensocial/docs/0.7/reference/gadgets.rpc.ht
> ml#register<http://code.google.com/apis/opensocial/docs/0.7/reference/gadgets.rpc.ht%0Aml#register>
>
> I look into the code and it appears that "this.f" refers to the iframe
> window's name. Why the name? Wouldn't the iframe's ID be better? Also,
> why not include the module ID or the application ID?


The iframe ID is not accessible by the iframe itself.

We don't bother with other ids because the container can easily map these on
their own, and the size of the container -> gadget payload must be kept as
small as possible (hence the cryptic property names).


>
>
> I'd be happy to make these changes if you like.
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> SHOP*COMTM
> Shop Smart, Save Big(tm)
> www.shop.com
>
>
> -----Original Message-----
> From: Kevin Brown [mailto:etnu@google.com]
> Sent: Wednesday, April 08, 2009 10:24 AM
> To: shindig-dev@incubator.apache.org
> Subject: Re:
> http://cwiki.apache.org/SHINDIGxSITE/how-to-support-features-that-depend
> -on-gadgetsrpc.html<http://cwiki.apache.org/SHINDIGxSITE/how-to-support-features-that-depend%0A-on-gadgetsrpc.html>
>
> See documentation on the 'process' function in the source (
> http://svn.apache.org/viewvc/incubator/shindig/trunk/features/src/main/j
> avascript/features/rpc/rpc.js?revision=762984&view=markup<http://svn.apache.org/viewvc/incubator/shindig/trunk/features/src/main/j%0Aavascript/features/rpc/rpc.js?revision=762984&view=markup>
> )
>
> This should probably be moved to register to more closely match the
> calling
> API I suppose.
>
> On Wed, Apr 8, 2009 at 10:13 AM, Jordan Zimmerman <jo...@shop.com>
> wrote:
>
> > *bump*
> >
> > What are the values passed to the handler? How can I get the iframe ID
> > or any value that allows resolution to the iframe that posted the
> > message?
> >
> > Jordan Zimmerman
> > Principal Software Architect
> > 831.647.4712
> > 831.214.2990 (cell)
> > jordanz@shop.com
> >
> > SHOP*COMTM
> > Shop Smart, Save Big(tm)
> > www.shop.com
> >
> >
> > -----Original Message-----
> > From: Jordan Zimmerman [mailto:jordanz@shop.com]
> > Sent: Monday, April 06, 2009 5:11 PM
> > To: shindig-dev@incubator.apache.org
> > Subject: RE:
> >
> http://cwiki.apache.org/SHINDIGxSITE/how-to-support-features-that-depend
> >
> -on-gadgetsrpc.html<http://cwiki.apache.org/SHINDIGxSITE/how-to-support-
> features-that-depend%0A-on-gadgetsrpc.html<http://cwiki.apache.org/SHINDIGxSITE/how-to-support-%0Afeatures-that-depend%0A-on-gadgetsrpc.html>
> >
> >
> > How does the handler passed to gadgets.rpc.register() get context for
> > the gadget? i.e. how does it know which gadget on the page is the
> > caller? It seems there is a structure passed that has a few fields,
> but
> > none of them correspond to anything I'm familiar with. Getting the
> > application ID or module ID would be nice.
>
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this
> message
> immediately if this is an electronic communication.
>
> Thank you.
>

RE: Shindig working with Liferay now

Posted by astha <as...@gmail.com>.

Hi Tim,

Sorry for replying back late. Just got hooked up with few other things.

We have created the issue at Liferay JIRA and its corresponding
patch:http://issues.liferay.com/browse/LPS-3097
 
We have also attached a deployable war file along with this patch :
shindig-portlet.5.2.0.1.war
 
You can deploy this war as a plugin through Plugin Installation (Control
Panel -> Server -> Plugin Installation -> Install More Portlets -> Upload
File) in liferay. 
 
Once the war is deployed,you will be able to add this portlet through
clicking the 'Add Application' link in the menu. You will find the 'Shindig
Gadget Portlet' in category 'Sample'.
 
Yep, it is compatible with liferay 5.2.
 
We are waiting for the feedback and comments on the patch we submitted to
Liferay. Simultaneously we are working to make it compatible with the latest
version of Shindig and opensocial 0.8.Accordingly we will contribute the
updated version.

Let me know if you have further questions.

Thanks,
Astha
 


-----Original Message-----
From: Fisher, Tim [mailto:Tim.Fisher@compuware.com] 
Sent: Monday, May 04, 2009 6:40 PM
To: asthabhatnagar2008@gmail.com
Subject: RE: Shindig working with Liferay now

Astha,

Can you tell me where I can find the shindig-portlet for Liferay?

Also a couple of questions..

Currently, is it compatible with Liferay 5.2?

Any idea on when it will be compatible with the latest version of
Shindig and opensocial 0.8?

Tim


The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.

From: astha [mailto:asthabhatnagar2008@gmail.com] 
Sent: Friday, May 01, 2009 11:51 PM
To: shindig-dev@incubator.apache.org
Subject: Shindig working with Liferay now

Hi,

The shindig-portlet in Liferay provides the integration of liferay with
opensocial 0.7. Shindig code used for this is gadgets-svn-r648103.war.

The current shindig-portlet available in the Liferay svn trunk was not
rendering anything on deployment. We have tried to fix the issues,
enhanced the features and made it compatible with Liferay 5.2.0. So yes,
now we can run OpenSocial gadgets on Liferay :) With respect to this we
have also created the issue at Liferay JIRA and its corresponding patch:
http://issues.liferay.com/browse/LPS-3097

The roadmap item further is to make this compatible with the Shindig's
latest version.

Thanks,
Astha

Shindig working with Liferay now

Posted by astha <as...@gmail.com>.

Hi,

The shindig-portlet in Liferay provides the integration of liferay with
opensocial 0.7. Shindig code used for this is gadgets-svn-r648103.war.

The current shindig-portlet available in the Liferay svn trunk was not
rendering anything on deployment. We have tried to fix the issues, enhanced
the features and made it compatible with Liferay 5.2.0. So yes,  now we can
run OpenSocial gadgets on Liferay :)
With respect to this we have also created the issue at Liferay JIRA and its
corresponding patch: http://issues.liferay.com/browse/LPS-3097

The roadmap item further is to make this compatible with the Shindig's
latest version.

Thanks,
Astha

RE: Shindig, OpenSocial, and Portlets

Posted by "Fisher, Tim" <Ti...@compuware.com>.

Ian,

Thank you for the response and the very thoughtful comments.  Yes, I do
agree that all things being equal, it would make the most sense to not
use 168 and use a JavaScript layout manager.  However, we have an
existing 168 compliant portal product that we are trying to add open
social gadget support to.  Given that, I have been trying to determine
the best way of doing this.

What I've done so far I believe is equivalent to your "trivial"
solution.  I have an iFrame portlet that is loading a trimmed down
version of the sample container that is packaged with shindig.  This
results in a gadget being rendered in the iframe.  As you say, this is a
pretty trivial solution, but I'm not sure if it's the best solution.
I'm looking for other options that ideally do not result in a huge
amount of work.

Tim 

-----Original Message-----
From: Ian Boston [mailto:ianboston@googlemail.com] On Behalf Of Ian
Boston
Sent: Monday, April 13, 2009 3:57 PM
To: shindig-dev@incubator.apache.org
Subject: Re: Shindig, OpenSocial, and Portlets

Presenting a portlet in a gadget should be no problem, its a portal
layout with a single portlet hosted inside a gadget iframe, IMHO,
slightly pointless over a servlet (as thats all a single portlet on a
page is conceptually) but if the code is all written....

Presenting a gadget in a portlet, there are 3 flavors, one trivial two
quite hard.
Trivial is a portlet that contains a gadget iframe, from the 168 point
of view this rather breaks the whole point of 168 which is a flat page
with no iframes.

Presenting a cajoled gadget inside a flat portlet is going to be hard as
168 will be trying to control the page lifecycle and the cajoed gadget
will also be expecting no page refresh.

Even harder would be to make a gadget obey the 168 page lifecycle.

IMVHO, it would make far more sense to make the portal layout manager
javascript and not use 168, then Gadgets and the 168 spec wouldn't be
fighting for control of the page lifecycle.

Ian
On 13 Apr 2009, at 09:45, <vi...@wipro.com>
<vinod.pillai@wipro.com 
 > wrote:

> Tim,
>
> This is an interesting problem :). While you are trying to host  
> gadgets
> using a Portal Server (front) over Shindig (back), I'm exploring the
> possibility of using Shindig (front) over Portal Server(back) i.e.
> exposing everything as gadgets (web pages, applications and portlets).
> Has anyone here written a portlet-gadget bridge or knows how to  
> present
> any JSR 168/286 portlet through a gadget (URL gadget?).
>
> Regards,
> Vinod
>
> -----Original Message-----
> From: Hafiz A Haq [mailto:hafizahaq@gmail.com]
> Sent: Saturday, April 11, 2009 1:33 PM
> To: shindig-dev@incubator.apache.org
> Subject: Re: Shindig, OpenSocial, and Portlets
>
> I am integrating shindig into gxt based portlets, but it uses gwt .
>
> I am not sure if it would help you in anyway.
>
> Thanks and Regards,
> Hafiz
>
> 2009/4/10 Fisher, Tim <Ti...@compuware.com>
>
>> Thanks for the response...   I'm told that the work Liferay did to
>> integrate Shindig is dated now and probably won't work with the most
> recent
>> version of Shindig.  The code is supposed to be in the Liferay SVN
>> repository, but I'm having a hard time even finding the code they
> wrote to
>> implement a Shindig portlet.
>>
>> I thought maybe someone would have some input even on integrating
> Shindig
>> into any portlet container.
>>
>> Tim
>>
>> -----Original Message-----
>> From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
>> Sent: Wednesday, April 08, 2009 5:54 PM
>> To: shindig-dev@incubator.apache.org
>> Subject: Re: Shindig, OpenSocial, and Portlets
>>
>> IIRC Liferay adds recently a new shindig portlet plugin. I guess it
> will be
>> your first starting point :)
>>
>> Cheers,
>>
>> Vincent
>>
>> 2009/4/8 Fisher, Tim <Ti...@compuware.com>:
>>> Has anyone rendered an OpenSocial gadget within a Liferay Portlet?
>>> Liferay portlets are JSR 168 & 286 compliant, so even if you
>>> integrated OpenSocial into another portlet container that would be
>>> interesting to me.  I'm thinking the solution would include Liferay
>>> rendering the portlet which then calls Shindig to render the gadget.
>>>
>>> Anyone with any relevant experience doing this?
>>>
>>> Tim
>>> The contents of this e-mail are intended for the named addressee
> only. It
>> contains information that may be confidential. Unless you are the
> named
>> addressee or an authorized designee, you may not copy or use it, or
> disclose
>> it to anyone else. If you received it in error please notify us
> immediately
>> and then destroy it.
>>>
>>
>>
>
>
> --
> He who asks is a fool for five minutes, but he who does not ask  
> remains
> a
> fool forever.
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any  
> attachments to this message are intended for the exclusive use of  
> the addressee(s) and may contain proprietary, confidential or  
> privileged information. If you are not the intended recipient, you  
> should not disseminate, distribute or copy this e-mail. Please  
> notify the sender immediately and destroy all copies of this message  
> and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The  
> recipient should check this email and any attachments for the  
> presence of viruses. The company accepts no liability for any damage  
> caused by any virus transmitted by this email.
>
> www.wipro.com

Re: Shindig, OpenSocial, and Portlets

Posted by Ian Boston <ie...@tfd.co.uk>.

Presenting a portlet in a gadget should be no problem, its a portal  
layout with a single portlet hosted inside a gadget iframe, IMHO,  
slightly pointless over a servlet (as thats all a single portlet on a  
page is conceptually) but if the code is all written....

Presenting a gadget in a portlet, there are 3 flavors, one trivial two  
quite hard.
Trivial is a portlet that contains a gadget iframe, from the 168 point  
of view this rather breaks the whole point of 168 which is a flat page  
with no iframes.

Presenting a cajoled gadget inside a flat portlet is going to be hard  
as 168 will be trying to control the page lifecycle and the cajoed  
gadget will also be expecting no page refresh.

Even harder would be to make a gadget obey the 168 page lifecycle.

IMVHO, it would make far more sense to make the portal layout manager  
javascript and not use 168, then Gadgets and the 168 spec wouldn't be  
fighting for control of the page lifecycle.

Ian
On 13 Apr 2009, at 09:45, <vi...@wipro.com> <vinod.pillai@wipro.com 
 > wrote:

> Tim,
>
> This is an interesting problem :). While you are trying to host  
> gadgets
> using a Portal Server (front) over Shindig (back), I'm exploring the
> possibility of using Shindig (front) over Portal Server(back) i.e.
> exposing everything as gadgets (web pages, applications and portlets).
> Has anyone here written a portlet-gadget bridge or knows how to  
> present
> any JSR 168/286 portlet through a gadget (URL gadget?).
>
> Regards,
> Vinod
>
> -----Original Message-----
> From: Hafiz A Haq [mailto:hafizahaq@gmail.com]
> Sent: Saturday, April 11, 2009 1:33 PM
> To: shindig-dev@incubator.apache.org
> Subject: Re: Shindig, OpenSocial, and Portlets
>
> I am integrating shindig into gxt based portlets, but it uses gwt .
>
> I am not sure if it would help you in anyway.
>
> Thanks and Regards,
> Hafiz
>
> 2009/4/10 Fisher, Tim <Ti...@compuware.com>
>
>> Thanks for the response...   I'm told that the work Liferay did to
>> integrate Shindig is dated now and probably won't work with the most
> recent
>> version of Shindig.  The code is supposed to be in the Liferay SVN
>> repository, but I'm having a hard time even finding the code they
> wrote to
>> implement a Shindig portlet.
>>
>> I thought maybe someone would have some input even on integrating
> Shindig
>> into any portlet container.
>>
>> Tim
>>
>> -----Original Message-----
>> From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
>> Sent: Wednesday, April 08, 2009 5:54 PM
>> To: shindig-dev@incubator.apache.org
>> Subject: Re: Shindig, OpenSocial, and Portlets
>>
>> IIRC Liferay adds recently a new shindig portlet plugin. I guess it
> will be
>> your first starting point :)
>>
>> Cheers,
>>
>> Vincent
>>
>> 2009/4/8 Fisher, Tim <Ti...@compuware.com>:
>>> Has anyone rendered an OpenSocial gadget within a Liferay Portlet?
>>> Liferay portlets are JSR 168 & 286 compliant, so even if you
>>> integrated OpenSocial into another portlet container that would be
>>> interesting to me.  I'm thinking the solution would include Liferay
>>> rendering the portlet which then calls Shindig to render the gadget.
>>>
>>> Anyone with any relevant experience doing this?
>>>
>>> Tim
>>> The contents of this e-mail are intended for the named addressee
> only. It
>> contains information that may be confidential. Unless you are the
> named
>> addressee or an authorized designee, you may not copy or use it, or
> disclose
>> it to anyone else. If you received it in error please notify us
> immediately
>> and then destroy it.
>>>
>>
>>
>
>
> --
> He who asks is a fool for five minutes, but he who does not ask  
> remains
> a
> fool forever.
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any  
> attachments to this message are intended for the exclusive use of  
> the addressee(s) and may contain proprietary, confidential or  
> privileged information. If you are not the intended recipient, you  
> should not disseminate, distribute or copy this e-mail. Please  
> notify the sender immediately and destroy all copies of this message  
> and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The  
> recipient should check this email and any attachments for the  
> presence of viruses. The company accepts no liability for any damage  
> caused by any virus transmitted by this email.
>
> www.wipro.com

RE: Shindig, OpenSocial, and Portlets

Posted by vi...@wipro.com.

Tim, 

This is an interesting problem :). While you are trying to host gadgets
using a Portal Server (front) over Shindig (back), I'm exploring the
possibility of using Shindig (front) over Portal Server(back) i.e.
exposing everything as gadgets (web pages, applications and portlets).
Has anyone here written a portlet-gadget bridge or knows how to present
any JSR 168/286 portlet through a gadget (URL gadget?).

Regards,
Vinod

-----Original Message-----
From: Hafiz A Haq [mailto:hafizahaq@gmail.com] 
Sent: Saturday, April 11, 2009 1:33 PM
To: shindig-dev@incubator.apache.org
Subject: Re: Shindig, OpenSocial, and Portlets

I am integrating shindig into gxt based portlets, but it uses gwt .

I am not sure if it would help you in anyway.

Thanks and Regards,
Hafiz

2009/4/10 Fisher, Tim <Ti...@compuware.com>

> Thanks for the response...   I'm told that the work Liferay did to
> integrate Shindig is dated now and probably won't work with the most
recent
> version of Shindig.  The code is supposed to be in the Liferay SVN
> repository, but I'm having a hard time even finding the code they
wrote to
> implement a Shindig portlet.
>
> I thought maybe someone would have some input even on integrating
Shindig
> into any portlet container.
>
> Tim
>
> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> Sent: Wednesday, April 08, 2009 5:54 PM
> To: shindig-dev@incubator.apache.org
> Subject: Re: Shindig, OpenSocial, and Portlets
>
> IIRC Liferay adds recently a new shindig portlet plugin. I guess it
will be
> your first starting point :)
>
> Cheers,
>
> Vincent
>
> 2009/4/8 Fisher, Tim <Ti...@compuware.com>:
> > Has anyone rendered an OpenSocial gadget within a Liferay Portlet?
> > Liferay portlets are JSR 168 & 286 compliant, so even if you
> > integrated OpenSocial into another portlet container that would be
> > interesting to me.  I'm thinking the solution would include Liferay
> > rendering the portlet which then calls Shindig to render the gadget.
> >
> > Anyone with any relevant experience doing this?
> >
> > Tim
> > The contents of this e-mail are intended for the named addressee
only. It
> contains information that may be confidential. Unless you are the
named
> addressee or an authorized designee, you may not copy or use it, or
disclose
> it to anyone else. If you received it in error please notify us
immediately
> and then destroy it.
> >
>
>


-- 
He who asks is a fool for five minutes, but he who does not ask remains
a
fool forever.

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com

Re: Shindig, OpenSocial, and Portlets

Posted by Hafiz A Haq <ha...@gmail.com>.

I am integrating shindig into gxt based portlets, but it uses gwt .

I am not sure if it would help you in anyway.

Thanks and Regards,
Hafiz

2009/4/10 Fisher, Tim <Ti...@compuware.com>

> Thanks for the response...   I'm told that the work Liferay did to
> integrate Shindig is dated now and probably won't work with the most recent
> version of Shindig.  The code is supposed to be in the Liferay SVN
> repository, but I'm having a hard time even finding the code they wrote to
> implement a Shindig portlet.
>
> I thought maybe someone would have some input even on integrating Shindig
> into any portlet container.
>
> Tim
>
> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> Sent: Wednesday, April 08, 2009 5:54 PM
> To: shindig-dev@incubator.apache.org
> Subject: Re: Shindig, OpenSocial, and Portlets
>
> IIRC Liferay adds recently a new shindig portlet plugin. I guess it will be
> your first starting point :)
>
> Cheers,
>
> Vincent
>
> 2009/4/8 Fisher, Tim <Ti...@compuware.com>:
> > Has anyone rendered an OpenSocial gadget within a Liferay Portlet?
> > Liferay portlets are JSR 168 & 286 compliant, so even if you
> > integrated OpenSocial into another portlet container that would be
> > interesting to me.  I'm thinking the solution would include Liferay
> > rendering the portlet which then calls Shindig to render the gadget.
> >
> > Anyone with any relevant experience doing this?
> >
> > Tim
> > The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or disclose
> it to anyone else. If you received it in error please notify us immediately
> and then destroy it.
> >
>
>


-- 
He who asks is a fool for five minutes, but he who does not ask remains a
fool forever.

RE: Shindig, OpenSocial, and Portlets

Posted by "Fisher, Tim" <Ti...@compuware.com>.

Thanks for the response...   I'm told that the work Liferay did to integrate Shindig is dated now and probably won't work with the most recent version of Shindig.  The code is supposed to be in the Liferay SVN repository, but I'm having a hard time even finding the code they wrote to implement a Shindig portlet.

I thought maybe someone would have some input even on integrating Shindig into any portlet container.

Tim 

-----Original Message-----
From: Vincent Siveton [mailto:vincent.siveton@gmail.com] 
Sent: Wednesday, April 08, 2009 5:54 PM
To: shindig-dev@incubator.apache.org
Subject: Re: Shindig, OpenSocial, and Portlets

IIRC Liferay adds recently a new shindig portlet plugin. I guess it will be your first starting point :)

Cheers,

Vincent

2009/4/8 Fisher, Tim <Ti...@compuware.com>:
> Has anyone rendered an OpenSocial gadget within a Liferay Portlet?
> Liferay portlets are JSR 168 & 286 compliant, so even if you 
> integrated OpenSocial into another portlet container that would be 
> interesting to me.  I'm thinking the solution would include Liferay 
> rendering the portlet which then calls Shindig to render the gadget.
>
> Anyone with any relevant experience doing this?
>
> Tim
> The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
>

Re: Shindig, OpenSocial, and Portlets

Posted by Vincent Siveton <vi...@gmail.com>.

IIRC Liferay adds recently a new shindig portlet plugin. I guess it
will be your first starting point :)

Cheers,

Vincent

2009/4/8 Fisher, Tim <Ti...@compuware.com>:
> Has anyone rendered an OpenSocial gadget within a Liferay Portlet?
> Liferay portlets are JSR 168 & 286 compliant, so even if you integrated
> OpenSocial into another portlet container that would be interesting to
> me.  I'm thinking the solution would include Liferay rendering the
> portlet which then calls Shindig to render the gadget.
>
> Anyone with any relevant experience doing this?
>
> Tim
> The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
>

Shindig, OpenSocial, and Portlets

Posted by "Fisher, Tim" <Ti...@compuware.com>.

Has anyone rendered an OpenSocial gadget within a Liferay Portlet?
Liferay portlets are JSR 168 & 286 compliant, so even if you integrated
OpenSocial into another portlet container that would be interesting to
me.  I'm thinking the solution would include Liferay rendering the
portlet which then calls Shindig to render the gadget.

Anyone with any relevant experience doing this?

Tim
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.