Hi Jeremy Sounds interesting! (my way of saying I kinda get it but can't quite visualize it yet). Build it, and walk me through it, and I will be the first one in line to try it out.
Dave On Wednesday, July 31, 2013 7:59:47 AM UTC-5, Jeremy Ruston wrote: > > I understand the rough idea, that in addition to tags, fields would also >> become important for identifying tiddlers and even grouping tiddlers and >> tags. > > > That's not quite it. Under the hood, tags are stored in a special field > called "tags". The content of that field is a list of tiddler titles. The > proposal is to make the "tags" field less special by making it possible to > give any field the same structure and behaviour. > > >> And a benefit would be the ability to graph the field data into things >> like d3. But could you briefly describe what the user would see, what you >> expect the user to want to do with it, and what steps s/he would have to do >> to get there? >> > > This change wouldn't be particularly important to a casual end user; it > would be more something that somebody setting up and configuring a > TiddlyWiki would encounter. > > The change would manifest itself in several ways: > > * When adding a new field to the tiddler, one would be able to stipulate > the type of the field. The list of types would include "string", "date", > "integer", "color", "tiddler title", and, now, "tiddler list". (At the > moment fields have a type but it only manifests itself in Chrome where > "color" fields get a colour picker in the editor) > > * Certain widgets and filter operations that currently apply to tags will > be broadened to cover other tiddler list fields. For example, if I've added > a field called "extags" that is defined as a tiddler list that I am using > as a separate tags field, then I would be able to write a filter like > [extag[MyTag]] to test for a tag within that field > > * Things like drag and drop reordering of lists would be implemented as > standard widgets that could operate on any tiddler list field > > It's one of those cases where by we're taking an existing core mechanism > within TW5 and extending and generalising it just a little so that it can > be used to address more our missing features. It's actually a > simplification of the design of TW5, accomplished through extending it's > capabilities. > > Best wishes > > Jeremy > > >> >> Dave >> >> >> >>> With respect to the comments about handling multiple tag fields, I'm >>> increasingly interested in the idea of generalising "list of tiddlers" as a >>> field type; the tags field would then just be an instance of that field >>> type. So you'd be able to create many different fields each of the type >>> "list of tiddlers". This idea also fits in nicely with the work I've been >>> doing on D3 integration: in D3 the fundamental datatype is the list (or >>> array). This would allow us to model a table as a list of lists, which >>> would fit very naturally. >>> >>> A potential side effect of the change is that the ordering of the tags >>> applied to a tiddler would be properly retained, allowing users to reorder >>> tags to convey their relative importance. >>> >>> Does that make sense? >>> >>> Best wishes >>> >>> Jeremy >>> >>> >>> >>> >>> On Tue, Jul 30, 2013 at 10:34 PM, David Gifford <[email protected]>wrote: >>> >>>> Awwww, it didn't work. After the hangout I tried adding the tag creater >>>> to the TiddlerInfo window. But afterward I opened the information area and >>>> clicked in the tag window, and the information area closed. Apparently it >>>> doesn't like me. >>>> >>>> Dave >>>> >>>> >>>> On Monday, July 29, 2013 10:45:36 AM UTC-5, David Gifford wrote: >>>>> >>>>> OR - and here is a wild idea - >>>>> >>>>> What if you moved tag creation from the edittemplate to the >>>>> information area in the viewtemplate? >>>>> >>>>> What if you ditched the information icon and replaced it with a tag >>>>> icon like http://www.iconsea.com/**uploadi**mage/smallsort/4015/** >>>>> vdfo2orj4n**q.png<http://www.iconsea.com/uploadimage/smallsort/4015/vdfo2orj4nq.png>, >>>>> >>>>> >>>>> >>>>> And clicking the tag icon opened the same information area at the top >>>>> of the tiddler, and had the following: >>>>> >>>>> At the top, the add tag area currently found in the viewtemplate >>>>> Beneath it, the proposed ability to add new fields for custom tag >>>>> categories >>>>> Beneath it, the tabbed folders of references, tagging and fields that >>>>> is already in the information area >>>>> >>>>> This would be clean, the tag icon would make sense to any user who has >>>>> used Evernote, Wordpress, and other products that use tags, and would >>>>> lessen the time that people would have to spend in the scary edittemplate >>>>> nether regions. And it would remove clutter from the edittemplate and >>>>> make >>>>> it less scary. The edittemplate would just be for changing the title and >>>>> content, and for those who need it, fields at the bottom. >>>>> >>>>> >>>>> >>> >>> >>> -- >>> Jeremy Ruston >>> mailto:[email protected] >>> >> > > > -- > Jeremy Ruston > mailto:[email protected] <javascript:> > -- 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/groups/opt_out.
