Mark,
One way to do this is to define 3 collections
<div ex:role="collection" id="the-services"
ex:itemTypes="Service"></div>
<div ex:role="collection" id="the-servers"
ex:baseCollectionID="the-services" ex:expression=".server"></div>
<div ex:role="collection" id="the-environments"
ex:baseCollectionID="the-servers" ex:expression=".env"></div>
Then display the environments
<div ex:role="view" ex:collectionID="the-environments"></div>
given this nested lens template
<div ex:role="lens" ex:itemTypes="Environment" style="display: none;">
<div>
<div>Env: <span ex:content=".label"></span></div>
... env details...
</div>
<ul ex:content="!env">
<li>
<div>Server: <span ex:content=".label"></span></div>
... server details
<ul ex:content="!server'>
<li>
<div>Service: <span ex:content=".label"></span></div>
... service details ...
</li>
</ul>
</li>
</ul>
</div>
Then hook the facets to the services
<div ex:role="facet" ex:collectionID="the-services"
ex:expression=".foo"></div>
David
mleden wrote:
> Thanks for your response, David. Ideally, I'd like the facets to be
> from any of the 3 tables. However, if that doesn't really fit the
> Exhibit paradigm, I could probably make it work with only facets from
> the service (child) table.
>
> -Mark
>
>
> On Mar 31, 8:52 pm, David Huynh <[email protected]> wrote:
>
>> Hi Mark,
>>
>> Which tables (environment, server, or service) do you want the facets to
>> apply on?
>>
>> David
>>
>> mleden wrote:
>>
>>> I am struggling with something that I imagine Exhibit handles easily.
>>> I want to display my many-to-many data with "duplicates suppressed",
>>> kind of a "master-detail report". Imagine this setup:
>>> a server "table" of data
>>> an environment "table"
>>> a service "table"
>>> The service table is the child of both the server & environment tables
>>> with "foreign keys" to each.
>>>
>>> I want to display as:
>>> Environment i
>>> -> Server 1
>>> --> Service a
>>> --> Service b
>>> -> Server 2
>>> --> Service c
>>> --> Service d
>>> Environment ii
>>> -> Server 1
>>> --> Service e
>>> -> Server 3
>>> --> Service f
>>> --> Service g
>>> --> Service h
>>>
>>> From what I can tell the Thumbnail and Tile views handle this
>>> structure "out of the box", if I set the Collection to "service" and
>>> order by "environment" and "server". However, it does not appear that
>>> I can modify the "group by" headers. They will always display as
>>> "Environment i (4)" and "Server 1 (2)" where 4 and 2 represent the
>>> number of services (for that environment or server). I actually want
>>> to display additional "Environment" and "Server" data in those
>>> "headers".
>>>
>>> Thanks for reading this far! Appreciate any suggestions on what I'm
>>> doing wrong.
>>>
>>> -Mark
>>>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SIMILE Widgets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/simile-widgets?hl=en
-~----------~----~----~----~------~----~------~--~---
