I think this proposal is the main way to get a lot of requested features (structured meta data = user-defined properties):
1) they could be inherited from the ancestor type (e.g. a flag can be added to type and tags at children creation time)
2) a group of thoughts of same (or similar type) can be crossed together to form a table view:
on the rows can lie the thoughts selected, on the columns their (common) properties values: a new group thought can be created as ancestor for all compared thoughts and the table view attached (just to recycle current features)
3) this table could be updated/refreshed on command or ordered by a property: note that if a time/date property is used for thoughts and a table view with this only property as column, then ordering by time you get a timeline, user-defined; if a counter is used, you can get a sequence of thoughts...
4) the concept above may be extended to form the idea of calculated properties: for sub-trees of thoughts of same type, the value of a property can be obtained aggregating the values of related children properties: economic balances, work tree charts, etc are obtained this way; the simple property: 'number of children' may give indication of the weight of a thought
... may be it could be better add new ideas for these items, anyway they are only possible if properties are implemented
I think this proposal is the main way to get a lot of requested features (structured meta data = user-defined properties):
1) they could be inherited from the ancestor type (e.g. a flag can be added to type and tags at children creation time)
2) a group of thoughts of same (or similar type) can be crossed together to form a table view:
on the rows can lie the thoughts selected, on the columns their (common) properties values: a new group thought can be created as ancestor for all compared thoughts and the table view attached (just to recycle current features)
3) this table could be updated/refreshed on command or ordered by a property: note that if a time/date property is used for thoughts and a table view with this only property as column, then ordering by time you get a timeline, user-defined; if a counter is used, you can get a sequence of thoughts...
4) the concept above may be extended to form the idea of calculated properties: for sub-trees of thoughts of same type, the value of a property can be obtained aggregating the values of related children properties: economic balances, work tree charts, etc are obtained this way; the simple property: 'number of children' may give indication of the weight of a thought
... may be it could be better add new ideas for these items, anyway they are only possible if properties are implemented