Changes

We could have only Objects in Journal(in terms of "storage" not Journal View). And operate these Objects in one unified way - Create(or copy existed) in Journal, Reuse(Change) them in Journal and Share Journal Objects.

We could have only Objects in Journal(in terms of "storage" not Journal View). And operate these Objects in one unified way - Create(or copy existed) in Journal, Reuse(Change) them in Journal and Share Journal Objects.

==Proposal==

== Proposal ==

==== Modify Journal ====

(in addition to Journal), I propose treat Activities as regular Journal objects.

Home View should mutate from "storage" of activities to Tags View of

to store Activities code in Journal

Journal objects. It could have tags cloud and etc.

And final, all sugar stuff could be treated as Objects in Journal(Journal as a technical term not Journal View). User could operate them from various View backends: Tags View, "classical" Home and Journal Views.

 

to start activities from Journal's paths

 

==== Create Views of Journal ====

 

==Pro==

==Pro==