Is apache shindig mature enough ?
17 views
Skip to first unread message
frougeot
Dec 9, 2009, 10:26:46 AM12/9/09
to Talk about Widgets
What is to your point of view the maturity of apache Shindig, is it
now realistic to integrate it into a web portal 2.0 site ?
What are the difficulties that we may encounter ?
Can we consider that integrating Shindig with an OSGi server, or even
apache Sling, may result in a good practive to build a next generation
portal application, that help us to forget the nightmare of JSR 168
portal ?
Is there any serious competitor to Shindig ?
now realistic to integrate it into a web portal 2.0 site ?
What are the difficulties that we may encounter ?
Can we consider that integrating Shindig with an OSGi server, or even
apache Sling, may result in a good practive to build a next generation
portal application, that help us to forget the nightmare of JSR 168
portal ?
Is there any serious competitor to Shindig ?
Evgeny Bogdanov
Dec 10, 2009, 3:36:47 AM12/10/09
to Talk about Widgets
Both java and php versions install like a dream.
Now I am trying to connect our social database to it,
it seems as it is quite straight forward ...
To see the source of an example social application that uses shindig,
you could try to install partuza:
it is a social application that uses shindig to render gadgets.
Now I am trying to connect our social database to it,
it seems as it is quite straight forward ...
To see the source of an example social application that uses shindig,
you could try to install partuza:
it is a social application that uses shindig to render gadgets.
Scott Wilson
Dec 10, 2009, 3:44:56 AM12/10/09
to talk-abou...@googlegroups.com
I think Shindig v1.1 is pretty stable, and ready to use in production.
The main issues are around configuration (still tricky and with lots
of settings in odd places) and the backend data integration (SPI),
which is a bit arcane unless you're using something already designed
around it like Partuza.
The main issues are around configuration (still tricky and with lots
of settings in odd places) and the backend data integration (SPI),
which is a bit arcane unless you're using something already designed
around it like Partuza.
Apache Wookie is still in pre-release, but should be released in Q1,
and handles W3C Widgets. Its not really a competitor as such as you
can use both Wookie+Shindig as an integrated widget engine. I know at
least one company using Wookie as part of a JetSpeed solution as a
replacement for traditional portlets in the manner you're suggesting.
S
> --
>
> You received this message because you are subscribed to the Google
> Groups "Talk about Widgets" group.
> To post to this group, send email to talk-abou...@googlegroups.com
> .
> To unsubscribe from this group, send email to talk-about-widg...@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/talk-about-widgets?hl=en
> .
>
>
Ivan Zuzak
Dec 10, 2009, 5:03:49 AM12/10/09
to Talk about Widgets
We built a prototype widget composition platform on top of Shindig
( http://161.53.65.222:8080/geppeto/index.html ) and it was pretty-
much quick and painless - it's mature for production-level projects,
stable and a fair number of projects/people are now using it so there
is a supporting community at hand.
Cheers,
Ivan
( http://161.53.65.222:8080/geppeto/index.html ) and it was pretty-
much quick and painless - it's mature for production-level projects,
stable and a fair number of projects/people are now using it so there
is a supporting community at hand.
Cheers,
Ivan
Reply all
Reply to author
Forward
0 new messages