You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Paul Lindner (JIRA)" <ji...@apache.org> on 2008/03/15 22:54:26 UTC
[jira] Created: (SHINDIG-132) Provide a way for container specific
views to gracefully degrade to well-known views.
Provide a way for container specific views to gracefully degrade to well-known views.
-------------------------------------------------------------------------------------
Key: SHINDIG-132
URL: https://issues.apache.org/jira/browse/SHINDIG-132
Project: Shindig
Issue Type: Improvement
Reporter: Paul Lindner
Many containers may want to implement custom views. However they should not have to force developers to provide these views if an acceptable fallback view is available.
An example of this is the hi5 preview view, which will cause display errors for applications that have explicit profile and canvas views, but do not have a Content section without any view definition.
I propose that we provide a way to specify a fallback view by adding configuration to syndicators.js which will be considered during the rendering process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-132) Provide a way for container specific
views to gracefully degrade to well-known views.
Posted by "Paul Lindner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Lindner updated SHINDIG-132:
---------------------------------
Component/s: Gadgets Server - Java
> Provide a way for container specific views to gracefully degrade to well-known views.
> -------------------------------------------------------------------------------------
>
> Key: SHINDIG-132
> URL: https://issues.apache.org/jira/browse/SHINDIG-132
> Project: Shindig
> Issue Type: Improvement
> Components: Gadgets Server - Java
> Reporter: Paul Lindner
>
> Many containers may want to implement custom views. However they should not have to force developers to provide these views if an acceptable fallback view is available.
> An example of this is the hi5 preview view, which will cause display errors for applications that have explicit profile and canvas views, but do not have a Content section without any view definition.
> I propose that we provide a way to specify a fallback view by adding configuration to syndicators.js which will be considered during the rendering process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-132) Provide a way for container
specific views to gracefully degrade to well-known views.
Posted by "Kevin Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579126#action_12579126 ]
Kevin Brown commented on SHINDIG-132:
-------------------------------------
This same issue came up during orkut and igoogle integration. We settled on using the de facto standard views across the board there ("canvas", "profile", etc.), but we knew it was going to come up again as well.
It seems that if we move views configuration out of the normal "features" config and into a standalone "gadgets.features", we can make this work. It'll require a small manual configuration output hack such as the one done for core.util -- which makes me wonder if we shouldn't just flatten this structure.
> Provide a way for container specific views to gracefully degrade to well-known views.
> -------------------------------------------------------------------------------------
>
> Key: SHINDIG-132
> URL: https://issues.apache.org/jira/browse/SHINDIG-132
> Project: Shindig
> Issue Type: Improvement
> Components: Gadgets Server - Java
> Reporter: Paul Lindner
>
> Many containers may want to implement custom views. However they should not have to force developers to provide these views if an acceptable fallback view is available.
> An example of this is the hi5 preview view, which will cause display errors for applications that have explicit profile and canvas views, but do not have a Content section without any view definition.
> I propose that we provide a way to specify a fallback view by adding configuration to syndicators.js which will be considered during the rendering process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SHINDIG-132) Provide a way for container specific
views to gracefully degrade to well-known views.
Posted by "Kevin Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Brown closed SHINDIG-132.
-------------------------------
Resolution: Fixed
> Provide a way for container specific views to gracefully degrade to well-known views.
> -------------------------------------------------------------------------------------
>
> Key: SHINDIG-132
> URL: https://issues.apache.org/jira/browse/SHINDIG-132
> Project: Shindig
> Issue Type: Improvement
> Components: Gadgets Server - Java
> Reporter: Paul Lindner
>
> Many containers may want to implement custom views. However they should not have to force developers to provide these views if an acceptable fallback view is available.
> An example of this is the hi5 preview view, which will cause display errors for applications that have explicit profile and canvas views, but do not have a Content section without any view definition.
> I propose that we provide a way to specify a fallback view by adding configuration to syndicators.js which will be considered during the rendering process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.