docs(user): move collections one level up
BIN
docs/User Guide/User Guide/Collections/10_Calendar View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 3.5 KiB |
BIN
docs/User Guide/User Guide/Collections/10_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 605 B |
BIN
docs/User Guide/User Guide/Collections/11_Calendar View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 2.8 KiB |
BIN
docs/User Guide/User Guide/Collections/11_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 22 KiB |
BIN
docs/User Guide/User Guide/Collections/12_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 68 KiB |
BIN
docs/User Guide/User Guide/Collections/13_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 31 KiB |
BIN
docs/User Guide/User Guide/Collections/14_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 5.4 KiB |
BIN
docs/User Guide/User Guide/Collections/15_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 44 KiB |
BIN
docs/User Guide/User Guide/Collections/16_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 249 KiB |
BIN
docs/User Guide/User Guide/Collections/17_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 179 B |
BIN
docs/User Guide/User Guide/Collections/18_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 14 KiB |
BIN
docs/User Guide/User Guide/Collections/1_Calendar View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 909 B |
BIN
docs/User Guide/User Guide/Collections/1_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 141 KiB |
BIN
docs/User Guide/User Guide/Collections/1_Presentation View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 264 KiB |
BIN
docs/User Guide/User Guide/Collections/2_Calendar View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 14 KiB |
BIN
docs/User Guide/User Guide/Collections/2_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 210 KiB |
BIN
docs/User Guide/User Guide/Collections/3_Calendar View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 11 KiB |
BIN
docs/User Guide/User Guide/Collections/3_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 1.8 KiB |
BIN
docs/User Guide/User Guide/Collections/4_Calendar View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 7.6 KiB |
BIN
docs/User Guide/User Guide/Collections/4_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 3.5 KiB |
BIN
docs/User Guide/User Guide/Collections/5_Calendar View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 1014 B |
BIN
docs/User Guide/User Guide/Collections/5_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 9.6 KiB |
BIN
docs/User Guide/User Guide/Collections/6_Calendar View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 966 B |
BIN
docs/User Guide/User Guide/Collections/6_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 62 KiB |
BIN
docs/User Guide/User Guide/Collections/7_Calendar View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 4.3 KiB |
BIN
docs/User Guide/User Guide/Collections/7_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 8.5 KiB |
BIN
docs/User Guide/User Guide/Collections/8_Calendar View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 42 KiB |
BIN
docs/User Guide/User Guide/Collections/8_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 338 KiB |
BIN
docs/User Guide/User Guide/Collections/9_Calendar View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 3.0 KiB |
BIN
docs/User Guide/User Guide/Collections/9_Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 108 KiB |
64
docs/User Guide/User Guide/Collections/Board View.md
vendored
Normal file
@@ -0,0 +1,64 @@
|
||||
# Board View
|
||||
<figure class="image"><img style="aspect-ratio:918/248;" src="Board View_image.png" width="918" height="248"></figure>
|
||||
|
||||
The Board view presents sub-notes in columns for a Kanban-like experience. Each column represents a possible value for a status label, which can be adjusted.
|
||||
|
||||
## How it works
|
||||
|
||||
When first creating a collection of _Board_ type, a few subnotes will be created, each having a `#status` label set. The board then groups each note by the value of the status attribute.
|
||||
|
||||
Notes are displayed recursively, so even the child notes of the child notes will be displayed. However, unlike the <a class="reference-link" href="Table%20View.md">Table View</a>, the notes are not displayed in a hierarchy.
|
||||
|
||||
## Interaction with columns
|
||||
|
||||
* Create a new column by pressing _Add Column_ near the last column.
|
||||
* Once pressed, a text box will be displayed to set the name of the column. Press <kbd>Enter</kbd> to confirm, or <kbd>Escape</kbd> to dismiss.
|
||||
* To reorder a column, simply hold the mouse over the title and drag it to the desired position.
|
||||
* To delete a column, right click on its title and select _Delete column_.
|
||||
* To rename a column, click on the note title.
|
||||
* Press Enter to confirm.
|
||||
* Upon renaming a column, the corresponding status attribute of all its notes will be changed in bulk.
|
||||
* If there are many columns, use the mouse wheel to scroll.
|
||||
|
||||
## Interaction with notes
|
||||
|
||||
* Create a new note in any column by pressing _New item_
|
||||
* Enter the name of the note and press <kbd>Enter</kbd> or click away. To dismiss the creation of a new note, simply press <kbd>Escape</kbd> or leave the name empty.
|
||||
* Once created, the new note will have an attribute (`status` label by default) set to the name of the column.
|
||||
* To open the note, simply click on it.
|
||||
* To change the title of the note directly from the board, hover the mouse over its card and press the edit button on the right.
|
||||
* To change the state of a note, simply drag a note from one column to the other to change its state.
|
||||
* The order of the notes in each column corresponds to their position in the tree.
|
||||
* It's possible to reorder notes simply by dragging them to the desired position within the same columns.
|
||||
* It's also possible to drag notes across columns, at the desired position.
|
||||
* For more options, right click on a note to display a context menu with the following options:
|
||||
* Open the note in a new tab/split/window or quick edit.
|
||||
* Move the note to any column.
|
||||
* Insert a new note above/below the current one.
|
||||
* Archive/unarchive the current note.
|
||||
* Delete the current note.
|
||||
* If there are many notes within the column, move the mouse over the column and use the mouse wheel to scroll.
|
||||
|
||||
## Keyboard interaction
|
||||
|
||||
The board view has mild support for keyboard-based navigation:
|
||||
|
||||
* Use <kbd>Tab</kbd> and <kbd>Shift</kbd>+<kbd>Tab</kbd> to navigate between column titles, notes and the “New item” button for each of the columns, in sequential order.
|
||||
* To rename a column or a note, press <kbd>F2</kbd> while it is focused.
|
||||
* To open a specific note or create a new item, press <kbd>Enter</kbd> while it is focused.
|
||||
* To dismiss a rename of a note or a column, press <kbd>Escape</kbd>.
|
||||
|
||||
## Configuration
|
||||
|
||||
### Grouping by another attribute
|
||||
|
||||
By default, the label used to group the notes is `#status`. It is possible to use a different label if needed by defining a label named `#board:groupBy` with the value being the attribute to use (without `#` attribute prefix).
|
||||
|
||||
> [!NOTE]
|
||||
> It's currently not possible to set a relation as the grouping criteria. There are plans to add support for it.
|
||||
|
||||
## Interaction
|
||||
|
||||
## Limitations
|
||||
|
||||
* It is not possible yet to use group by a relation, only by label.
|
||||
BIN
docs/User Guide/User Guide/Collections/Board View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 18 KiB |
128
docs/User Guide/User Guide/Collections/Calendar View.md
vendored
Normal file
@@ -0,0 +1,128 @@
|
||||
# Calendar View
|
||||
<figure class="image image-style-align-center"><img style="aspect-ratio:767/606;" src="4_Calendar View_image.png" width="767" height="606"></figure>
|
||||
|
||||
The Calendar view will display each child note in a calendar that has a start date and optionally an end date, as an event.
|
||||
|
||||
The Calendar view has multiple display modes:
|
||||
|
||||
* Week view, where all the 7 days of the week (or 5 if the weekends are hidden) are displayed in columns. This mode allows entering and displaying time-specific events, not just all-day events.
|
||||
* Month view, where the entire month is displayed and all-day events can be inserted. Both time-specific events and all-day events are listed.
|
||||
* Year view, which displays the entire year for quick reference.
|
||||
* List view, which displays all the events of a given month in sequence.
|
||||
|
||||
Unlike other Collection view types, the Calendar view also allows some kind of interaction, such as moving events around as well as creating new ones.
|
||||
|
||||
## Creating a calendar
|
||||
|
||||
| | | |
|
||||
| --- | --- | --- |
|
||||
| 1 |  | The Calendar View works only for Collection note types. To create a new note, right click on the note tree on the left and select Insert note after, or Insert child note and then select _Collection_. |
|
||||
| 2 |  | Once created, the “View type” of the Collection needs changed to “Calendar”, by selecting the “Collection Properties” tab in the ribbon. |
|
||||
|
||||
## Creating a new event/note
|
||||
|
||||
* Clicking on a day will create a new child note and assign it to that particular day.
|
||||
* You will be asked for the name of the new note. If the popup is dismissed by pressing the close button or escape, then the note will not be created.
|
||||
* It's possible to drag across multiple days to set both the start and end date of a particular note.
|
||||

|
||||
* Creating new notes from the calendar will respect the `~child:template` relation if set on the Collection note.
|
||||
|
||||
## Interacting with events
|
||||
|
||||
* Hovering the mouse over an event will display information about the note.
|
||||

|
||||
* Left clicking the event will open a <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Quick%20edit.md">Quick edit</a> to edit the note in a popup while allowing easy return to the calendar by just dismissing the popup.
|
||||
* Middle clicking will open the note in a new tab.
|
||||
* Right click will offer more options including opening the note in a new split or window.
|
||||
* Drag and drop an event on the calendar to move it to another day.
|
||||
* The length of an event can be changed by placing the mouse to the right edge of the event and dragging the mouse around.
|
||||
|
||||
## Configuring the calendar view
|
||||
|
||||
In the _Collections_ tab in the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Ribbon.md">Ribbon</a>, it's possible to adjust the following:
|
||||
|
||||
* Hide weekends from the week view.
|
||||
* Display week numbers on the calendar.
|
||||
|
||||
## Configuring the calendar using attributes
|
||||
|
||||
The following attributes can be added to the Collection type:
|
||||
|
||||
<table><thead><tr><th>Name</th><th>Description</th></tr></thead><tbody><tr><td><code>#calendar:hideWeekends</code></td><td>When present (regardless of value), it will hide Saturday and Sundays from the calendar.</td></tr><tr><td><code>#calendar:weekNumbers</code></td><td>When present (regardless of value), it will show the number of the week on the calendar.</td></tr><tr><td><code>#calendar:view</code></td><td><p>Which view to display in the calendar:</p><ul><li><code>timeGridWeek</code> for the <em>week</em> view;</li><li><code>dayGridMonth</code> for the <em>month</em> view;</li><li><code>multiMonthYear</code> for the <em>year</em> view;</li><li><code>listMonth</code> for the <em>list</em> view.</li></ul><p>Any other value will be dismissed and the default view (month) will be used instead.</p><p>The value of this label is automatically updated when changing the view using the UI buttons.</p></td></tr><tr><td><code>~child:template</code></td><td>Defines the template for newly created notes in the calendar (via dragging or clicking).</td></tr></tbody></table>
|
||||
|
||||
In addition, the first day of the week can be either Sunday or Monday and can be adjusted from the application settings.
|
||||
|
||||
## Configuring the calendar events using attributes
|
||||
|
||||
For each note of the calendar, the following attributes can be used:
|
||||
|
||||
| Name | Description |
|
||||
| --- | --- |
|
||||
| `#startDate` | The date the event starts, which will display it in the calendar. The format is `YYYY-MM-DD` (year, month and day separated by a minus sign). |
|
||||
| `#endDate` | Similar to `startDate`, mentions the end date if the event spans across multiple days. The date is inclusive, so the end day is also considered. The attribute can be missing for single-day events. |
|
||||
| `#startTime` | The time the event starts at. If this value is missing, then the event is considered a full-day event. The format is `HH:MM` (hours in 24-hour format and minutes). |
|
||||
| `#endTime` | Similar to `startTime`, it mentions the time at which the event ends (in relation with `endDate` if present, or `startDate`). |
|
||||
| `#color` | Displays the event with a specified color (named such as `red`, `gray` or hex such as `#FF0000`). This will also change the color of the note in other places such as the note tree. |
|
||||
| `#calendar:color` | Similar to `#color`, but applies the color only for the event in the calendar and not for other places such as the note tree. |
|
||||
| `#iconClass` | If present, the icon of the note will be displayed to the left of the event title. |
|
||||
| `#calendar:title` | Changes the title of an event to point to an attribute of the note other than the title, can either a label or a relation (without the `#` or `~` symbol). See _Use-cases_ for more information. |
|
||||
| `#calendar:displayedAttributes` | Allows displaying the value of one or more attributes in the calendar like this: <br> <br> <br> <br>`#weight="70" #Mood="Good" #calendar:displayedAttributes="weight,Mood"` <br> <br>It can also be used with relations, case in which it will display the title of the target note: <br> <br>`~assignee=@My assignee #calendar:displayedAttributes="assignee"` |
|
||||
| `#calendar:startDate` | Allows using a different label to represent the start date, other than `startDate` (e.g. `expiryDate`). The label name **must not be** prefixed with `#`. If the label is not defined for a note, the default will be used instead. |
|
||||
| `#calendar:endDate` | Similar to `#calendar:startDate`, allows changing the attribute which is being used to read the end date. |
|
||||
| `#calendar:startTime` | Similar to `#calendar:startDate`, allows changing the attribute which is being used to read the start time. |
|
||||
| `#calendar:endTime` | Similar to `#calendar:startDate`, allows changing the attribute which is being used to read the end time. |
|
||||
|
||||
## How the calendar works
|
||||
|
||||

|
||||
|
||||
The calendar displays all the child notes of the Collection that have a `#startDate`. An `#endDate` can optionally be added.
|
||||
|
||||
If editing the start date and end date from the note itself is desirable, the following attributes can be added to the Collection note:
|
||||
|
||||
```
|
||||
#viewType=calendar #label:startDate(inheritable)="promoted,alias=Start Date,single,date"
|
||||
#label:endDate(inheritable)="promoted,alias=End Date,single,date"
|
||||
#hidePromotedAttributes
|
||||
```
|
||||
|
||||
This will result in:
|
||||
|
||||

|
||||
|
||||
When not used in a Journal, the calendar is recursive. That is, it will look for events not just in its child notes but also in the children of these child notes.
|
||||
|
||||
## Use-cases
|
||||
|
||||
### Using with the Journal / calendar
|
||||
|
||||
It is possible to integrate the calendar view into the Journal with day notes. In order to do so change the note type of the Journal note (calendar root) to Collection and then select the Calendar View.
|
||||
|
||||
Based on the `#calendarRoot` (or `#workspaceCalendarRoot`) attribute, the calendar will know that it's in a calendar and apply the following:
|
||||
|
||||
* The calendar events are now rendered based on their `dateNote` attribute rather than `startDate`.
|
||||
* Interactive editing such as dragging over an empty era or resizing an event is no longer possible.
|
||||
* Clicking on the empty space on a date will automatically open that day's note or create it if it does not exist.
|
||||
* Direct children of a day note will be displayed on the calendar despite not having a `dateNote` attribute. Children of the child notes will not be displayed.
|
||||
|
||||
<img src="8_Calendar View_image.png" width="1217" height="724">
|
||||
|
||||
### Using a different attribute as event title
|
||||
|
||||
By default, events are displayed on the calendar by their note title. However, it is possible to configure a different attribute to be displayed instead.
|
||||
|
||||
To do so, assign `#calendar:title` to the child note (not the calendar/Collection note), with the value being `name` where `name` can be any label (make not to add the `#` prefix). The attribute can also come through inheritance such as a template attribute. If the note does not have the requested label, the title of the note will be used instead.
|
||||
|
||||
<table><thead><tr><th> </th><th> </th></tr></thead><tbody><tr><td><pre><code class="language-text-x-trilium-auto">#startDate=2025-02-11 #endDate=2025-02-13 #name="My vacation" #calendar:title="name"</code></pre></td><td><p> </p><figure class="image image-style-align-center"><img style="aspect-ratio:445/124;" src="5_Calendar View_image.png" width="445" height="124"></figure></td></tr></tbody></table>
|
||||
|
||||
### Using a relation attribute as event title
|
||||
|
||||
Similarly to using an attribute, use `#calendar:title` and set it to `name` where `name` is the name of the relation to use.
|
||||
|
||||
Moreover, if there are more relations of the same name, they will be displayed as multiple events coming from the same note.
|
||||
|
||||
<table><thead><tr><th> </th><th> </th></tr></thead><tbody><tr><td><pre><code class="language-text-x-trilium-auto">#startDate=2025-02-14 #endDate=2025-02-15 ~for=@John Smith ~for=@Jane Doe #calendar:title="for"</code></pre></td><td><img src="6_Calendar View_image.png" width="294" height="151"></td></tr></tbody></table>
|
||||
|
||||
Note that it's even possible to have a `#calendar:title` on the target note (e.g. “John Smith”) which will try to render an attribute of it. Note that it's not possible to use a relation here as well for safety reasons (an accidental recursion of attributes could cause the application to loop infinitely).
|
||||
|
||||
<table><thead><tr><th> </th><th> </th></tr></thead><tbody><tr><td><pre><code class="language-text-x-trilium-auto">#calendar:title="shortName" #shortName="John S."</code></pre></td><td><figure class="image image-style-align-center"><img style="aspect-ratio:296/150;" src="1_Calendar View_image.png" width="296" height="150"></figure></td></tr></tbody></table>
|
||||
BIN
docs/User Guide/User Guide/Collections/Calendar View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 968 B |
182
docs/User Guide/User Guide/Collections/Geo Map View.md
vendored
Normal file
@@ -0,0 +1,182 @@
|
||||
# Geo Map View
|
||||
> [!IMPORTANT]
|
||||
> Starting with Trilium v0.97.0, the geo map has been converted from a standalone [note type](../Note%20Types.md) to a type of view for the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/Notes/Note%20List.md">Note List</a>.
|
||||
|
||||
<figure class="image image-style-align-center"><img style="aspect-ratio:892/675;" src="9_Geo Map View_image.png" width="892" height="675"></figure>
|
||||
|
||||
This note type displays the children notes on a geographical map, based on an attribute. It is also possible to add new notes at a specific location using the built-in interface.
|
||||
|
||||
## Creating a new geo map
|
||||
|
||||
| | | |
|
||||
| --- | --- | --- |
|
||||
| 1 | <figure class="image"><img style="aspect-ratio:483/413;" src="15_Geo Map View_image.png" width="483" height="413"></figure> | Right click on any note on the note tree and select _Insert child note_ → _Geo Map (beta)_. |
|
||||
| 2 | <figure class="image image-style-align-center image_resized" style="width:53.44%;"><img style="aspect-ratio:1720/1396;" src="8_Geo Map View_image.png" width="1720" height="1396"></figure> | By default the map will be empty and will show the entire world. |
|
||||
|
||||
## Repositioning the map
|
||||
|
||||
* Click and drag the map in order to move across the map.
|
||||
* Use the mouse wheel, two-finger gesture on a touchpad or the +/- buttons on the top-left to adjust the zoom.
|
||||
|
||||
The position on the map and the zoom are saved inside the map note and restored when visiting again the note.
|
||||
|
||||
## Adding a marker using the map
|
||||
|
||||
### Adding a new note using the plus button
|
||||
|
||||
| | | |
|
||||
| --- | --- | --- |
|
||||
| 1 | To create a marker, first navigate to the desired point on the map. Then press the  button in the [Floating buttons](../Basic%20Concepts%20and%20Features/UI%20Elements/Floating%20buttons.md) (top-right) area. <br> <br>If the button is not visible, make sure the button section is visible by pressing the chevron button () in the top-right of the map. | |
|
||||
| 2 | <img class="image_resized" style="aspect-ratio:1730/416;width:100%;" src="2_Geo Map View_image.png" width="1730" height="416"> | Once pressed, the map will enter in the insert mode, as illustrated by the notification. <br> <br>Simply click the point on the map where to place the marker, or the Escape key to cancel. |
|
||||
| 3 | <img class="image_resized" style="aspect-ratio:1586/404;width:100%;" src="7_Geo Map View_image.png" width="1586" height="404"> | Enter the name of the marker/note to be created. |
|
||||
| 4 | <img class="image_resized" style="aspect-ratio:1696/608;width:100%;" src="16_Geo Map View_image.png" width="1696" height="608"> | Once confirmed, the marker will show up on the map and it will also be displayed as a child note of the map. |
|
||||
|
||||
### Adding a new note using the contextual menu
|
||||
|
||||
1. Right click anywhere on the map, where to place the newly created marker (and corresponding note).
|
||||
2. Select _Add a marker at this location_.
|
||||
3. Enter the name of the newly created note.
|
||||
4. The map should be updated with the new marker.
|
||||
|
||||
### Adding an existing note on note from the note tree
|
||||
|
||||
1. Select the desired note in the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Note%20Tree.md">Note Tree</a>.
|
||||
2. Hold the mouse on the note and drag it to the map to the desired location.
|
||||
3. The map should be updated with the new marker.
|
||||
|
||||
This works for:
|
||||
|
||||
* Notes that are not part of the geo map, case in which a [clone](../Basic%20Concepts%20and%20Features/Notes/Cloning%20Notes.md) will be created.
|
||||
* Notes that are a child of the geo map but not yet positioned on the map.
|
||||
* Notes that are a child of the geo map and also positioned, case in which the marker will be relocated to the new position.
|
||||
|
||||
> [!NOTE]
|
||||
> Dragging existing notes only works if the map is in editing mode. See the _Read-only_ section for more information.
|
||||
|
||||
## How the location of the markers is stored
|
||||
|
||||
The location of a marker is stored in the `#geolocation` attribute of the child notes:
|
||||
|
||||
<img src="18_Geo Map View_image.png" width="1288" height="278">
|
||||
|
||||
This value can be added manually if needed. The value of the attribute is made up of the latitude and longitude separated by a comma.
|
||||
|
||||
## Repositioning markers
|
||||
|
||||
It's possible to reposition existing markers by simply drag and dropping them to the new destination.
|
||||
|
||||
As soon as the mouse is released, the new position is saved.
|
||||
|
||||
If moved by mistake, there is currently no way to undo the change. If the mouse was not yet released, it's possible to force a refresh of the page (<kbd>Ctrl</kbd>+<kbd>R</kbd> ) to cancel it.
|
||||
|
||||
## Interaction with the markers
|
||||
|
||||
* Hovering over a marker will display a <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Note%20Tooltip.md">Note Tooltip</a> with the content of the note it belongs to.
|
||||
* Clicking on the note title in the tooltip will navigate to the note in the current view.
|
||||
* Middle-clicking the marker will open the note in a new tab.
|
||||
* Right-clicking the marker will open a contextual menu (as described below).
|
||||
* If the map is in read-only mode, clicking on a marker will open a <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Quick%20edit.md">Quick edit</a> popup for the corresponding note.
|
||||
|
||||
## Contextual menu
|
||||
|
||||
It's possible to press the right mouse button to display a contextual menu.
|
||||
|
||||
1. If right-clicking an empty section of the map (not on a marker), it allows to:
|
||||
1. Displays the latitude and longitude. Clicking this option will copy them to the clipboard.
|
||||
2. Open the location using an external application (if the operating system supports it).
|
||||
3. Adding a new marker at that location.
|
||||
2. If right-clicking on a marker, it allows to:
|
||||
1. Displays the latitude and longitude. Clicking this option will copy them to the clipboard.
|
||||
2. Open the location using an external application (if the operating system supports it).
|
||||
3. Open the note in a new tab, split or window.
|
||||
4. Remove the marker from the map, which will remove the `#geolocation` attribute of the note. To add it back again, the coordinates have to be manually added back in.
|
||||
|
||||
## Icon and color of the markers
|
||||
|
||||
<figure class="image image-style-align-center"><img style="aspect-ratio:523/295;" src="Geo Map View_image.jpg" alt="image" width="523" height="295"></figure>
|
||||
|
||||
The markers will have the same icon as the note.
|
||||
|
||||
It's possible to add a custom color to a marker by assigning them a `#color` attribute such as `#color=green`.
|
||||
|
||||
## Adding the coordinates manually
|
||||
|
||||
In a nutshell, create a child note and set the `#geolocation` attribute to the coordinates.
|
||||
|
||||
The value of the attribute is made up of the latitude and longitude separated by a comma.
|
||||
|
||||
### Adding from Google Maps
|
||||
|
||||
| | | |
|
||||
| --- | --- | --- |
|
||||
| 1 | <figure class="image image-style-align-center image_resized" style="width:56.84%;"><img style="aspect-ratio:732/918;" src="12_Geo Map View_image.png" width="732" height="918"></figure> | Go to Google Maps on the web and look for a desired location, right click on it and a context menu will show up. <br> <br>Simply click on the first item displaying the coordinates and they will be copied to clipboard. <br> <br>Then paste the value inside the text box into the `#geolocation` attribute of a child note of the map (don't forget to surround the value with a `"` character). |
|
||||
| 2 | <figure class="image image-style-align-center image_resized" style="width:100%;"><img style="aspect-ratio:518/84;" src="4_Geo Map View_image.png" width="518" height="84"></figure> | In Trilium, create a child note under the map. |
|
||||
| 3 | <figure class="image image-style-align-center image_resized" style="width:100%;"><img style="aspect-ratio:1074/276;" src="11_Geo Map View_image.png" width="1074" height="276"></figure> | And then go to Owned Attributes and type `#geolocation="`, then paste from the clipboard as-is and then add the ending `"` character. Press Enter to confirm and the map should now be updated to contain the new note. |
|
||||
|
||||
### Adding from OpenStreetMap
|
||||
|
||||
Similarly to the Google Maps approach:
|
||||
|
||||
| | | |
|
||||
| --- | --- | --- |
|
||||
| 1 | <img class="image_resized" style="aspect-ratio:562/454;width:100%;" src="1_Geo Map View_image.png" width="562" height="454"> | Go to any location on openstreetmap.org and right click to bring up the context menu. Select the “Show address” item. |
|
||||
| 2 | <img class="image_resized" style="aspect-ratio:696/480;width:100%;" src="Geo Map View_image.png" width="696" height="480"> | The address will be visible in the top-left of the screen, in the place of the search bar. <br> <br>Select the coordinates and copy them into the clipboard. |
|
||||
| 3 | <img class="image_resized" style="aspect-ratio:640/276;width:100%;" src="5_Geo Map View_image.png" width="640" height="276"> | Simply paste the value inside the text box into the `#geolocation` attribute of a child note of the map and then it should be displayed on the map. |
|
||||
|
||||
## Adding GPS tracks (.gpx)
|
||||
|
||||
Trilium has basic support for displaying GPS tracks on the geo map.
|
||||
|
||||
| | | |
|
||||
| --- | --- | --- |
|
||||
| 1 | <figure class="image image-style-align-center"><img style="aspect-ratio:226/74;" src="3_Geo Map View_image.png" width="226" height="74"></figure> | To add a track, simply drag & drop a .gpx file inside the geo map in the note tree. |
|
||||
| 2 | <figure class="image image-style-align-center"><img style="aspect-ratio:322/222;" src="14_Geo Map View_image.png" width="322" height="222"></figure> | In order for the file to be recognized as a GPS track, it needs to show up as `application/gpx+xml` in the _File type_ field. |
|
||||
| 3 | <figure class="image image-style-align-center"><img style="aspect-ratio:620/530;" src="6_Geo Map View_image.png" width="620" height="530"></figure> | When going back to the map, the track should now be visible. <br> <br>The start and end points of the track are indicated by the two blue markers. |
|
||||
|
||||
> [!NOTE]
|
||||
> The starting point of the track will be displayed as a marker, with the name of the note underneath. The start marker will also respect the icon and the `color` of the note. The end marker is displayed with a distinct icon.
|
||||
>
|
||||
> If the GPX contains waypoints, they will also be displayed. If they have a name, it is displayed when hovering over it with the mouse.
|
||||
|
||||
## Read-only mode
|
||||
|
||||
When a map is in read-only all editing features will be disabled such as:
|
||||
|
||||
* The add button in the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Floating%20buttons.md">Floating buttons</a>.
|
||||
* Dragging markers.
|
||||
* Editing from the contextual menu (removing locations or adding new items).
|
||||
|
||||
To enable read-only mode simply press the _Lock_ icon from the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Floating%20buttons.md">Floating buttons</a>. To disable it, press the button again.
|
||||
|
||||
## Configuration
|
||||
|
||||
### Map Style
|
||||
|
||||
The styling of the map can be adjusted in the _Collection Properties_ tab in the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Ribbon.md">Ribbon</a> or manually via the `#map:style` attribute.
|
||||
|
||||
The geo map comes with two different types of styles:
|
||||
|
||||
* Raster styles
|
||||
* For these styles the map is represented as a grid of images at different zoom levels. This is the traditional way OpenStreetMap used to work.
|
||||
* Zoom is slightly restricted.
|
||||
* Currently, the only raster theme is the original OpenStreetMap style.
|
||||
* Vector styles
|
||||
* Vector styles are not represented as images, but as geometrical shapes. This makes the rendering much smoother, especially when zooming and looking at the building edges, for example.
|
||||
* The map can be zoomed in much further.
|
||||
* These come both in a light and a dark version.
|
||||
* The vector styles come from [VersaTiles](https://versatiles.org/), a free and open-source project providing map tiles based on OpenStreetMap.
|
||||
|
||||
> [!NOTE]
|
||||
> Currently it is not possible to use a custom map style.
|
||||
|
||||
### Scale
|
||||
|
||||
Activating this option via the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Ribbon.md">Ribbon</a> or manually via `#map:scale` will display an indicator in the bottom-left of the scale of the map.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
<figure class="image image-style-align-right image_resized" style="width:34.06%;"><img style="aspect-ratio:678/499;" src="13_Geo Map View_image.png" width="678" height="499"></figure>
|
||||
|
||||
### Grid-like artifacts on the map
|
||||
|
||||
This occurs if the application is not at 100% zoom which causes the pixels of the map to not render correctly due to fractional scaling. The only possible solution is to set the UI zoom at 100% (default keyboard shortcut is <kbd>Ctrl</kbd>+<kbd>0</kbd>).
|
||||
BIN
docs/User Guide/User Guide/Collections/Geo Map View_image.jpg
vendored
Normal file
|
After Width: | Height: | Size: 18 KiB |
BIN
docs/User Guide/User Guide/Collections/Geo Map View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 32 KiB |
23
docs/User Guide/User Guide/Collections/Grid View.md
vendored
Normal file
@@ -0,0 +1,23 @@
|
||||
# Grid View
|
||||
<figure class="image"><img style="aspect-ratio:990/590;" src="Grid View_image.png" width="990" height="590"></figure>
|
||||
|
||||
This view presents the child notes in a grid format, allowing for a more visual navigation experience.
|
||||
|
||||
Each tile contains:
|
||||
|
||||
* The title of a note.
|
||||
* A snippet of the content.
|
||||
* For empty notes, the sub-children are also displayed, allowing for quick navigation.
|
||||
|
||||
Depending on the type of note:
|
||||
|
||||
* For <a class="reference-link" href="../Note%20Types/Text.md">Text</a> notes, the text can be slightly scrollable via the mouse wheel to reveal more context.
|
||||
* For <a class="reference-link" href="../Note%20Types/Code.md">Code</a> notes, syntax highlighting is applied.
|
||||
* For <a class="reference-link" href="../Note%20Types/File.md">File</a> notes, a preview is made available for audio, video and PDF notes.
|
||||
* If the note does not have a content, a list of its child notes will be displayed instead.
|
||||
|
||||
The grid view is also used by default in the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/Notes/Note%20List.md">Note List</a> of every note, making it easy to navigate to children notes.
|
||||
|
||||
## Configuration
|
||||
|
||||
Unlike most other view types, the grid view is not actually configurable.
|
||||
BIN
docs/User Guide/User Guide/Collections/Grid View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 78 KiB |
11
docs/User Guide/User Guide/Collections/List View.md
vendored
Normal file
@@ -0,0 +1,11 @@
|
||||
# List View
|
||||
<figure class="image"><img style="aspect-ratio:1387/758;" src="List View_image.png" width="1387" height="758"></figure>
|
||||
|
||||
List view is similar to <a class="reference-link" href="Grid%20View.md">Grid View</a>, but in the list view mode, each note is displayed in a single row with only the title and the icon of the note being visible by the default. By pressing the expand button it's possible to view the content of the note, as well as the children of the note (recursively).
|
||||
|
||||
In the example above, the "Node.js" note on the left panel contains several child notes. The right panel displays the content of these child notes as a single continuous document.
|
||||
|
||||
## Interaction
|
||||
|
||||
* Each note can be expanded or collapsed by clicking on the arrow to the left of the title.
|
||||
* In the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Ribbon.md">Ribbon</a>, in the _Collection_ tab there are options to expand and to collapse all notes easily.
|
||||
BIN
docs/User Guide/User Guide/Collections/List View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 119 KiB |
85
docs/User Guide/User Guide/Collections/Presentation View.md
vendored
Normal file
@@ -0,0 +1,85 @@
|
||||
# Presentation View
|
||||
<figure class="image"><img style="aspect-ratio:1120/763;" src="Presentation View_image.png" width="1120" height="763"></figure>
|
||||
|
||||
The Presentation view allows the creation of slideshows directly from within Trilium.
|
||||
|
||||
## How it works
|
||||
|
||||
* Each slide is a child note of the collection.
|
||||
* The order of the child notes determines the order of the slides.
|
||||
* Unlike traditional presentation software, slides can be laid out both horizontally and vertically (see belwo for more information).
|
||||
* Direct children will be laid out horizontally and the children of those will be laid out vertically. Children deeper than two levels of nesting are ignored.
|
||||
|
||||
## Interaction and navigation
|
||||
|
||||
In the floating buttons section (top-right):
|
||||
|
||||
* Edit button to go to the corresponding note of the current slide.
|
||||
* Press Overview button (or the <kbd>O</kbd> key) to show a birds-eye view of the slides. Press the button again to disable it.
|
||||
* Press the “Start presentation” button to show the presentation in full-screen.
|
||||
|
||||
The following keyboard shortcuts are supported:
|
||||
|
||||
* Press <kbd>←</kbd> and <kbd>→</kbd> (or <kbd>H</kbd> and <kbd>L</kbd>) to go to the slide on the left or on the right (horizontal).
|
||||
* Press <kbd>↑</kbd> and <kbd>↓</kbd> (or <kbd>K</kbd> and <kbd>J</kbd>) to go to the upward or downward slide (vertical).
|
||||
* Press <kbd>Space</kbd> and <kbd>Shift</kbd> + <kbd>Space</kbd> or to go to the next/previous slide in order.
|
||||
* And a few more, press <kbd>?</kbd> to display a popup with all the supported keyboard combinations.
|
||||
|
||||
## Vertical slides and nesting
|
||||
|
||||
Unlike traditional presentation software such as Microsoft PowerPoint, the slides in Trilium can be laid out horizontally or vertically in order to create depth or better organize the slides by topic.
|
||||
|
||||
This horizontal/vertical organization affects transitions (especially on the “slide” transition), however it is most noticeable in navigation.
|
||||
|
||||
* Pressing <kbd>←</kbd> and <kbd>→</kbd> will navigate through slides horizontally, thus skipping vertical notes under the current slide. This is useful to skip entire chapters/related slides.
|
||||
* Pressing <kbd>↑</kbd> and <kbd>↓</kbd> will navigate through the vertical slides at the current level.
|
||||
* Pressing <kbd>Space</kbd> and <kbd>Shift</kbd> + <kbd>Space</kbd> will go to the next/previous slide in order, regardless of the direction. This is generally the key combination to use when presenting.
|
||||
* The arrows on the bottom-right of the slide will also reflect this navigation scheme.
|
||||
|
||||
<figure class="image image-style-align-right image_resized" style="width:55.57%;"><img style="aspect-ratio:890/569;" src="1_Presentation View_image.png" width="890" height="569"></figure>
|
||||
|
||||
All direct children of the collection will be laid out horizontally. If a direct child also has children, those children will be placed as vertical slides.
|
||||
|
||||
In the following example, the note structure is as follows:
|
||||
|
||||
* Presentation collection
|
||||
* Trilium Notes (demo page)
|
||||
* “Introduction” slide
|
||||
* “The challenge of personal knowledge management”
|
||||
* “Note-taking structures”
|
||||
* “Demo & Feature highlights” slide
|
||||
* “Really fast installation process”
|
||||
* Video slide
|
||||
|
||||
## Customization
|
||||
|
||||
At collection level, it's possible to adjust:
|
||||
|
||||
* The theme of the entire presentation to one of the predefined themes by going to the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Ribbon.md">Ribbon</a> and looking for the _Collection Properties_ tab.
|
||||
* It's currently not possible to create custom themes, although it is planned.
|
||||
* Note that it is note possible to alter the CSS via <a class="reference-link" href="../Theme%20development/Custom%20app-wide%20CSS.md">Custom app-wide CSS</a> because the slides are rendered isolated (in a shadow DOM).
|
||||
|
||||
At slide level:
|
||||
|
||||
* It's possible to adjust the background color of a slide by using the [predefined promoted attribute](../Advanced%20Usage/Attributes/Promoted%20Attributes.md) for the color or manually setting `#slide:background` to a hex color.
|
||||
* More complex backgrounds can be achieved via gradients. There's no UI for it; it has to be set via `#slide:background` to a CSS gradient definition such as: `linear-gradient(to bottom, #283b95, #17b2c3)`.
|
||||
|
||||
## Tips and tricks
|
||||
|
||||
* Text notes generally respect the formatting (bold, italic, foreground and background colors) and font size. Code blocks and tables also work.
|
||||
* Try using more than just text notes, the presentation uses the same mechanism as [shared notes](../Advanced%20Usage/Sharing.md) and <a class="reference-link" href="../Basic%20Concepts%20and%20Features/Notes/Note%20List.md">Note List</a> so it should be able to display <a class="reference-link" href="../Note%20Types/Mermaid%20Diagrams.md">Mermaid Diagrams</a>, <a class="reference-link" href="../Note%20Types/Canvas.md">Canvas</a> and <a class="reference-link" href="../Note%20Types/Mind%20Map.md">Mind Map</a> in full-screen (without the interactivity).
|
||||
* Consider using a transparent background for <a class="reference-link" href="../Note%20Types/Canvas.md">Canvas</a>, if the slides have a custom background (go to the hamburger menu in the Canvas, press the button select a custom color and write `transparent`).
|
||||
* For <a class="reference-link" href="../Note%20Types/Mermaid%20Diagrams.md">Mermaid Diagrams</a>, some of them have a predefined background which can be changed via the frontmatter. For example, for XY-charts:
|
||||
|
||||
```
|
||||
---
|
||||
config:
|
||||
themeVariables:
|
||||
xyChart:
|
||||
backgroundColor: transparent
|
||||
---
|
||||
```
|
||||
|
||||
## Under the hood
|
||||
|
||||
The Presentation view uses [Reveal.js](https://revealjs.com/) to handle the navigation and layout of the slides.
|
||||
BIN
docs/User Guide/User Guide/Collections/Presentation View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 422 KiB |
151
docs/User Guide/User Guide/Collections/Table View.md
vendored
Normal file
@@ -0,0 +1,151 @@
|
||||
# Table View
|
||||
<figure class="image"><img style="aspect-ratio:1050/259;" src="Table View_image.png" width="1050" height="259"></figure>
|
||||
|
||||
The table view displays information in a grid, where the rows are individual notes and the columns are <a class="reference-link" href="../Advanced%20Usage/Attributes/Promoted%20Attributes.md">Promoted Attributes</a>. In addition, values are editable.
|
||||
|
||||
## How it works
|
||||
|
||||
The tabular structure is represented as such:
|
||||
|
||||
* Each child note is a row in the table.
|
||||
* If child rows also have children, they will be displayed under an expander (nested notes).
|
||||
* Each column is a [promoted attribute](../Advanced%20Usage/Attributes/Promoted%20Attributes.md) that is defined on the Collection note.
|
||||
* Actually, both promoted and unpromoted attributes are supported, but it's a requirement to use a label/relation definition.
|
||||
* The promoted attributes are usually defined as inheritable in order to show up in the child notes, but it's not a requirement.
|
||||
* If there are multiple attribute definitions with the same `name`, only one will be displayed.
|
||||
|
||||
There are also a few predefined columns:
|
||||
|
||||
* The current item number, identified by the `#` symbol.
|
||||
* This simply counts the note and is affected by sorting.
|
||||
* <a class="reference-link" href="../Advanced%20Usage/Note%20ID.md">Note ID</a>, representing the unique ID used internally by Trilium
|
||||
* The title of the note.
|
||||
|
||||
## Interaction
|
||||
|
||||
### Creating a new table
|
||||
|
||||
Right click the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Note%20Tree.md">Note Tree</a> and select _Insert child note_ and look for the _Table item_.
|
||||
|
||||
### Adding columns
|
||||
|
||||
Each column is a [promoted or unpromoted attribute](../Advanced%20Usage/Attributes/Promoted%20Attributes.md) that is defined on the Collection note.
|
||||
|
||||
To create a new column, either:
|
||||
|
||||
* Press _Add new column_ at the bottom of the table.
|
||||
* Right click on an existing column and select Add column to the left/right.
|
||||
* Right click on the empty space of the column header and select _Label_ or _Relation_ in the _New column_ section.
|
||||
|
||||
### Adding new rows
|
||||
|
||||
Each row is actually a note that is a child of the Collection note.
|
||||
|
||||
To create a new note, either:
|
||||
|
||||
* Press _Add new row_ at the bottom of the table.
|
||||
* Right click on an existing row and select _Insert row above, Insert child note_ or _Insert row below_.
|
||||
|
||||
By default it will try to edit the title of the newly created note.
|
||||
|
||||
Alternatively, the note can be created from the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Note%20Tree.md">Note Tree</a> or [scripting](../Scripting.md).
|
||||
|
||||
### Context menu
|
||||
|
||||
There are multiple menus:
|
||||
|
||||
* Right clicking on a column, allows:
|
||||
* Sorting by the selected column and resetting the sort.
|
||||
* Hiding the selected column or adjusting the visibility of every column.
|
||||
* Adding new columns to the left or the right of the column.
|
||||
* Editing the current column.
|
||||
* Deleting the current column.
|
||||
* Right clicking on the space to the right of the columns, allows:
|
||||
* Adjusting the visibility of every column.
|
||||
* Adding new columns.
|
||||
* Right clicking on a row, allows:
|
||||
* Opening the corresponding note of the row in a new tab, split, window or quick editing it.
|
||||
* Inserting a new note above or below the selected row. These options are only enabled if the table is not sorted.
|
||||
* Inserting a new child note for the selected row.
|
||||
* Deleting the row.
|
||||
|
||||
### Editing data
|
||||
|
||||
Simply click on a cell within a row to change its value. The change will not only reflect in the table, but also as an attribute of the corresponding note.
|
||||
|
||||
* The editing will respect the type of the promoted attribute, by presenting a normal text box, a number selector or a date selector for example.
|
||||
* It also possible to change the title of a note.
|
||||
* Editing relations is also possible
|
||||
* Simply click on a relation and it will become editable. Enter the text to look for a note and click on it.
|
||||
* To remove a relation, remove the title of the note from the text box and click outside the cell.
|
||||
|
||||
### Editing columns
|
||||
|
||||
It is possible to edit a column by right clicking it and selecting _Edit column._ This will basically change the label/relation definition at the collection level.
|
||||
|
||||
If the _Name_ field of a column is changed, this will trigger a batch operation in which the corresponding label/relation will be renamed in all the children.
|
||||
|
||||
## Working with the data
|
||||
|
||||
### Sorting by column
|
||||
|
||||
By default, the order of the notes matches the order in the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Note%20Tree.md">Note Tree</a>. However, it is possible to sort the data by the values of a column:
|
||||
|
||||
* To do so, simply click on a column.
|
||||
* To switch between ascending or descending sort, simply click again on the same column. The arrow next to the column will indicate the direction of the sort.
|
||||
* To disable sorting and fall back to the original order, right click any column on the header and select _Clear sorting._
|
||||
|
||||
### Reordering and hiding columns
|
||||
|
||||
* Columns can be reordered by dragging the header of the columns.
|
||||
* Columns can be hidden or shown by right clicking on a column and clicking the item corresponding to the column.
|
||||
|
||||
### Reordering rows
|
||||
|
||||
Notes can be dragged around to change their order. To do so, move the mouse over the three vertical dots near the number row and drag the mouse to the desired position.
|
||||
|
||||
This will also change the order of the note in the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Note%20Tree.md">Note Tree</a>.
|
||||
|
||||
Reordering does have some limitations:
|
||||
|
||||
* If the parent note has `#sorted`, reordering will be disabled.
|
||||
* If using nested tables, then reordering will also be disabled.
|
||||
* Currently, it's possible to reorder notes even if column sorting is used, but the result might be inconsistent.
|
||||
|
||||
### Nested trees
|
||||
|
||||
If the child notes of the collection also have their own child notes, then they will be displayed in a hierarchy.
|
||||
|
||||
Next to the title of each element there will be a button to expand or collapse. By default, all items are expanded.
|
||||
|
||||
Since nesting is not always desirable, it is possible to limit the nesting to a certain number of levels or even disable it completely. To do so, either:
|
||||
|
||||
* Go to _Collection Properties_ in the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/UI%20Elements/Ribbon.md">Ribbon</a> and look for the _Max nesting depth_ section.
|
||||
* To disable nesting, type 0 and press Enter.
|
||||
* To limit to a certain depth, type in the desired number (e.g. 2 to only display children and sub-children).
|
||||
* To re-enable unlimited nesting, remove the number and press Enter.
|
||||
* Manually set `maxNestingDepth` to the desired value.
|
||||
|
||||
Limitations:
|
||||
|
||||
* While in this mode, it's not possible to reorder notes.
|
||||
|
||||
## Limitations
|
||||
|
||||
* Multi-value labels and relations are not supported. If a <a class="reference-link" href="../Advanced%20Usage/Attributes/Promoted%20Attributes.md">Promoted Attributes</a> is defined with a _Multi value_ specificity, they will be ignored.
|
||||
* There is no support to filter the rows by a certain criteria. Consider using the table view in search for that use case.
|
||||
|
||||
## Use in search
|
||||
|
||||
The table view can be used in a <a class="reference-link" href="../Note%20Types/Saved%20Search.md">Saved Search</a> by adding the `#viewType=table` attribute.
|
||||
|
||||
Unlike when used in a Collection, saved searches are not limited to the sub-hierarchy of a note and allows for advanced queries thanks to the power of the <a class="reference-link" href="../Basic%20Concepts%20and%20Features/Navigation/Search.md">Search</a>.
|
||||
|
||||
However, there are also some limitations:
|
||||
|
||||
* It's not possible to reorder notes.
|
||||
* It's not possible to add a new row.
|
||||
|
||||
Columns are supported, by being defined as <a class="reference-link" href="../Advanced%20Usage/Attributes/Promoted%20Attributes.md">Promoted Attributes</a> to the <a class="reference-link" href="../Note%20Types/Saved%20Search.md">Saved Search</a> note.
|
||||
|
||||
Editing is also supported.
|
||||
BIN
docs/User Guide/User Guide/Collections/Table View_image.png
vendored
Normal file
|
After Width: | Height: | Size: 34 KiB |