Hi Tobias
> - a core awareness of field-types that can be defined somewhere > > Fields already have a type - look at the tiddler object definition in boot.js. 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. Best wishes Jeremy. For example, another usecase — although not nearly as challenging — would > be to have a "boolean" field set via checkbox, even in the default field > editor that has been made "type-aware". > > > Apart form doing basic date manipulation as you want, another meaningful > addition for editing dates would be a date picker. > > Yet another field may provide you with the option to select from a number > of predefined defaults, etc... etc... > > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/tiddlywiki. > For more options, visit https://groups.google.com/d/optout. > -- Jeremy Ruston mailto:[email protected] -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
