Thanks. I'll do... 
https://groups.google.com/forum/?hl=en#!topic/tiddlywikidev/xlcJpCUzJJk

понеділок, 21 жовтня 2019 р. 00:46:51 UTC+3 користувач TonyM написав:
>
> Olegh
>
> This looks like a valuable contribution. Consider posting in the 
> https://groups.google.com/forum/?hl=en#!forum/tiddlywikidev group as that 
> is more oriented to development of tiddlywiki and its features over simply 
> using it.
>
> I would help more but my knowledge of GitHub is insufficient at this point 
> in time. 
>
> Thanks for your contributions
>
> Regards
> Tony
>
>
>
> On Monday, October 21, 2019 at 5:45:55 AM UTC+11, oleghbond wrote:
>>
>> I've just issued the second version of *TW farm* (
>> https://github.com/protw/twfarm). It is re-written completely in JS for 
>> node instead of Octave. So, now it looks more natural in the TW environment.
>>
>> Now I have got an ambition to include *TW Farm* method into BobEXE as a 
>> plugin. I'm not a programmer and not familiar with the TW programming 
>> environment at all. 
>>
>> That is why I'm looking for TW experts interested in raising this task. 
>> Any ideas and suggestions are appreciated.
>>
>> Olegh Bondarenko
>> https://bit.ly/oleghbond
>>
>> неділя, 18 серпня 2019 р. 21:42:19 UTC+3 користувач oleghbond написав:
>>>
>>> *TW5 Farm* is a method of centralized multi-wiki support on the 
>>> Internet.
>>>
>>> Conceptually, technology comprises the following phases:
>>>    
>>>    - Preparing a separate wiki by means of Tiddlywiki 
>>>    <https://tiddlywiki.com/> by a group of authors on their own local 
>>>    computers.
>>>    - When creating the content, the authors synchronize the wiki folder 
>>>    through the Google Drive <https://drive.google.com/> cloud.
>>>    - For each wiki, the editor pre-creates a wiki repository on Github 
>>>    <https://github.com/>, from which then the wiki is published on the 
>>>    Internet using Github Pages <https://pages.github.com/>.
>>>
>>> *An excellent feature of the TW5 Farm technology is the function of 
>>> automated collection of information on all wikis included in the collection 
>>> and presentation in a separate central wiki.* The central wiki for this 
>>> collection called *Project Hub* is located at https://protw.github.io/.
>>>
>>>
>>> To provide this feature, each wiki contains a standardized $:/boa/logo 
>>> tiddler 
>>> (as a separate article is referred *Tiddlywiki*), which contains the 
>>> information needed to represent the wiki outside.
>>>
>>> The core of the technology is the tw_builder.m script, written by means 
>>> of a high-level programming language - *Octave*. The editor runs this 
>>> script on own computer. The script updates the wiki information in the 
>>> *Github* repository, updates the wiki collection information, prepares 
>>> and executes the process of publishing on the Internet.
>>>
>>>
>>> The script code, additional resources, and description of the technology 
>>> are available at https://github.com/protw/twfarm. The technology 
>>> description wiki is available at https://protw.github.io/twfarm.
>>>
>>>
>>> For a full-fledged work, the author must be able to write texts using 
>>> *Tiddlywiki* and also install on own computer:
>>>
>>>    - a local server for multiple wikis on *Tiddlywiki* - OokTech / 
>>>    TW5-BobEXE <https://github.com/OokTech/TW5-BobEXE>;
>>>    - Google application Backup and sync 
>>>    <https://www.google.com/drive/download/backup-and-sync/>.
>>>
>>> The editor in order to run the tw_builder.m script, in addition to the 
>>> above list, has to install on own computer Octave sofware 
>>> <https://www.gnu.org/software/octave/> and the function library 
>>> fangq/jsonlab <https://github.com/fangq/jsonlab> to process *JSON* data.
>>>
>>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1423e0ea-56bc-47c3-aae2-8cd064f00a57%40googlegroups.com.

Reply via email to