Hi Jeremy, I will try to change the twexe behaviour to default to the current tiddler if no arguments are supplied and write a viewtemplate as you have suggested,
Thanks for the input, James. On Thursday, 27 March 2014 09:35:42 UTC, Jeremy Ruston wrote: > > Hi James > > > I was thinking of creating a custom dropzone which could catch specific > file extensions and create correctly formatted tiddlers for use with twexe. > This would be a case of customizing the dropzone widget and navigator.js > right? > > Better might be to extend the import infrastructure so that pluggable > filters can be applied to incoming tiddlers. We need something like that to > massage TWC wikitext tiddlers as they are imported. > > > Also while i have your attention, if I specify a tiddler's type field as > twexe how could i go about creating a custom renderer for it? (I was > thinking if it was displayed in the story river rendering the button > associated with it would be more useful than just having the text) > > I'm not sure that the type field is the right way to do this. The type > field is intended to convey the content type needed to parse the content; > it's not intended to convey semantics - that's why we end up with the > module-type field, for instance. > > Better might just be to adopt a standard tag for your twexe tiddlers, and > then add a segment to the viewtemplate that displays the TWExe widget for > tiddlers that have that tag. > > For example, if the tag were "executable", then you'd create a tiddler > called "$:/plugins/welford/twexe/viewtemplate" with the tag > "$:/tags/ViewTemplate", and the following content: > > <$list filter="[is[current]tag[executable]]" variable="listItem"> > <$twexe/> > </$list> > > (Assuming the twexe widget defaults to the current tiddler if the > "tiddler" attribute isn't provided). > > Best wishes > > Jeremy. > > > On Wed, Mar 26, 2014 at 10:36 PM, James Anderson > <[email protected]<javascript:> > > wrote: > >> James Anderson would be fine. >> >> I was thinking of creating a custom dropzone which could catch specific >> file extensions and create correctly formatted tiddlers for use with twexe. >> This would be a case of customizing the dropzone widget and navigator.js >> right? >> >> Also while i have your attention, if I specify a tiddler's type field as >> twexe how could i go about creating a custom renderer for it? (I was >> thinking if it was displayed in the story river rendering the button >> associated with it would be more useful than just having the text) >> >> Thanks, >> >> James >> >> On Thursday, 27 March 2014 06:25:43 UTC+9, Jeremy Ruston wrote: >> >>> Hi James >>> >>> Thank you for contributing this. Very useful for sysops, amongst others. >>> >>> I'd like to add a link to tw.com - would you prefer to be creditted as >>> James Anderson? >>> >>> Best wishes >>> >>> Jeremy >>> >>> >>> >>> On Tue, Mar 25, 2014 at 11:03 PM, James Anderson >>> <[email protected]>wrote: >>> >>>> I have started writing a plugin primarily aimed at an offline >>>> Tiddlywiki running under HTA. The source is here: https://github.com/ >>>> welford/twexe >>>> >>>> The basic widget syntax is: >>>> <$twexe file="c:/some_batch_or_exe.bat" comment="a basic explanation >>>> of the functionality">Click Me</$twexe> >>>> >>>> This will create a button named "Click Me" that when clicked runs the >>>> executable specified by file, and when hovered over displays the comment >>>> parameter. >>>> >>>> You can also specify a twexe indirectly via a tiddler: >>>> <$twexe tiddler="tiddler_name"/> >>>> >>>> in this case the file parameter is the tiddler's "twexe_target" field, >>>> the comment comes from the tiddler text and the button name from the >>>> tiddler's name. >>>> >>>> When you right click on the button you are given the options to: >>>> >>>> 1. open the file in it's folder using windows explorer >>>> 2. copy the file parameter to the clipboard >>>> 3. open the defining tiddler in TW (if applicable) >>>> >>>> I maybe plan to add file extension specific actions in the future, and >>>> I have written some very rough notes on the experience of creating a >>>> widget >>>> here: http://welford.github.io/ These will get updated and cleaned up >>>> as continue development, the contain some info i couldn't easily find >>>> elsewhere. >>>> >>>> Any suggestions are appreciated. >>>> >>>> James >>>> >>>> -- >>>> 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 [email protected]. >>>> To post to this group, send email to [email protected]. >>>> >>>> Visit this group at http://groups.google.com/group/tiddlywikidev. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Jeremy Ruston >>> mailto:[email protected] >>> >> > > > -- > Jeremy Ruston > mailto:[email protected] <javascript:> > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
