fix labeled view handling of multi-line content

+status

open

+priority

low

+tag

views

+issues

We'd like to keep label + content to just one line per card.

If the content is long enough, it wraps to a new line.
If the content has any h1 or h2 text that gets put on its own line.
On wide screens (even just 17") the label has a huge margin to the left, reducing how much content will fit.

+example

http://johnabbe.wagn.org/media - look under "Other cards tagged with media"

labeled was really intended for short, simple, one-line content. but I suppose people will try to use it for other stuff.

--Ethan McCutchen.....2013-07-17 01:54:45 +0000

we could also consider only supporting labeled view for certain cardtypes like phrase, number, pointer, etc.

--Ethan McCutchen.....2013-07-17 18:38:50 +0000

Seems like their ought to be a way with HTML and CSS to pretty easily just have content chop off at the right edge and never go to a second line. But I know we actually calculate/guess how many Pointer items to include in closed views, so maybe not?

Are there already other views that only work for certain types?

--John Abbe.....2013-07-19 05:23:42 +0000

If we're chopping content, doesn't there need to be clear visual indication? Closed views seems to suggest that (especially in lists), but labeled ones don't. It seems to me like an unchopped but wrapping labeled view is more valuable than a chopped one.

yes, views are defined by set.

--Ethan McCutchen.....2013-07-19 16:18:42 +0000

For my purposes at least, I want labeled to stay on one line. I think adding a visual indication would be good, curious what you see as one on closed view? How hard would it be to have the text fade out in the last inch or so on the right edge?

Thought I would check what happens when you try to apply a view to a card not in that view's set, but I'm struggling to find one like that - can you give an example?

--John Abbe.....2013-07-19 17:52:49 +0000

well, for example, an image has a "source" view that just gives its url

--Ethan McCutchen.....2013-07-19 18:01:12 +0000

Tx. So I see we return eg "view source not supported for foo" - seems right.

Source is new to me, at one point the plan was to have the raw content be the URL but I see we went another direction. Source gives a relative URL, we don't expose the site's root URL anywhere do we? Something like *siteurl?

Still wondering about visual indications of chopping...

--John Abbe.....2013-07-19 18:18:55 +0000

I just meant that default closed views have a line above and a line below. In a list, it gives the clear impression that you're only seeing a line's worth of data. Idiomatically it looks like email subjects / content. It's not explicit, but it's clearly implicit that there might be more.

--Ethan McCutchen.....2013-07-19 18:27:48 +0000

Makes sense. What do you think of the fae-out idea?

--John Abbe.....2013-07-19 18:39:27 +0000

probably doable. that kind of thing (as well as closed view stuff) needs to be skin-specific. there's pretty much a moratorium on new styling until we get skins.

--Ethan McCutchen.....2013-07-19 18:52:00 +0000