Embed existing lists/sublists, not just hyperlinks (similar to symlinks). Was: checklist of checklists
Active links. Ability to nest checklists. Checklist could be your own or someone elses that you are collaborating on. This provides the opportunity for more complex tasks
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
Another request for this: https://plus.google.com/u/0/107726650825619130706/posts/833btHWmtnP?cfem=1
Hi Chris, thanks for the comment and for the reference to leoeditor - we'll take a look :)
I just came across checkvist and I like it very much, good job!
Although this feature would really improve checkvist a lot.
Some years ago I tried to use leoeditor.com as a PIM and the
main feature for that in leo was creating "clones" of nodes
which is exactly what I would be looking for.
It is doable to implement this feature "the right way", but it is rather resource-heavy, and we don't have much resources at hand yet :)
Given that we have to finalize our mobile app, we have to postpone this feature so far (despite that we already have a Checkvist outline for the implementation plan).
I wonder if a fairly simple implementation could be done entirely on the client side. So that when a link to an item is encountered, the client renders the item as an iframe containing the linked item tree. Maybe not literally an iframe, but the same basic idea. For a client which doesn't implement that feature, it would just display as a link to the item. The circular reference problem could be handled on the client side as well by propagating a hash table each time a link is encountered and rendering a link instead of an iframe if a loop is encountered.
Thanks for the comment, I think we'll try to disallow circular references.
Mario T. Lanza commented
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
Thanks for your comment. I suppose regarding hard link/soft link issue - probably there won't be a difference in implementation, all links will be soft. Unfortunately, the current data structure in Checkvist does not allow hard links, because each item is coupled with its list. Of course, there will be an indicator where the 'master' item is located in UI.
Thanks again for the comment,
Юрій Бабак commented
Hardlinks for items, symlinks for branch — really critical feature.
Often if you have a complex structure it is needed to show same items or same branch in few places (different contexts). Not showing link to other item/branch, but show their actual content.
Currently we have to copy items for this and it is hard to maintain them as you have to edit item is many places.
Hard-links for items symlinks for branch should solve this problem — you edit item in one place and all other instances updated.
But there will be needed some indication that item has other instances, and probably some warning when editing.
This would put checkvist in a whole new level for me. It would allow me to organize in a much cleaner way. Would love this.
I had to google conref, and yes, looks like similar to it.
Jean-Francois Joly commented
Like a conref??
Peter Moran commented
Bump because this would be an amazing power feature. My use case is I would love to use this to make a mega list, allowing me to get a total overview of everything. Another case is it would allow me to email in new items to specific nodes in my list or share specific nodes. The more nodes and lists can become interchangeable, the more powerful features can become.
This is the one thing I want most. Checkvist is an amazing tool and has kept me much more organized, but this feature would allow for some amazing opportunities for collaboration and organization. I haven't upgraded to the Pro version of checkvist yet (although that may change with the winter sale), but this would make it an insta-buy. And I would likely get my entire department at work to use it.
I see this was suggested a long time ago, and I'm sure there are good reasons for it not being implemented yet (complexity, higher priority tasks, etc). I don't pretend to know or understand the reasons, but I hope it is still in the pipeline. You guys are making a great product, keep it up.
+1 This seems essential for true collaboration, delegation, and DRY (Don't repeat yourself) design.
@EHansen I've updated the name of this request so it better reflects the idea behind. Thanks for the suggestion!
Jonathan Sheller had a similar request, with many more details which was declined and pointed here instead. I prefer Jonathan's description but assume as it was considered similar then the implementation of this which you do will work is his suggested manner, and then it has my vote :)
His was titled:
Embed existing lists/sublists, not just hyperlinks (similar to symlinks)
Being able to embed/nest a specific node/tree from a different list would definitely streamline project management in Checkvist.
Jonathan Sheller commented
Still holding out hope for this feature. The ability to effectively embed nodes within other lists, symlink style so that they're the same data element and are "synced" (i.e. if someone edits the sub-items in the Node which is in list A, those edits will also show up in the identical Node which is embedded in list B since it is one and the same Node, just displaying in two places). I think it would be a real killer feature.
This is a fantastic idea. It makes a lot of sense for collaboration, e.g. if you are building up a complex knowledge document. Different team members could work on different areas of research, and then a master document could be composed just using inline, dynamically embedded outlines.
Somebody mentioned that this might bloat Checkvist into a full-on project manager, but I disagree. This feature need not have any significant effect on the software design, or your workflow, if you opt not to use it.