Also, if you're going to add this, you might add named searches.
@next = ^today || ^tomorrow || ^now || ^asap || ^overdue || #now || #soon
The first defines and executes a named search. The second executes it. The third deletes it.
If implemented, please consider maintaining a parity between the way (the ui) notes are kept on lists and items. Doing so provides a consistent way to promote items to lists and demote lists to items.
I agree that implementing a good looking ui is a concern, but I think it's possible. Here's a possibility:
First I like Sthithapragnan's suggestion of extending tags into pairs. I've see the paran syntax in TaskPaper and I like it. An alternative is to use a colon -- e.g. #taskaddedby:xxx. The colon syntax is easier to enter since the user doesn't need to remember a closing paran.
It is also possible to nicely display these in the ui. They are after all, just tags. Just display the value portion in a different color. The next issue is that if too many valued tags are entered it may clutter the ui. This could be handled by collapsing and expanding the complete set of valued tags.
(Firstly, simple tags with no values would appear just as they already do. These would be followed by the valued tags.) The user can add a setting on each list to indicate which valued tags (listing their keys) are shown by default. The set of valued pairs would have a three way toggle: show the default ones, show all, show none. These correlate to what Windows calls: normal, minimize, maximize. A simple ellipses could be used used to help convey that some are being collapsed out of view.
Using valued tags allows limitless extension since you can basically add whatever attributes you want (NoSQL style). It also accommodates the request for adding columns. Since displaying valued tags as columns is nothing more than another way of viewing them. So they could either appear similarly to normal tags as valued tags or as columnar values.
There would be no need to define data types. Just as YAML intuitive recognizes data types by the way they're entered, so could Checkvist.
214 votesAdminsashika (Admin, Checkvist) responded
Dear Adrian, thanks for giving your vote to this issue! We’ll try hard to keep the user interface simple – promise!
I agree with James' sentiment. Checkvist is a cut above other outliners. It's elegant, useful, and fast. Speed always ranks near the top in providing a pleasant user experience so great job in providing exactly that!
And yet, I read lots of requests here for different views of the data. Some want to see their outlines as mind maps, some as Kanban boards, some in Gantt charts, etc. The sentiment is that users sometimes want different views of their data, which I get and completely concur with. As an I.T. guy myself I have long been contemplating how to address this kind of issue and I've arrived at a reasonable solution, though it does involve some coordination with other parties.
It starts with Dropbox or some other data host. Right now, I believe, Checkvist hosts the user data and backs up data to third parties like Dropbox. Thus, Dropbox owns a secondary copy, not a primary copy of the data.
If the primary copy were owned by the third party and Checkvist merely provided the application for viewing and manipulating outline data files, we'd be one step closer to my proposed solution. (I once used Fargo, an outliner, that takes exactly this approach.)
The second step is finding an ubiquitous format for outline data such as OPML. I know relatively nothing about the OPML spec other than it attempts to standardize outline data.
What I don't know is how well third party tools like Checkvist are at utilizing the spec in a way that permits features beyond those envisioned by the authorities that oversee OPML. For example, you can export an Excel spreadsheet to CSV but this will cause a loss of features on import. I don't know how well Checkvist could function using the "ubiquitous file format" whatever it may be. Likewise, I don't know how well other apps like mind maps and Gantt charts could function using the ubiquitous file format, but that's the key and I think you can see where I'm going.
If user data is hosted elsewhere and if various vendors can access and manipulate it while adding their own custom attributes and not interfering with the custom attributes of other vendors, we arrive at the happy place where Checkvist can remain simple and users have a potentially unlimited number of ways to view and manipulate their data.
142 votesAdminKirill Maximov (Admin, Checkvist) responded
A note – checkvist provides a simple way to create links to other lists. To do this, start adding or editing a list item, and type lst: in the list item text. Read more about other tricks here: http://checkvist.tumblr.com/post/55179489998/a-quick-note-on-using-checkvist-for-online-research
The circular reference concern can be handled in several ways.
1) Don't allow them
2) Don't preload symlinks; dynamically expand them as users opens them and don't allow them to open items already appearing above in the node hierarchy
As lists can be assigned tags, I recommend using tags for indicating the kind of list. These tags will show up in the view that shows active lists.
I know Checkvist isn't designed for bookmarking; however, the bookmarks I save will be included as information that gets related to projects I'm working. I am not using it for bookmark management, but it makes sense to routinely associate bookmarks to work.
Under getting things done (GTD), the capture and organize steps are separate which is ideal. Writing an article used to take me forever. I later learned that writing and editing are separate steps. You don't do one while doing the other. I feel the same truth applies to GTD. Capturing and organizing are separate steps. An inbox list acts as an in-basket of unfiled thoughts (including bookmarks). Initially, I just want to capture things into the inbox. Filing comes later.
By the way: great product.Mario T. Lanza shared this idea ·