Multiple Views - Kanban, Column, Calendar etc

[Aaron]

I noticed this is an important goal according to your support site but there’s no corresponding Trello card for it.

I’ve seen the existing Article View feature but I think this feature would be far more useful if implemented per-item.

In the item menu there could be a setting for ‘Select View’ which would allow an item to be set as List View (default/outliner), Kanban View, Column View etc.

The bullet for this item would then be highlighted as being a ‘special View’ type e.g.

These multiple Views obviously require a lot of time to implement in their fully-featured versions, but there are quick minimum versions that can be implemented with less features.

It would likely be easiest to initially make the item unable to be expanded, only zoomed in on (full-screen mode only).

Also you can make these special Views read-only at first, so if users want to add data they have to switch the View back to List View in order to add it.

[Erica]

There’s no Trello card for it because it’s more like an epic rather than a specific feature. There’s no clear spec for “multiple views”, basically.

The thing about letting each item have different views is that mixing them can be weird and also hard to implement. Imagine a Kanban item inside a normal item, and one of the Kanban item’s children items is a calendar item… all on the same page. Is that what you’re suggesting?

[Aaron]

There could be separate cards for each View so voting can help prioritise which View first?

No I’m not suggesting any mixing of Views. My idea was that children of a special View can’t have their own special View.

For example the highlighted items here represent the special View ‘title’ basically, and the children of each are entirely shown within their corresponding View:

All of the example data children for ‘Kanban’ can be switched back from Kanban to List View (as it is shown above) by setting the parent ‘Kanban’ item back to List View.

Only then could a child item be changed to a Kanban View, like so (represented by the purple highlight):

Let me know if I’m explaining this well enough.

[Erica]

I think I understand what you’re saying, but don’t understand where you’re coming from. By that I mean, I don’t get why this restriction is needed.

If I understand correctly, you’re suggesting disabling nesting views?

I would be more interested in hearing more about why per-item is better than per-document. Per-item view is more complicated for both us and the user, so in my opinion it requires some significant benefits for us to consider doing things that way. What do you think?

[Aaron]

Thinking about it now with the way I suggested is mostly the same result as the per-document method.

There is a slight usability advantage to the per-item view, similar to this method I found in an excellent article on embedding iframes such as spreadsheets, mindmaps and documents under an item. This way you can just expand or collapse items as needed to see each special View.

But to be fair I’d rather just have the new Views in any way I can ASAP rather than per-item (in particular having a Table View because Dynalist is not well suited to that sort of data at the moment).

[butlermatt]

I would be more interested in hearing more about why per-item is better than per-document. Per-item view is more complicated for both us and the user, so in my opinion it requires some significant benefits for us to consider doing things that way. What do you think?

I love the idea of a “per-document” view. So when creating a document you could choose the type of document it was going to be (Kanban, Calendar etc.). Then as soon as you click on the document it just loads it with that particular view. It sounds super sexy. Long way off I realize but I personally like that one (maybe a slightly different icon to distinguish between the various document types?) But yeah I like that better than a per-item level which I feel would get really confusing when looking at a high-level item in the regular list, then you click on an item or certain sub-item and suddenly the view changes completely

[Brian]

Desperately want column/kanban view. I’m migrating from Notion and that’s the main thing I’m missing.
I share Erica’s confusion at the idea of per-item views.
I can see it implemented several ways. The simplest version I envision would be just having 2-4 documents up side-by-side simultaneously, assuming I could drag items between them. Per-document view also makes sense to me.

[Erica]

I can see it implemented several ways. The simplest version I envision would be just having 2-4 documents up side-by-side simultaneously, assuming I could drag items between them. Per-document view also makes sense to me.

By “2-4 documents” do you mean different documents or 2-4 views of the same document?

If you mean different documents that would be split view.

[Jonathan_Leung1]

I’d really love to just have a simple Kanban View where on any bullet, I can see all of it’s children as columns, and all of the children’s children as items in that column.

As an alternative implementation, I submitted this idea: Split screen

[Jonathan_Leung1]

This is what I’m doing in the mean time:

Using this bookmarklet script:
(function(){window.open('https://dynalist.io', '','width=320,height=480');})(); to open really small windows