visgl / deck.gl-community Goto Github PK

v9.1

• Fork @ibgreen
• Docs
  • Integrate into website
  • Clean up / extend
• Fix examples
• Modernize examples
• Integrate examples into website

v9

• Get all examples passing and migrated to TypeScript
  • #15
  • #38
  • fix 'graph-layers' examples
  • add 'layers' examples
  • Add @deck.gl-community/editable-layers to example dependencies after it's published
    #63
• Update modules/* to build against deck.gl v9
• Get all unit tests passing (with Jest-style syntax, Deck v9, and TypeScript)
• Migrate modules/* to TypeScript
  • #14
• Update modules/*/test/* to Jest-style tests
  • Could use Jest, Vitest, or Bun as the test runner. Consider options and make a decision. Vitest seems more batteries-included and ESM-friendly than Jest, where ESM is experimental. No opinion on Bun yet.
  • #41
  • #42
  • #45
  • #46
• Fix ESLint and TSC errors and warnings as practical
  • #53
  • #54
  • #55
  • #64

v9.1

• Move generic layers from `editable-layers?
• Move generic layers from `graph-layers?

v9.0

• Docs for TileSourceLayer?
• Example for TileSourceLayer?
• Docs for DataDrivenTile3Dlayer?
• Add example to website

deck.gl-community is under open governance through the OpenJS / Linux Foundations. Join the discussion on our slack or attend our bi-weekly meetings: https://www.openvisualization.org/#get-involved

Trackers for individual modules

• #80
• #38
• #78
• #79

Candidate modules

• raster-layers
• earthengine-layers
• viv-layers

• we have a docusaurus website running locally
• and somehow even the jest tests are “working” when we run yarn test node,
• however we get silent failure on browser tests:
• when we comment out all modules, it starts but browser doesn’t find index.html on the specified port.

Blocked on #10 #11 and setting up the npm org.

Im not able to run the examples. Steps I performed

git clone <repo>
npm i
npm run build # build works

I am not able to run the tests, getting below error

TSError: ⨯ Unable to compile TypeScript:
error TS6046: Argument for '--module' option must be: 'none', 'commonjs', 'amd', 'system', 'umd', 'es6', 'es2015', 'es2020', 'es2022', 'esnext', 'node12', 'nodenext'.

I am using
node v18.16.1 and tried with v16

If you can you update the Readme or add steps to run different modules, examples and the website that will be great. Thanks

For testing the graph layer, I just copied required jsx files into my project and tested it out.

Determine best names for what are current graph-gl and react-graph-gl, maybe it should be something to reflect a core, layers, and the react component?

v9.1

• Audit
  • Rename modules to use @deck.gl-community prefix?
  • graph-layers - MarkerLayer seems very generic, including icon packing script
  • deckgl-react-graph-layers Move button, viewport to generic react module
  • deckgl-react-graph-layers GraphGL component / hook is quite big - if so much helper code is needed, port to pureJS? Could it be a widget?

v9.0

• api and module structure
  • Move graph independent react components from deck-react-graph-layers to @deck.gl-community/react
  • Refactor graph helper code to be react independent and remove deck-react-graph-layers module.
• examples
  • fix 'graph-layers' examples
  • modernize 'graph-layers' examples
  • Get all examples passing and migrated to TypeScript
• *docs
  • audit docs for correctness / completeness / freshness
• website
  • Add examples to website.

v9.1+ Roadmap

• Docs - make sure the docs get the reader up to speed on the right things.
• MeshLayer - is it still needed? Docs says it should be replaced
• Toolbox React component - Could it be an EditorLayer composite layer with a suite of widgets?

v9.0 - Initial forking from nebula.gl

• Website -
• Add editor example #76 @birkskyum
• Add advanced example
• editable-layers/editable-h3-cluster-layer
• editable-layers/sf (⚠️ renders, but throws errors)
• editable-layers/overlays
• editable-layers/no-map
• editable-layers/getting-started
• editable-layers/codesandbox
• examples* - Make all nebula.gl examples build again
  • editable-layers/editor
  • editable-layers/advanced
  • editable-layers/editable-h3-cluster-layer
  • editable-layers/sf (⚠️ renders, but throws errors)
  • editable-layers/overlays
  • editable-layers/no-map
  • editable-layers/getting-started
  • editable-layers/codesandbox
  • Maplibre, token free basemaps, etc @birkskyum
  • React 18, functional components, etc
• Remove @deck.gl-community/react-editable-layers #96
  • Create new react module @deck.gl-community/react
  • Move independent react components from @deck.gl-community/react-editable-layers to @deck.gl-community/react @ibgreen
  • Move overlays to @deck.gl-community/react
  • Move EditorModal to @deck.gl-community/react
  • Toolbox component - move toeditor example.
• forking
  • Add EditableGeojsonLayer & related code from nebula.g repo #37 @ibgreen
  • Apply the fixes needed for v9 EditableGeojsonLayer @donmccurdy
  • Publish package to npm
  • Migrate tests to modern tooling @donmccurdy
  • Notify community in nebula.gl repo and slack channels @ibgreen

Background

nebula.gl has become stale, and it is not possible to migrate it to deck.gl v9 easily. A number of project depend on it, in particular the EditableGeojsonLayer. In order to move forward, the code will be moved into this repo and published under a new npm package

Forking old repositories into this repo is just the first step. We need to review the APIs and make sure they are will consistent.

v9

• editable-layers
  • MeshLayer - is it still needed? Docs says it should be replaced
• graph-layers
  • MarkerLayer seems very generic, including icon packing script
• react-editable-layers (goal: remove entire module)
  • Strip out non-graph specific react functionality
  • Create new react module
  • Move overlays to new react module
  • Move EditorModal to new react module
  • ExportModal - is this still needed? can we just move into examples?
  • Toolbox component - is this needed? In that case shouldn't it be React independent? Could it be a widget?
• deckgl-react-graph-layers
  • Move button, viewport to generic react module
  • GraphGL component / hook is quite big - if so much helper code is needed, port to pureJS? Could it be a widget?

Port examples from old website for graphgl.

Publish new website somewhere.