[twdev] Re: Draft mechanism - how to test tiddler has a draft but is not the draft itself?

> > >- I do not want to list the original tiddler name when a draft exists > > get[draft.of] > >- the result would be a list of tiddlers, if a tiddler is in draft >mode the *non draft of the tiddler will not be listed*. > > I didn't test this but: <$vars hasdrafts={{{

[twdev] Re: Plugin Packaging Question

You're asking about naming shadow tids: There's a convention, probably mostly for practical reasons, to keep the plugin title as prefix but shadows can have any name. This makes sense because you might want a readily editable tiddler that is really an overwritten shadow but you don't want the

[twdev] Draft mechanism - how to test tiddler has a draft but is not the draft itself?

Folks, When a tiddler is being edited you can add to your filter `!has[draft.of]` so your list does not include tiddlers in draft mode. I am looking for a method to do the following - I do not want to list the original tiddler name when a draft exists - the result would be a list of

[twdev] Plugin Packaging Question

Folks, I build a lot of macros I do not publish as plugins yet, However eventually I will publish a library. Because of this I create tiddlers of the form $:/PSaT/*projectname* and tiddlers below that. I hope to automate the movement of a project into a plugin, so this is an important

[twdev] A Little Github help please

Folks, I have mastered the mechanism to submit changes to tiddlywiki.com because of the pink bar Can you help us improve this documentation? Find out how to edit this tiddler on GitHub Contributing to the core on some fairly

Re: [twdev] Re: Caret position - Take 2

Mat and Saq, I love where this is going and the design principals of generalisation. This sound like a future core component or plugin, if not a configurable one. I stand ready for testing or any other way I can help, including harvesting content for the insertions. Just give me sufficient

[twdev] Re: Active Tiddler Tools RFC

Folks, I am starting to side with active tiddler as target is too "aggressive". As in the demo the fields tab shows, interacting with the "active" tiddler has a lot of possibilities. The Side Editor, status setting and other controls could be provided for the active tiddler in the side bar.

Re: [twdev] Re: Caret position - Take 2

I also recommend to look through the wikitext changes in the popup Tiddler, so you understand what changes were made and why. On Thu, 9 Jul 2020, 19:13 Mat, wrote: > between <$edit> and > > > Aha, thanks. The docs explicitly > states "The content of

[twdev] Re: Caret position - Take 2

> between <$edit> and Aha, thanks. The docs explicitly states "The content of the <$edit-text> widget is ignored." but maybe this refers to something else. My suggestion is to first test this demo robustly. > Gotcha. I'll pass it through hell.

[twdev] Re: Caret position - Take 2

Hi Mat, > > >> Secondly: If we move the reveal for the popup in *$:/core/ui/* >> *EditTemplate/body/editor*, inside of the closing tag, it would >> allow editor toolbar commands to work when included in the popup. Nice >> bonus. >> > > huh? Is that some super trick or is it an established

[twdev] Re: Active Tiddler Tools RFC

On Thursday, July 9, 2020 at 2:24:36 AM UTC-7, Mat wrote: > > I think "Active tiddler" makes sense and I believe rhymes well with what > :active in CSS means. > "Active tiddler" was my first suggestion. I only added "Current tiddler" as another alternative. I still like "Active tiddler" as my