Basics | Plugins | Howtos

Lino basics

Signing in

Most –but not all– Lino sites require you to sign in using a username and password.

user settings

The settings stored for your user account. You can edit your user settings by selecting My settings from the user menu. Some application also provide a quick link [My settings].

user menu

The sub-menu of the main menu that holds commands related to your authentication: signing in or out, editing your user settings, acting as another user, …

The main page

When you enter a Lino site, you see the main page. The main page includes the main menu, some welcome messages, a series of quick links and your dashboard.

Welcome messages get generated dynamically each time your main window is being displayed. Unlike notifications you don’t get rid of them by marking them as seen.

These welcome messages and quick links are determined programmatically, you cannot “configure” them yourself manually. If you think that a welcome message or quick link is missing or superfluous, you should report this to your application developer.

Each dashboard item displays some data from your database. Most Lino applications allow you to configure that dashboard in your user settings.

main page

The content of the browser page presented to the end user before they select any action from the main menu.

See The main page

main menu

The top-level menu that leads to all functions of an application. You can access it in every Lino window. Each time you select a command from the main menu, Lino opens a new window which will be placed over any other open windows. A window remains open until you close it. So you have a stack of windows.

A shortcut link in the main page that opens some data window or executes some other action.

welcome message

A short message in the main page that inform the end user about something after signing in.

dashboard

The series of data views displayed in the main page.

Window types

data window

A window that displays some data from the database. The layout and behaviour of a data window are defined by its data view.

See Data windows.

grid window

A data window in grid mode.

list window

A data window in list mode.

detail window

A data window in detail mode. The layout of a detail window is defined by a detail layout.

A window that shows one row at a time. Unlike the grid window it is meant to focus on that single row and to show more details about it.

insert window

A window that will cause a new database row to be created when you submit it. It asks you to to enter some data fields of the new row.

dialog window

A pop-up window used to enter additional information before actually executing a requested action.

parameter window

A window used to edit the values of the parameters of an action.

A detail window usually opens by double-clicking or hitting enter on one item of a list window.

An insert window can be called from both a detail window and a grid window.

Data windows

Most commands of the main menu open a data window that displays some set of data rows from your database. And in most cases these data rows are presented as a “table” with rows and columns like a spreadsheet.

  • Hit Enter or double click on a row of a grid window to open a detail window on that row (if that table has a detail view defined).

  • Hit Escape or click the X in the upper right corner of the window to close that window and return to the home screen.

  • You can edit individual cells of a grid by hitting F2 or by simply clicking on it.

The toolbar

Most data windows have a toolbar, with a quick search field and a series of buttons for navigating or running actions.

../_images/toolbar.png
toolbar

A row with action buttons at the top of a list window or detail window.

navigation buttons

A series of action buttons used to navigate within a set of data rows, i.e. to go to the previous, next, first or last row within the set of rows defined by a list window.

action button

Any button of a toolbar that will fire an action when you click it.

The quick search field

quick search field

A field where you can enter text for quickly filtering the rows to be displayed.

If the search string starts with “#”, then Lino searches for a row with that primary key.

If the search string starts with “*”, then Lino searches for a row with that reference.

You might wonder how Lino knows where to search when you type some text in the quick search field.

For example, when doing a quick search in a list of persons, Lino searches only the name field and not for example the street. That’s because street names often contain names of persons. A user who enters “berg” in the quick search field don’t want to see all persons living in a street named after a person whose name contained “berg”.

A special type of quick search is when the search string starts with “#”. In that case you get the database row with that primary key.

Display modes

A data view can have different modes to display the data. We call these modes display mode.

display mode

The mode or layout used by a data view to display its data.

Lino knows the following display modes:

grid mode

A display mode that shows data as an editable table with rows and columns like a spreadsheet.

../_images/albums.AllFiles.grid.png
detail mode

A display mode that shows data with one page for each row.

../_images/albums.AllFiles.detail.png
list mode

A display mode that shows data as a list of items.

../_images/albums.AllFiles.list.png
cards mode

A display mode that shows data as “cards”.

../_images/albums.AllFiles.cards.png

A display mode that shows its data as an image gallery.

../_images/albums.AllFiles.gallery.png
summary mode

A display mode that shows a customizable summary of its data.

plain mode

A display mode that shows its data as a “plain” html table that is not editable.

Not all data views feature all display modes. It is up to the application developer to specify which display modes are available in a given data view and which of them is the default.

The grid mode and the plain mode are “tabular” because they use “rows” and “columns”.

Slave panels

In a detail window you can have slave panels.

For example, the lino_xl.lib.contacts plugins differentiates between organizations and persons, each of them has its own database model. A third database model defines the relation between persons and organizations.

Here is the detail window of an organization, which shows the persons who work for this organization (the bottom right panel, Contact persons of Bäckerei Ausdemwald):

../_images/contacts.Companies.detail.png

We call such a panel a slave panel (and its data view a slave table) because they make sense only when the master instance is known. In our example, the organization Bäckerei Ausdemwald is the master instance. Don’t take this politically.

A slave panel has a special button eject in its upper right corner. Click this button to open that slave table in a data window on its own. This is good to know for several reasons:

  • If the slave panel’s display mode is 'summary', the eject button is the only way to see that data as a table.

  • The slave panel is meant as a preview, it has no navigation toolbar and shows only a limited number of rows.

Keep in mind

slave table

A data view that is designed to display only the rows that are related to a given database row, which the slave table calls its master instance.

slave panel

A panel showing data that is related to the current row being displayed in a detail window but stored in a separate database table. The actor behind a slave panel is called a slave table.

master instance

The database object that acts as master of a slave table.

master table

A data view that is not bound to a master instance.

Site parameters

Many Lino applications have a menu command Configure ‣ System ‣ Site parameters, usually available only to site managers.

Lino jargon

Here is a list of the Lino jargon words that you should understand after having read this page.

phantom row

The last, empty, row in a grid window. When you enter something into a cell on this row, Lino will create a new database row. You can double-click on the phantom row to open an insert window and create a new item. Lino adds a phantom row only in a grid window where you have permission to add new rows.

choicelist

A list of concepts that look like database rows but cannot be edited via the web interface. If you want to edit a choicelist, you need to ask your site maintainer. Such a change is usually trivial, but requires at least a server restart.

simple text representation

A single-line plain text that represents a given database row independently of any context.

The application developer can customize this by overriding the __str__ method of the database model.

About front ends

A Lino application can run under two different front ends. The same “soul” can have different “skins”.

ExtJS front end

The classical front end for Lino, based on the Sencha ExtJS JavaScript library.

React front end

The modern front end for Lino, based on ReactJS and the PrimeReact widget library.

Both front ends are actively maintained and used in production. Both have their advantages and limits. The ExtJS front end is older and won’t change very much any more.

As an end user you must decide with your site maintainer which front end you want to use. You may opt to use them both, in which case each front end has its own URL so that you can easily switch between them. For example you might prefer the React front end when accessing Lino from your mobile phone while you use the ExtJS front end when working from your desktop computer.