Ticket

+commit
 

there's HTML that makes munges up current export

 

Like naked, but remove:

  • add/edit link and paging cruft
  • pointer- and search-item spans around items
  • link markup around each item
  • references to cards that don't exist?

Add commas between items.

 

 

also see add csv file format


References to cards that don't exist is a question mark because I know that for Pattern Language of Group Process we actually *do* want them. Not sure what to do if there are use cases where we don't want them, smells like a potentially general pattern.

  --John Abbe.....Mon Jan 24 12:33:13 -0800 2011


you know, I'm not sure this should be a view. it might just be that this is the :naked view in the CsvRenderer (or Formatter or whatever we end up calling it)

  --Ethan McCutchen.....Wed Feb 16 12:14:01 -0800 2011


Are the various renderers (or formatters or whatever) listed somewhere?

 

I occasionally itch for access to the code repository, just so I can look around. I don't need permission or anything for that, right?

  --John Abbe.....Wed Feb 16 13:07:46 -0800 2011


nope: https://github.com/wagn/wagn

 

there aren't many renderers yet. so far it's really just slot.rb and renderer.rb

  --Ethan McCutchen.....Wed Feb 16 13:12:40 -0800 2011


thx. and it's something there will be more of?

 

and my 2 cents is to stick with renderer, since we already have forms/formatting and are likely about to add formats :)

  --John Abbe.....Wed Feb 16 13:31:38 -0800 2011


this is tightly bound to the other use of formats; that's why gerry wants to change it.

 

I don't like renderer. I think Viewer may be my favorite.

  --Ethan McCutchen.....Wed Feb 16 13:51:32 -0800 2011


certainly easier to pronounce. how do viewers relate to views?

  --John Abbe.....Wed Feb 16 14:04:31 -0800 2011


Did you end up calling them Viewers? And if so, shall I ticket (or replace this with) add CSV Viewer?

 

And is core/naked view really sufficient? Seems like for many uses of CSV we might want to strip out some of the HTML within the content as well, as described in the solution. Oh, and data from multiple cards need to be string together with commas. Yeah, I don't see how core is sufficient. If I'm exporting a bunch of formatted cards, I want the data in the plus cards attached to each card to be strung together on one line separated by commas. (And to escape commas within content - I assume there's a standard way to do this.)

 

If I'm totally missing something here please fill me in...

  --John Abbe.....2013-03-18 16:26:17 +0000


Maybe this continuation of Basic import is related here? Sorry if I'm over-generalizing, it is a way that my understanding goes awry sometimes.

  --Gerry Gleason.....2013-03-18 17:54:54 +0000


Not understanding your question, sorry.

  --John Abbe.....2013-03-18 22:30:52 +0000


this is obsolete. csv is a format, not a view. closing.

  --Ethan McCutchen.....2013-03-20 02:34:32 +0000


so is it done, or is there already a ticket, or do I add add CSV format?

  --John Abbe.....2013-03-20 14:25:36 +0000