Jonathan Sheller

My feedback

  1. 79 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Checkvist Web  ·  Flag idea as inappropriate…  ·  Admin →
    Jonathan Sheller supported this idea  · 
  2. 667 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    103 comments  ·  Checkvist Web  ·  Flag idea as inappropriate…  ·  Admin →
    Jonathan Sheller supported this idea  · 
  3. 595 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    60 comments  ·  Checkvist Web  ·  Flag idea as inappropriate…  ·  Admin →
    Jonathan Sheller supported this idea  · 
  4. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Checkvist Web  ·  Flag idea as inappropriate…  ·  Admin →
    Jonathan Sheller shared this idea  · 
  5. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Checkvist Web  ·  Flag idea as inappropriate…  ·  Admin →
    Jonathan Sheller shared this idea  · 
  6. 142 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    36 comments  ·  Checkvist Web  ·  Flag idea as inappropriate…  ·  Admin →
    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.

    Jonathan Sheller commented  · 

    Kirill asked to merge the other feature request, so adding my notes & use case to this thread for public comment/feedback:

    Embed existing lists/sublists, not just hyperlinks (similar to symlinks)

    Rather than simply linking to a list/sublist, which embeds a hyperlink in my existing list, a real killer feature would be to actually embed that sublist in my current list. This would be have a lot like a symlink, with the key feature being that if I edit something in the sublist that edit is reflected everywhere in Checkvist that that sublist appears.

    Example use case: If I am listing out travel ideas by Geography as follows:
    - Italy
    --- Wine tasting
    - Puerto Rico:
    --- Caving
    -------- Tour operators information
    -------- links
    -------- other information specific to puerto rico caving, etc
    --- Scuba Diving
    --- Beaches
    ... etc

    And I also have another bucket list, which is organized around Activity Type as follows:
    - Natural Wonders
    - Rafting trips
    - Caving trips
    - Diving trips
    - Sailing trips

    What I would really love to be able to do, is embed the Puerto Rico Caving sublist (in the 1st list above - Geographies) into the "Caving" section of the second list (Activity Types) above. This allows me to enter more information and flesh that sublist out further, regardless of whether I'm currently thinking along Geography or Activity Type. Changes are reflected in both.

    At a meta-level, this allows lists to go beyond 1 "hinge" of data. I can effectively organize my information across 2 criteria/dimensions, rather than being limited to 1 (I can organize specific information about caving in Puerto Rico so that it appears on my list of travel ideas organized by Geography as well as my list of travel ideas organized by Activity Type). More generally, this allows massive flexibility.

    It will also form the backbone to some pretty amazing sharing features. For example, I could share a sublist with someone and instead of them having to view it as a "list", they could actually move it around within their own list structures. Maybe I share a specific Todo list with someone (i.e. fix site CSS) which has multiple sub-tasks. Instead of having to view this as a full list, they can actually take this and move it around their todo list (however they may organize it). Since all it really is, is a symlink to my subtask-list, any edits they or I make will sync.

    Workflowy implemented something similar to this, focused only on sharing. They allow you to share a sublist with someone, and for them to move that sublist around in their own hierarchy with ease. What they have not implemented and what could be extremely interesting, is sharing that same sublist with yourself. This would allow you to move it around your own lists and hierarchy, so that even if a list item should appear in multiple places you don't have to duplicate it.

    Implementation-wise, the only real hairy piece is circular references. I Imagine this is a nightmare for workflowy since their users just have one big mega-list. However, for Checkvist, it could actually be very easy: don't allow people to embed/symlink any lists of sublists within one List. Only allow symlinking/embedding sublists across separate Lists (full list objects).

    In my opinion, this is the single last thing Checkvist would have to do to be a full-fledged collaboration tool (and not just an awesome individual tool). It allows people to share "todos", but not just full lists. If you get your data structure to support this, it will all me to, for example, share a task, including subtasks, (from a big project-list) with someone and allow them to organize it how they like within their own organizational system.

    There are times where sharing an entire "project" or List with someone is what you want. There are other times when sharing a Todo (task) from that list is what you want. It also enables you to embed a sub-tree across multiple Lists, and have changes synced.

    Jonathan Sheller commented  · 

    I think this may be similar to an idea I just created, which can be found here: http://checkvist.uservoice.com/forums/2121-general/suggestions/3713589-embed-existing-lists-sublists-not-just-hyperlinks

    The idea is to allow a sublist to be embedded elsewhere in Checkvist. Changes to the sublist or it's children are reflected anywhere this sublist is embedded.

    Profound implications for sharing, organizing, and de-duping across checkvist. Would love to hear whether this is what the original post of this idea intended, or something else. And, of course, what the checkvist developers think about it!

    My idea is similar to a feature workflowy just implemented, which can be found here
    http://blog.workflowy.com/post/31422897499/embed-shared-workflowy-lists-in-your-own-account

    Jonathan Sheller supported this idea  · 
    Jonathan Sheller commented  · 

    Depending on how this is implemented, this feature could be a duplicate of: http://checkvist.uservoice.com/forums/2121-general/suggestions/898937-zoom-and-view-features?ref=title

    Jonathan Sheller commented  · 

    This is a great idea, and would improve the usefulness of CheckVist immensely. Please see WorkFlowy (www.workflowy.com) for a beautiful rendition of this concept.

    This concept also allows very elegant sharing features, as you could share just a branch of a large tree. This branch would show up as a full list (just a zoomed in view) for the sharee. What this means is that you could share at any level.

    In general, the way WorkFlowy deals with sharing and "zooming" is brilliant. I love everything else better about Checkvist, but LOVE those features in WorkFlowy. If you were able to combine them it would be truly powerful.

  7. 113 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  Checkvist Web  ·  Flag idea as inappropriate…  ·  Admin →

    Really good and useful request.

    Regarding accidental data loss: Checkvist Pro account gives you up to 10 daily backups of all your lists. Not the same, but may help in some cases.

    Jonathan Sheller supported this idea  · 
  8. 81 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Checkvist Web  ·  Flag idea as inappropriate…  ·  Admin →
  9. 143 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  Checkvist Web  ·  Flag idea as inappropriate…  ·  Admin →
    Jonathan Sheller supported this idea  · 
    Jonathan Sheller commented  · 

    that would work. I still worry that there would be a bit of confusion in terms of intuitiveness, if you were to mark something as "complete" and "delay" in exactly the same manner. if i set a due date of next monday, but then complete the task today (and don't remove that date) it may be a surprise when it pops back up close to next monday. I think it's better to somehow separate out the "delay" versus "complete" functions. This could be either a) there is a different layer of "complete" which gives the task these properties (instead of completing, you mark something as "postponed") b) there is a different "date" field that is the postpone-until date.

    I just think that without making it a bit more explicit (or explaining heavily upfront), the behavior could be confusing to most users.

    Total tangent: is there a way currently to see when a task was actually marked as complete? If I set a task as due next tuesday, but then complete it today, is the completion date of "today" recorded anywhere or do I need to manually update the date to today and then complete it in order to store that information for future reference?

    Jonathan Sheller commented  · 

    i think that would work. basically you can "complete" tasks today to get them out of view, but if you have set a future due date they will pop back in then.

    only issue here, is that it could cause confusion if you have a tasks set to be due next tuesday and for some reason you are able to complete it today. so then you mark it as completed. but if the default is that completed tasks become visible again if they have a future due date, this tasks would pop back in even though you meant to "really" complete it and not just postpone it. need some sort of delineation between these two cases.

    at least that is how i understood your suggestion. perhaps i'm missing something.

    Jonathan Sheller commented  · 

    really like this idea, would allow my lists to be wildly less cluttered. you could basically make a task act very similarly to a completely task, until the due date is triggered -- at which time it pops back into view. Due dates are great, but given that their purpose is largely to remind you in the future it would be great to be able to put items out of sight and mind until then

  10. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Checkvist Web  ·  Flag idea as inappropriate…  ·  Admin →
    Jonathan Sheller commented  · 

    Great idea, but I'm out of votes currently!

  11. 194 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  Checkvist Web  ·  Flag idea as inappropriate…  ·  Admin →
    Jonathan Sheller supported this idea  · 
    Jonathan Sheller commented  · 

    great suggestion, would be extremely useful.

  12. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Checkvist Web  ·  Flag idea as inappropriate…  ·  Admin →

    By the moment, you can modify Checkvist presentation in the PRO plan. You can alter some colors, and provide advanced custom CSS styles which allow to change the font size. But this requires hard CSS coding. We need to provide simple way to specify different styles for a list.

    The sample CSS for reducing font size in the list is:
    ul.topLevel li { font-size: 12px;}
    ul.topLevel ul li, ul.topLevel ul li.task { font-size: 10px;}

    Some more customisation samples can be seen in this list: https://checkvist.com/checklists/486715

Feedback and Knowledge Base