+
+When a note has one or more child notes, they will be listed at the end of the note for easy navigation.
The view types dictate how the child notes are represented.
By default, the notes will be displayed in a grid, however there are also some other view types available.
- -
-This view presents the child notes in a grid format, allowing for a more - visual navigation experience.
-This is the default view type.
-
-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 calendar view, child notes are represented as events, with a start - date and optionally an end date. The view also has interaction support - such as moving or creating new events. See Calendar View for more information.
\ No newline at end of file +Generally the view type can only be changed in a Collections note from the
+ Ribbon, but it can also be changed manually on any type of note using
+ the #viewType attribute.
-The Calendar view of Book notes will display each child note in a calendar - that has a start date and optionally an end date, as an event.
+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:
Unlike other Book view types, the Calendar view also allows some kind - of interaction, such as moving events around as well as creating new ones.
+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.
|
- The Calendar View works only for Book 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 Book. | +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 Book needs changed to “Calendar”, - by selecting the “Book Properties” tab in the ribbon. | +Once created, the “View type” of the Collection needs changed to “Calendar”, + by selecting the “Collection Properties” tab in the ribbon. |
~child:template relation
- if set on the book note.The following attributes can be added to the book type:
-In the Collections tab in the Ribbon, + it's possible to adjust the following:
+The following attributes can be added to the Collection type:
+In addition, the first day of the week can be either Sunday or Monday - and can be adjusted from the application settings.
-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:
- - - 
- - #weight="70" #Mood="Good" #calendar:displayedAttributes="weight,Mood"
- - It can also be used with relations, case in which it will display the - title of the target note: - - ~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. |
-
- 
-
The calendar displays all the child notes of the book 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 book 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.
-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 Book 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:
dateNote attribute
- rather than startDate.dateNote attribute. Children of the child notes
- will not be displayed.
- 
-
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/book 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.
In addition, the first day of the week can be either Sunday or Monday + and can be adjusted from the application settings.
+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:
+ + +
+ + #weight="70" #Mood="Good" #calendar:displayedAttributes="weight,Mood"
+ + It can also be used with relations, case in which it will display the + title of the target note: + + ~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. |
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.
-
+
+
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.
+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:
dateNote attribute
+ rather than startDate.dateNote attribute. Children of the child notes
+ will not be displayed.
+
+
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.
|
-
- 
- |
-
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).
| - | - | |
|---|---|---|
| |
+
+
|
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.
+| + | + |
|---|---|
|
+
+
+ |
+
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).
| + | + |
|---|---|
|
+
+
+ |
+
+This view presents the child notes in a grid format, allowing for a more + visual navigation experience.
+Each tile contains:
+Depending on the type of note:
+The grid view is also used by default in the Note List of + every note, making it easy to navigate to children notes.
+Unlike most other view types, the grid view is not actually configurable.
\ No newline at end of file diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Notes/Note List/Grid View_image.png b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Notes/Note List/Grid View_image.png new file mode 100644 index 000000000..8de2914c1 Binary files /dev/null and b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Notes/Note List/Grid View_image.png differ diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Notes/Note List/List View.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Notes/Note List/List View.html new file mode 100644 index 000000000..7326df26c --- /dev/null +++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Notes/Note List/List View.html @@ -0,0 +1,20 @@ +
+List view is similar to Grid View, + 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.
+Each column is a promoted attribute that - is defined on the Book note. Ideally, the promoted attributes need to be - inheritable in order to show up in the child notes.
+ is defined on the Collection note. Ideally, the promoted attributes need + to be inheritable in order to show up in the child notes.To create a new column, simply press Add new column at the bottom of the table.
There are also a few predefined columns:
@@ -24,7 +24,7 @@Each row is actually a note that is a child of the book note.
+Each row is actually a note that is a child of the Collection note.
To create a new note, press Add new row at the bottom of the table. By default it will try to edit the title of the newly created note.
Alternatively, the note can be created from thePromoted Attributes.
The table view can be used in a Saved Search by
adding the #viewType=table attribute.
Unlike when used in a book, saved searches are not limited to the sub-hierarchy - of a note and allows for advanced queries thanks to the power of the - Search.
+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 Search.
However, there are also some limitations:
A Book Note in Trilium is a special type of note designed - to display the contents of its child notes sequentially, creating a linear, - book-like reading experience. This format is particularly useful for viewing - multiple smaller notes in a cohesive, continuous manner.
-
- 
-
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.
-The Book Note format compiles the contents of all child notes into one - continuous view. This makes it ideal for reading extensive information - broken into smaller, manageable segments.
-It uses the Note List mechanism - to display the child notes, allowing the use of any of the view types (grid, - list, calendar).
-To adjust the view type, see the dedicated Book tab in the +
Collections are a unique type of notes that don't have a content, but + instead display its child notes in various presentation methods.
+Classic collections are read-only mode and compiles the contents of all + child notes into one continuous view. This makes it ideal for reading extensive + information broken into smaller, manageable segments.
+More specialized collections were introduced, such as the:
+For a quick presentation of all the supported view types, see the child + notes of this help page, including screenshots.
+To adjust the view type, see the dedicated Collections tab in + the Ribbon.
+Since collections are based on the Note List mechanism, + it's possible to apply the same configuration to Saved Search to + do advanced querying and presenting the result in an adequate matter such + as a calendar, a table or even a map.
+Collections by themselves are simply notes with no content that rely on + the Note List mechanism + (the one that lists the children notes at the bottom of a note) to display + information.
+By default, new collections use predefined Templates that + are stored safely in the Hidden Notes to + define some basic configuration such as the type of view, but also some Ribbon.
\ No newline at end of file + class="reference-link" href="#root/pOsGYCXsbNQG/tC7s2alapj8V/zEY4DaJG4YT5/_help_OFXdgB2nNk1F">Promoted Attributes to make editing easier. +Collections don't store their configuration (e.g. the position on the + map, the hidden columns in a table) in the content of the note itself, + but as attachments.
\ No newline at end of file diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/Calendar View.clone.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/Calendar View.clone.html new file mode 100644 index 000000000..9ccdbfa74 --- /dev/null +++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/Calendar View.clone.html @@ -0,0 +1 @@ +This is a clone of a note. Go to its primary location.
\ No newline at end of file diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/Geo Map View.clone.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/Geo Map View.clone.html new file mode 100644 index 000000000..b4d153e64 --- /dev/null +++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/Geo Map View.clone.html @@ -0,0 +1 @@ +This is a clone of a note. Go to its primary location.
\ No newline at end of file diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/Grid View.clone.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/Grid View.clone.html new file mode 100644 index 000000000..c00abb546 --- /dev/null +++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/Grid View.clone.html @@ -0,0 +1 @@ +This is a clone of a note. Go to its primary location.
\ No newline at end of file diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/List View.clone.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/List View.clone.html new file mode 100644 index 000000000..21dae316b --- /dev/null +++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/List View.clone.html @@ -0,0 +1 @@ +This is a clone of a note. Go to its primary location.
\ No newline at end of file diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/Table View.clone.html b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/Table View.clone.html new file mode 100644 index 000000000..31f21928f --- /dev/null +++ b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections/Table View.clone.html @@ -0,0 +1 @@ +This is a clone of a note. Go to its primary location.
\ No newline at end of file diff --git a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections_image.png b/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections_image.png deleted file mode 100644 index ba4e1dd7a..000000000 Binary files a/apps/server/src/assets/doc_notes/en/User Guide/User Guide/Note Types/Collections_image.png and /dev/null differ diff --git a/docs/User Guide/!!!meta.json b/docs/User Guide/!!!meta.json index 28a2e0095..628797d11 100644 --- a/docs/User Guide/!!!meta.json +++ b/docs/User Guide/!!!meta.json @@ -3631,82 +3631,38 @@ "isInheritable": false, "position": 10 }, + { + "type": "label", + "name": "iconClass", + "value": "bx bxs-grid", + "isInheritable": false, + "position": 10 + }, { "type": "relation", "name": "internalLink", "value": "GTwFsgaA0lCt", "isInheritable": false, - "position": 20 + "position": 80 }, { "type": "relation", "name": "internalLink", "value": "BlN9DFI679QC", "isInheritable": false, - "position": 30 - }, - { - "type": "relation", - "name": "internalLink", - "value": "iPIMuisry3hd", - "isInheritable": false, - "position": 40 - }, - { - "type": "relation", - "name": "internalLink", - "value": "6f9hih2hXXZk", - "isInheritable": false, - "position": 50 - }, - { - "type": "relation", - "name": "internalLink", - "value": "W8vYD3Q1zjCR", - "isInheritable": false, - "position": 60 - }, - { - "type": "relation", - "name": "internalLink", - "value": "xWbu3jpNWapp", - "isInheritable": false, - "position": 70 - }, - { - "type": "label", - "name": "iconClass", - "value": "bx bxs-grid", - "isInheritable": false, - "position": 10 + "position": 90 } ], "format": "markdown", "dataFileName": "Note List.md", "attachments": [ { - "attachmentId": "1SA0UPq471jp", + "attachmentId": "9VbOf4HySQjH", "title": "image.png", "role": "image", "mime": "image/png", "position": 10, "dataFileName": "Note List_image.png" - }, - { - "attachmentId": "2xoejxffj82c", - "title": "image.png", - "role": "image", - "mime": "image/png", - "position": 10, - "dataFileName": "1_Note List_image.png" - }, - { - "attachmentId": "mppVaDhlClF7", - "title": "image.png", - "role": "image", - "mime": "image/png", - "position": 10, - "dataFileName": "2_Note List_image.png" } ], "dirFileName": "Note List", @@ -3741,6 +3697,13 @@ "value": "ZjLYv08Rp3qC", "isInheritable": false, "position": 20 + }, + { + "type": "relation", + "name": "internalLink", + "value": "BlN9DFI679QC", + "isInheritable": false, + "position": 30 } ], "format": "markdown", @@ -4162,6 +4125,124 @@ "dataFileName": "18_Geo Map View_image.png" } ] + }, + { + "isClone": false, + "noteId": "8QqnMzx393bx", + "notePath": [ + "pOsGYCXsbNQG", + "gh7bpGYxajRS", + "BFs8mudNFgCS", + "0ESUbbAxVnoK", + "8QqnMzx393bx" + ], + "title": "Grid View", + "notePosition": 50, + "prefix": null, + "isExpanded": false, + "type": "text", + "mime": "text/html", + "attributes": [ + { + "type": "relation", + "name": "internalLink", + "value": "0ESUbbAxVnoK", + "isInheritable": false, + "position": 10 + }, + { + "type": "label", + "name": "iconClass", + "value": "bx bxs-grid", + "isInheritable": false, + "position": 20 + }, + { + "type": "relation", + "name": "internalLink", + "value": "iPIMuisry3hd", + "isInheritable": false, + "position": 30 + }, + { + "type": "relation", + "name": "internalLink", + "value": "6f9hih2hXXZk", + "isInheritable": false, + "position": 40 + }, + { + "type": "relation", + "name": "internalLink", + "value": "W8vYD3Q1zjCR", + "isInheritable": false, + "position": 50 + } + ], + "format": "markdown", + "dataFileName": "Grid View.md", + "attachments": [ + { + "attachmentId": "al3KatZRq5TB", + "title": "image.png", + "role": "image", + "mime": "image/png", + "position": 10, + "dataFileName": "Grid View_image.png" + } + ] + }, + { + "isClone": false, + "noteId": "mULW0Q3VojwY", + "notePath": [ + "pOsGYCXsbNQG", + "gh7bpGYxajRS", + "BFs8mudNFgCS", + "0ESUbbAxVnoK", + "mULW0Q3VojwY" + ], + "title": "List View", + "notePosition": 60, + "prefix": null, + "isExpanded": false, + "type": "text", + "mime": "text/html", + "attributes": [ + { + "type": "label", + "name": "iconClass", + "value": "bx bx-list-ul", + "isInheritable": false, + "position": 10 + }, + { + "type": "relation", + "name": "internalLink", + "value": "BlN9DFI679QC", + "isInheritable": false, + "position": 30 + }, + { + "type": "relation", + "name": "internalLink", + "value": "8QqnMzx393bx", + "isInheritable": false, + "position": 40 + } + ], + "format": "markdown", + "dataFileName": "List View.md", + "attachments": [ + { + "attachmentId": "igeOEpKp4ygW", + "title": "image.png", + "role": "image", + "mime": "image/png", + "position": 10, + "dataFileName": "List View_image.png" + } + ] } ] } @@ -8408,13 +8489,6 @@ "type": "text", "mime": "text/markdown", "attributes": [ - { - "type": "relation", - "name": "internalLink", - "value": "BFs8mudNFgCS", - "isInheritable": false, - "position": 10 - }, { "type": "relation", "name": "internalLink", @@ -8422,13 +8496,6 @@ "isInheritable": false, "position": 20 }, - { - "type": "relation", - "name": "internalLink", - "value": "BlN9DFI679QC", - "isInheritable": false, - "position": 30 - }, { "type": "label", "name": "shareAlias", @@ -8442,18 +8509,162 @@ "value": "bx bx-book", "isInheritable": false, "position": 20 + }, + { + "type": "relation", + "name": "internalLink", + "value": "OFXdgB2nNk1F", + "isInheritable": false, + "position": 60 + }, + { + "type": "relation", + "name": "internalLink", + "value": "BlN9DFI679QC", + "isInheritable": false, + "position": 70 + }, + { + "type": "relation", + "name": "internalLink", + "value": "8QqnMzx393bx", + "isInheritable": false, + "position": 80 + }, + { + "type": "relation", + "name": "internalLink", + "value": "mULW0Q3VojwY", + "isInheritable": false, + "position": 90 + }, + { + "type": "relation", + "name": "internalLink", + "value": "xWbu3jpNWapp", + "isInheritable": false, + "position": 100 + }, + { + "type": "relation", + "name": "internalLink", + "value": "81SGnPGMk7Xc", + "isInheritable": false, + "position": 110 + }, + { + "type": "relation", + "name": "internalLink", + "value": "2FvYrpmOXm29", + "isInheritable": false, + "position": 120 + }, + { + "type": "relation", + "name": "internalLink", + "value": "m523cpzocqaD", + "isInheritable": false, + "position": 130 + }, + { + "type": "relation", + "name": "internalLink", + "value": "KC1HB96bqqHX", + "isInheritable": false, + "position": 140 + }, + { + "type": "relation", + "name": "internalLink", + "value": "2mUhVmZK8RF3", + "isInheritable": false, + "position": 150 } ], "format": "markdown", "dataFileName": "Collections.md", - "attachments": [ + "attachments": [], + "dirFileName": "Collections", + "children": [ { - "attachmentId": "lpq3QC1C5LWg", - "title": "image.png", - "role": "image", - "mime": "image/jpg", - "position": 10, - "dataFileName": "Collections_image.png" + "isClone": true, + "noteId": "8QqnMzx393bx", + "notePath": [ + "pOsGYCXsbNQG", + "KSZ04uQ2D1St", + "GTwFsgaA0lCt", + "8QqnMzx393bx" + ], + "title": "Grid View", + "prefix": null, + "dataFileName": "Grid View.clone.md", + "type": "text", + "format": "markdown", + "isExpanded": false + }, + { + "isClone": true, + "noteId": "mULW0Q3VojwY", + "notePath": [ + "pOsGYCXsbNQG", + "KSZ04uQ2D1St", + "GTwFsgaA0lCt", + "mULW0Q3VojwY" + ], + "title": "List View", + "prefix": null, + "dataFileName": "List View.clone.md", + "type": "text", + "format": "markdown", + "isExpanded": false + }, + { + "isClone": true, + "noteId": "xWbu3jpNWapp", + "notePath": [ + "pOsGYCXsbNQG", + "KSZ04uQ2D1St", + "GTwFsgaA0lCt", + "xWbu3jpNWapp" + ], + "title": "Calendar View", + "prefix": null, + "dataFileName": "Calendar View.clone.md", + "type": "text", + "format": "markdown", + "isExpanded": false + }, + { + "isClone": true, + "noteId": "2FvYrpmOXm29", + "notePath": [ + "pOsGYCXsbNQG", + "KSZ04uQ2D1St", + "GTwFsgaA0lCt", + "2FvYrpmOXm29" + ], + "title": "Table View", + "prefix": null, + "dataFileName": "Table View.clone.md", + "type": "text", + "format": "markdown", + "isExpanded": false + }, + { + "isClone": true, + "noteId": "81SGnPGMk7Xc", + "notePath": [ + "pOsGYCXsbNQG", + "KSZ04uQ2D1St", + "GTwFsgaA0lCt", + "81SGnPGMk7Xc" + ], + "title": "Geo Map View", + "prefix": null, + "dataFileName": "Geo Map View.clone.md", + "type": "text", + "format": "markdown", + "isExpanded": false } ] }, diff --git a/docs/User Guide/User Guide/Basic Concepts and Features/Notes/1_Note List_image.png b/docs/User Guide/User Guide/Basic Concepts and Features/Notes/1_Note List_image.png deleted file mode 100644 index 4f0329d42..000000000 Binary files a/docs/User Guide/User Guide/Basic Concepts and Features/Notes/1_Note List_image.png and /dev/null differ diff --git a/docs/User Guide/User Guide/Basic Concepts and Features/Notes/2_Note List_image.png b/docs/User Guide/User Guide/Basic Concepts and Features/Notes/2_Note List_image.png deleted file mode 100644 index 4b581bbe9..000000000 Binary files a/docs/User Guide/User Guide/Basic Concepts and Features/Notes/2_Note List_image.png and /dev/null differ diff --git a/docs/User Guide/User Guide/Basic Concepts and Features/Notes/Note List.md b/docs/User Guide/User Guide/Basic Concepts and Features/Notes/Note List.md index dec95d577..d06a9e544 100644 --- a/docs/User Guide/User Guide/Basic Concepts and Features/Notes/Note List.md +++ b/docs/User Guide/User Guide/Basic Concepts and Features/Notes/Note List.md @@ -1,4 +1,6 @@ # Note List +| 1 | | The Calendar View works only for Book 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 Book. |
| 2 | | Once created, the “View type” of the Book needs changed to “Calendar”, by selecting the “Book Properties” tab in the ribbon. |
| 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. |
| Name | Description |
|---|---|
#calendar:hideWeekends | When present (regardless of value), it will hide Saturday and Sundays from the calendar. |
#calendar:weekNumbers | When present (regardless of value), it will show the number of the week on the calendar. |
#calendar:view | Which view to display in the calendar:
Any other value will be dismissed and the default view (month) will be used instead. The value of this label is automatically updated when changing the view using the UI buttons. |
~child:template | Defines the template for newly created notes in the calendar (via dragging or clicking). |
|
|