mirror of
https://github.com/d3/d3.git
synced 2025-12-08 19:46:24 +00:00
* checkpoint vitepress docs * edits * edits * hero drop shadow * d3-array edits * resolve d3 * split d3-array * move d3-array stuff around * d3-array is collapsed: true * italicize parameter names * searching edits * update dependencies * d3-array edits * array edits * array edits * array edits * array edits * array edits * move files * array edits * array edits * array edits * getting started edits * modules page * array edits * more structure * live example * dsv edits * fetch edits * dsv edits * random edits * time format edits * time edits * time edits * modules edits * color edits * color edits * interpolate edits * scale-chromatic edits * selection edits * break up d3-interpolate * scale edits * time scale edits * scale edits * scale edits * band edits * band edits * more descriptive titles * band and point edits * sequential edits * diverging edits * quantize edits * quantile edits * threshold edits * doc edits * fix titles * sequential edits * axis edits * axis edits * axis edits * shape edits * shape edits * dark mode chart * dark mode chart * curve edits * interpolate edits * line edits * link edits * radial edits * pie edits * symbol edits * stack edits * stack examples * path edits * polygon edits * quadtree edits * random examples * ease edits * ease edits * ease edits * timer edits * delaunay edits * quadtree find example * voronoi edits * dispatch edits * contour edits * chord edits * chord edits * fix find highlight * quadtree animation * transition edits * transition edits * transition edits * zoom edits * drag edits * brush edits * force edits * voronoi neighbors example * hierarchy edits * api edits * community edits * getting started edits * geo edits * Add short "D3 in React" section (#3659) * Add short "D3 in React" section I know you removed the TODO but I was already trying to fill it in! I think just making the distinction of modules that touch the DOM and those that don't was super clarifying for me personally when I figured that out. And I always forget the most basic ref pattern (and still might've messed it up here). I don't think we should get into updating or interactivity or whatever, but I think just this much goes a long way toward demystifying (and showing just the most basic best practices). * forgot i made data generic, rm reference to normal distribution * useEffect cleans up after itself Co-authored-by: Mike Bostock <mbostock@gmail.com> * Update getting-started.md --------- Co-authored-by: Mike Bostock <mbostock@gmail.com> * build fixes * index edits --------- Co-authored-by: Toph Tucker <tophtucker@gmail.com>
50 lines
1.1 KiB
Vue
50 lines
1.1 KiB
Vue
<script>
|
|
|
|
import * as d3 from "d3";
|
|
|
|
export default {
|
|
async mounted() {
|
|
// Declare the chart dimensions and margins.
|
|
const width = 640;
|
|
const height = 400;
|
|
const marginTop = 20;
|
|
const marginRight = 20;
|
|
const marginBottom = 30;
|
|
const marginLeft = 40;
|
|
|
|
// Declare the x (horizontal position) scale.
|
|
const x = d3.scaleUtc()
|
|
.domain([new Date("2023-01-01"), new Date("2024-01-01")])
|
|
.range([marginLeft, width - marginRight]);
|
|
|
|
// Declare the y (vertical position) scale.
|
|
const y = d3.scaleLinear()
|
|
.domain([0, 100])
|
|
.range([height - marginBottom, marginTop]);
|
|
|
|
// Create the SVG container.
|
|
const svg = d3.create("svg")
|
|
.attr("width", width)
|
|
.attr("height", height);
|
|
|
|
// Add the x-axis.
|
|
svg.append("g")
|
|
.attr("transform", `translate(0,${height - marginBottom})`)
|
|
.call(d3.axisBottom(x));
|
|
|
|
// Add the y-axis.
|
|
svg.append("g")
|
|
.attr("transform", `translate(${marginLeft},0)`)
|
|
.call(d3.axisLeft(y));
|
|
|
|
// Append the SVG element.
|
|
this.$el.append(svg.node());
|
|
}
|
|
}
|
|
|
|
</script>
|
|
|
|
<template>
|
|
<div></div>
|
|
</template>
|