Each axis is either a Search (e.g. {"type": "Company"}, or a list of arbitrary cards (e.g. selected "fields" hard-formatted on Company cards - via a Pointer card?). Then in the simple case, each cell is populated with the content of card A+B where A is the card of the row you're on and B is the card of the column you're on (row/column can be vice-versa). The complex case is contextual - in a table included on page A, each cell is A+B+C
--John Abbe.....Thu Jan 24 23:02:24 PST 2008
Public Wagns would be improved and easier to maintain with this.
Compare a MediaWiki-based report generator: http://semeb.com/dpldemo/index.php?title=Main_Page
A wider scope for tables would be any two-dimensional (or even N-dimensional?) representations of a bunch of cards. Above is something like a spreadsheet, but think of a table as a piece of furniture you can lay out cards on. A Wagn table could allow for arbitrary placement of cards via drag-and-drop, like icon view in a file browser window, or Rhizosphere. The arrangement of cards would be saved with the table card, the same way that the order of Pointer items is stored in the Pointer.
(Also, polar vs. Cartesian; other coordinate systems?)
Occurs to me the most common case for table usage might be accomplished in tinyMCE. We could make it an option, anyway.
--Moe (Not signed in).....Tue Feb 03 06:53:27 -0800 2009
Any objection to integration of http://www.socialtext.net/open/index.cgi?socialcalc with wagn? I suppose this goes against "everything is a card" design pattern
Making each cell in a spreadsheet into a card seems rather expensive on resources, should you have a large spreadsheet. Although, I can see advantages too
--Sam Rose.....Mon May 25 15:46:58 -0700 2009
In the long run, I'd think both, and let Wagneers decide what's appropriate to the task at hand. As time goes by, people can move spreadsheets that were too resource intensive from something like socialcalc over to tables built out of cards.
--John Abbe.....Mon Mar 14 21:20:42 -0700 2011
+3 to John's comment on "both"
--Michael "Networking" Maranda.....Thu Mar 24 09:03:55 -0700 2011
Trying to wrap my head around different scenarios pertinent to this ...
One is card layout - showing different cards in a tabular layout..
One is tabular layout of info or data -- which need not be in separate cards -- I think treating this as two separate cases is worthwhile
Another case is Tabular with Spreadsheet functions ... i..e allowing calculation among cells or columns. If each cell is a card, that's one way, surely, tho I think a combo approach is also nice, because I agree in many cases it would be overkill/drain on resources.
Are any of these sensible to achieve as module/extensions, or is this really more complex and therefore suited to a baked in card type? (or types)
--Michael "Networking" Maranda.....Thu Mar 24 09:10:02 -0700 2011
basically all card types will soon be done as modules, though there are several that Wagn's core depends on. There may need to be some core enhancements to make table types fly, but, yes, they'll basically be modules.
I think you could basically do tables with non-card cells now by turning on tinyMCE's table handling, no?
--Ethan McCutchen.....Thu Mar 24 10:18:40 -0700 2011
i.e. we can do a cardtype which defaults that on?
--Michael "Networking" Maranda.....Thu Mar 24 10:21:32 -0700 2011
There's one *tinyMCE card which applies site-wide, though of course we could make *tinyMCE into a Setting so that different TinyME preferences applied to different sets of cards. On TinyMCE there are links to documentation where you can look up how tod add buttons to the toolbar to, e.g., insert table markup. The only question is whether we currently strip out such markup, but that would be pretty easy to change (maybe even without code changes?).
--John Abbe.....Thu Mar 24 10:47:06 -0700 2011
we don't strip the basic table tags (table, td, tr). Changing what gets stripped server side does require code changes.
Not sure whether the setting idea would work -- tinymce may not be able to handle different configurations on a single page.
--Ethan McCutchen.....Thu Mar 24 10:57:35 -0700 2011
however this gets implemented, it's almost certainly a pack.
--Ethan McCutchen.....Thu Dec 01 15:22:55 -0800 2011
+discussed in support tickets
+relevant user stories