> > -- are multiple instances of the same string necessary in a list >> (currently only one is permitted)? >> > > I would perhaps not start with that for now. > Maybe later if someone truly needs a *basket: coffee coffee coffee* field. >
I disagree with this. I think it is very important to support arbitrary ordered lists. One of the bigger problems I had making my demo was that the parseStringArray function in the core removed duplicates from the list. Since the idea is to move toward using polymorphic fields I think that the basic operations need to be as flexible as possible. Trying to code for more restrictive operations and then relaxing those restrictions is going to be harder than going the other way. A simple example of where this would be useful would be for tracking items sold where if arbitrary lists are supported you would just need to click a button that adds the item name to the list. You could then use the count widget to get display how many of each item was sold. If this gets added to the core than doing something like that would require almost no knowledge and nothing outside of the core tiddlywiki to create. I think that is important. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2700120a-63d0-4810-98d3-0d4b4174fb4a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
