As an update I have decided to not to use modals, and use the natural tiddlywiki flow by using the zoomin story view instead. I want to make something that works in all the ways not just depend on modals.
On Saturday, May 18, 2019 at 9:03:36 AM UTC-7, passingby wrote: > > > > On Saturday, May 18, 2019 at 5:09:58 AM UTC-7, TonyM wrote: >> >> Passingby >> >> The following may be obvious but worth remembering. >> >> If you have no need to use a template or apply tags to create a new >> tidder, a simple link even [[new tiddler]] is enough. The new here button >> helps create tiddlers tagged with the current of course. >> >> but all the sophisticated options are available and I can help with those >> as I have studied them. >> >> Regards >> Tony >> > > Tony, > > Thank you for your input. What I am trying to accomplish is create a food > journal for personal health issues. The target is to record everything I > eat or drink and record the symptoms that follow. The general idea is > create a journal tiddler. It should have a custom view template which > displays a kind of a menu with buttons in which I can create child tiddlers > such as events: breakfast/lunch/dinner/snack, drink, medication/supplement, > exercise/yoga/, Stress, Sleep. And then outcomes: physical symptoms, energy > level, mood, main thoughts(spiritual/job-related/creativity-related etc). > > I was thinking I should have the child tiddlers such as events and > outcomes show up in a modal state. They should have a simple and minimal > layout with all the fields being displayed. Then there should (preferably) > be to buttons to either cancel or confirm the data change. > > In order to create a view template in which fields can be displayed I am > taking help from technique used by http://tw5magick.tiddlyspot.com/ in > the tiddler [[Creating a simple Contacts DB]]. I have tiddler which shows a > form whose fields are linked with the child tiddler. The name of the child > tiddler is picked up from another tiddler something like $:/_temp/meal. So > the way it happens is that whenever the button is pressed on the journal to > show a child tiddler, the name of that child is saved into $:/_temp/meal > and then the form tiddler is shown in a modal. The form tiddler then shows > up the data because its fields are picking up the name from $:/_temp/meal. > > The problem right now is whether it is possible to have a save/cancel > mechanism on the form tiddler. I don't think this is possible because in > this process the actuall child tiddler is not being put into an edit mode > and the tm-edit-tiddler event is not being fired and therefore > tm-cancel-tiddler cannot be used. So this is the problem right now. > > If I think about not taking this path but showing the actual child tiddler > in an edit mode, then I do not know how to change the editTemplate as to > per my taste. Because what I want in that is, have a clean simple form and > 2 buttons with cancel or confirm operations. > So this is where I am at. Any suggestions or pointers or even a different > approach altogether is welcome. > > > -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/bbb50678-82df-49f7-bd4b-4731550e1e53%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
