bce.design
minimal tooling, essential dependencies, high productivity, no migrations, web component starter for non-trivial web applications
run
To launch the application:
- Install browsersync
git clone https://github.com/AdamBien/bce.designcd app- Perform:
browser-sync src -f src -b "google chrome" --no-notify
IDE
- Visual Studio Code
- Setup: JS imports
- lit-html plugin for syntax highlighting inside html templates
- redux devtools chrome extension
update dependencies
Checkout libs
external ingredients
- lit-html
- redux toolkit
- vaadin router (suggestion / optional)
- rollup (for updates / optional)
what is BCE?
Boundary Control Entity (BCE) pattern is used to organize elements according to their responsibilities: https://en.wikipedia.org/wiki/Entity-control-boundary.
Why it is needed? BCE was published in 1992 and since then described in various books and articles. Also: the boundary, control, entity icons are available in all modelling, drawing and designing tools.
The best of all: with BCE we don't have to discuss the naming anymore and therefore completely ignore the Parkinson's law of triviality :-).
unidirectional data flow
vaadin router
static hosting on Amazon S3
resources
https://github.com/adambien/mockend is useful as a mock backend with throttling functionality.
Mockend can slow down responses, what simplifies the testing of asynchronous view updates. Fetch-requests in the control layer can be delayed for test purposes.
Article: Web Components, Boundary Control Entity (BCE) and Unidirectional Data Flow with redux