Hi David,
yes, exactly, thanks for your help.
I tried to find out what you did, and I think there were basically two
changes, the selector in the facet, and, I guess more importantly, you
moved the Tier items from
{
id: "de",
...
}
over to
{
label: "de",
...
}
with those items having no id properties at all anymore. Is that
correct? If so, mind explaining why that fixed it?
I'd hope that I would actually end up not needing your help with the
next few ;-)
FYI, I just put http://l10n.mozilla.org/buildbot/statistics live the
other day, an exhibit for navigating timeplots :-) If only timeplots
would allow faceted browsing.
Axel
2008/1/27, David Huynh <[EMAIL PROTECTED]>:
> Axel,
>
> I copied your code over and was able to get the Tiers facet filled in:
>
>
> http://people.csail.mit.edu/dfhuynh/misc/mozilla-l10n-dashboard/dashboard.html
>
> Let me know if this is what you want.
>
> David
>
> Axel Hecht wrote:
> > 2008/1/23, David Huynh <[EMAIL PROTECTED]>:
> >
> >> Axel Hecht wrote:
> >>
> >>> 2008/1/16, David Huynh <[EMAIL PROTECTED]>:
> >>>
> >>>
> >>>> Hi Axel,
> >>>>
> >>>> That's pretty cool! I'm glad you Mozilla folks are finding our tools
> >>>> useful for internal processes.
> >>>>
> >>>> The content at that URL is indeed missing. For some reason I never got
> >>>> around to it.
> >>>>
> >>>> Regarding "get stuff working deeper", could you elaborate? What do you
> >>>> want to happen? I'm not understanding the problem.
> >>>>
> >>>>
> >>> I tried to do a one-stop sample. Basically, I have a bunch of builds,
> >>> and they share properties. In my example, those are of type
> >>> Localization. I drafted a graph, and I think that the html follows
> >>> that graph well enough.
> >>>
> >>>
> >> Nice graph :)
> >>
> >>
> >>> There are two problems with this:
> >>>
> >>> The facets report "Localization" items, which makes it a bit
> >>> confusing. I.e., I will have localizations that don't have a tier, and
> >>> the facet shows both Localization items and Build items linking to
> >>> Localizations without a tier as "missing this field".
> >>>
> >>> Oh, and the facets don't actually work, I think.
> >>>
> >>>
> >> I just took a look at your data file again, and I couldn't find any item
> >> of type "Localization". They are all "Build"s. Have you changed the data
> >> lately?
> >>
> >> What you want to do is this:
> >> 1. put the Build items back into the data
> >> 2. re-define the "default" collection (what would be shown in the view)
> >> by including this div right after <body>
> >>
> >> <div ex:role="collection" ex:itemTypes="Build"></div>
> >>
> >> 3. re-define the Tier facet as follows
> >>
> >> <div ex:role="facet"
> >> ex:expression=".target.tier"
> >> ex:facetLabel="Tier"
> >> ex:fixedOrder="1;2"></div>
> >>
> >> I presume that the Build items point to the Localization items through
> >> the "target" property.
> >>
> >
> > The Localization items are actually just in the one-file test.html
> > example that I attached in my previous mail, the live demo has a
> > slightly different structure still. That one contains the data inline
> > as plain js, so it's really just that one file.
> >
> > As I noted in my other reply, it seems that a root collection and
> > facets exclude each other, the facets in my example started working
> > again when I removed ex:collectionID="blds" from the view div. But
> > then all the different item types showed up intermingled.
> >
> >
> >>>> As a side note, I got the data link off your exhibit, but it's all on
> >>>> one line. So then I copied and pasted the JSON into the left text area of
> >>>>
> >>>>
> >>> That's actually intentional to get the data size down.
> >>>
> >>>
> >>>> http://simile.mit.edu/repository/juggler/trunk/src/main/webapp/index.html
> >>>> and hit Run, and got a nicely formatted JSON output on the right.
> >>>> Juggler is a Javascript-based tool for transforming JSON.
> >>>>
> >>>> Regarding Mozilla's use of Exhibit, I wonder if there's any value in
> >>>> offering Exhibit's faceted browsing features on bookmarks in Firefox and
> >>>> on mail messages in Thunderbird. It seems very do-able. What do you
> >>>> think?
> >>>>
> >>>>
> >>> With places, http://developer.mozilla.org/en/docs/Places, we moved to a
> >>> pretty strict schema, it might work. Sounds like a nice playground for an
> >>> extension developer.
> >>>
> >>>
> >> Do you think we can start a project inside labs.mozilla.org for that?
> >>
> >
> > Hooked that up in a different thread.
> >
> >
> >>> Btw, supporting offline cache in fx3 might be interesting for exhibit
> >>> performance. Sadly, I haven't found good docs on that yet.
> >>> http://www.whatwg.org/specs/web-apps/current-work/multipage/section-offline.html
> >>> has most right now, I hope that
> >>> http://developer.mozilla.org/en/docs/Firefox_3_for_developers will
> >>> have something soon.
> >>>
> >>>
> >> Yes! Indeed, David Karger has been bugging me about making a Firefox
> >> extension that boost Exhibit's performance by using Firefox's native
> >> data facilities.
> >>
> >
> > Actually I just overheard on irc today that offline resources are
> > going to make it into fx3, so there should be some <link> foo or
> > whatnot that you could just add that would make fx pin your js files
> > to the cache. It shouldn't require an extension or anything. I think
> > that should be https://bugzilla.mozilla.org/show_bug.cgi?id=402272,
> > waiting for dev-docs.
> >
> > Axel
> > _______________________________________________
> > 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
