table unbundled from Tags

The granularity of Tag is too large for table, and it leads to the inflexibility of table and confusion for tag. The details are posted in this link:Suggestions for improvement and workflow of table | RemNote

There could be three types of tables in RemNote actually, which are

table for the visualization of an outline’s parent-child structure,

table for visualization for rem with pre-designed template

table for visualization of multi-dimensional structure of advanced queries.

But the current table can't meet all the requirements, it mainly pay attention to the function of visualiziton for rem with pre-designed template.

Set the parent rem-properties structure as the core workflow instead of the instance-property method , free the tag from table, we don't need list view and we should not import the new concept "instance", what we need is just the power up "property" and the new folder "Template". We just need improve our old workflow instead of creating a new one to replace them, that's too confusing and lose the direct connection with the outline form.

• Any parent rem with a property can be converted into a table alone, which is not possible with the current table, the advantage is that this table can be an index table, showing what I feel is more core content (core and generic content can only be used with a property, this is the only thing to remember)——table for the visualization of an outline’s parent-child structure

• The rows and columns of the table have the search function, which is, the search portal function is introduced in the blank table type of table to generate the upper concept and the upper concept template.

  • fill the instance in the row firstly, and generate the template and construct the upper concept by automatic retrieval

  • fill the properties in the column firstly, and classify them by automatically retrieving the corresponding instances