AllenInstitute / AllenInstitute/vis
Web Components
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 1
- Avg merge
- 10h 24m
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
It would be nice to make web components to provide a base on which to build framework-specific UI components
Describe the solution you'd like
A web component for:
- DZI viewer
- OME-Zarr viewer
- Scatterbrain
Describe alternatives you've considered
We could just build React packages, but then the tools are far less usable since not everybody uses React
Additional context
I've started an OME-Zarr one that does display information, but it's not nearly as nice as our React example one: https://github.com/lanesawyer/vis/tree/lane/omezarr-info-display
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing OME-Zarr work at the linked lane/omezarr-info-display branch and compare it with the React example referenced in the issue. Determine the shared web-component scope for the DZI viewer, OME-Zarr viewer, and Scatterbrain; done means framework-independent components exist for all three with feature parity appropriate to the examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- data-visualization, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100