renamed attributes to labels

azivner 2018-03-24 22:04:49 -04:00
parent e22a92c77b
commit b3d7474129
3 changed files with 19 additions and 19 deletions

@ -56,4 +56,4 @@ These are hooked in Electron to be similar to native browser keyboard shortcuts.
* ```ALT+H``` - show note history * ```ALT+H``` - show note history
* ```CTRL+S``` - toggle search form in tree pane * ```CTRL+S``` - toggle search form in tree pane
* ```ALT+R``` - show recent changes dialog * ```ALT+R``` - show recent changes dialog
* ```ALT+A``` - show note attributes dialog * ```ALT+A``` - show note labels dialog

@ -1,45 +1,45 @@
Note attributes is a set of key-value records owned by (assigned to) given note. Note labels is a set of key-value records owned by (assigned to) given note.
They are used mainly for several things: They are used mainly for several things:
* user can use them as tags/labels with optional value - e.g. when catalogizing books, you might add attributes like @year=1999, @genre=sci-fi, @author=Neal Stephenson * user can use them as tags/labels with optional value - e.g. when catalogizing books, you might add labels like @year=1999, @genre=sci-fi, @author=Neal Stephenson
* attributes can be used to configure some advanced features / settings - see below * labels can be used to configure some advanced features / settings - see below
* plugins / scripts can use these to mark notes with some special values / metadata (e.g. note with imported reddit comment will have attribute with comment ID) * plugins / scripts can use these to mark notes with some special values / metadata (e.g. note with imported reddit comment will have label with comment ID)
Both of these can then be used in filters. Both of these can then be used in filters.
### Show / edit attributes ### Show / edit labels
Click on note -> Note actions -> Attributes (or use keyboard shortcut ```ALT+A```). Click on note -> Note actions -> Labels (or use keyboard shortcut ```ALT+A```).
### Filter query syntax ### Filter query syntax
Following examples demonstrates syntax: Following examples demonstrates syntax:
* ```@abc``` - matches notes with attribute abc * ```@abc``` - matches notes with label abc
* ```@!abc``` - matches notes without abc attribute (maybe not the best syntax) * ```@!abc``` - matches notes without abc label (maybe not the best syntax)
* ```@abc=true``` - matches notes with attribute abc having value true * ```@abc=true``` - matches notes with label abc having value true
* ```@abc!=true``` * ```@abc!=true```
* ```@"weird attribute"="weird value"``` - works also with whitespace inside names values * ```@"weird label"="weird value"``` - works also with whitespace inside names values
* ```@abc and @def``` - matches notes with both abc and def * ```@abc and @def``` - matches notes with both abc and def
* ```@abc @def``` - AND relation is implicit when specifying multiple attributes * ```@abc @def``` - AND relation is implicit when specifying multiple labels
* ```@abc or @def``` - OR relation * ```@abc or @def``` - OR relation
* ```@abc<=5``` - numerical comparison (also >, >=, <). * ```@abc<=5``` - numerical comparison (also >, >=, <).
* ```some search string @abc @def``` - combination of fulltext and attribute search - both of them need to match (OR not supported) * ```some search string @abc @def``` - combination of fulltext and label search - both of them need to match (OR not supported)
* ```@abc @def some search string``` - same combination * ```@abc @def some search string``` - same combination
### Standard attributes ### Standard labels
Following attributes are used for advanced configuration: Following labels are used for advanced configuration:
* ```disable_versioning``` - disables auto-versioning. Useful for e.g. large, but unimportant notes - e.g. large JS libraries used for scripting * ```disable_versioning``` - disables auto-versioning. Useful for e.g. large, but unimportant notes - e.g. large JS libraries used for scripting
* ```calendar_root``` - marks note which should be used as root for "day notes". Only one should be marked as such. * ```calendar_root``` - marks note which should be used as root for "day notes". Only one should be marked as such.
* ```run_on_startup``` - JavaScript notes with this attribute will be executed after Trilium startup * ```run_on_startup``` - JavaScript notes with this label will be executed after Trilium startup
* ```hide_in_autocomplete``` - notes with this attribute won't be visible in autocomplete-based search (jump to, add link). Applies also to all its sub-notes. * ```hide_in_autocomplete``` - notes with this label won't be visible in autocomplete-based search (jump to, add link). Applies also to all its sub-notes.
* ```exclude_from_export``` - notes (with their sub-tree) won't be included in any note export * ```exclude_from_export``` - notes (with their sub-tree) won't be included in any note export
* ```run``` - defines on which events script should run. Possible values are: * ```run``` - defines on which events script should run. Possible values are:
* ```frontend_startup``` - when Trilium frontend starts up (or is refreshed). * ```frontend_startup``` - when Trilium frontend starts up (or is refreshed).
* ```backend_startup``` - when Trilium backend starts up * ```backend_startup``` - when Trilium backend starts up
* ```hourly``` - run once an hour * ```hourly``` - run once an hour
* ```daily``` - run once a day * ```daily``` - run once a day
* ```disable_inclusion``` - scripts with this attribute won't be included into parent script execution. * ```disable_inclusion``` - scripts with this label won't be included into parent script execution.

@ -1,6 +1,6 @@
Trilium doesn't come (yet) with any built-in themes, but allows you to create custom CSS which is attached to the main HTML page. Trilium doesn't come (yet) with any built-in themes, but allows you to create custom CSS which is attached to the main HTML page.
Just create a code note with CSS type, put your custom CSS code into the note's content and create "app_css" [[attribute|Attributes]]. When Trilium frontend starts, all notes with "app_css" attribute are appended in the style element of the Trilium HTML page. Just create a code note with CSS type, put your custom CSS code into the note's content and create "app_css" [[label|Labels]]. When Trilium frontend starts, all notes with "app_css" label are appended in the style element of the Trilium HTML page.
Once you made your changes, you can reload the Trilium frontend by pressing CTRL-R after which the changes will take effect. Once you made your changes, you can reload the Trilium frontend by pressing CTRL-R after which the changes will take effect.