Presenting: Tids-to-Table ~ generate tables from filters

Plugins
#1

Proudly unleashing:

    Tids-to-Table

This replaces both list-rows and the much earlier list-table-draggable.

Tids-to-Table is simple to use, basically you type <<table>> and you get a little setup form where you fill in the tiddler filter and other settings. The output is a table based on the tiddlers from the filter.

This uses the dynamic power of filters and templates and the fundamentals of html so really complex tables can be generated. This is way more powerful than wikitext pipe | tables and way more efficient than building static html tables. Try it out, I’m pretty sure you’ll like it.

8 Likes
Please, take this 3 second screen test!
Re-presenting: list-rows ~ formatted data in draggable rows
#2

Congratulations Mat! This looks very useful, especially since you should be able to create the equivalent of an SQL “join” table.

A comment about the demonstration. The explanatory text floats over the demo and prevents accessing items on the right side:

image

#3

Right - the “power” of a table becomes a matter about the filter!

Thanks for the heads up about the demo. And, by the way, it is thanks to your previous feedback about a need for some some kind of “redo” feature that there is now the button to (re-)enter the setup.

#4

Hi Mat, I notice that it isn’t possible to drag an item to the very last position in the table. This is doable by adding an extra droppable widget after the last table row. The core list* macros use a similar approach.

#5

Good point @saqimtiaz !

And again, thanks for your previous feedback. It was incorporated into this new version!

#6

Very nice Mat!

One very minor point is that the macro <> may confuse pre-existing users of TiddlyTables. Obviously there are several work-arounds that can avoid this, but new users may encounter confusion. The older package is “stable” and unlikely to be updates.

#7

Forum tip: Put code ticks (control-e) around anything in angle brackets, otherwise the forum will attempt to interpret them as HTML tags. e.g. <<table>>

#8

(<<table>>, right?) I’ve never tried TiddlyTables so I was not aware of this but I did consider the risk of previous macros using this most obvious name. I reasoned that it is “very TW” to generate content by means of filtering tiddlers so I, evidently like the author of TiddlyTables for his/her macro, felt it was justified with this name. But as you hint at, if anyone is not happy with this then it is simple enough for that person to just overwrite my macro (and in a single place, if I’m not mistaken, i.e the very macro definition name).

#9

I totally agree that its a minor point and a simple search should clear up any confusion.

If you haven’t seen the other version, a quick peek at this http://tiddlytables.tiddlyspot.com/ may be of interest.

Best,
Hans

1 Like
#10

 
  Updated!

This now allows for dropping the dragged row also at very bottom of the table (as per @saqimtiaz request). The update also has some other code improvements.

#11

@pmario wrote:

The demo 3/6 does not allow my to click the Config-Button … It hides from the mouse cursor – I’m almost sure that’s intendend :wink:

Edit: Using FireFox on Widows. … It seems to be OK with Edge

I can’t replicate the issue. Using FF on Windows shows as intended on my machine. Can you tell what might be causing it? In all the demos I added a margin:2em to make the tabled display more prominently - is that relevant for the issue? Are you using some non standard display? I can image that a tight theme, that removes the tiddler gutters, would not like a button that is position:absolute; margin-left:-2.1em; .

EDIT: Maybe this is what you mean: The button easily disappears when you approach it. Yes, this is “intentional” in the sense that you must “enter” it from the table, without “passing” outside of the table on the way there. (.tids-to-table:hover .tids-to-table-ctrl {display:block;}) I figured that users won’t re-enter the settings very often so the button should be accessible but you shouldn’t risk accidentally clicking it when dragging (which is probably a more frequent activity). … But the behaviour should not be different between different browsers… so maybe this is not what you refer to? Or would it be better if I doubled the height of the area for the settings button?