Mat, On further thought if we could have an update view and this was extensible we could build a designer view where tidbiz actively builds the tiddler, once build however it can all be hidden in the other views.
I think your desired approach is achievable with the following functions., - A Special dropzone on tiddlers (perhaps only in a designer view) where dropping a snipit will create a field eg; display-1 display-2 fields. It would also be helpful if this could be reordered with drag and drop. - Then in view or update mode each of these are transcluded in order and rendered. These would be your reusable code eg; lookup tag, a text editor view a checkbox tool. They can just be macros if desired. My own MyMenus plugin http://tiddlywiki.psat.com.au/mymenus/has menu items that work in a similar way to above. What I have discovered is these snipits are like your code moduals and the traditional snipit so I am building a library of them. I will eventually also add an Editor toolbar button that allows you to search only snipits and insert them in the text field. Also working to allow field management such that should you create a menu-fieldname you can select its value from a dropdown of all other menu items/snipits. Regards Tony On Saturday, April 28, 2018 at 7:59:43 PM UTC+10, Mat wrote: > > @TonyM, > > yes, but: > > I think it makes sense to improve the editmode experience and I have some > opinions on what should be done BUT I think *the main problem is the very > editor*! I really wish we could have a more interactive editor that > featured something comparable to Intellisense > <https://www.youtube.com/watch?v=lSPHucggmLo> - word completion, hover > over a widgetname to get e.g parameter list etc. This *really* would > simplify editing. (It really doesn't make sense that we have to look up > parameters etc in the docs all the time!) > > (Of course, TidBitz <http://tidbitz.tiddlyspot.com/> is an attempt to > even further save the user from having to go into edit view. Unfortunately > dev there is stuck.) > > Now, that said, I'm curious to hear more about your vision. Who exactly is > the audience for the modified edit view? If the UpdateTiddler view is both > designed by me and then intended to be used by me... then I'm not sure the > benefits are worth the effort. Especially if the idea is that I make > different such a customized edit modes for different applications (again > with myself as end user). > > Or is the idea to use it for multi-user-TWs? I could see value in that > context... but multi-user-TWs are not quite established yet. I know only of > Jeds late MultiUser > <https://groups.google.com/d/msg/tiddlywiki/-372GqEo4pY/9jTMTzaQBwAJ> > creation which I hope will be useful but I've yet not had a context to use > it in. > > <:-) > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywikidev@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/cac47d23-315a-49f6-a229-8522e8c21ed0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
