diff options
| author | CoprDistGit <infra@openeuler.org> | 2023-05-05 03:59:16 +0000 |
|---|---|---|
| committer | CoprDistGit <infra@openeuler.org> | 2023-05-05 03:59:16 +0000 |
| commit | aa1674c834abff77e096311d57cf7f27c25c2854 (patch) | |
| tree | f4ddcca80bee7c30167c374bbe36b7c4dd398b0d | |
| parent | e01ff8d437129fadb67c6c3cb3db3c80ffd61391 (diff) | |
automatic import of python-webviz-subsurface-componentsopeneuler20.03
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-webviz-subsurface-components.spec | 462 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 464 insertions, 0 deletions
@@ -0,0 +1 @@ +/webviz_subsurface_components-0.4.15.tar.gz diff --git a/python-webviz-subsurface-components.spec b/python-webviz-subsurface-components.spec new file mode 100644 index 0000000..9239b45 --- /dev/null +++ b/python-webviz-subsurface-components.spec @@ -0,0 +1,462 @@ +%global _empty_manifest_terminate_build 0 +Name: python-webviz-subsurface-components +Version: 0.4.15 +Release: 1 +Summary: Custom Dash components for use in Webviz +License: MPL +URL: https://github.com/equinor/webviz-subsurface-components +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/3d/e1/5abfe8e6a28b7b37bf3f942bd25c2167fd2bb329c4ce062031043e704cf1/webviz_subsurface_components-0.4.15.tar.gz +BuildArch: noarch + +Requires: python3-dash +Requires: python3-numpy +Requires: python3-pandas +Requires: python3-dash +Requires: python3-numpy +Requires: python3-pandas +Requires: python3-bandit +Requires: python3-black +Requires: python3-dash[testing] +Requires: python3-geojson +Requires: python3-jsonpatch +Requires: python3-jsonpointer +Requires: python3-matplotlib +Requires: python3-orjson +Requires: python3-Pillow +Requires: python3-pylint +Requires: python3-scipy +Requires: python3-selenium +Requires: python3-vtk +Requires: python3-webviz-core-components +Requires: python3-xtgeo + +%description +[](https://badge.fury.io/py/webviz-subsurface-components) +[](https://badge.fury.io/js/%40webviz%2Fsubsurface-components) +[](https://github.com/equinor/webviz-subsurface-components/actions?query=branch%3Amaster) +[](https://lgtm.com/projects/g/equinor/webviz-subsurface-components/alerts/) +[](https://lgtm.com/projects/g/equinor/webviz-subsurface-components/context:javascript) +[](https://lgtm.com/projects/g/equinor/webviz-subsurface-components/context:python) +[](https://www.python.org/) +[](https://github.com/psf/black) +[](https://github.com/prettier/prettier) +[](https://codecov.io/gh/equinor/webviz-subsurface-components) + +# Webviz subsurface components + +`webviz_subsurface_components` is a Dash/React component library for use in `webviz`, +which have in common that they are geared towards subsurface dashboards. There storybook is available at https://equinor.github.io/webviz-subsurface-components/storybook-static. +And the demo of old components is available at https://equinor.github.io/webviz-subsurface-components. + +## How to install the components + +You can quickly get started using the components in Dash by: + +1. Run `pip install webviz-subsurface-components` +2. Run `python examples/example_hm.py` +3. Visit http://localhost:8050 in your web browser + +This project was originally generated by the +[dash-component-boilerplate](https://github.com/plotly/dash-component-boilerplate). +(with some modifications). + +If you are only interested in using the JavaScript code in your own JavaScript project, +you can install the [`npmjs` deployed version](https://www.npmjs.com/package/@webviz/subsurface-components): +``` +npm i @webviz/subsurface-components +``` +## How to contribute + +### Install dependencies + +If you want to build and develop yourself, you should fork + clone the repository, and +then: + +1. Install npm packages + ``` + npm ci --ignore-scripts --prefix ./react + ``` +2. Run some potentially optional postinstall scripts + ``` + npm run setup-deckgl-types --prefix ./react # only needed if ignored scripts during install + npm run copy-package-json --prefix ./react # only needed if building Dash components + ``` +3. Install python packages required to build components. + ``` + pip install .[dependencies] + pip install dash[dev] + ``` +4. Install the python packages for testing. + ``` + pip install .[tests] + ``` + +### Write component code in `src/lib/components/<component_name>/<component_name>.jsx` + +- The demo app is in `src/demo` and is where you will import an example of your + component. To start the existing demo app, run `npm start`. +- To test your code in a Python environment: + 1. Build your code + ``` + npm run build --prefix ./react + ``` + 2. Install the Python pacakge in development mode (if not already done and + assuming you are using a virtual environment): + ``` + pip install -e . + ``` + 3. Create a new example in `examples/` which uses your new component. + +- Write tests for your component. + - Tests exist in `tests/`. Take a look at them to see how to write tests using + the Dash test framework. + - Run the tests with `pytest tests`. + +- Add custom styles to your component by putting your custom CSS files into + your distribution folder (`webviz_subsurface_components`). + - Make sure that they are referenced in `MANIFEST.in` so that they get + properly included when you're ready to publish your component. + - Make sure the stylesheets are added to the `_css_dist` dict in + `webviz_subsurface_components/__init__.py` so dash will serve them + automatically when the component suite is requested. + +- Every file related to the component should be located in the component directory, unless the file is shared between multiple components. For example the file-structure should look something like this: +``` +src +|--lib + |----<component_name> + |----components + |----<sub_component>.ts + |----utils + |----<component_name>.tsx + |----<component_name>.css + |----index.ts +``` + +### Automatically upload demo application + +This repository has a GitHub workflow which can automatically build and deploy a demo +app with your changes, to GitHub pages. + +- On push to your feature branch, in your fork, the workflow will build and deploy a + demo app to your fork's GitHub page, given that your commit message includes the + substring `[deploy test]`. +- On merge to `master` in the main repository, a build + deploy will be done to the + official GitHub page in the main repository. + +For this to work in your own fork, you will need to create a branch `gh-pages` +(this you only need to do once). One way of creating this branch is e.g.: +```bash +git checkout --orphan gh-pages +git rm -rf . +git commit --allow-empty -m "Create GitHub pages branch" +git push origin gh-pages +``` + +You are encouraged to rebase and squash/fixup unnecessary commits before pull request is merged to `master`. + + +%package -n python3-webviz-subsurface-components +Summary: Custom Dash components for use in Webviz +Provides: python-webviz-subsurface-components +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-webviz-subsurface-components +[](https://badge.fury.io/py/webviz-subsurface-components) +[](https://badge.fury.io/js/%40webviz%2Fsubsurface-components) +[](https://github.com/equinor/webviz-subsurface-components/actions?query=branch%3Amaster) +[](https://lgtm.com/projects/g/equinor/webviz-subsurface-components/alerts/) +[](https://lgtm.com/projects/g/equinor/webviz-subsurface-components/context:javascript) +[](https://lgtm.com/projects/g/equinor/webviz-subsurface-components/context:python) +[](https://www.python.org/) +[](https://github.com/psf/black) +[](https://github.com/prettier/prettier) +[](https://codecov.io/gh/equinor/webviz-subsurface-components) + +# Webviz subsurface components + +`webviz_subsurface_components` is a Dash/React component library for use in `webviz`, +which have in common that they are geared towards subsurface dashboards. There storybook is available at https://equinor.github.io/webviz-subsurface-components/storybook-static. +And the demo of old components is available at https://equinor.github.io/webviz-subsurface-components. + +## How to install the components + +You can quickly get started using the components in Dash by: + +1. Run `pip install webviz-subsurface-components` +2. Run `python examples/example_hm.py` +3. Visit http://localhost:8050 in your web browser + +This project was originally generated by the +[dash-component-boilerplate](https://github.com/plotly/dash-component-boilerplate). +(with some modifications). + +If you are only interested in using the JavaScript code in your own JavaScript project, +you can install the [`npmjs` deployed version](https://www.npmjs.com/package/@webviz/subsurface-components): +``` +npm i @webviz/subsurface-components +``` +## How to contribute + +### Install dependencies + +If you want to build and develop yourself, you should fork + clone the repository, and +then: + +1. Install npm packages + ``` + npm ci --ignore-scripts --prefix ./react + ``` +2. Run some potentially optional postinstall scripts + ``` + npm run setup-deckgl-types --prefix ./react # only needed if ignored scripts during install + npm run copy-package-json --prefix ./react # only needed if building Dash components + ``` +3. Install python packages required to build components. + ``` + pip install .[dependencies] + pip install dash[dev] + ``` +4. Install the python packages for testing. + ``` + pip install .[tests] + ``` + +### Write component code in `src/lib/components/<component_name>/<component_name>.jsx` + +- The demo app is in `src/demo` and is where you will import an example of your + component. To start the existing demo app, run `npm start`. +- To test your code in a Python environment: + 1. Build your code + ``` + npm run build --prefix ./react + ``` + 2. Install the Python pacakge in development mode (if not already done and + assuming you are using a virtual environment): + ``` + pip install -e . + ``` + 3. Create a new example in `examples/` which uses your new component. + +- Write tests for your component. + - Tests exist in `tests/`. Take a look at them to see how to write tests using + the Dash test framework. + - Run the tests with `pytest tests`. + +- Add custom styles to your component by putting your custom CSS files into + your distribution folder (`webviz_subsurface_components`). + - Make sure that they are referenced in `MANIFEST.in` so that they get + properly included when you're ready to publish your component. + - Make sure the stylesheets are added to the `_css_dist` dict in + `webviz_subsurface_components/__init__.py` so dash will serve them + automatically when the component suite is requested. + +- Every file related to the component should be located in the component directory, unless the file is shared between multiple components. For example the file-structure should look something like this: +``` +src +|--lib + |----<component_name> + |----components + |----<sub_component>.ts + |----utils + |----<component_name>.tsx + |----<component_name>.css + |----index.ts +``` + +### Automatically upload demo application + +This repository has a GitHub workflow which can automatically build and deploy a demo +app with your changes, to GitHub pages. + +- On push to your feature branch, in your fork, the workflow will build and deploy a + demo app to your fork's GitHub page, given that your commit message includes the + substring `[deploy test]`. +- On merge to `master` in the main repository, a build + deploy will be done to the + official GitHub page in the main repository. + +For this to work in your own fork, you will need to create a branch `gh-pages` +(this you only need to do once). One way of creating this branch is e.g.: +```bash +git checkout --orphan gh-pages +git rm -rf . +git commit --allow-empty -m "Create GitHub pages branch" +git push origin gh-pages +``` + +You are encouraged to rebase and squash/fixup unnecessary commits before pull request is merged to `master`. + + +%package help +Summary: Development documents and examples for webviz-subsurface-components +Provides: python3-webviz-subsurface-components-doc +%description help +[](https://badge.fury.io/py/webviz-subsurface-components) +[](https://badge.fury.io/js/%40webviz%2Fsubsurface-components) +[](https://github.com/equinor/webviz-subsurface-components/actions?query=branch%3Amaster) +[](https://lgtm.com/projects/g/equinor/webviz-subsurface-components/alerts/) +[](https://lgtm.com/projects/g/equinor/webviz-subsurface-components/context:javascript) +[](https://lgtm.com/projects/g/equinor/webviz-subsurface-components/context:python) +[](https://www.python.org/) +[](https://github.com/psf/black) +[](https://github.com/prettier/prettier) +[](https://codecov.io/gh/equinor/webviz-subsurface-components) + +# Webviz subsurface components + +`webviz_subsurface_components` is a Dash/React component library for use in `webviz`, +which have in common that they are geared towards subsurface dashboards. There storybook is available at https://equinor.github.io/webviz-subsurface-components/storybook-static. +And the demo of old components is available at https://equinor.github.io/webviz-subsurface-components. + +## How to install the components + +You can quickly get started using the components in Dash by: + +1. Run `pip install webviz-subsurface-components` +2. Run `python examples/example_hm.py` +3. Visit http://localhost:8050 in your web browser + +This project was originally generated by the +[dash-component-boilerplate](https://github.com/plotly/dash-component-boilerplate). +(with some modifications). + +If you are only interested in using the JavaScript code in your own JavaScript project, +you can install the [`npmjs` deployed version](https://www.npmjs.com/package/@webviz/subsurface-components): +``` +npm i @webviz/subsurface-components +``` +## How to contribute + +### Install dependencies + +If you want to build and develop yourself, you should fork + clone the repository, and +then: + +1. Install npm packages + ``` + npm ci --ignore-scripts --prefix ./react + ``` +2. Run some potentially optional postinstall scripts + ``` + npm run setup-deckgl-types --prefix ./react # only needed if ignored scripts during install + npm run copy-package-json --prefix ./react # only needed if building Dash components + ``` +3. Install python packages required to build components. + ``` + pip install .[dependencies] + pip install dash[dev] + ``` +4. Install the python packages for testing. + ``` + pip install .[tests] + ``` + +### Write component code in `src/lib/components/<component_name>/<component_name>.jsx` + +- The demo app is in `src/demo` and is where you will import an example of your + component. To start the existing demo app, run `npm start`. +- To test your code in a Python environment: + 1. Build your code + ``` + npm run build --prefix ./react + ``` + 2. Install the Python pacakge in development mode (if not already done and + assuming you are using a virtual environment): + ``` + pip install -e . + ``` + 3. Create a new example in `examples/` which uses your new component. + +- Write tests for your component. + - Tests exist in `tests/`. Take a look at them to see how to write tests using + the Dash test framework. + - Run the tests with `pytest tests`. + +- Add custom styles to your component by putting your custom CSS files into + your distribution folder (`webviz_subsurface_components`). + - Make sure that they are referenced in `MANIFEST.in` so that they get + properly included when you're ready to publish your component. + - Make sure the stylesheets are added to the `_css_dist` dict in + `webviz_subsurface_components/__init__.py` so dash will serve them + automatically when the component suite is requested. + +- Every file related to the component should be located in the component directory, unless the file is shared between multiple components. For example the file-structure should look something like this: +``` +src +|--lib + |----<component_name> + |----components + |----<sub_component>.ts + |----utils + |----<component_name>.tsx + |----<component_name>.css + |----index.ts +``` + +### Automatically upload demo application + +This repository has a GitHub workflow which can automatically build and deploy a demo +app with your changes, to GitHub pages. + +- On push to your feature branch, in your fork, the workflow will build and deploy a + demo app to your fork's GitHub page, given that your commit message includes the + substring `[deploy test]`. +- On merge to `master` in the main repository, a build + deploy will be done to the + official GitHub page in the main repository. + +For this to work in your own fork, you will need to create a branch `gh-pages` +(this you only need to do once). One way of creating this branch is e.g.: +```bash +git checkout --orphan gh-pages +git rm -rf . +git commit --allow-empty -m "Create GitHub pages branch" +git push origin gh-pages +``` + +You are encouraged to rebase and squash/fixup unnecessary commits before pull request is merged to `master`. + + +%prep +%autosetup -n webviz-subsurface-components-0.4.15 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-webviz-subsurface-components -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 0.4.15-1 +- Package Spec generated @@ -0,0 +1 @@ +e7d1cb73a4dd813c9fe3e6a327faebb0 webviz_subsurface_components-0.4.15.tar.gz |