I use a different workflow, in each of my plugin folders I have a build 
directory, this include a 'demo edition' that I use for testing, so any 
tiddlers I need for development can be include there. See 
https://github.com/buggyj/TW5-taglist/build
You could copy theses files,
modify
build/demo/tiddlywiki.info 
and change the 'plugin' entry to your plugin name 

put your tiddlers in
build/demo/tiddlers

to build I do
cd plugins/buggyj/TW5-taglist/build
./bld.sh
the result is at
plugins/jermolene.github.com/demo.html

best of luck!

BJ
On Sunday, June 8, 2014 5:52:44 PM UTC+2, Danielo Rodríguez wrote:
>
> Hello BJ
>
> The problem with that workflow is that I can't test the plugin while 
> developing.
> My plugins usually includes a lot of wikitext that I need tho test it out. 
> Maybe some people can just write the whole thing and then try it out but I 
> need to use the preview most of the time for the plugins that includes 
> wikitext.
>
> How do you work with it?
>
> El domingo, 8 de junio de 2014 13:18:17 UTC+2, BJ escribió:
>>
>> Hi Danielo,
>> if you are working on your plugin "encryptWidget" then the most simplest 
>> way to work is to include your files in 
>> /wikifolder/plugins/danielo/encryptWidget/,
>> then add    
>>
>>  "plugins": [
>>         "danielo/encryptWidget",
>>
>> into the  tiddlywiki.info file within editions/tw5.com
>>
>> then use ./qbld.sh to build the tiddlywiki
>>
>> Once you get used to developing using node.js I think you will find that 
>> it is much easier to develop you code this way,  
>>
>> all the best
>>
>> BJ  
>> On Sunday, June 8, 2014 12:49:22 PM UTC+2, Danielo Rodríguez wrote:
>>>
>>> Hello Mario,
>>>
>>> Thank you for your fast response.
>>> I just discovered a very cool thing about this.
>>>
>>> If I put single javascript files inside the plugin directory tiddlywiki 
>>> will create a proper tiddler based on the information you provide in the 
>>> header. So, for example a javascript file with this header:
>>>
>>> /*\ title: $:/plugins/danielo/encryptWidget/encryptWidget.js type: 
>>> application/javascript module-type: widget Test of javascript \*/
>>>
>>> Will be inserted into a tiddler with the appropiate type, title and 
>>> module fields. I wanted this since I started programming widgets for TW. I 
>>> thought many times about why js tiddlers include that header but I never 
>>> experimented with it. I have to admit that I'm amazed. 
>>>
>>> About the link you posted, I will read it a bit more carefully, but it 
>>> does't seems to be very different from the git configuration.
>>>
>>> El domingo, 8 de junio de 2014 12:31:31 UTC+2, PMario escribió:
>>>>
>>>> IMO there is no easy workflow at the moment. 
>>>> Once this issue is resolved: 
>>>> https://github.com/Jermolene/TiddlyWiki5/issues/531 it should be easy 
>>>> to do what you want.
>>>>
>>>> IMO ... You should _not_ avoid the github workflow. ... I'm pretty sure 
>>>> you will run into a lot of problems, just because of that.
>>>>
>>>> have fun!
>>>> mario
>>>>
>>>

-- 
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.

Reply via email to