Bertrand Delacretaz wrote: > Hi, > > On Mon, Dec 1, 2008 at 8:52 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: >> ...if you want to display some random data contained in the >> repository, the primary node type is used as it is very likely that you >> don't have the special sling:* properties already set for your data. >> >> I think this is a very handy behaviour when it comes to check out Sling, >> so I personally would rather tell new people to use script resolution >> based on node types than using a special property.... > > You mean this in the context of existing data in a repository, right? > > In this case I agree that it might make sense to use script resolution > based on node types, but in the general case I find the > sling:resourceType way of resolving scripts closer to our "data first, > structure later" recommendation. > > My best practice recommendation would then be to use > sling:resourceType if possible, and nodetype-based script resolution > only if one has to. > Hmm, ok, although I personally don't like to add rendering hints into the content, but anyways, what about documenting this? :)
Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
