About the Lino framework¶
- Lino framework¶
Lino is being developed and maintained since 2010 by Rumma & Ko Ltd, a family-owned company in Estonia employing two developers and one system administrator to serve a dozen of customers. Their biggest customers are public administrations in Belgium.
Lino is not well known because nobody sells it. Rumma & Ko Ltd functions well with their customers, they have neither the need nor the resources to attract more customers. But Lino was designed from its beginnings –and is placidly on its way– to become a standard solution for low-cost and sustainably free application development.
Lino is a RAD tool and as such in concurrence with SAP, Oracle ADF and similar big players. There is only one reason why this makes sense: Lino is Sustainably Free Software. It avoids you to get locked into a given vendor or service provider. It can be used by anybody, either yourself or a service provider of your choice, for writing a new Lino application or hosting an existing one. See also The Lino vision.
Lino is based on established Free and Open-Source Software technologies like `Django, React, Sencha ExtJS, Sphinx and Python.
Lino is everything that is documented under the lino-framework.org domain. It is stored as a set of public source repositories : the Lino core, the Lino Extensions Library, a series of Lino applications, a series of front ends and a series of documentation trees.
A Lino site can be used either for internal use by your employees in your local network, or as a public website. All Lino sites have a similar, typical, look and feel, which is optimized for efficient daily usage.
Every Lino site is owned by its site operator who manages user accounts of their site and assigns permissions. The site operator owns the data on their site. The site operator designates a site maintainer who is responsible for installing and updating the software on the site.
Every Lino site has a web interface under a domain or subdomain name, a set of local settings and configuration files, and usually its own database. Multiple sites can share a same database in order to provide different front ends.
- Lino application¶
The product carrier decides which functionalities are available in their Lino application: the database structure (how data is stored), the view layouts (how end users see the data) and the actions (what users can do with the data).
The work of developing and maintaining your own database application is usually expensive and makes sense only for bigger companies. Lino makes it possible also for small and medium-sized organizations.