This project was bootstrapped with Create React App.

##This project for a FileMaker custom app. FileMaker is a "Workplace Innovation Platform" and is the platform I build databases and custom apps for clients. You can read more about FileMaker here: https://www.filemaker.com/

The FileMaker platform works natively with FileMaker inside of a "web viewer" object. We can run any JS in there, and it's useful to do so to provide clients with modern and interactive interfaces. I've written a lot about using JS in FileMaker. https://www.geistinteractive.com/filemaker-javascript/ https://www.geistinteractive.com/?s=javascript

I'm actually teaching a full-day training session on JS and FileMaker at our annual conference. (If you want to come I have a free registration for you! ☺) https://www.filemaker.com/learning/devcon/2019/tracks.html

I work for a company called "Geist Interactive". We have many web-apps that use JS and, more recently use React. I didn't build them, but I tried to understand them. https://www.geistinteractive.com/products/filemaker-rich-text-editor/ https://www.geistinteractive.com/products/filemaker-kanban/ https://www.geistinteractive.com/products/widgetstudio/

##To see the result of the React App in full functionality:

1. Download the trial of FileMaker Pro 18 Advanced: https://www.filemaker.com/trial/
2. Open the TimeAllocations.fmp12 file in FileMaker.

##Preview Video Here I show you what the full-functioninig app looks like. https://vimeo.com/343508103/a8d5dc7fd8

---

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Code Splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

Analyzing the Bundle Size

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

Making a Progressive Web App

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

Advanced Configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

Deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

npm run build fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify