Hi Andreas, > But in practice I think that was a poor decision, and it makes more sense > for all fields to be strings and to be parsed to the required data type as > needed. Otherwise there are problems when different plugins want to > specify a different type for the same field. >
Actually, perhaps not. If I had a widget and tell it to "please use field foo as date so I can pick a day or do some other mathemagics", there really is no need to have some global type declaration, especially for user created fields. As for Andreas' request for certain control buttons, some pointer may be found as to the computational magic from *dateChooserPlugin* in MPTW <http://mgsd.tiddlyspot.com/demo3.html#%5B%5BOkay%20to%20donate%20blood%20again%5D%5D%20dateChooserPlugin%20TitleButtons> . Best wishes, Tobias. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
