Under Development
Kolibri and its home page are under development at GitHub, which is also the place for any discussions and issues.
Contributions
Kolibri aims to be a sustainable, high-quality toolkit. Contributions are validated through usability testing and automated tests. Industry experts and academic advisers assess the code quality and the completeness of the documentation. Every contribution must have proven its worth in an application.
- Andermatt, Brodwolf
- code, git book
- Häfliger, Misic
- code, documentation.pdf
- Christen, Robin
- code, git book
- Berchtold, Duss
- documentation.pdf, info
- Wild, Wyss
- code, documentation
- Altermatt, Schnidrig
- code, documentation, showcase
- Advisors and Experts
- Prof. Dierk König, Fabian Affolter, Dr. Dieter Holz, Daniel Kröni, François Martin, Marco Sanfratello, Dirk Lemmermann
Live Test Cases
Have a look at the live test case report.
Showing the report actually runs the latest test cases live in your current browser window. The Kolibri test facility does not require any build steps or extra tooling.
A Live Tutorial from Examples
It is instructive to take a tour through the examples in order to understand how Kolibri helps with developing web applications. They are arranged from simple to increasingly complex and introduce new concepts along the way.
Create a simple form very efficiently with just one line of code.
Enforce and test business rules in the UI to interactively manage working hours in a day.
Put the daily work hours in a week overview and keep all the business rules in place by simply delegating to what we have done before. Show compositionality of controllers and projectors.
Have some fun with multi-way editing in a master-detail view. It builds on what we already know and adds real interactive richness to our application.
Wait for more to come here ...
Installation without dependency
Common wisdom has it that web development comes with a myriad of dependencies. Kolibri follows a different approach. We do not use any dependencies at all - neither at runtime nor at build-time. There actually is no build-time since we never need building.
Likewise, a project that uses Kolibri should be able to follow the same approach and not even depend on Kolibri itself!
We assume that you simply copy the Kolibri source code (everything under the src directory) into your own project. You become the owner of the copied code - just as if you copied it from stackoverflow.
This copy includes the documentation, examples, the testing facility, and the test cases. It will likely contain more than you need for your production code but that does no harm. Kolibri is fully written as ES6 modules, which means that you can "treeshake" with any bundler to remove all unused parts from your own production bundle while still having all the best developer experience when programming.
For the die-hard "but I just want to have Kolibri as a single file" developers, there is an automatically generated production bundle that always reflects the latest version (see version). It contains the production code, type definitions, and documentation but neither the test cases nor the examples. This might be useful for quick experiments.