On Sunday, July 8, 2018 at 2:19:53 PM UTC+9, TonyM wrote: > > JD, > > I have also being working on a sophisticated "tiddler Viewer" like > TWOutlier > https://groups.google.com/forum/?hl=en#!msg/tiddlywiki/ol_3zvGPbk8/EdIG3awlBAAJ;context-place=forum/tiddlywiki > > but with advanced handling of tiddlers in a TOC structure, this may be a > good way to present tiddlers that the key use is to edit their text > content. Add an Edit Text field to their ViewMode and they would never need > to edit the test. However remember there is value in the draft.of process > on the main editor. >
Oh, wow, I haven't followed that thread diligently, but I wish to combine it with Dave's NoteSlam <http://giffmex.org/tw.adaptations/noteslam.online.html>, which I think is simply fantastic. Although taking up such a project with no end-user in sight would certainly mean it's of lowest priority in my project list, I am very interested to do it. > > I have being more interested in the ability to create custom forms from > individual tiddlers and this means being able to insert edit fields macros > in the wiki text so they work in view mode or in a custom field > edit-fields-list so they just open below the tiddler text, I achieved this > but did not publish because when I thought about it just providing edit > text on a field is useful in many cases but what if it is used for a date, > a unique ID, and icon or image link. So now I am building field templates > that you can save as a prefix/fieldname that define how to handle the field > when editing. So one based on an image allows image selection, or one based > on a date, to stamp with now, or to select a date from a calendar. Of > course you are free to edit this definition and make the edit-field as > sophisticated as you desire. > Oh, I see the point. The type of edittext widget produced in view tiddler mode would depend on what "kind" of field is being editted. Like how the field "color" brings up a type=color input in edit tiddler mode. I was playing with edit-fields support for the "text" field, and have not > quite determined how to make it full width and have the number of rows as > the content, like the normal edit text fields work, I may very well find > the answer in TiddlyWikis edit template, which is the beauty of TiddlyWiki, > almost everything you want to do is done in some way already in tiddlywiki. > It might be a question of styling, and your comfortability with using display: flex; (my favorite). I think the first thing that needs to be taken care of is the backend stuff, if both can't be handled at the same time. > > On Sunday, July 8, 2018 at 2:19:27 PM UTC+10, JD wrote: >> >> Ooh, I am definitely talking about both. >> >> I've implemented a rather barebones way of editing select fields of a >> tiddler in view mode, in a wiki I use with other people in my work group. >> The reason for needing such implementation being that someone in my group >> doesn't want to interact with any other field other than the Text field, >> and work-related ones. >> >> I'm looking forward to testing your plugin, and seeing how it could be >> applied to that specific work wiki :D >> >> On Sunday, July 8, 2018 at 10:46:23 AM UTC+9, TonyM wrote: >>> >>> JD, >>> >>> Are you talking about Marks dragon or the edit-fields or both? >>> >>> The edit-fields is working for me, but I know to make it east to adopt >>> by others it needs a professional layer of documentation (Mohammads Reveal >>> Gradually Macro sets a high standard). >>> >>> The edit fields allows you define field types, then fields and how to >>> edit them such as dates etc... thus it is a tad more complex to document >>> effectively, just as my previous "initial release" plugin MyMenus was. >>> >>> To me it is essential we can can add fields from a list of possible >>> fields to the edit-fields-list and then change the order, when editing >>> fields, this is what I need to complete before it deserves listing. >>> >>> Regards >>> Tony >>> >>> On Saturday, July 7, 2018 at 10:16:02 PM UTC+10, JD wrote: >>>> >>>> Wow this is amazing and very useful! You should create a demo site for >>>> this so it could be listed to the semi-official DynaList ! >>>> >>>> Or maybe that can also just link to your post as a permalink? >>>> >>>> On Thursday, July 5, 2018 at 2:08:30 PM UTC+9, Mark S. wrote: >>>>> >>>>> Hi Tony, >>>>> >>>>> Here's a first pass at your original request. Make a global macro: >>>>> >>>>> \define dragoncopy(copyfield) >>>>> <$action-setfield $tiddler="$:/fields/$(currentTiddler)$" fieldname= >>>>> """$copyfield$""" fieldvalue={{!!$copyfield$}}/> >>>>> \end >>>>> \define dragonfield(field) >>>>> <$draggable tiddler="$:/fields/$(currentTiddler)$" >>>>> startactions=<<dragoncopy >>>>> "$field$">>>{{!!$field$}}</$draggable> >>>>> \end >>>>> \define dragondrop3(tid,fieldname) >>>>> <$action-setfield $field="$fieldname$" $value={{$tid$!!fieldvalue}}/> >>>>> \end >>>>> \define dragondrop2(tid) >>>>> <$macrocall $name=dragondrop3 tid="$tid$" fieldname={{$tid$!!fieldname >>>>> }}/> >>>>> \end >>>>> \define dragondrop() >>>>> <$macrocall $name="dragondrop2" tid=<<actionTiddler>>/> >>>>> \end >>>>> \define dragonzone(label) >>>>> <$droppable actions=<<dragondrop>>>$label$</$droppable> >>>>> \end >>>>> >>>>> Invoke the drag object like this: >>>>> >>>>> <<dragonfield "field1">> >>>>> >>>>> and in another tiddler put the drop zone like this: >>>>> >>>>> <<dragonzone "Drop Here!">> >>>>> >>>>> Have fun >>>>> -- Mark >>>>> >>>>> >>>>> On Wednesday, July 4, 2018 at 6:49:49 PM UTC-7, TonyM wrote: >>>>>> >>>>>> Mark, >>>>>> >>>>>> Thanks for this suggestion. The irony is I want to build this >>>>>> "feature" to allow reordering through dragging values in a field, as >>>>>> part >>>>>> of a tool, that allows you to edit-fields in the tiddler view mode, >>>>>> which >>>>>> itself demands this edit-fields from another tiddler approach. >>>>>> >>>>>> I am yet to develop a systematic way to do this, and until I do it >>>>>> seems hard to get my head around it. >>>>>> >>>>>> This is in fact the motivation for this edit-fields tools solution, >>>>>> because I am sick of having to wrap my head around bespoke solutions to >>>>>> edit-fields in the current tiddler, which for many is the most likely >>>>>> place >>>>>> they want to edit-fields. >>>>>> >>>>>> This is a gap in TiddlyWiki at the moment I raised a GitHub issue >>>>>> <https://github.com/Jermolene/TiddlyWiki5/issues/3350> >>>>>> >>>>>> I also created a collaborative document in Yammer >>>>>> <https://www.yammer.com/tiddlywiki/#/files/141096709> >>>>>> >>>>>> Regards >>>>>> TOny >>>>>> >>>>>> On Wednesday, July 4, 2018 at 3:23:25 PM UTC+10, Mark S. wrote: >>>>>>> >>>>>>> I think I see how this could work. >>>>>>> >>>>>>> In the draggable widget, use a corresponding (probably system >>>>>>> tiddler) to hold the value. Use the startactions attribute to assign >>>>>>> the >>>>>>> field. >>>>>>> >>>>>>> <$draggable tiddler="$:/field1" startaction=<<macro that copies >>>>>>> field1 into $:/field1!!value>>{{!!field1}}</$draggable> >>>>>>> >>>>>>> Then in the droppable widget, use the actions attribute to grab the >>>>>>> value from $(actionTiddler)$!!value and save it to the field >>>>>>> corresponding >>>>>>> to the dropzone. >>>>>>> >>>>>>> If you just want one dropzone that handles multiple fields, then you >>>>>>> could have the draggable widget also store the field name in a >>>>>>> fieldname >>>>>>> field and then the droppable can also fetch the destination from >>>>>>> $(actionTiddler)$!!fieldname. >>>>>>> >>>>>>> Once you have the draggable macro working, then you can make as many >>>>>>> field/zones as you want with <<dragfield field1>>, <<dragfield field2>> >>>>>>> etc. >>>>>>> >>>>>>> Good luck! >>>>>>> -- Mark >>>>>>> >>>>>>> On Tuesday, July 3, 2018 at 8:35:42 PM UTC-7, TonyM wrote: >>>>>>>> >>>>>>>> Folks, >>>>>>>> >>>>>>>> I am building a button to allow the dragging of values from a >>>>>>>> fields values in a tiddler. >>>>>>>> >>>>>>>> Looking through all the draggable widgets and use on buttons etc... >>>>>>>> I can only see reference to tiddlers, not parts there of. >>>>>>>> >>>>>>>> Can any one tell me how to specify a fields content as the payload >>>>>>>> or tell me a direction I could take. >>>>>>>> >>>>>>>> - A tool or code example exists? >>>>>>>> - Clone and rework an existing widget? >>>>>>>> - Use CSS/Html? >>>>>>>> >>>>>>>> I will also be looking to find a way to drop field contents on a >>>>>>>> field where it erases the existing content to. >>>>>>>> >>>>>>>> I will be turning this into a reusable solution I will share. >>>>>>>> >>>>>>>> Thanks in advance >>>>>>>> >>>>>>> -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/e29e8faf-4432-4672-bf91-3f7619e77450%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
