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:56:25 UTC
[jira] Updated: (SHINDIG-132) Provide a way for container specific
views to gracefully degrade to well-known views.
[ 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.