i was wondering if the data and form plugins could use fields rather than the data being stored in the tiddler. then there would be no data in tiddlers. it can confuse.
i think there maybe a feeling that in the community that data plugin and formTemplates might stymie progress ones progress in the long term. I have a project which uses dataplugin and formTemplate. I came across a problem and Tobias re-wrote the whole lot (!) solving the problem though using native tiddlywiki data holders - slices, fields, tags and tiddlers. Alex 2010/1/27 twgrp <[email protected]> > You may wish to look into Abegos FormTiddlerPlugin > (+DataTiddlerPlugin) to create forms that are more easily filled in in > view-mode. It makes a structured data approach easier. The > StandardSections can be made as separate forms. Several such can be > combined int o a bigger template. > (One difficulty I'm wrestling with myself is hwo to automatically make > content in form elements into tags, though.) > > HTH > > On Jan 27, 1:48 am, mOede <[email protected]> wrote: > > Hello Group, > > > > I am so excited to jump in to the world of TW. I came across it just > > a week ago, and have already had several "light bulb" moments for > > things that I want to pursue with TW as a tool. > > > > For one such item, I would like to get some general design guidance. > > As I'm not a very proficient programmer, I would like to describe the > > problem, and get advice on how best to approach it. Then I will > > describe what I've done so far, and maybe I've gotten close and folks > > can just tweak it a bit. Thank you so much in advance for all of your > > great help. This google group is by far the most helpful community I > > have ever seen. > > > > I am trying to create a TW site for preparing technical specification > > documents. Each document could have 20+ sections (but not always the > > same sections). I would like to start out with a standard document, > > and then make copies of each section as needed so I can edit it for a > > project without changing the standard set. I would also like the > > ability to attach comments (separate from the edited section) that are > > searchable/accessible anytime I look at the "standard" section. Hope > > this makes sense. > > > > Here is what I have tried already. I have created a new tiddler for > > each standard section and tagged it StandardSection. I have used > > Eric's copyTiddler for each of these sections, tagged it back to the > > standard section tiddler and tagged it to a compile tiddler for the > > document using matchTags. So, using TagglyTagging, I can go to a > > standard section and see a list of project specific sections that > > relate to the standard, and comments related to those project specific > > sections. > > > > So, the question is, do you think this is a good approach? Is there > > anything that would be better from a design perspective? Also, one of > > the key features to make this work will be developing an easy way to > > copy and tag sections for a new document. I have used ToggleTag to > > apply a new tag, but is there a way to have a list of tiddlers by one > > tag, and select an option box and copy all of those tiddlers and tag > > the new one? > > > > Thank you again. > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<tiddlywiki%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/tiddlywiki?hl=en. > > -- http://www.multiurl.com/g/64 -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
