Hi. This is in relation to my previous post on deeper JSON data
structure hiearchies: do I understand correctly that this child
element solution below can only handle actual items, as opposed to
whichever data structure .co-winner evaluates to? I am trying to do
the latter. Or will I simple have to flatten my tree much like Neil
Ireson did? (see http://simile.mit.edu/mail/ReadMsg?
listName=General&msgId=21628)
Mummi
On 20 Oct 2007, at 14:47, David Huynh wrote:
> You can already do this:
>
> <div ex:role="lens" class="nobelist">
> ...
> <ul ex:content=".co-winner">
> <li>
> Name: <span ex:content="value"></span>,
> Age: <span ex:content=".age"></span>
> </li>
> </ul>
>
> Child elements of an element with ex:content are used as a template
> for
> rendering items that ex:content evaluates to. This solution
> requires you
> to specify explicitly however many nested levels you need, but does
> not
> cause infinite recursion.
>
> David
>
> Daniel B. Giffin wrote:
>> in the display of an item, i'd like some of the items that occur as
>> its property values to be rendered "inline" (directly in the page)
>> instead of as popups.
>>
>> (there was an earlier thread under the subject "Exhibit Handling
>> Hierarchical JSON Data", and this could be one way to show some more
>> of the graph's depth.)
>>
>> i think inline rendering could be specified in a lens by adding an
>> attribute like "ex:inline" to an element that uses ex:content.
>>
>> for example:
>>
>> <div ex:role="lens" class="nobelist">
>> ...
>> <span ex:content=".co-winner" ex:inline="true">
>>
>> this would mean that the .co-winner property values should be
>> rendered
>> inline here.
>>
>> of course, there's some danger of writing recursive lenses that go on
>> rendering dom nodes until your browser explodes. (i think my example
>> would do that.) but i don't think that's a reason not to provide the
>> facility.
>>
>> thoughts?
>>
>> (i might have a go at implementing this myself. i'm eyeing
>> Exhibit.Lens.prototype._constructDefaultUI(). it seems like it could
>> be straightforward, although it looks like there are some subtleties
>> concerning rendering an item more than once, and perhaps other
>> stuff i
>> haven't thought of.)
>> _______________________________________________
>> General mailing list
>> [email protected]
>> http://simile.mit.edu/mailman/listinfo/general
>>
>
> _______________________________________________
> General mailing list
> [email protected]
> http://simile.mit.edu/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
