Open jsavage opened 10 years ago
That's a good idea. This somewhat overlaps with #100.
Getting the UI on both right is challenging.
I can imagine. I found myself wanting to do some tiddying up and when it came to delete a tank I then realised that I didn't have confidence that the tank was truly empty and that there was no way (other than going to the API) of seeing what was there. A simple list what is there might be all that this use case needs providing that it includes binarys etc.
On 14 April 2014 22:55, Chris Dent notifications@github.com wrote:
That's a good idea. This somewhat overlaps with #100https://github.com/cdent/tank/issues/100 .
Getting the UI on both right is challenging.
— Reply to this email directly or view it on GitHubhttps://github.com/cdent/tank/issues/113#issuecomment-40423216 .
<img src="
http://mystatus.skype.com/balloon/jdcsavage" style="border: none;"
width="150" height="60" alt="My status" />
Get Skype and call me
for free.
I've deployed a first stab at making this go, if you could give it a gander and let me know if it is in the right direction, that would be great. It's certainly not perfect yet, just an effort to get the data displayed and available for better formatting.
For example what should the ordering or the tiddlers be. Right now it's by title as that seemed an easy default.
Before deleting a tank it really should be possible to confirm that there is no content that is still required stored within the tank. As a minimum, I would suggest a count of tiddlers within each tank. Clicking on that number could then list the tiddlers contained and logically then clicking on the name of a tiddler could then link to the tiddler.