--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ac15bee4-dd10-4ef4-8118-7cbcadfc9bcf%40googlegroups.com.
Great question Mohammad! It was built using only TW code, no JS. Certain features would have been easier to build using js code (like pagination) but this project was primarily a learning experience for me to learn the TW syntax and see how far I could take it. By the way, this plugin is TW 5.1.16 compatible so it doesn't even utilize the new math operators. I'm sure performance and usability would be improved if I implemented some js code and that may be the direction I go in the future. I left the version in beta because I hope to get feedback on these sort of topics before saying it is ready for production use. Thanks for the question!
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ec0c0148-a3d9-4037-8286-130f5fd3d2cf%40googlegroups.com.
There are several differences compared to the WidgetMessage: tm-delete-tiddler:I think switching deletion to the tm-delete-tiddler message would handle the confirmation.
- The user is not prompted to confirm the deletion
- No automatic updating of the story list
- No special handling of draft tiddlers
I just assumed sorry. You have already done it.
Love your work
Thanks
Tony
Alan,
Spontaneous feedback:
"Holla die Waldfee!" - literally translated "Be aware of the the Forest Fairy" - exclamation of surprise in face of an unlikely, unexpected, unprecedented, (often) pleasant observation - contemporal: WOW, OMG - british "I dare say!" or "Well, I never!"
Great icons, task-function exciting
Has the potential to become a standard lighthouse-plugin
Pit
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ac15bee4-dd10-4ef4-8118-7cbcadfc9bcf%40googlegroups.com.
_________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
[all[shadows]prefix[$:/info]!prefix[$:/info/browser]] [[$:/info/browser/name]]
<$tiddler tiddler="Has Changed">
<<table>>
</$tiddler>
<$tiddler tiddler="Has Changed">
<<table>>
</$tiddler>
You absolutely can and this is what makes TiddlyTables so powerful. Basically, the elements of the table are all modular and are controlled by templates. I will go into detail about editing templates in my next post, but the template that controls the body of the title column is: $:/plugins/aaldrich/tables/template/body/title.
<td><$view tiddler=<<currentRecord>> field="title"/></td>
<<currentColumn>>
title
Alan:I've been cautiously testing your TiddlyTables creation for some time now. First and foremost, I think its a wondrous tool! Thank you very much for sharing this creation.
Its not packaged yet. Would a short descriptive video be ok?
Yony
<$reveal class="tbl-delete-confirm" type="match" state="$:/temp/tables/delete-all!!text" text=<<currentTable>> tag="div">
Delete all displayed records?
<$button class="tc-btn-invisible">
<$list filter=<<tableFilter>> variable="currentRecord">
<$action-setfield $tiddler=<<tempTableStyle>> $index=<<currentRecord>> $value=""/>
<$action-deletetiddler $tiddler=<<currentRecord>>/>
<$action-deletetiddler $tiddler="$:/temp/tables/delete-all"/>
</$list>
{{$:/core/images/delete-button}} ''yes''
</$button> or
<$button class="tc-btn-invisible">
<$list filter=<<tableFilter>> variable="currentRecord">
<$action-deletetiddler $tiddler="$:/temp/tables/delete-all"/>
</$list>
{{$:/core/images/close-button}} ''no''
</$button>
</$reveal>
I would love to get more technical feedback on the code in case there are some optimizations that can be made. I may need to post something on TiddlyWikiDev for that. In any case, I think the next big milestone is the 1.0 stable release. I want to make sure there aren't any missing use cases, documentation is adequate, and of course no bugs. Thank you for your feedback so far and thanks in advance for any future testing/feedback.
Hi Alan,TiddlyTables is quite powerful now but it needs more documentation and example to simply be learned by new users.Yes, the focus loses needs to be investigated and the best solution introduced!I hope other users give their feedback!
Suggestion: A self-contained plugin that simply sorts tables could be a spin-off that would be widely adopted?
<td class=<<tagcls>>><$tiddler tiddler=<<currentRecord>>>{{||$:/core/ui/ViewTemplate/tags}}</$tiddler></td>
.tagclass .tc-tags-wrapper{ margin:2px 0px; }
- When the limit on the footer set to show all you, the pagination disappeared and you can not set a new limit and one has to edit the tiddler and set the tbl-limit field
- When the width set to some values less than 100% none of footer (pagination) nor the red strip (warning for delete all tiddlers) follow the width setting and occupy the 100% of tiddler width
Hi Mohammad,These are both inherent limitations of working with index values in TiddlyTables. Let me explain...In your first example, you are trying to sort by an index. There is no simple way to do this in TiddlyWiki and because the table is generated by a filter, no simple way to do this in TiddlyTables.Here is a thread discussing this issue, and a couple macro-based solutions. In fact, you replied that you would try one of the solutions in your Dynamic Tables plugin. Did you have any success? any
suggestions?
\define tableFilter_indexes() [enlist<items>]+[$(sortneg)$$(sortType)$[]]
\define getitems()
<$set name=Index tiddler=<<tempTableSort>> index="sortIndex">
<$list filter="[subfilter<inputFilter>!has[draft.of]]" >
<$text text="[["/>{{{ [<currentTiddler>getindex<Index>addsuffix[°≡°]] }}}<<currentTiddler>><$text text="]]"/>
</$list>
</$set>
\end
\define display_body_indexes()
<$wikify name="items" text=<<getitems>> >
<$list filter=<<tableFilter_indexes>> variable="currentItem" >
<$list filter="[<currentItem>split[°≡°]last[]]" variable="currentRecord">
<<display_one_record>>
</$list>
</$list>
</$wikify>
\end
In your second example, you want the plugin to intelligently determine whether to create a new field "ic" or a new index "ic". the way the plugin works is if a field exists with that name it will take precedence over the index. I opted for a simplicity here though I suppose the plugin could make a more advanced decision based on whether that index exists and whether there is already data in the text field. That is the main reason it defaults to field instead of index. There is a risk of accidentally overwriting existing data in the text field if you inadvertently "create an index" by editing.I agree the documentation could be improved. I wish I had more time. I plan to add something to this effect:There are some limitations when using indexes as columns. This is due to inherent limitations of index support in filters. The most noticeable is that index values cannot be sorted. A mix of fields and indexes can be used as columns in a single table, but there is no way for the user to distinguish a "field" column from an "index" column. If an index and field exist with the same name, it is possible to have a mix of index values and field values in a single column. If a tiddler has both a field and index with the same name or if neither exist, the field value will always take precedence whether viewing or editing.
Thank you for pointing this out. I hope this helps,Alan
Greetings All, I am a long time fan of TiddlyWiki but new to the community. First and foremost, I would like to thank Jeremy for creating TiddlyWiki and everyone who supports it. As a way to learn the ins and outs of TiddlyWiki I started a "table builder" plugin that I have been gradually improving in my spare time. I finally got around to finishing it up recently and would like to share it with the community.The ability for the entire wiki to import/export to/from a spreadsheet is a fascinating feature of TiddlyWiki, and I wanted to build on that strength by creating a simple way to query data in the wiki and display it in a tabular way. I am calling it TiddlyTables. The following link contains installation instructions and examples:There is also a "task manager" plugin that can be downloaded. Its primary purpose is to demonstrate the features of TiddlyTables. I look forward to hearing from you. I will do my best to answer questions and I appreciate any feedback.Thanks,Alan Aldrich
--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/VFf0ZJW_Noo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/93010043-5171-4438-b4bd-012ff17cb7f6n%40googlegroups.com.