Граф коммитов

8 Коммитов

Автор SHA1 Сообщение Дата
Mike Bostock 0696bf089f Backwards-compatibility for inlining.
There's now a new API for invoking the hierarchy layout (hierarchy.nodes) rather
than calling the layout function directly. Calling the new API enables inlining,
which is disabled by default for backwards-compatibility.
2011-07-02 17:14:34 -07:00
Mike Bostock 6bdbe4b863 Move data files into examples directory.
This way, we don't need symlinks (which don't work on Windows). This commit also
simplifies the structure of the flare.json file, so that we don't need to tricky
conversion of the JSON map—it can be read directly by the hierarchy layout.
2011-07-02 16:31:12 -07:00
Mike Bostock bd505a22a9 Remove `inline` property, making it the default. 2011-07-02 15:59:19 -07:00
Mike Bostock 2773cd9f27 Adopt inline(true) for all hierarchy examples.
The ones with transitions were a bit trickier, because they depended on the
layout creating new copy of the nodes when the layout runs.
2011-07-02 15:49:50 -07:00
Mike Bostock 43e2ccca41 Fix fill color for iOS. 2011-04-14 16:53:33 -07:00
Mike Bostock d4e571eb88 Replace flare.json's with symlinks. 2011-04-13 23:58:46 -07:00
Mike Bostock c5c6614d9e Simplify pack layout.
The pack layout now sorts nodes by ascending value by default. The `radius`
property is removed, as the radius is always computed from the node value. The
`spacing` property is also removed; it doesn't seem particularly useful. The
`radius` property is renamed to `r` to match `x` and `y`.

I also optimized the implementation slightly, and namespaced temporary state
under the prefix `_pack_`.
2011-04-11 12:44:17 -07:00
Jason Davies ccfbb06729 Add circle-packing layout.
Based on the Protovis layout.  I've kept the convention of using `size`
for the width/height and `separation` for the spacing.  The Protovis
layout had a `size` property but this was used to compute the radius.
I've left this out as I've assumed it's straightforward enough to pass
in the appropriate `radius` function instead.  Likewise, I think the
existing hierarchy `sort` property can handle situations that `order`
was intended for in the Protovis version.
2011-04-11 10:01:11 +01:00