You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/10/17 15:47:51 UTC
[jira] Reopened: (SLING-61) Rendering of references within the
repository
[ https://issues.apache.org/jira/browse/SLING-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reopened SLING-61:
------------------------------------
Reopen the issue for further consideration.
Carsten, could you please comment ? Thanks.
> Rendering of references within the repository
> ---------------------------------------------
>
> Key: SLING-61
> URL: https://issues.apache.org/jira/browse/SLING-61
> Project: Sling
> Issue Type: New Feature
> Components: Core
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
>
> If compound content is rendered (a node and its children), it would be good to provide a mechanism which references other trees in the repository.
> Example:
> Node A
> + header
> + footer
> Node B
> + content
> Node C
> + content
> When node B or C are rendered, the header and footer of node A should be rendered as well.
> A new node type sling:Reference with a path property will be introduced to allow such references:
> Node B
> + header [sling:Reference (path = /A/header)]
> + content
> + footer [sling:Reference (path = /A/footer)]
> A new content and component (ReferenceContent and ReferenceComponent) will be added.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Reopened: (SLING-61) Rendering of references within the
repository
Posted by Carsten Ziegeler <cz...@apache.org>.
Tobias Bocanegra wrote:
>>> ...So, you have a node storing all documents as sub nodes. Now, you want to
>>> make a view on these documents containing just a bunch of them. With the
>>> references, you create a "view node" containing several reference nodes
>>> and are done....
>> The header/footer example was a bit scary though ;-)
> right. i just wanted to make sure, that this header/footer example
> would be the wrong way to use reference components. the other examples
> make more sense.
>
Yepp, sorry for the dumb example - I just came up with a better proposal
for the templating stuff.
Hopefully this one fits better the page/header/footer use case...
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: [jira] Reopened: (SLING-61) Rendering of references within the repository
Posted by Tobias Bocanegra <to...@day.com>.
> > ...So, you have a node storing all documents as sub nodes. Now, you want to
> > make a view on these documents containing just a bunch of them. With the
> > references, you create a "view node" containing several reference nodes
> > and are done....
> The header/footer example was a bit scary though ;-)
right. i just wanted to make sure, that this header/footer example
would be the wrong way to use reference components. the other examples
make more sense.
regards, toby
--
-----------------------------------------< tobias.bocanegra@day.com >---
Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
-----------------------------------------------< http://www.day.com >---
Re: [jira] Reopened: (SLING-61) Rendering of references within the repository
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 10/18/07, Carsten Ziegeler <cz...@apache.org> wrote:
> ...So, you have a node storing all documents as sub nodes. Now, you want to
> make a view on these documents containing just a bunch of them. With the
> references, you create a "view node" containing several reference nodes
> and are done....
Ok, with this example (and Felix's) I agree that this might be useful.
The header/footer example was a bit scary though ;-)
-Bertrand
Re: [jira] Reopened: (SLING-61) Rendering of references within the
repository
Posted by Carsten Ziegeler <cz...@apache.org>.
Bertrand Delacretaz wrote:
> On 10/17/07, Carsten Ziegeler <cz...@apache.org> wrote:
>
>> ...Let's consider an example with a page node which has a header, footer
>> and content node. Rendering of the page node is always the same (header,
>> content, footer). Now, with these references it's possible to reference
>> parts of the page from a template or master page. And the page rendering
>> does not need to know these things....
>
> IIUC this means you want to put nodes in the content, which are here
> just to define how that content is rendered? Sounds like I'd get a
> slap on my fingers if I did that in school ;-)
>
:) Hmm, no, it's a little different I think/hope. Let's forget about
this page/header/footer example which might be a bad one for this feature.
Perhaps this reference thing doesn't make sense and I'm totally off
track, but what about creating artifical views for lets say document
collections.
So, you have a node storing all documents as sub nodes. Now, you want to
make a view on these documents containing just a bunch of them. With the
references, you create a "view node" containing several reference nodes
and are done.
Does this make sense?
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: [jira] Reopened: (SLING-61) Rendering of references within the repository
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 10/17/07, Carsten Ziegeler <cz...@apache.org> wrote:
> ...Let's consider an example with a page node which has a header, footer
> and content node. Rendering of the page node is always the same (header,
> content, footer). Now, with these references it's possible to reference
> parts of the page from a template or master page. And the page rendering
> does not need to know these things....
IIUC this means you want to put nodes in the content, which are here
just to define how that content is rendered? Sounds like I'd get a
slap on my fingers if I did that in school ;-)
-Bertrand
Re: [jira] Reopened: (SLING-61) Rendering of references within the
repository
Posted by Felix Meschberger <fm...@gmail.com>.
I have another use case which comes from a real-world CMS :-)
Consider you have a pages containing paragraphs of text. There may be
crossreferences of even shared paragraphs. It would be nice, if instead
of copying the shared paragraph we could just refer to it.
Another use case probably is content inheritance on another level:
Consider a system for where we have support for multiple languages. We
would have a tree for the default language and additional trees per
language. Instead of just copying the complete default language tree for
each additional language, we could just create page nodes in the
languages and add references to the contents of the default language
tree.
Both use cases will of course define and properly handle the case of
updating the content: The reference paragraph case might just edit to
target paragraph while the multi language case might create a (partial)
copy on write.
Regards
Felix
Am Mittwoch, den 17.10.2007, 16:21 +0200 schrieb Carsten Ziegeler:
> Okay, the main idea is to have some kind of references which allows to
> create virtual trees in a transparent way. I thought that this could be
> useful. :)
>
> Let's consider an example with a page node which has a header, footer
> and content node. Rendering of the page node is always the same (header,
> content, footer). Now, with these references it's possible to reference
> parts of the page from a template or master page. And the page rendering
> does not need to know these things.
>
> So, that's the basic idea - now, there might be better/other ways to
> handle such things, but they are not transparent.
>
> Carsten
>
>
> Felix Meschberger (JIRA) wrote:
> > [ https://issues.apache.org/jira/browse/SLING-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> >
> > Felix Meschberger reopened SLING-61:
> > ------------------------------------
> >
> >
> > Reopen the issue for further consideration.
> >
> > Carsten, could you please comment ? Thanks.
> >
> >> Rendering of references within the repository
> >> ---------------------------------------------
> >>
> >> Key: SLING-61
> >> URL: https://issues.apache.org/jira/browse/SLING-61
> >> Project: Sling
> >> Issue Type: New Feature
> >> Components: Core
> >> Reporter: Carsten Ziegeler
> >> Assignee: Carsten Ziegeler
> >>
> >> If compound content is rendered (a node and its children), it would be good to provide a mechanism which references other trees in the repository.
> >> Example:
> >> Node A
> >> + header
> >> + footer
> >> Node B
> >> + content
> >> Node C
> >> + content
> >> When node B or C are rendered, the header and footer of node A should be rendered as well.
> >> A new node type sling:Reference with a path property will be introduced to allow such references:
> >> Node B
> >> + header [sling:Reference (path = /A/header)]
> >> + content
> >> + footer [sling:Reference (path = /A/footer)]
> >> A new content and component (ReferenceContent and ReferenceComponent) will be added.
> >
>
>
Re: [jira] Reopened: (SLING-61) Rendering of references within the
repository
Posted by Carsten Ziegeler <cz...@apache.org>.
Okay, the main idea is to have some kind of references which allows to
create virtual trees in a transparent way. I thought that this could be
useful. :)
Let's consider an example with a page node which has a header, footer
and content node. Rendering of the page node is always the same (header,
content, footer). Now, with these references it's possible to reference
parts of the page from a template or master page. And the page rendering
does not need to know these things.
So, that's the basic idea - now, there might be better/other ways to
handle such things, but they are not transparent.
Carsten
Felix Meschberger (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/SLING-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Felix Meschberger reopened SLING-61:
> ------------------------------------
>
>
> Reopen the issue for further consideration.
>
> Carsten, could you please comment ? Thanks.
>
>> Rendering of references within the repository
>> ---------------------------------------------
>>
>> Key: SLING-61
>> URL: https://issues.apache.org/jira/browse/SLING-61
>> Project: Sling
>> Issue Type: New Feature
>> Components: Core
>> Reporter: Carsten Ziegeler
>> Assignee: Carsten Ziegeler
>>
>> If compound content is rendered (a node and its children), it would be good to provide a mechanism which references other trees in the repository.
>> Example:
>> Node A
>> + header
>> + footer
>> Node B
>> + content
>> Node C
>> + content
>> When node B or C are rendered, the header and footer of node A should be rendered as well.
>> A new node type sling:Reference with a path property will be introduced to allow such references:
>> Node B
>> + header [sling:Reference (path = /A/header)]
>> + content
>> + footer [sling:Reference (path = /A/footer)]
>> A new content and component (ReferenceContent and ReferenceComponent) will be added.
>
--
Carsten Ziegeler
cziegeler@apache.org