Value-add from presentations
Desktop users will be able to author vault content and traverse that content with agility and minimal effort. The formatting presented in this section will aid in fast navigation because it guarantees uniformity in style and important navigational cues. The following is a list of presentation options that are available right out of the box.
The basic lists are a very commonly used presentation format. Most of the context nodes in the examples shipped with the UD App consist primarily of these lists. Sections 2 through 5 of the documentation deal exclusively with this fundamental presentation option. To give a context node basic list formatting, have its 'default presentation' value in the display properties set to 'list'.
The format for a list is not surprising and you've seen it already, but for clarity, here is what such formatting for a node looks like:
Editing operations work on this type of list just as they would on a basic list.
A comma-separated list is a nice view of a group of items that conserves more space on the page. You don't type the commas, that's taken care of for you, and you can switch to other views without having to delete them. To display a comma-separated list, select 'wrapping comma-separated list' as the 'default presentation';
Editing operations work on this type of list just as they would on a basic list.Here is what the comma-separated list will look like:
The 'Key-value pairs' format is a handy way to present anything that makes sense as a set of keys and values. This presentation format gives things a clean professional look that will help set things apart from other data. It is readable on its own, but also maintains visual continuity with other data in the vault.
Only the key fields are selectable, and editing these values is just a matter of clicking 'edit' when the key is highlited. To edit the value that the keys point to, you will need to highlight it's key first, push 'Enter' and then select the value, and you will be able to edit it in the normal way for basic lists.
Deeper hierarchical views
Deeper hierarchical views
One such option is the 'two-level hierarchy' option, which will make multiple parents and their child items visible as seen here...
To see an entire branch or even the entire contents of your vault in a tree format, choose the 'entire branch' option. With this option, indentation is the single indicator of how deep in the tree something is, and of the parent, sibling and child relationships of the items.
You will be able to cycle through each item of the branch using the arrow key or by, scrolling and clicking on the text. The 'Enter' button lets you navigate to that item.
Despite the word 'basic' here in the title, the table that is provided right out-of-the-box is actually not a trivial presentation option. To make something into a table you will edit the display properties and choose 'table' as the 'default presentation'.
Working with a table is a bit different from interactions with the previous formatting options we have seen thus far. The table format adds its own menuitems to the GUI interface. Note: It is recommended to use the table menuitems when adding new rows or new data cells, rather than try to manually construct them using descendent context items.
To add an additional row to your table you will use the 'add -> table row' menuitem, or hit the 'r' shortcut key.
To add additional data cells to your table, you will use the 'add -> table data cell' menuitem, or hit the 'd' shortcut key.
Creating new table rows causes each row box (the shaded column on the very left of your table) to display a default label. The 'r1' or 'r2' ... 'r[n]' are dynamically generated numberings that will continue to display until you edit the label yourself.
Editing a cell or a row item in a table is a matter of using the 'edit' menuitem or hitting the 'e' shortcut key. As with other formats, when you do, a simple edit popup will allow you to update the value.
An incredibly fun aspect of this is that when you take a context node that already exists and convert it into a table, it will draw differently. Constructing a table without using the provided cell data creation actions means that, presumably, the 'table cell' presentation format isn't being used, and this will in turn affect how things are drawn. In all cases, cells of the table will draw according to the display properties that are assigned to them. This scheme allows you to have preferred view formats, i.e., 'comma-separated' or what have you, nested in side a table.
Our company was founded in July 2017 by Bradley Pliam.
The headquarters is currently in Austin, Texas.
Ideas that have been in gestation since the early 2000s have now finally been given 'wings'.
The mission of the company is to deliver happiness in the form of value and great user experience via high quality software, being honest about what is being delivered, and up-front about any current limitations. The world of software has some great things, along with some insidiously bad aspects. We intend to be a positive influence.
Meet our current staff...