Skip to content

Commit

Permalink
Release 0.5.0 (#186)
Browse files Browse the repository at this point in the history
* implicit ids in events

* fix timeline selections

* fix corner condition

* allow loading multiple events

* filters on OSM

* WIP: filters as narratives always

* move those dates to the top

* apply narratives only if FILTERS_AS_NARRATIVES set

* update example config

* fix hierarchical tag toggle

* update React to latest

* fix too small message

* desc -> description in sources

* add hack to fix timeline not showing

* add support for arrow keys

* show error for invalid dates

it srsly messes with binary search!

* drop invalidly dated events entirely

* fix corner cases in narrative left/right

* insetSource in filter narrative

* lint

* fix lint

* Bump npm-registry-fetch from 4.0.0 to 4.0.5

Bumps [npm-registry-fetch](https://github.com/npm/registry-fetch) from 4.0.0 to 4.0.5.
- [Release notes](https://github.com/npm/registry-fetch/releases)
- [Changelog](https://github.com/npm/npm-registry-fetch/blob/latest/CHANGELOG.md)
- [Commits](https://github.com/npm/registry-fetch/commits)

Signed-off-by: dependabot[bot] <[email protected]>

* move cover over loading

* add USE_FILTER_DESCRIPTIONS option

* add support for showing filter descriptions in narrativised mode

* infopopup copy more general

* make caret flip on card open

* nicer date, remove precision magic

* cover more sensible defaults

* up and down arrows for movement

* better logo styling, variable button text

* add bellingcat logo

* add support for custom fields

* nicer dates in timeline header

* don't rely on unique location names

* update cover

* cover with optional buttons

* change to red!

* fix img occlusion

* fix on safari

* ++

* update

* lint

* Remove unneccesary if statement

name = Sol
email = [email protected]

* Update app.js

Update for linter

* Remove lines for linter

* remove comment on minTime and maxTime variables

* Bump lodash from 4.17.11 to 4.17.19

Bumps [lodash](https://github.com/lodash/lodash) from 4.17.11 to 4.17.19.
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@4.17.11...4.17.19)

Signed-off-by: dependabot[bot] <[email protected]>

* add default rangeLimits

* fix corner case when bad data

* rm unnecessary deps

* initial search bar feature added on new branch

* bug fixes

* lint fixes

* more lint fixes

* cards clickability added

* lint fixes

* lint

* map and cards clickable

* lint fix

* lint fixes

* lint fixes

* Refactored to pass down methods as props. Added CSS pointer

* lint fix

* rename variables

* remove moveinnarrative function

* refactor onselect

* added and changed var names

* lint fixes

* lint fixes

* removed console log

* simplified component logic

* lint fixes

* console logs removed and changes made

* Pulling in associations correctly; condensed filters and narratives into associations

* Modified validators file to match new associations schema and necessary semantic and sanitization changes

* Finding association duplicates; sanitizing appropriately; beginning to edit narrativise function in UI

* Filter render broken; moved narrative and narrativeState to app.filters and restructured appropriately with narrativeIdx selector

* Refactored filter list for display; converting filter paths to node, child objects that are toggleable

* correct

* Bump node-sass from 4.12.0 to 4.13.1

Bumps [node-sass](https://github.com/sass/node-sass) from 4.12.0 to 4.13.1.
- [Release notes](https://github.com/sass/node-sass/releases)
- [Changelog](https://github.com/sass/node-sass/blob/master/CHANGELOG.md)
- [Commits](sass/node-sass@v4.12.0...v4.13.1)

Signed-off-by: dependabot[bot] <[email protected]>

* requested changes made

* Bump js-yaml from 3.12.0 to 3.14.0

Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 3.12.0 to 3.14.0.
- [Release notes](https://github.com/nodeca/js-yaml/releases)
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@3.12.0...3.14.0)

Signed-off-by: dependabot[bot] <[email protected]>

* Bump esm from 3.0.84 to 3.2.25

Bumps [esm](https://github.com/standard-things/esm) from 3.0.84 to 3.2.25.
- [Release notes](https://github.com/standard-things/esm/releases)
- [Commits](standard-things/esm@3.0.84...3.2.25)

Signed-off-by: dependabot[bot] <[email protected]>

* Bump http-proxy from 1.17.0 to 1.18.1

Bumps [http-proxy](https://github.com/http-party/node-http-proxy) from 1.17.0 to 1.18.1.
- [Release notes](https://github.com/http-party/node-http-proxy/releases)
- [Changelog](https://github.com/http-party/node-http-proxy/blob/master/CHANGELOG.md)
- [Commits](http-party/node-http-proxy@1.17.0...1.18.1)

Signed-off-by: dependabot[bot] <[email protected]>

* Working narrative feature minus getNarrativeLinks (need further clarification); working on modifying narrativise filters feature

* Need clarification on USE_ASSOCIATION_DESCRIPTIONS for narrativise feature

* Setting USE_ASSOC_DESC to fals

* Beginning to remove extraneous components and logic

* Deprecated usage of env constants USE_ASSOCIATION_DESCRIPTIONS, USE_NARRATIVESand FILTERS_AS_NARRATIVES to instead check for existence of narratives; deprecated usage of unused components such as CardFilters, CardNarrative, and NarrativeLink

* Got rid of narrativeLinks in CardStack and deprecated usage of USE_ASSOCIATION_DESCRIPTIONS in embedded logic

* Fixed up event schema to reduce filters and narratives to associations; removed extraneous comments for deprecated functions

* Events now only have associations; when filters and narratives are needed fromevents, interpolate from evt.associations

* Removed tags array from event schema

* Minor typo with env var GRAPH_NONLOCATED

* Fixed linting issues

* No associated events for a filter => alert shows when attempting to narrativise

* Linting fixes

* map changed to some

* console.log removed

* Need to resolve minor issues with association duplicates; removing prototype tooltip; source not showing up and event gets deselected

* Removing tooltip import

* initial search bar feature added on new branch

* lint fixes

* more lint fixes

* cards clickability added

* lint fixes

* requested changes made

* map changed to some

* console.log removed

* Wrote new recursive function to accurately map filter paths to filter list in panel; need to fix selection of filters upon toggle

* Debugging issues with broken sources

* Issue with the difference between clicking on a card and clicking on the caret (ie is there an onClick functionality for the card?)

* Working onSelect with respect to caret toggle; onSelect doesnt fire off when caret is selected

* Linting fixes

* Working multi-select; need to stop firing update timerange upon select

* rm unused search

* rm import

* Removed extraneous USE_SEARCH declarations

* Timeline no longer adjusts upon selection of events; set of events aren't modified according to their place in the timeline

* Building with supercluster; working on map refactor

* Clustering working upon zoom; loading cluster data appropriately initially; need to style and add markers

* Individual points showing with cluster logic; need to define styling and appearance for larger clusters

* Creating cluster styling and component to handle cluster visualization and mapping

* Working cluster visualization; need to modify styling for clusters for size and work out color based on events

* Cluster sizes showing up appropriately and unclustering upon zoom; need to nail down styling and add onSelect for clusters

* Getting appropriate clusterZoom; flyto moving to incorrect location on map

* Working onCluster select; zooming in and watching clusters break down into individual clusters and points

* Broken onClick clusters working after validating longitude and latitude and only allowing locations to contain valid coordinates

* Working on select that selects all events in a cluster; need to configure UI to both zoom and select events

* Removed logic for selecting all cards on cluster select; putting out PR to get feedback

* Linting fixes

* Removing commented out sections

* Categories showing up on timeline with events; events are stacked on both and connected by a bar which looks like a UI bug somewhere

* Working filters with added check to make sure empty locations dont create clusters

* Configuring maxbounds in config to allow pan to not snap out of center

* Bug with graph nonlocated and getY function; need to refactor toolbar so that it selects the categories on the timeline

* Setting initial categories upon load; need to modify for timeline and related events

* Events showing up on timeline after interpolating categories from associations and passing into getY

* Ability to toggle categories on / off on timeline

* Rewrote opacity alg for clusters

* Modified cluster styling to have gradients

* Changed back to normal opacities instead of radial gradients; could add a var that's read from the config to determine styling: radial gradient || normal opacity

* Modified clusters to take in radial gradient as input if specified

* Removed commented out logic

* Linting fixes

* Linting fixes

* Created utility function isIdentical; moved DefsClusters into Clusters file

* Some linting fixes

* Injecting loading overlay into map for cases where domain hasnt been loaded yet

* Removed line

* Loads index when locations are finally available in props; added through componentDidUpdate method

* Linting fixes

* check for USE_CATEGORIES

* fix timeline render when there are no categories

* return reduce logic for when event shadows exist

* lint

* fix corner case where clusters sometimes remain on screen without events

* lint

* Working index load on initial map render; needed to add callback to set state function

* Moved supercluster config outside of map; to set the lowest level at which clusters appear, set maxZoom in config

* Trailing comma

* Feature/ux fixes (#167)

* fix card toggle

* fix bug and bar marker

* reinstate timeline arrows

* adjust (hard to interpret) category y calculation

* shadows for markers as well

* return markers when there are no categories

* remove year in timeline

* make notifications optional

* WIP: render hovered counts

* show number on hover

* lint

* revert to filteredLocations

* linting

* return mapClustersToLocations

* 💄

* lint

Co-authored-by: efarooqui <[email protected]>

* fix check to render a dot or bar in timeline

* Feature/add coloring algorithm (#169)

* Fixed bug: when all child filters unselected, turn off parent as well

* Refactored placement of onSelectFilter to be in Layout; working logic for updating coloring sets

* Linting fixes and removal of console logs

* Added separate component for colored markers which clusters and events will use; working calculation of color percentages based off of coloringset

* Working colors for clusters; need to implement for individual points as well

* Adding two new features to select whether to color by association or by category (can't do both)

* Working colors for filter list panel; text and checkbox change according to colorset groupings

* Working timeline events with coloring algorithm

* Handle select acts different on map when we don't render all points and only filter through clusters; can fix this by not filtering before passing in locations to events in map

* Removed extraneous prop

* Working point count on hover again; numbers were showing up below the colored markers

* Linting fixes and minor refactor of calculateColorPercentage for linting to ass

* Comments and more linting fixes

* add dev command for windows subsystem for linux

* return default styles for category toggles

* dynamically filter out timelines

* calibrate styling

* further calibrations

* correct contrast

* lint

Co-authored-by: efarooqui <[email protected]>
Co-authored-by: Lachlan Kermode <[email protected]>

* fix recursive case

fix corner case for nested filters

cleanup

* fix corner case for toggling parents off

* Update utilities.js

change opacity back to not using a base value

* Update toolbar.scss

removing hover and default active color for name of filter in panel

* Feature/add coloring algorithm (#172)

* Fixed bug: when all child filters unselected, turn off parent as well

* Refactored placement of onSelectFilter to be in Layout; working logic for updating coloring sets

* Linting fixes and removal of console logs

* Added separate component for colored markers which clusters and events will use; working calculation of color percentages based off of coloringset

* Working colors for clusters; need to implement for individual points as well

* Adding two new features to select whether to color by association or by category (can't do both)

* Working colors for filter list panel; text and checkbox change according to colorset groupings

* Working timeline events with coloring algorithm

* Handle select acts different on map when we don't render all points and only filter through clusters; can fix this by not filtering before passing in locations to events in map

* Removed extraneous prop

* Working point count on hover again; numbers were showing up below the colored markers

* Linting fixes and minor refactor of calculateColorPercentage for linting to ass

* Comments and more linting fixes

* add dev command for windows subsystem for linux

* return default styles for category toggles

* dynamically filter out timelines

* calibrate styling

* further calibrations

* correct contrast

* lint

* wip: fixing corner case

* Cluster opacity feature was out of date

* When deselecting a child, whose parent is on, you cant reselect the child; fixed that bug but replaced it with a bug where you deselect a child and then toggle the parent and the toggle of the child switches instead of toggling like the parent

* generalize isOn check when creating click handler

* rename vars, fix styling

* rm cherrpick

Co-authored-by: efarooqui <[email protected]>

* Importing <Card /> from NPM-published design-system library (#171)

* Importing cards from NPM

* Added an abstraction inside the store and config for creating layouts for cards

* Adding layout render order for Card

* Allowing lists in the reducer validation

* Added design system package to package.json

* Any version over 0.5.0

* fix lint

Co-authored-by: Lachlan Kermode <[email protected]>

* Using new Card API

* Feature/infopopup (#173)

* make intropopup possible

* aesthetic changes

* lint

* correct infopopup styles

* Added new fields to the rendering of the Card Component

* Adding color for categories

* Added against field

* Added markdown component for hiding source

* Lint fix

* Added new layout for cards

* Update version of design-system

* Feature/handle cluster select from timeline (#175)

* Updating some styles for cover; updating copy

* Wrote up getSelectedClusters function; testing

* Working on select with clusters being highlighted; rendering highlight around both clusters and individual points, so there's a little overlap

* Removed extraneous props being passed down to cluster

Co-authored-by: efarooqui <[email protected]>

* Feature/update splash page copy (#176)

* Updating some styles for cover; updating copy

* Changed font size to 18

Co-authored-by: efarooqui <[email protected]>
Co-authored-by: Lachlan Kermode <[email protected]>

* Feature/smallfixes (#177)

* return logos

* dates w/o commas

* make arrows slightly larger

* intro/info popup fixes

* Pin infopopup to top, let it float on top of timeline on reduced viewport height

* Bump up opacity of infopopup

* Lint fix

* Make width responsive through a CSS variable that's accessed in React

* some styling fixes (#178)

* logos at bottom

* use GT-Zirkon font

* update filter/category copy

* add a fallback font

* stop tracking

* make timeline smaller for smaller laptops

* fix for firefox responsive intropopup

* mobile fallback

* update design system version

* update example (#180)

* Don't fall back when on tablet - Fix infopoup on top of screen, so the close button isn't obscured on small viewports

* Added generators for card layouts.  (#182)

* Added generators for card layouts. These are optionally defined in the timemap config

* Removed US2020-specific layout generation - now it's being specified in the config

* amend config (#183)

* update CONTRIBUTING.md (#185)

* update contributing

* update READMe

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Sol <[email protected]>
Co-authored-by: efarooqui <[email protected]>
Co-authored-by: Sol Abrahams <[email protected]>
Co-authored-by: Ebrahem Farooqui <[email protected]>
Co-authored-by: Zac Ioannidis <[email protected]>
  • Loading branch information
7 people authored Nov 25, 2020
1 parent 13a8420 commit 32feff8
Show file tree
Hide file tree
Showing 81 changed files with 5,022 additions and 4,570 deletions.
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ tags.lock
tags.temp

src/\.DS_Store
src/assets/fonts

\.DS_Store

Expand Down
123 changes: 69 additions & 54 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,28 @@
# Contributing to TimeMap

First and foremost, thank you so much. We really appreciate you take the time to try and contribute and make TimeMap better for those who use it.

#### Contributing means many things

Contributing can indeed be about contributing code or creating an issue, but can also take many other forms, and this document is an attempt to describing what are all the possible ways in which you can contribute.
Hi there! Thank you already, for taking the time to try and contribute and
improve timemap. This document is the place to start on your journey. Read it
thoroughly!

## What do I need to know to help?
### Javascript / React / Redux
In order to contribute code upstream, you'll likely need to have a sense of ES6
Javascript, React, and Redux. If these terms are new to you, or not as familiar
as you might like, here's a good tutorial to get you up to speed:

- [Building a voting app with Redux and React](https://teropa.info/blog/2015/09/10/full-stack-redux-tutorial.html)

### Node JS and Docker
Timemap doesn't actually use these technologies; but the main way of getting up
and running with a data provider for timemap,
[datasheet-server](https://github.com/forensic-architecture/datasheet-server),
does, and so they're helpful to know.

## Do I need to be an experienced JS developer?
Contributing can of course be about contributing code, but it can also take
many other forms. A great amount of work that remains to be done to make
timemap a usable community tool doesn't involve writing a line of code. The
following are all very welcome contributions:

- Updating or correcting documentation
- Fixing an open issue
Expand All @@ -13,52 +31,49 @@ Contributing can indeed be about contributing code or creating an issue, but can

If you're new to this project, you could check the issues that are tagged ["good first issue"](https://github.com/forensic-architecture/timemap/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22). These are generally those that are considered easy ways in.

#### Showing support for TimeMap

Please keep in mind that open source software is built by people like you, who spend their free time creating things the rest the community can use.

There are other ways in which you can contribute to the communal success of this project, such as starring the [project](https://github.com/forensic-architecture/timemap) on Github.

## Getting Started

- Make sure you have a [GitHub account](https://github.com/signup/free)
- Fork the repository on GitHub

## Issues

WIP

### Before creating an issue

Try to follow these guidelines:

- **Investigate the issue**: WIP
- **See if a ticket already exists**: WIP
- **Ask the community**: WIP
- **Proceed in creating your issue**: WIP

### Creating an issue

WIP

## Pull Requests

### Before making changes

WIP. Here we'll describe what the expected process and workflow is when making code changes, with regards to branching, forking and so on.

### Submitting changes as Pull Requests

WIP

## Additional resources

More information will be available on the [git workflow wiki page](https://github.com/forensic-architecture/timemap/wiki).

You can also refer to Github's guide to [forking a repository](https://help.github.com/articles/fork-a-repo/) and to [syncing a fork](https://help.github.com/articles/syncing-a-fork/).

If you have any questions or just want to chat, please join our team [fa_open_source](https://keybase.io/team/fa_open_source) on Keybase for community discussion. Keybase is a great platform for encrypted chat and file sharing.

## Other

This contributing guide is based on the guidelines of the [SuperCollider contributing guide](https://raw.githubusercontent.com/supercollider/supercollider/develop/CONTRIBUTING.md).
## How do I make a contribution?

1. Make sure you have a [GitHub account](https://github.com/signup/free)
2. Fork the repository on GitHub. This is necessary so that you can push your
changes, as you can't do this directly on our repo.

3. Get set up with a local instance of timemap and datasheet-server. The easiest
way to do this is by reading [this blog post on our website](https://forensic-architecture.org/investigation/timemap-for-cartographic-platforms).
4. [Join our Discord server](https://discord.gg/PjHKHJD5KX). Here you'll be able
to track commits that are actively being made across our projects; but more
importantly it's where you can ask questions if something's not clear or
not working as you expect. The #timemap and #support channels are the two
best places to ask questions about setting timemap up.

Once you're set up with a local copy of timemap and datasheet-server, you can
start modifying code and making changes.

When you're ready to submit a contribution, you can do it by making a pull
request from a branch on your forked copy of timemap to this repository. You
can do this with the following steps:
1. Push the changes to a remote repository. If the changes you have made
address a bug, you should name it `bug/{briefdesc}`, where `{briefdesc}` is
a hyphen-separated description of your change. If instead you are
contributing changes as a feature request, name it `feature/{briefdesc`}. If
in doubt, prefix your branch with `feature/`.
2. Submit a pull request to the `develop` branch of `forensic-architecture/timemap`.
3. Wait for the pull request to be reviewed by a maintainer.
4. Make changes to the pull request if the reviewing maintainer recommends
them.
5. Celebrate your success once your pull request is merged!

## How do I validate my changes?
We are still working on a set of tests. Right now, it is enough to confirm that
the application runs as expected with `npm run dev`. If your changes introduce
other issues, a maintainer will flag it in stage 3 of the submission process
above.

## Credits
This contributing guide is based on the guidelines of both the
[SuperCollider contributing guide](https://raw.githubusercontent.com/supercollider/supercollider/develop/CONTRIBUTING.md),
and the [nteract contributing
guide](https://github.com/nteract/nteract/blob/master/CONTRIBUTING.md) (two
excellent open source projects!).

Thanks to [Scott Carver](https://github.com/scztt) for advice on how to put
a guide together.
29 changes: 12 additions & 17 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
</h1>

<p align="center">
<strong>TimeMap is a tool for exploration, monitoring and classification of incidents in time and space.<br>See a <a href="https://ilovaisk.forensic-architecture.org">live instance here</a>.</strong><br>
<strong>TimeMap is a tool for exploration, monitoring and classification of incidents in time and space.<br>See a <a href="https://blmprotests.forensic-architecture.org">live instance here</a>.</strong><br>
</p>

![](docs/example-timemap.png)
Expand All @@ -27,53 +27,48 @@ A fully-functioning live version can be found as a result of the Forensic Archit
## Get up and running

These easiest way to get up and running with timemap and datasheet-server is to
[follow the tutorial here](https://forensic-architecture.org/investigation/timemap-for-cartographic-platforms).
[follow the in-depth tutorial here](https://forensic-architecture.org/investigation/timemap-for-cartographic-platforms).

### Instructions
### Quickstart

1. Pull this repository.

```shell
git clone https://github.com/forensic-architecture/timemap
```

2. Install dependencies via yarn (recommended, it's just faster) or npm.
2. Install dependencies via npm.

```shell
yarn # npm install
npm install
```

3. Run it via yarn.
3. Run the development server, which will be available at http://localhost:8080.

```shell
yarn dev # npm run dev
npm run dev
```

To run with a file that is not 'config.js' in the root directory, set the `CONFIG` environment variable:
```
CONFIG="myotherconfig.js" yarn dev
CONFIG="myotherconfig.js" npm run dev
```

IMPORTANT: Although the application will run _just like that_, in order for TimeMap to be able to display interesting information, you'll have to make sure to have the capacity to serve data, as well as adjusting some configuration parameters. See next section.
In order for TimeMap to be able to display interesting information, you'll have to make sure to have the capacity to serve data, as well as adjusting some configuration parameters. Follow the in-depth tutorial linked above!

#### Running without datasheet-server

Technically, timemap is backend agnostic, but it requires a series of endpoints to provide data for it to visualize. The data is expected in JSON format. Some data elements are required and their format has some required fields. Other additional endpoints are optional, and if enabled, they simply add features to your taste.

The combination of all these data types is called the `domain` of the application in the context of TimeMap.

## Contribute
### Contributing

### [Code of Conduct](CODE_OF_CONDUCT.md)
Interested in helping us improve timemap? See [our contributing guide](CONTRIBUTING.md) to learn how to contribute and make suggestions. Please also read our [code of conduct](CODE_OF_CONDUCT.md). We endeavour to cultivate a community around timemap and other OSS at Forensic Architecture that is inclusive and respectful. Please join us in this!

Please read before contributing. We endeavour to cultivate a community around timemap and other OSS at Forensic Architecture that is inclusive and respectful. Please join us in this!

### [Contributing Guide](CONTRIBUTING.md)

Learn more about our development process, i.e. how to propose bugfixes and improvements.

## Community
If you have any questions or just want to chat, please join our team [fa_open_source](https://keybase.io/team/fa_open_source) on Keybase for community discussion. Keybase is a great platform for encrypted chat and file sharing that we use as a public forum.
If you have any questions or just want to chat, please [join our Discord server](https://discord.gg/PjHKHJD5KX). This is where you can ask questions, as well as track our internal development on timemap and other codebases at Forensic Architecture.

## [License](LICENSE.md)

Expand Down
3 changes: 1 addition & 2 deletions docs/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,7 @@ The URLs for these endpoints, as well as other configurable settings in your tim
| SITES_EXT | Endpoint for sites, concatenated with SERVER_ROOT | String | Yes |
| MAP_ANCHOR | Geographic coordinates for original map anchor | Array of numbers | No |
| MAPBOX_TOKEN | Access token for Mapbox satellite imagery | String | No |
| features.USE_FILTERS | Enable / Disable filters | boolean | No |
| features.USE_SEARCH | Enable / Disable search | boolean | No |
| features.USE_ASSOCIATIONS | Enable / Disable filters | boolean | No |
| features.USE_SITES | Enable / Disable sites | boolean | No |

In this configuration file you'll need to add your Mapbox token (see [here for more info](https://www.mapbox.com/help/define-access-token/)). Additionally, you'll need to replace the required endpoints by functioning ones. Finally, you'll want to initialize your application set in `MAP_ANCHOR`, as a (lat, long) pair, which determines the specific location at which the application will center itself on start.
Expand Down
Binary file modified docs/example-timemap.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
17 changes: 3 additions & 14 deletions example.config.js
Original file line number Diff line number Diff line change
Expand Up @@ -4,34 +4,23 @@ module.exports = {
SERVER_ROOT: 'http://localhost:4040',
EVENTS_EXT: '/api/timemap_data/export_events/deeprows',
CATEGORIES_EXT: '/api/timemap_data/export_categories/rows',
FILTERS_EXT: '/api/timemap_data/export_filters/tree',
ASSOCIATIONS_EXT: '/api/timemap_data/export_associations/deeprows',
SOURCES_EXT: '/api/timemap_data/export_sources/deepids',
NARRATIVE_EXT: '',
SITES_EXT: '',
SHAPES_EXT: '',
DATE_FMT: 'MM/DD/YYYY',
TIME_FMT: 'hh:mm',
// MAPBOX_TOKEN: 'pk.YOUR_MAPBOX_TOKEN',
store: {
app: {
map: {
anchor: [31.356397, 34.784818]
}
},
ui: {
style: {
// tiles: 'your-mapbox-account-name/x5678-map-id'
}
},
features: {
USE_CATEGORIES: false,
CATEGORIES_AS_FILTERS: false,
USE_FILTERS: false,
USE_SOURCES: true,
USE_ASSOCIATIONS: true,
USE_SOURCES: false,
USE_COVER: false,
USE_SEARCH: false,
USE_SITES: false,
USE_SHAPES: false,
GRAPH_NONLOCATED: false,
HIGHLIGHT_GROUPS: false
}
Expand Down
21 changes: 7 additions & 14 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -6,41 +6,34 @@
"private": true,
"scripts": {
"dev": "webpack-dev-server --content-base static --mode development",
"dev:wsl": "npm run dev -- --host 0.0.0.0",
"build": "NODE_ENV=production webpack --mode production",
"test": "ava --verbose",
"test-watch": "ava --watch",
"lint": "standard \"src/**/*.js\" \"src/**/*.jsx\" \"test/**/*.js\"",
"lint:fix": "npm run lint -- --fix"
},
"dependencies": {
"babel-polyfill": "^6.26.0",
"@forensic-architecture/design-system": "0.6.1",
"d3": "^5.7.0",
"es6-promise": "^4.1.1",
"esm": "^3.2.25",
"joi": "^14.0.1",
"js-yaml": "^3.13.1",
"leaflet": "^1.0.3",
"marked": "^0.7.0",
"moment": "^2.26.0",
"normalizr": "^3.2.3",
"npm-check-updates": "^3.1.20",
"object-hash": "^1.3.0",
"ramda": "^0.26.1",
"react": "^16.6.3",
"react": "^16.13.1",
"react-device-detect": "^1.6.2",
"react-dom": "^16.6.3",
"react-dom": "^16.13.1",
"react-image": "^1.5.1",
"react-portal": "^4.2.0",
"react-redux": "^5.0.4",
"react-tabs": "3.0.0",
"react-zoom-pan-pinch": "^1.6.1",
"redux": "^3.6.0",
"redux-thunk": "^2.2.0",
"reselect": "^3.0.1",
"uuid": "^3.1.0",
"video-react": "^0.13.1",
"video.js": "^5.19.2",
"whatwg-fetch": "^2.0.3"
"supercluster": "^7.1.0",
"video-react": "^0.13.1"
},
"devDependencies": {
"@babel/core": "^7.1.2",
Expand All @@ -53,7 +46,7 @@
"html-webpack-plugin": "^3.2.0",
"mini-css-extract-plugin": "^0.4.4",
"mocha": "^5.2.0",
"node-sass": "4.12.0",
"node-sass": "4.13.1",
"redux-devtools": "^3.4.0",
"sass-loader": "^7.1.0",
"standard": "^12.0.1",
Expand Down
Loading

0 comments on commit 32feff8

Please sign in to comment.