always return to sensible view after save

Idea

+priority
Tickets By Priority  

Low priority tickets

+tags
expand_more views
Wagn's flexibility in displaying data comes from organizing views of cards. Views are most often applied
...
expand_more Tests
Regarding the automated tests that run on Wagn's code (before any manual testing).  

Needed tests

  • correct default type for cards added via Pointers
...
expand_more Design
Whereas traditional web development stumbles whenever data structures emerge that weren't envisaged at the onset of the project, Decko embraces the idea that structures will ...

 

+issue

When you edit a card you got to via card/changes (or other tabs respectively) you get Changes interface after saving. You should get the normal look.

 

You also get Changes interface when clicking the "View" tab

 

 

 

expand_less +discussion

Almost certainly we don't have any tests for this sort of thing, so I added a tag for that.


if I go to, say, /Menu?view=content, then presumably we want to set the "home view" as content. Same for /Menu?view=titled

 

The above url is equivalent to /Menu?view=changes. In fact, I would like to make the canonical url /Menu?changes.

 

So the question becomes, how do we know when the prescribed view should not be treated as a home_view. You could treat it as something about the nature of the view. As in, some views (open, content, titled) are candidates for the view tab, others (changes, editor, etc) aren't.

 

Or, we could say that links in this context should just be explicit about the home view. so you could do /card/changes/Menu?home_view=open, or perhaps ?home_view=_auto or something. That would leave open the possibility of having any view as the home_view.

 

I think the point is that we're overloading the word "View" a bit on that tab. Functionally it currently means the "home_view", which can be any view. But the standard user expectation is probably that you're seeing, at a minimum, the card content.

 

I don't think we're ready to work on this until we know what approach we're taking. It's currently confusing, but not exactly buggy, because the behavior is exactly what is intended under the "home view" model.

  --Ethan McCutchen.....Fri Apr 20 20:45:40 +0000 2012


I get the idea of the Tests tag, but that's going to be noise on wagn.org. better done in code.

  --Ethan McCutchen.....Fri Apr 20 20:46:21 +0000 2012


maybe I'm wrong about that. let's leave it for now and discuss once we figure out the design issue.

  --Ethan McCutchen.....Fri Apr 20 20:59:17 +0000 2012

+relevant user stories