Skip to content

JoernT/Fore

Folders and files

NameName
Last commit message
Last commit date

Latest commit

8431232 · Mar 12, 2021
Feb 11, 2021
Jan 8, 2021
Mar 12, 2021
Mar 12, 2021
Mar 12, 2021
Mar 12, 2021
Mar 12, 2021
Oct 6, 2018
Jan 29, 2021
Mar 12, 2021
Mar 12, 2021
Mar 4, 2021
May 16, 2019
Jul 2, 2020
Dec 6, 2019
Mar 4, 2021
Feb 26, 2021
Feb 27, 2020
Feb 27, 2020
Jun 20, 2019
Mar 12, 2021
Mar 12, 2021
Feb 13, 2020
Feb 21, 2019
Mar 12, 2021
Jun 20, 2019
Jun 20, 2019
Feb 27, 2020

Repository files navigation

Moved to https://github.com/Jinntec/Fore effective after 12.03.2021

Fore

'situated in front of something else' - Merriam Webster

An xformish forms framework in Web Components

Fore is a model-driven forms framework that follows the ideas of the XForms Standard.

Warning

This project is still in its early stages.

Development and Contributions

Contributions are always welcome. Default branch of development is 'dev'. PRs feature additions or bugfixes will always go into 'dev'.

The master branch is only used for releases.

Dependencies

  • see package.json

must be build with npm run build - outputs fontoxpath in 'output' dir.

ATTENTION: due to my humble knowledge with rollup you still have to change the last line of fontoxpath.js to export default fontoxpath; to make it work.

To check if installation was correct run npm run test. Tests should run green.

Preparing assets

To allow browser-compatible module loading there is a npm script called 'empathy'. This must be called whenever new node modules are introduced into the project.

npm run empathy

This will create a directory 'assets' with all dependencies converted to use local pathes instead of node_module pathes.

This approach will eventually change.

Running

npm run start

starts the testserver with 'doc/index.html' as entry page. Under 'examples' on the left you find

Ideas

make model editable in dev mode

introduce a mode which allows to edit the model itself within the page.

  • serialization?
  • the model as an instance?