Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hi Jeremy

On Tue, Jul 3, 2018 at 11:26 AM Yakov > 
> wrote:
>
>> By the way, does anybody know how to build TiddlySaver from its source? I 
>> can't see any docs besides the sign.readme 
>>  
>> and verify.readme 
>>  
>> which are for later stages of the process. Also I wonder if there's a way 
>> to get TiddlySaver version (if there's any versioning at all) since I'm not 
>> even sure whether the latest version is packed in the download archive on 
>> classic.tiddlywiki.com Any ideas?
>>
>
> I think it's just a matter of compiling the source at 
> https://github.com/TiddlyWiki/TiddlyWiki/blob/master/java/src/TiddlySaver.java
>  
> into TiddlySaver.jar, and then signing it as described in the file.
>
> Back in the day, BiDiX used to do the builds on UnaMesa's behalf, and had 
> the necessary signing keys. I can try to put you in touch?
>
> That would be nice. The time to explore TiddlySaver in deep has not quite 
come (I'd like to finish the work on debugging upgrading first, see the 
other thread 
), but 
contacting BidiX would be nice (as far as I can remember I've tried to 
write to him once, to BidiX at bidix.info, and mail delivery system 
responded "can not be delivered" and bidix.info is down these days, only 
the old bidix.tiddlyspot.com is up) as well as getting more info about 
building TiddlySaver.

Best regards,
Yakov.
 

> Best wishes
>
> Jeremy.
>  
>
>>
>> вторник, 3 июля 2018 г., 13:21:26 UTC+3 пользователь Yakov написал:
>>>
>>> Hello Okido, sorry for the delay,
>>>
>>> yeah, you are right, surprisingly there's 2 types of shadows: those 
>>> stored in shadowArea (ColorPalette, EditTemplate, GettingStarted, 
>>> ImportTiddlers, MarkupPreHead, OptionsPanel, PageTemplate, 
>>> StyleSheetColors, StyleSheetLayout, StyleSheetLocale, StyleSheetPrint, 
>>> ViewTemplate) and those merged to config.shadowTiddlers by JavaScript (line 
>>> 1209 and below: DefaultTiddlers, MainMenu, SiteTitle, SiteSubtitle, 
>>> SiteUrl, SideBarOptions, SideBarTabs, TabMore). Not sure what's the main 
>>> difference (I'd guess that the first ones should be loaded quicker but 
>>> since GettingStarted is in the first group while DefaultTiddlers is in the 
>>> second, I'm not really sure).
>>>
>>> It is most likely the first group is "cooked" as html (hence  and 
>>> ) via the .externalizeTiddler method ( 
>>> https://github.com/TiddlyWiki/TiddlyWiki/blob/master/js/TW21Saver.js#L9 
>>> ). I'm afraid I can't provide much more details without diving into TW5 
>>> code: the building script for index.html is just one line
>>>
>>> node %TIDDLYWIKI5_DIR%/tiddlywiki.js ./wiki --verbose --load 
>>> ./index.html.recipe --rendertiddler 
>>> $:/core/templates/tiddlywiki2.template.html %TIDDLYWIKI_DEST%/index.html 
>>> text/plain
>>>
>>> although building empty.html is done in a stranger manner: it is build 
>>> from index.html (TW with content for classic.tiddlywiki.com):
>>>
>>> echo BUILD: creating EMPTY.HTML and INDEX.XML from INDEX.HTML
>>> %BROWSER% phantom_driver.js
>>>
>>> Best regards,
>>> Yakov.
>>>
>>> четверг, 21 июня 2018 г., 12:54:17 UTC+3 пользователь okido написал:

 Hello Yakov,

 When I use the file 
 https://github.com/YakovL/tiddlywiki/blob/YLTW/shadows/GettingStarted.tid 
 it contains a macro call: <>
 Code:
 title: GettingStarted

 To get started with this blank [[TiddlyWiki]], you'll need to modify 
 the following tiddlers: 
 * [[SiteTitle]] & [[SiteSubtitle]]: The title and subtitle of the site, 
 as shown above (after saving, they will also appear in the browser title 
 bar) 
 * [[MainMenu]]: The menu (usually on the left) 
 * [[DefaultTiddlers]]: Contains the names of the tiddlers that you want 
 to appear when the TiddlyWiki is opened 
 You'll also need to enter your username for signing your edits: 
 <>

 When I look up this code in your build that is here: 
 https://groups.google.com/forum/#!topic/tiddlywikiclassic/4xiDlSbiY9c 
 the code is inserted at line 117 and looks like this:

 
 
 To get started with this blank [[TiddlyWiki]], you'll need to 
 modify the following tiddlers:
 * [[SiteTitle]]  [[SiteSubtitle]]: The title and subtitle of the 
 site, as shown above (after saving, they will also appear in the browser 
 title bar)
 * [[MainMenu]]: The menu (usually on the left)
 * [[DefaultTiddlers]]: Contains the names of the tiddlers that you want 
 to appear when the TiddlyWiki is opened
 You'll also need to enter your username for signing your edits: 
 option txtUserName
 
 



 As you can see the macro changed from <> to 
 option txtUserName this is no problem as it executes 
 properly.
 The issue is that when I 

Re: [twdev] Build Process for TiddlyWiki Classic

[Jeremy Ruston]

Hi Yakov
On Tue, Jul 3, 2018 at 11:26 AM Yakov 
wrote:

> By the way, does anybody know how to build TiddlySaver from its source? I
> can't see any docs besides the sign.readme
> 
> and verify.readme
> 
> which are for later stages of the process. Also I wonder if there's a way
> to get TiddlySaver version (if there's any versioning at all) since I'm not
> even sure whether the latest version is packed in the download archive on
> classic.tiddlywiki.com Any ideas?
>

I think it's just a matter of compiling the source at
https://github.com/TiddlyWiki/TiddlyWiki/blob/master/java/src/TiddlySaver.java
into TiddlySaver.jar, and then signing it as described in the file.

Back in the day, BiDiX used to do the builds on UnaMesa's behalf, and had
the necessary signing keys. I can try to put you in touch?

Best wishes

Jeremy.


>
> вторник, 3 июля 2018 г., 13:21:26 UTC+3 пользователь Yakov написал:
>>
>> Hello Okido, sorry for the delay,
>>
>> yeah, you are right, surprisingly there's 2 types of shadows: those
>> stored in shadowArea (ColorPalette, EditTemplate, GettingStarted,
>> ImportTiddlers, MarkupPreHead, OptionsPanel, PageTemplate,
>> StyleSheetColors, StyleSheetLayout, StyleSheetLocale, StyleSheetPrint,
>> ViewTemplate) and those merged to config.shadowTiddlers by JavaScript (line
>> 1209 and below: DefaultTiddlers, MainMenu, SiteTitle, SiteSubtitle,
>> SiteUrl, SideBarOptions, SideBarTabs, TabMore). Not sure what's the main
>> difference (I'd guess that the first ones should be loaded quicker but
>> since GettingStarted is in the first group while DefaultTiddlers is in the
>> second, I'm not really sure).
>>
>> It is most likely the first group is "cooked" as html (hence  and
>> ) via the .externalizeTiddler method (
>> https://github.com/TiddlyWiki/TiddlyWiki/blob/master/js/TW21Saver.js#L9
>> ). I'm afraid I can't provide much more details without diving into TW5
>> code: the building script for index.html is just one line
>>
>> node %TIDDLYWIKI5_DIR%/tiddlywiki.js ./wiki --verbose --load
>> ./index.html.recipe --rendertiddler
>> $:/core/templates/tiddlywiki2.template.html %TIDDLYWIKI_DEST%/index.html
>> text/plain
>>
>> although building empty.html is done in a stranger manner: it is build
>> from index.html (TW with content for classic.tiddlywiki.com):
>>
>> echo BUILD: creating EMPTY.HTML and INDEX.XML from INDEX.HTML
>> %BROWSER% phantom_driver.js
>>
>> Best regards,
>> Yakov.
>>
>> четверг, 21 июня 2018 г., 12:54:17 UTC+3 пользователь okido написал:
>>>
>>> Hello Yakov,
>>>
>>> When I use the file
>>> https://github.com/YakovL/tiddlywiki/blob/YLTW/shadows/GettingStarted.tid
>>> it contains a macro call: <>
>>> Code:
>>> title: GettingStarted
>>>
>>> To get started with this blank [[TiddlyWiki]], you'll need to modify the
>>> following tiddlers:
>>> * [[SiteTitle]] & [[SiteSubtitle]]: The title and subtitle of the site,
>>> as shown above (after saving, they will also appear in the browser title
>>> bar)
>>> * [[MainMenu]]: The menu (usually on the left)
>>> * [[DefaultTiddlers]]: Contains the names of the tiddlers that you want
>>> to appear when the TiddlyWiki is opened
>>> You'll also need to enter your username for signing your edits: <>> txtUserName>>
>>>
>>> When I look up this code in your build that is here:
>>> https://groups.google.com/forum/#!topic/tiddlywikiclassic/4xiDlSbiY9c
>>> the code is inserted at line 117 and looks like this:
>>>
>>> 
>>> 
>>> To get started with this blank [[TiddlyWiki]], you'll need to
>>> modify the following tiddlers:
>>> * [[SiteTitle]]  [[SiteSubtitle]]: The title and subtitle of the
>>> site, as shown above (after saving, they will also appear in the browser
>>> title bar)
>>> * [[MainMenu]]: The menu (usually on the left)
>>> * [[DefaultTiddlers]]: Contains the names of the tiddlers that you want
>>> to appear when the TiddlyWiki is opened
>>> You'll also need to enter your username for signing your edits: 
>>> option
>>> txtUserName
>>> 
>>> 
>>>
>>>
>>>
>>> As you can see the macro changed from <> to
>>> option txtUserName this is no problem as it executes
>>> properly.
>>> The issue is that when I build from the code that contains << and >> I
>>> need to replace the << >> by   etc else it renders
>>> incorrect, it becomes <>;\n.
>>> It only is happening with the shadow tiddlers.
>>> Hence my question if your build script replaces the << >>  to html
>>> entity names.
>>>
>>> I hope this makes it clear.
>>>
>>>
>>> Have a nice day, Okido
>>>
>>> --
> 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.

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

By the way, does anybody know how to build TiddlySaver from its source? I 
can't see any docs besides the sign.readme 
 and 
verify.readme 
 
which are for later stages of the process. Also I wonder if there's a way 
to get TiddlySaver version (if there's any versioning at all) since I'm not 
even sure whether the latest version is packed in the download archive on 
classic.tiddlywiki.com Any ideas?

вторник, 3 июля 2018 г., 13:21:26 UTC+3 пользователь Yakov написал:
>
> Hello Okido, sorry for the delay,
>
> yeah, you are right, surprisingly there's 2 types of shadows: those stored 
> in shadowArea (ColorPalette, EditTemplate, GettingStarted, ImportTiddlers, 
> MarkupPreHead, OptionsPanel, PageTemplate, StyleSheetColors, 
> StyleSheetLayout, StyleSheetLocale, StyleSheetPrint, ViewTemplate) and 
> those merged to config.shadowTiddlers by JavaScript (line 1209 and below: 
> DefaultTiddlers, MainMenu, SiteTitle, SiteSubtitle, SiteUrl, 
> SideBarOptions, SideBarTabs, TabMore). Not sure what's the main difference 
> (I'd guess that the first ones should be loaded quicker but since 
> GettingStarted is in the first group while DefaultTiddlers is in the 
> second, I'm not really sure).
>
> It is most likely the first group is "cooked" as html (hence  and 
> ) via the .externalizeTiddler method ( 
> https://github.com/TiddlyWiki/TiddlyWiki/blob/master/js/TW21Saver.js#L9 
> ). I'm afraid I can't provide much more details without diving into TW5 
> code: the building script for index.html is just one line
>
> node %TIDDLYWIKI5_DIR%/tiddlywiki.js ./wiki --verbose --load 
> ./index.html.recipe --rendertiddler 
> $:/core/templates/tiddlywiki2.template.html %TIDDLYWIKI_DEST%/index.html 
> text/plain
>
> although building empty.html is done in a stranger manner: it is build 
> from index.html (TW with content for classic.tiddlywiki.com):
>
> echo BUILD: creating EMPTY.HTML and INDEX.XML from INDEX.HTML
> %BROWSER% phantom_driver.js
>
> Best regards,
> Yakov.
>
> четверг, 21 июня 2018 г., 12:54:17 UTC+3 пользователь okido написал:
>>
>> Hello Yakov,
>>
>> When I use the file 
>> https://github.com/YakovL/tiddlywiki/blob/YLTW/shadows/GettingStarted.tid 
>> it contains a macro call: <>
>> Code:
>> title: GettingStarted
>>
>> To get started with this blank [[TiddlyWiki]], you'll need to modify the 
>> following tiddlers: 
>> * [[SiteTitle]] & [[SiteSubtitle]]: The title and subtitle of the site, 
>> as shown above (after saving, they will also appear in the browser title 
>> bar) 
>> * [[MainMenu]]: The menu (usually on the left) 
>> * [[DefaultTiddlers]]: Contains the names of the tiddlers that you want 
>> to appear when the TiddlyWiki is opened 
>> You'll also need to enter your username for signing your edits: <> txtUserName>>
>>
>> When I look up this code in your build that is here: 
>> https://groups.google.com/forum/#!topic/tiddlywikiclassic/4xiDlSbiY9c 
>> the code is inserted at line 117 and looks like this:
>>
>> 
>> 
>> To get started with this blank [[TiddlyWiki]], you'll need to 
>> modify the following tiddlers:
>> * [[SiteTitle]]  [[SiteSubtitle]]: The title and subtitle of the 
>> site, as shown above (after saving, they will also appear in the browser 
>> title bar)
>> * [[MainMenu]]: The menu (usually on the left)
>> * [[DefaultTiddlers]]: Contains the names of the tiddlers that you want 
>> to appear when the TiddlyWiki is opened
>> You'll also need to enter your username for signing your edits: 
>> option 
>> txtUserName
>> 
>> 
>>
>>
>>
>> As you can see the macro changed from <> to 
>> option txtUserName this is no problem as it executes 
>> properly.
>> The issue is that when I build from the code that contains << and >> I 
>> need to replace the << >> by   etc else it renders 
>> incorrect, it becomes <>;\n.
>> It only is happening with the shadow tiddlers.
>> Hence my question if your build script replaces the << >>  to html entity 
>> names.
>>
>> I hope this makes it clear.
>>
>>
>> Have a nice day, Okido
>>
>>

-- 
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/ab5b29b3-53c4-46f1-80a3-1e318ae6d912%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hello Okido, sorry for the delay,

yeah, you are right, surprisingly there's 2 types of shadows: those stored 
in shadowArea (ColorPalette, EditTemplate, GettingStarted, ImportTiddlers, 
MarkupPreHead, OptionsPanel, PageTemplate, StyleSheetColors, 
StyleSheetLayout, StyleSheetLocale, StyleSheetPrint, ViewTemplate) and 
those merged to config.shadowTiddlers by JavaScript (line 1209 and below: 
DefaultTiddlers, MainMenu, SiteTitle, SiteSubtitle, SiteUrl, 
SideBarOptions, SideBarTabs, TabMore). Not sure what's the main difference 
(I'd guess that the first ones should be loaded quicker but since 
GettingStarted is in the first group while DefaultTiddlers is in the 
second, I'm not really sure).

It is most likely the first group is "cooked" as html (hence  and ) 
via the .externalizeTiddler method ( 
https://github.com/TiddlyWiki/TiddlyWiki/blob/master/js/TW21Saver.js#L9 ). 
I'm afraid I can't provide much more details without diving into TW5 code: 
the building script for index.html is just one line

node %TIDDLYWIKI5_DIR%/tiddlywiki.js ./wiki --verbose --load 
./index.html.recipe --rendertiddler 
$:/core/templates/tiddlywiki2.template.html %TIDDLYWIKI_DEST%/index.html 
text/plain

although building empty.html is done in a stranger manner: it is build from 
index.html (TW with content for classic.tiddlywiki.com):

echo BUILD: creating EMPTY.HTML and INDEX.XML from INDEX.HTML
%BROWSER% phantom_driver.js

Best regards,
Yakov.

четверг, 21 июня 2018 г., 12:54:17 UTC+3 пользователь okido написал:
>
> Hello Yakov,
>
> When I use the file 
> https://github.com/YakovL/tiddlywiki/blob/YLTW/shadows/GettingStarted.tid 
> it contains a macro call: <>
> Code:
> title: GettingStarted
>
> To get started with this blank [[TiddlyWiki]], you'll need to modify the 
> following tiddlers: 
> * [[SiteTitle]] & [[SiteSubtitle]]: The title and subtitle of the site, as 
> shown above (after saving, they will also appear in the browser title bar) 
> * [[MainMenu]]: The menu (usually on the left) 
> * [[DefaultTiddlers]]: Contains the names of the tiddlers that you want to 
> appear when the TiddlyWiki is opened 
> You'll also need to enter your username for signing your edits: < txtUserName>>
>
> When I look up this code in your build that is here: 
> https://groups.google.com/forum/#!topic/tiddlywikiclassic/4xiDlSbiY9c the 
> code is inserted at line 117 and looks like this:
>
> 
> 
> To get started with this blank [[TiddlyWiki]], you'll need to modify 
> the following tiddlers:
> * [[SiteTitle]]  [[SiteSubtitle]]: The title and subtitle of the 
> site, as shown above (after saving, they will also appear in the browser 
> title bar)
> * [[MainMenu]]: The menu (usually on the left)
> * [[DefaultTiddlers]]: Contains the names of the tiddlers that you want to 
> appear when the TiddlyWiki is opened
> You'll also need to enter your username for signing your edits: 
> option 
> txtUserName
> 
> 
>
>
>
> As you can see the macro changed from <> to 
> option txtUserName this is no problem as it executes 
> properly.
> The issue is that when I build from the code that contains << and >> I 
> need to replace the << >> by   etc else it renders 
> incorrect, it becomes <>;\n.
> It only is happening with the shadow tiddlers.
> Hence my question if your build script replaces the << >>  to html entity 
> names.
>
> I hope this makes it clear.
>
>
> Have a nice day, Okido
>
>

-- 
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/898ec3b0-2d36-4305-ba9f-4243b646bb01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[okido]

Hello Yakov,

When I use the file 
https://github.com/YakovL/tiddlywiki/blob/YLTW/shadows/GettingStarted.tid 
it contains a macro call: <>
Code:
title: GettingStarted

To get started with this blank [[TiddlyWiki]], you'll need to modify the 
following tiddlers: 
* [[SiteTitle]] & [[SiteSubtitle]]: The title and subtitle of the site, as 
shown above (after saving, they will also appear in the browser title bar) 
* [[MainMenu]]: The menu (usually on the left) 
* [[DefaultTiddlers]]: Contains the names of the tiddlers that you want to 
appear when the TiddlyWiki is opened 
You'll also need to enter your username for signing your edits: <>

When I look up this code in your build that is here: 
https://groups.google.com/forum/#!topic/tiddlywikiclassic/4xiDlSbiY9c the 
code is inserted at line 117 and looks like this:



To get started with this blank [[TiddlyWiki]], you'll need to modify 
the following tiddlers:
* [[SiteTitle]]  [[SiteSubtitle]]: The title and subtitle of the site, 
as shown above (after saving, they will also appear in the browser title 
bar)
* [[MainMenu]]: The menu (usually on the left)
* [[DefaultTiddlers]]: Contains the names of the tiddlers that you want to 
appear when the TiddlyWiki is opened
You'll also need to enter your username for signing your edits: option 
txtUserName





As you can see the macro changed from <> to 
option txtUserName this is no problem as it executes 
properly.
The issue is that when I build from the code that contains << and >> I need 
to replace the << >> by   etc else it renders incorrect, it 
becomes <>;\n.
It only is happening with the shadow tiddlers.
Hence my question if your build script replaces the << >>  to html entity 
names.

I hope this makes it clear.


Have a nice day, Okido

-- 
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/d48c8c51-f486-4461-a436-d21fb84c160c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hi Okido,

could you specify links to and parts of files which refer to? I mean, I've 
opened empty.html that I've built, found merge(config.shadowTiddlers,{ 
(line 1209) and SideBarTabs in it (line 1216) and there are "<", not "".

Actually, I haven't dived into the building scripts, they just worked and I 
thought "right, the building process works normally, now let's update the 
other parts of infrastructure (like tests and TWc site)".

But new lightweight scripts with documented internals are surely welcome.

Best regards,
Yakov.

среда, 20 июня 2018 г., 17:25:30 UTC+3 пользователь okido написал:
>
> Hi Yakov,
>
> I used the master from https://github.com/YakovL/tiddlywiki to build a 
> TWc and compared it with your published TWc 2.9.1.
> In the master the shadow tiddlers contain << and >>, in your build these 
> are replaced by  etc.
> Do you replace << by  in your build process ?
>
> Have a nice day, Okido
>

-- 
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/381b92fc-9ab6-4106-9240-29be5a6abf7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[okido]

Hi Yakov,

I used the master from https://github.com/YakovL/tiddlywiki to build a TWc 
and compared it with your published TWc 2.9.1.
In the master the shadow tiddlers contain << and >>, in your build these 
are replaced by  etc.
Do you replace << by  in your build process ?

Have a nice day, Okido

-- 
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/40451ffe-292b-4506-88b9-1c5c7ee30325%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[okido]

Hi Yakov,

I can only build an empty html TWc with a node script that retrieves the 
files, concate them and replaces the place holders in the template, no 
testing is done other than loading the TWc in a browser.
I am going to clean up the code a litle and will pass it on.

Have a nice day, Okido


Op woensdag 21 maart 2018 11:17:56 UTC+1 schreef Yakov:
>
> Hi okido,
>
> do you mean you use some custom script for building TW? Can you share it?
>
> Actually, now the building process using TW5 works well for me, although 
> the
>
> BUILD: creating EMPTY.HTML and INDEX.XML from INDEX.HTML
>
> stage works slower than I'd like it to.
>
> Do you have any problems with the current description 
>  of the building process? 
> I've updated it considerably although that was mostly about the structure 
> of the docs and I'm planning to update building details as well at some 
> point. Any feedback here is appreciated.
>
> Best regards,
> Yakov.
>
> четверг, 1 марта 2018 г., 16:01:34 UTC+3 пользователь okido написал:
>>
>> Hi Yakov,
>>
>> I used the github repo to build a fresh TWc, I just glued all files 
>> together with some node scripts.
>> The final TWc fails at one point, in Saving.js at line 126 there is a 
>> lost  tag that crashes the TWc when loaded.
>>
>> 125 content=content.replace(/savetest<\/div>/,'> id="saveTest">'); 
>> 126 //# clear  following , please use < / script >
>> 127 content=content.replace(/script>]*><\/applet>/g,'script>'
>> );
>>
>> Have a nice day, Okido
>>
>> Op zondag 28 januari 2018 21:15:50 UTC+1 schreef Yakov:
>>>
>>> Hi Jeremy,
>>>
>>> Terrific progress, well done!

 :D thanks for words of encouragement! I myself understand that for 
>>> end-users there's no progress at all for now, but these steps are necessary 
>>> and, in a way, are valuable experience.
>>>
>>> The tiddlywiki.github.com repo is for storing the output of the build 
 process; the files within it are exposed to the web as 
 https://classic.tiddlywiki.com. There shouldn't be anything in that 
 repo that was not generated by the build process.

 [...]

 Those .tid files were obtained from a backup of 
 tiddlywiki.tiddlyspace.com that I took before it shut down.

 To make further content changes you'd manually edit those .tid files, 
 recommit them to the TiddlyWiki/TiddlyWiki repo, and then re-run the build 
 process to regenerate tiddlywiki.github.com.

 Right, I see. Yet, I wonder if TW5 is also capable of "exploding" a TWc 
>>> into those .tid files: it would be a nicer workflow if I could edit content 
>>> in an ordinary TW and then explode + cook new index.html. Is there 
>>> currently such a feature?
>>>
>>> Best regards,
>>> Yakov.
>>>  
>>>
 Best wishes

 Jeremy.


 Best regards,
 Yakov.

 четверг, 25 января 2018 г., 1:31:16 UTC+3 пользователь Yakov написал:
>
> So, regarding classic.tiddlywiki.com..
>
> Is it correct that editing it can be done by just (forking and) 
> cloning the [1] repo and editing TW in a browser? (and pushing back to 
> fork 
> and merging) I mean are recipes at [2] outdated since TiddlySpace is down 
> (so [2] now has nothing to do with [1] and classic.tiddlywiki.com)?
>
> No, wait, this can't be. First, TW version won't be updated this way 
> (as well as the download package). Second, which is more surprising, for 
> now I have only cloned [2] and still got cooked/2.9.1/index.html with 
> classic.tiddlywiki.com's content in it once I've cooked TW.. is 
> content from [1] accounted at all?
>
> Any suggestions? What's the correct workflow? Yeah, the last change 
> was done back in 2013, so it won't surprise me if nobody remembers...
>
> Best regards,
> Yakov.
>
> [1] https://github.com/TiddlyWiki/tiddlywiki.github.com
> [2] https://github.com/TiddlyWiki/tiddlywiki.com/
>
> среда, 24 января 2018 г., 17:56:27 UTC+3 пользователь PMario написал:
>>
>> On Wednesday, January 24, 2018 at 2:09:11 PM UTC+1, Yakov wrote:
>>>
>>> PS is that correct that the upstream name is purely a convention 
>>> and git doesn't do anything different with regard to it, technically?
>>>
>>
>> Yes ... All aliases are just a convention. ... If you use the same 
>> schema for all your local repos, it helps to minify "user errors" 
>>
>> For me "push origin" means ... I can savely write to it. 
>>
>> "push upstream" means ... Be really carefull ... Messing it up, will 
>> cause a lot of work to fix it!
>>
>> -m
>>
> -- 
 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 tiddlywikide...@googlegroups.com.
 To post to this group, send email to 

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hi okido,

do you mean you use some custom script for building TW? Can you share it?

Actually, now the building process using TW5 works well for me, although the

BUILD: creating EMPTY.HTML and INDEX.XML from INDEX.HTML

stage works slower than I'd like it to.

Do you have any problems with the current description 
 of the building process? 
I've updated it considerably although that was mostly about the structure 
of the docs and I'm planning to update building details as well at some 
point. Any feedback here is appreciated.

Best regards,
Yakov.

четверг, 1 марта 2018 г., 16:01:34 UTC+3 пользователь okido написал:
>
> Hi Yakov,
>
> I used the github repo to build a fresh TWc, I just glued all files 
> together with some node scripts.
> The final TWc fails at one point, in Saving.js at line 126 there is a lost 
>  tag that crashes the TWc when loaded.
>
> 125 content=content.replace(/savetest<\/div>/,' id="saveTest">'); 
> 126 //# clear  following , please use < / script >
> 127 content=content.replace(/script>]*><\/applet>/g,'script>'
> );
>
> Have a nice day, Okido
>
> Op zondag 28 januari 2018 21:15:50 UTC+1 schreef Yakov:
>>
>> Hi Jeremy,
>>
>> Terrific progress, well done!
>>>
>>> :D thanks for words of encouragement! I myself understand that for 
>> end-users there's no progress at all for now, but these steps are necessary 
>> and, in a way, are valuable experience.
>>
>> The tiddlywiki.github.com repo is for storing the output of the build 
>>> process; the files within it are exposed to the web as 
>>> https://classic.tiddlywiki.com. There shouldn't be anything in that 
>>> repo that was not generated by the build process.
>>>
>>> [...]
>>>
>>> Those .tid files were obtained from a backup of 
>>> tiddlywiki.tiddlyspace.com that I took before it shut down.
>>>
>>> To make further content changes you'd manually edit those .tid files, 
>>> recommit them to the TiddlyWiki/TiddlyWiki repo, and then re-run the build 
>>> process to regenerate tiddlywiki.github.com.
>>>
>>> Right, I see. Yet, I wonder if TW5 is also capable of "exploding" a TWc 
>> into those .tid files: it would be a nicer workflow if I could edit content 
>> in an ordinary TW and then explode + cook new index.html. Is there 
>> currently such a feature?
>>
>> Best regards,
>> Yakov.
>>  
>>
>>> Best wishes
>>>
>>> Jeremy.
>>>
>>>
>>> Best regards,
>>> Yakov.
>>>
>>> четверг, 25 января 2018 г., 1:31:16 UTC+3 пользователь Yakov написал:

 So, regarding classic.tiddlywiki.com..

 Is it correct that editing it can be done by just (forking and) cloning 
 the [1] repo and editing TW in a browser? (and pushing back to fork and 
 merging) I mean are recipes at [2] outdated since TiddlySpace is down (so 
 [2] now has nothing to do with [1] and classic.tiddlywiki.com)?

 No, wait, this can't be. First, TW version won't be updated this way 
 (as well as the download package). Second, which is more surprising, for 
 now I have only cloned [2] and still got cooked/2.9.1/index.html with 
 classic.tiddlywiki.com's content in it once I've cooked TW.. is 
 content from [1] accounted at all?

 Any suggestions? What's the correct workflow? Yeah, the last change was 
 done back in 2013, so it won't surprise me if nobody remembers...

 Best regards,
 Yakov.

 [1] https://github.com/TiddlyWiki/tiddlywiki.github.com
 [2] https://github.com/TiddlyWiki/tiddlywiki.com/

 среда, 24 января 2018 г., 17:56:27 UTC+3 пользователь PMario написал:
>
> On Wednesday, January 24, 2018 at 2:09:11 PM UTC+1, Yakov wrote:
>>
>> PS is that correct that the upstream name is purely a convention and 
>> git doesn't do anything different with regard to it, technically?
>>
>
> Yes ... All aliases are just a convention. ... If you use the same 
> schema for all your local repos, it helps to minify "user errors" 
>
> For me "push origin" means ... I can savely write to it. 
>
> "push upstream" means ... Be really carefull ... Messing it up, will 
> cause a lot of work to fix it!
>
> -m
>
 -- 
>>> 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 tiddlywikide...@googlegroups.com.
>>> To post to this group, send email to tiddly...@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/6f29491c-ab84-4b9e-8e89-2058cd6a93b9%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>

-- 
You received this message because 

Re: [twdev] Build Process for TiddlyWiki Classic

[okido]

Hi Yakov,

I used the github repo to build a fresh TWc, I just glued all files 
together with some node scripts.
The final TWc fails at one point, in Saving.js at line 126 there is a lost 
 tag that crashes the TWc when loaded.

125 content=content.replace(/savetest<\/div>/,''); 
126 //# clear  following , please use < / script >
127 content=content.replace(/script>]*><\/applet>/g,'script>');

Have a nice day, Okido

Op zondag 28 januari 2018 21:15:50 UTC+1 schreef Yakov:
>
> Hi Jeremy,
>
> Terrific progress, well done!
>>
>> :D thanks for words of encouragement! I myself understand that for 
> end-users there's no progress at all for now, but these steps are necessary 
> and, in a way, are valuable experience.
>
> The tiddlywiki.github.com repo is for storing the output of the build 
>> process; the files within it are exposed to the web as 
>> https://classic.tiddlywiki.com. There shouldn't be anything in that repo 
>> that was not generated by the build process.
>>
>> [...]
>>
>> Those .tid files were obtained from a backup of 
>> tiddlywiki.tiddlyspace.com that I took before it shut down.
>>
>> To make further content changes you'd manually edit those .tid files, 
>> recommit them to the TiddlyWiki/TiddlyWiki repo, and then re-run the build 
>> process to regenerate tiddlywiki.github.com.
>>
>> Right, I see. Yet, I wonder if TW5 is also capable of "exploding" a TWc 
> into those .tid files: it would be a nicer workflow if I could edit content 
> in an ordinary TW and then explode + cook new index.html. Is there 
> currently such a feature?
>
> Best regards,
> Yakov.
>  
>
>> Best wishes
>>
>> Jeremy.
>>
>>
>> Best regards,
>> Yakov.
>>
>> четверг, 25 января 2018 г., 1:31:16 UTC+3 пользователь Yakov написал:
>>>
>>> So, regarding classic.tiddlywiki.com..
>>>
>>> Is it correct that editing it can be done by just (forking and) cloning 
>>> the [1] repo and editing TW in a browser? (and pushing back to fork and 
>>> merging) I mean are recipes at [2] outdated since TiddlySpace is down (so 
>>> [2] now has nothing to do with [1] and classic.tiddlywiki.com)?
>>>
>>> No, wait, this can't be. First, TW version won't be updated this way (as 
>>> well as the download package). Second, which is more surprising, for now I 
>>> have only cloned [2] and still got cooked/2.9.1/index.html with 
>>> classic.tiddlywiki.com's content in it once I've cooked TW.. is content 
>>> from [1] accounted at all?
>>>
>>> Any suggestions? What's the correct workflow? Yeah, the last change was 
>>> done back in 2013, so it won't surprise me if nobody remembers...
>>>
>>> Best regards,
>>> Yakov.
>>>
>>> [1] https://github.com/TiddlyWiki/tiddlywiki.github.com
>>> [2] https://github.com/TiddlyWiki/tiddlywiki.com/
>>>
>>> среда, 24 января 2018 г., 17:56:27 UTC+3 пользователь PMario написал:

 On Wednesday, January 24, 2018 at 2:09:11 PM UTC+1, Yakov wrote:
>
> PS is that correct that the upstream name is purely a convention and 
> git doesn't do anything different with regard to it, technically?
>

 Yes ... All aliases are just a convention. ... If you use the same 
 schema for all your local repos, it helps to minify "user errors" 

 For me "push origin" means ... I can savely write to it. 

 "push upstream" means ... Be really carefull ... Messing it up, will 
 cause a lot of work to fix it!

 -m

>>> -- 
>> 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 tiddlywikide...@googlegroups.com.
>> To post to this group, send email to tiddly...@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/6f29491c-ab84-4b9e-8e89-2058cd6a93b9%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>

-- 
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/f2b2bea8-4c4b-4687-b09e-b1b68b5525a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Jeremy Ruston]

Hi Yakov

Terrific progress, well done!

> What I still don't understand is how do I get those .tid files updated 
> (except for editing them as plain text) from the tiddlywiki.github.com repo 
> (and shouldn't we move the content files to that repo instead of the repo of 
> TW2 core?). It would be nice to edit a TW (tiddlywiki.github.com 
> repo/index.html) and get those files updated..

The tiddlywiki.github.com repo is for storing the output of the build process; 
the files within it are exposed to the web as https://classic.tiddlywiki.com. 
There shouldn't be anything in that repo that was not generated by the build 
process.

> Any suggestions? Jeremy, where did you get those .tid files from (and how?) 
> for making this commit: 
> https://github.com/TiddlyWiki/TiddlyWiki/commit/c5d5c85eb7337a4f052f0d0151de0679be72e0ed
>  ?

Those .tid files were obtained from a backup of tiddlywiki.tiddlyspace.com that 
I took before it shut down.

To make further content changes you'd manually edit those .tid files, recommit 
them to the TiddlyWiki/TiddlyWiki repo, and then re-run the build process to 
regenerate tiddlywiki.github.com.

Best wishes

Jeremy.

> 
> Best regards,
> Yakov.
> 
> четверг, 25 января 2018 г., 1:31:16 UTC+3 пользователь Yakov написал:
>> 
>> So, regarding classic.tiddlywiki.com..
>> 
>> Is it correct that editing it can be done by just (forking and) cloning the 
>> [1] repo and editing TW in a browser? (and pushing back to fork and merging) 
>> I mean are recipes at [2] outdated since TiddlySpace is down (so [2] now has 
>> nothing to do with [1] and classic.tiddlywiki.com)?
>> 
>> No, wait, this can't be. First, TW version won't be updated this way (as 
>> well as the download package). Second, which is more surprising, for now I 
>> have only cloned [2] and still got cooked/2.9.1/index.html with 
>> classic.tiddlywiki.com's content in it once I've cooked TW.. is content from 
>> [1] accounted at all?
>> 
>> Any suggestions? What's the correct workflow? Yeah, the last change was done 
>> back in 2013, so it won't surprise me if nobody remembers...
>> 
>> Best regards,
>> Yakov.
>> 
>> [1] https://github.com/TiddlyWiki/tiddlywiki.github.com
>> [2] https://github.com/TiddlyWiki/tiddlywiki.com/
>> 
>> среда, 24 января 2018 г., 17:56:27 UTC+3 пользователь PMario написал:
>>> 
 On Wednesday, January 24, 2018 at 2:09:11 PM UTC+1, Yakov wrote:
 PS is that correct that the upstream name is purely a convention and git 
 doesn't do anything different with regard to it, technically?
>>> 
>>> Yes ... All aliases are just a convention. ... If you use the same schema 
>>> for all your local repos, it helps to minify "user errors" 
>>> 
>>> For me "push origin" means ... I can savely write to it. 
>>> 
>>> "push upstream" means ... Be really carefull ... Messing it up, will cause 
>>> a lot of work to fix it!
>>> 
>>> -m
> 
> -- 
> 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/6f29491c-ab84-4b9e-8e89-2058cd6a93b9%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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/948502F4-7D51-46B2-B010-97AD3BE5B8C1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hi guys,

ok, from what I understand now, bld.bat creates index.html (for 
classic.tiddlywiki.com) with the following line:

node %TIDDLYWIKI5_DIR%/tiddlywiki.js ./wiki --verbose --load 
./index.html.recipe --rendertiddler 
$:/core/templates/tiddlywiki2.template.html %TIDDLYWIKI_DEST%/index.html 
text/plain

which points to the index.html.recipe which contains

recipe: ../tiddlywiki/tiddlywikinosaver.html.recipe
recipe: ../tiddlywiki/content/split.recipe

and the latter contains the list of tiddlers that are in the same folder (
tiddlywiki/content) which actually constitute content of index.html.

What I still don't understand is how do I get those .tid files updated 
(except for editing them as plain text) from the tiddlywiki.github.com repo 
(and shouldn't we move the content files to that repo instead of the repo 
of TW2 core?). It would be nice to edit a TW (tiddlywiki.github.com 
repo/index.html) and get those files updated..

Any suggestions? Jeremy, where did you get those .tid files from (and how?) 
for making this commit: 
https://github.com/TiddlyWiki/TiddlyWiki/commit/c5d5c85eb7337a4f052f0d0151de0679be72e0ed
 
?

Best regards,
Yakov.

четверг, 25 января 2018 г., 1:31:16 UTC+3 пользователь Yakov написал:
>
> So, regarding classic.tiddlywiki.com..
>
> Is it correct that editing it can be done by just (forking and) cloning 
> the [1] repo and editing TW in a browser? (and pushing back to fork and 
> merging) I mean are recipes at [2] outdated since TiddlySpace is down (so 
> [2] now has nothing to do with [1] and classic.tiddlywiki.com)?
>
> No, wait, this can't be. First, TW version won't be updated this way (as 
> well as the download package). Second, which is more surprising, for now I 
> have only cloned [2] and still got cooked/2.9.1/index.html with 
> classic.tiddlywiki.com's content in it once I've cooked TW.. is content 
> from [1] accounted at all?
>
> Any suggestions? What's the correct workflow? Yeah, the last change was 
> done back in 2013, so it won't surprise me if nobody remembers...
>
> Best regards,
> Yakov.
>
> [1] https://github.com/TiddlyWiki/tiddlywiki.github.com
> [2] https://github.com/TiddlyWiki/tiddlywiki.com/
>
> среда, 24 января 2018 г., 17:56:27 UTC+3 пользователь PMario написал:
>>
>> On Wednesday, January 24, 2018 at 2:09:11 PM UTC+1, Yakov wrote:
>>>
>>> PS is that correct that the upstream name is purely a convention and 
>>> git doesn't do anything different with regard to it, technically?
>>>
>>
>> Yes ... All aliases are just a convention. ... If you use the same schema 
>> for all your local repos, it helps to minify "user errors" 
>>
>> For me "push origin" means ... I can savely write to it. 
>>
>> "push upstream" means ... Be really carefull ... Messing it up, will 
>> cause a lot of work to fix it!
>>
>> -m
>>
>

-- 
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/6f29491c-ab84-4b9e-8e89-2058cd6a93b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

So, regarding classic.tiddlywiki.com..

Is it correct that editing it can be done by just (forking and) cloning the 
[1] repo and editing TW in a browser? (and pushing back to fork and 
merging) I mean are recipes at [2] outdated since TiddlySpace is down (so 
[2] now has nothing to do with [1] and classic.tiddlywiki.com)?

No, wait, this can't be. First, TW version won't be updated this way (as 
well as the download package). Second, which is more surprising, for now I 
have only cloned [2] and still got cooked/2.9.1/index.html with 
classic.tiddlywiki.com's content in it once I've cooked TW.. is content 
from [1] accounted at all?

Any suggestions? What's the correct workflow? Yeah, the last change was 
done back in 2013, so it won't surprise me if nobody remembers...

Best regards,
Yakov.

[1] https://github.com/TiddlyWiki/tiddlywiki.github.com
[2] https://github.com/TiddlyWiki/tiddlywiki.com/

среда, 24 января 2018 г., 17:56:27 UTC+3 пользователь PMario написал:
>
> On Wednesday, January 24, 2018 at 2:09:11 PM UTC+1, Yakov wrote:
>>
>> PS is that correct that the upstream name is purely a convention and git 
>> doesn't do anything different with regard to it, technically?
>>
>
> Yes ... All aliases are just a convention. ... If you use the same schema 
> for all your local repos, it helps to minify "user errors" 
>
> For me "push origin" means ... I can savely write to it. 
>
> "push upstream" means ... Be really carefull ... Messing it up, will 
> cause a lot of work to fix it!
>
> -m
>

-- 
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/e69479ec-a459-4880-af5d-1ed95ae1a979%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[PMario]

On Wednesday, January 24, 2018 at 2:09:11 PM UTC+1, Yakov wrote:
>
> PS is that correct that the upstream name is purely a convention and git 
> doesn't do anything different with regard to it, technically?
>

Yes ... All aliases are just a convention. ... If you use the same schema 
for all your local repos, it helps to minify "user errors" 

For me "push origin" means ... I can savely write to it. 

"push upstream" means ... Be really carefull ... Messing it up, will cause 
a lot of work to fix it!

-m

-- 
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/777c98c3-9b13-47d2-8211-fc99bb9a5c69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

PS is that correct that the upstream name is purely a convention and git 
doesn't do anything different with regard to it, technically?

среда, 24 января 2018 г., 16:05:17 UTC+3 пользователь Yakov написал:
>
> Hi Mario,
>
> thanks, I've almost came up with the same workflow, but the issue with 
> merging on github side was an unexpected one. For now I'll be using this 
> workflow, although may be I'll add rebasing and also I have to admit that 
> merging updates of master to each branch is somewhat annoying, I'll 
> probably do something about it.
>
> Now, yesterday I've done some debugging and found the real problem that 
> broke those tests. It's not formatter was created too late, rather it 
> wasn't created at all because startup process (main) crashes. The cause 
> is QUnit overwrites window.isLocal as a boolean while TW defines it and 
> main tries to call it as a function. Commenting out QUnit.isLocal = 
> !!(location.protocol === 'file:'); (which is later is set to window using 
> extend(window, 
> QUnit);) in test/qunit/qunit.js fixes all tests (but LoadingSaving and 
> slices) and removes the error messages. I wonder if this may break 
> something, but from what I see, no error messages are shown in console and 
> looking through the whole tests.html source (search for isLocal and in 
> QUnit, in window) makes me think it's ok to remove (comment out) that 
> line – as far as I can see, this property isn't really used anywhere. I'll 
> probably comment this out in the next PR.
>
> Best regards,
> Yakov.
>
> понедельник, 22 января 2018 г., 16:48:10 UTC+3 пользователь PMario написал:
>>
>> Hi Yakov,
>>
>> Along with fixing tests and issues I'll probably be learning using git 
>>> rebase: looks like it is an exact tool to deal with this mess 
>>> . If there are any 
>>> suggestions regarding this, let me know (as well as suggestions of how to 
>>> merge on GitHub in a proper way or other things regarding git/github 
>>> workflow).
>>
>>
>> I do use the following workflow (for TiddlyWiki5), which never caused 
>> merge conflicts for me. 
>>
>> I'm using 2 aliases for my local git repos: 
>>
>>  - origin ... points to my github account, where I do have write access.
>>  - upstream ... points to the "main project" account ... which only 
>> merges to master with pull requestes, even if I have write access!
>>
>> The most important rule for me is: 
>>
>>  - Never, ever *commit and push* to *origin remote master *branch!
>>
>> Except for 
>>
>>  - git status ... if working tree is clean I can go on. If not I need to 
>> commit to a "feature-branch" or I simply do a "git stash"
>>  - git checkout master
>>  - git pull upstream master
>>  - git push origin master    to update origin repo.
>>
>>  
>> *My local workflow looks like this: *
>>
>>  - git status ... if working tree is clean I can go on. If not I need to 
>> commit to a "feature-branch" or I simply do a "git stash"
>>  - git checkout master
>>  - git pull upstream master
>>  - git checkout -b new-feature-branch
>>  - git add .
>>  - git commit -m "detailed info"
>>  - git push origin new-feature-branch
>>
>>  - Create a PR with github web UI. 
>>  - Once the PR is merged start over with git status ... 
>>
>> 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 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/e57a1588-1c99-47e5-a3a6-77d056499fa4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hi Mario,

thanks, I've almost came up with the same workflow, but the issue with 
merging on github side was an unexpected one. For now I'll be using this 
workflow, although may be I'll add rebasing and also I have to admit that 
merging updates of master to each branch is somewhat annoying, I'll 
probably do something about it.

Now, yesterday I've done some debugging and found the real problem that 
broke those tests. It's not formatter was created too late, rather it 
wasn't created at all because startup process (main) crashes. The cause is 
QUnit overwrites window.isLocal as a boolean while TW defines it and main 
tries to call it as a function. Commenting out QUnit.isLocal = 
!!(location.protocol === 'file:'); (which is later is set to window using 
extend(window, 
QUnit);) in test/qunit/qunit.js fixes all tests (but LoadingSaving and 
slices) and removes the error messages. I wonder if this may break 
something, but from what I see, no error messages are shown in console and 
looking through the whole tests.html source (search for isLocal and in QUnit, 
in window) makes me think it's ok to remove (comment out) that line – as 
far as I can see, this property isn't really used anywhere. I'll probably 
comment this out in the next PR.

Best regards,
Yakov.

понедельник, 22 января 2018 г., 16:48:10 UTC+3 пользователь PMario написал:
>
> Hi Yakov,
>
> Along with fixing tests and issues I'll probably be learning using git 
>> rebase: looks like it is an exact tool to deal with this mess 
>> . If there are any 
>> suggestions regarding this, let me know (as well as suggestions of how to 
>> merge on GitHub in a proper way or other things regarding git/github 
>> workflow).
>
>
> I do use the following workflow (for TiddlyWiki5), which never caused 
> merge conflicts for me. 
>
> I'm using 2 aliases for my local git repos: 
>
>  - origin ... points to my github account, where I do have write access.
>  - upstream ... points to the "main project" account ... which only 
> merges to master with pull requestes, even if I have write access!
>
> The most important rule for me is: 
>
>  - Never, ever *commit and push* to *origin remote master *branch!
>
> Except for 
>
>  - git status ... if working tree is clean I can go on. If not I need to 
> commit to a "feature-branch" or I simply do a "git stash"
>  - git checkout master
>  - git pull upstream master
>  - git push origin master    to update origin repo.
>
>  
> *My local workflow looks like this: *
>
>  - git status ... if working tree is clean I can go on. If not I need to 
> commit to a "feature-branch" or I simply do a "git stash"
>  - git checkout master
>  - git pull upstream master
>  - git checkout -b new-feature-branch
>  - git add .
>  - git commit -m "detailed info"
>  - git push origin new-feature-branch
>
>  - Create a PR with github web UI. 
>  - Once the PR is merged start over with git status ... 
>
> 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 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/940380d0-193f-4c2d-a3ec-ae35da89cb34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[PMario]

Hi Yakov,

Along with fixing tests and issues I'll probably be learning using git 
> rebase: looks like it is an exact tool to deal with this mess 
> . If there are any 
> suggestions regarding this, let me know (as well as suggestions of how to 
> merge on GitHub in a proper way or other things regarding git/github 
> workflow).


I do use the following workflow (for TiddlyWiki5), which never caused merge 
conflicts for me. 

I'm using 2 aliases for my local git repos: 

 - origin ... points to my github account, where I do have write access.
 - upstream ... points to the "main project" account ... which only merges 
to master with pull requestes, even if I have write access!

The most important rule for me is: 

 - Never, ever *commit and push* to *origin remote master *branch!

Except for 

 - git status ... if working tree is clean I can go on. If not I need to 
commit to a "feature-branch" or I simply do a "git stash"
 - git checkout master
 - git pull upstream master
 - git push origin master    to update origin repo.

 
*My local workflow looks like this: *

 - git status ... if working tree is clean I can go on. If not I need to 
commit to a "feature-branch" or I simply do a "git stash"
 - git checkout master
 - git pull upstream master
 - git checkout -b new-feature-branch
 - git add .
 - git commit -m "detailed info"
 - git push origin new-feature-branch

 - Create a PR with github web UI. 
 - Once the PR is merged start over with git status ... 

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 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/dfcb5225-f37f-495b-91a0-2dc7acdd271a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Jeremy Ruston]

Hi Yakov

Happy New Year to you, too, and well done on the excellent progress.

I’ve merged the documentation PR: 
https://github.com/TiddlyWiki/tiddlywiki.com/pull/29

> I've successfully modified a couple of tests and will make a pull request 
> once I build a complete set of tests for extended slices, now I think I can 
> become a maintainer, although there's a number things to learn still (most 
> notably, how to update classic.tiddlywiki.com 
>  once a new version is ready). Jeremy, let me 
> know how should I proceed for this.

Great stuff. The next step is for you to be given the necessary access to the 
https://github.com/TiddlyWiki/tiddlywiki.github.com 
 repo (as well as the 
https://github.com/TiddlyWiki/tiddlywiki.com 
 and 
https://github.com/TiddlyWiki/TiddlyWiki 
 repos). I’ve gone ahead and done 
that, hopefully you’ll have received a notification from GitHub.

> ? TiddlyWiki/test/README says there are JSSpec tests, but I don't see them. 
> Were they removed? Should README be updated?

I suspect that the README needs updating.

> ? what is a .recipe file? How they are ~concatenated? Some of them contain 
> only tiddler or recipe commands (sounds like "include one recipe into 
> another) while others various commands like
> template, copyright, style, noscript, jsext (TiddlyWiki/html/split.recipe)
> prehead, shadow (TiddlyWiki/shadows/split.recipe)
> version, js (TiddlyWiki/js/split.recipe)
> jsdeprecated (TiddlyWiki/deprecated/split.recipe)
> jslib, jquery (TiddlyWiki/jquery/split.recipe, 
> TiddlyWiki/jquery/plugins/split.recipe)
> a whole zoo of them. Is there some docs/group threads with their description?

Recipe files were introduced with the original Ruby-based “cook” tool. I don’t 
think that the format was ever documented. I reverse engineered the Ruby code 
in order to develop the TW5 support:

https://github.com/Jermolene/TiddlyWiki5/blob/master/plugins/tiddlywiki/classictools/modules/recipe.js
 

> ? (for now, just out of curiosity) does TW5 use some unit-tests system? Which 
> one?

TW5 uses Jasmine:

https://github.com/Jermolene/TiddlyWiki5/tree/master/plugins/tiddlywiki/jasmine 

https://github.com/Jermolene/TiddlyWiki5/tree/master/editions/test 


Best wishes

Jeremy.


> 
> Best regards,
> Yakov.
> 
> вторник, 2 января 2018 г., 0:02:37 UTC+3 пользователь Yakov написал:
> Hi guys, happy new year :)
> 
> I've successfully modified a couple of tests and will make a pull request 
> once I build a complete set of tests for extended slices, now I think I can 
> become a maintainer, although there's a number things to learn still (most 
> notably, how to update classic.tiddlywiki.com 
>  once a new version is ready). Jeremy, let me 
> know how should I proceed for this.
> 
> Another thing to note is I've found a probable source of those multiple 
> TypeError: Cannot read property 'formatterRegExp' of null errors when 
> tests.html is opened. Since I've faced this error before in a plugin where 
> the problem was formatter is built before plugins are loaded and the plugin 
> used getPageTitle, I've suspected tests are launched before main – and it 
> looks so: first, the accepted answer at [1] suggests that window.onload 
> (which, as [2] suggests, is the same as ) fires later than 
> jQuery(document).ready(..); second, if (in tests.html) in
> 
> test("generateRss: feed for an empty store", function() {
> 
> I put
> 
> alert('1');
> alert(formatter);
> var rss = generateRss();
> alert('2');
> 
> instead of just var rss = generateRss();, I see the '1' alert before all of 
> those error alerts, second alert indicates that formatter is actually null, 
> then 5 of those errors are shown and then goes '2'.
> 
> It is tempting to use the same hack I've used in the plugin I've mentioned 
> before: substitute
> 
> problematicFunctionThatNeedsFormatterToBeBuilt();
> 
> with
> 
> formatter = new Formatter(config.formatters);
> problematicFunctionThatNeedsFormatterToBeBuilt();
> formatter = null;
> 
> but I'm not sure yet if that can trick some tests and it feels like there 
> should be a more consistent approach to this. Any suggestions? By the way, if 
> I extend the example above like this:
> 
> alert('1');
> var formatterCash = formatter;
> formatter = new Formatter(config.formatters);
> var rss = generateRss();
> formatter = formatterCash;
> alert('2');
> 
> all error messages between '1' and '2' alerts go away and all the "3. 
> GenerateRss" tests are passed.

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

PS on the design part: to put it simply, tests should be run after main() 
worked. Other 80+ alerts are for the Macros.js tests, and if I put

formatter = new Formatter(config.formatters);

after

module("Macros.js", {});

both alerts are removed and tests 34-60 are passed. Though it doesn't mean 
all of the alerts were there because of Macros.js tests since in this case 
I don't set formatter back to null (seemingly I have to set and unset 
formatter in each test separately to do that).

Other tests however need separate consideration (32, 33 for loading/saving; 
66 for readMacroParams should be updated for the new version 
, 76 should be updated, 
too, for extended slices).

I have some additional questions:

? TiddlyWiki/test/README says there are JSSpec tests, but I don't see them. 
Were they removed? Should README be updated?

? what is a .recipe file? How they are ~concatenated? Some of them contain 
only tiddler or recipe commands (sounds like "include one recipe into 
another) while others various commands like
template, copyright, style, noscript, jsext (TiddlyWiki/html/split.recipe)
prehead, shadow (TiddlyWiki/shadows/split.recipe)
version, js (TiddlyWiki/js/split.recipe)
jsdeprecated (TiddlyWiki/deprecated/split.recipe)
jslib, jquery (TiddlyWiki/jquery/split.recipe, 
TiddlyWiki/jquery/plugins/split.recipe)
a whole zoo of them. Is there some docs/group threads with their 
description?

? (for now, just out of curiosity) does TW5 use some unit-tests system? 
Which one?

Best regards,
Yakov.

вторник, 2 января 2018 г., 0:02:37 UTC+3 пользователь Yakov написал:
>
> Hi guys, happy new year :)
>
> I've successfully modified a couple of tests and will make a pull request 
> once I build a complete set of tests for extended slices, now I think I can 
> become a maintainer, although there's a number things to learn still (most 
> notably, how to update classic.tiddlywiki.com once a new version is 
> ready). Jeremy, let me know how should I proceed for this.
>
> Another thing to note is I've found a probable source of those multiple 
> TypeError: 
> Cannot read property 'formatterRegExp' of null errors when tests.html is 
> opened. Since I've faced this error before in a plugin where the problem 
> was formatter is built before plugins are loaded and the plugin used 
> getPageTitle, I've suspected tests are launched before main – and it 
> looks so: first, the accepted answer at [1] suggests that window.onload 
> (which, as [2] suggests, is the same as ) fires later 
> than jQuery(document).ready(..); second, if (in tests.html) in
>
> test("generateRss: feed for an empty store", function() {
>
> I put
>
> alert('1');
> alert(formatter);
> var rss = generateRss();
> alert('2');
>
> instead of just var rss = generateRss();, I see the '1' alert before all 
> of those error alerts, second alert indicates that formatter is actually 
> null, then 5 of those errors are shown and then goes '2'.
>
> It is tempting to use the same hack I've used in the plugin I've mentioned 
> before: substitute
>
> problematicFunctionThatNeedsFormatterToBeBuilt();
>
> with
>
> formatter = new Formatter(config.formatters);
> problematicFunctionThatNeedsFormatterToBeBuilt();
> formatter = null;
>
> but I'm not sure yet if that can trick some tests and it feels like there 
> should be a more consistent approach to this. Any suggestions? By the way, 
> if I extend the example above like this:
>
> alert('1');
> var formatterCash = formatter;
> formatter = new Formatter(config.formatters);
> var rss = generateRss();
> formatter = formatterCash;
> alert('2');
>
> all error messages between '1' and '2' alerts go away and all the "3. 
> GenerateRss" tests are passed.
>
> Best regards,
> Yakov.
>
> [1] https://stackoverflow.com/a/3698214/3995261
> [2] https://stackoverflow.com/a/191318/3995261
>
> среда, 27 декабря 2017 г., 18:52:15 UTC+3 пользователь Yakov написал:
>>
>> Hi Jeremy,
>>
>> I wanted to write once I manage to correct at least one test and be ready 
>> to become a maintainer of TWc, but as a short note: yeap, now building 
>> works somewhat as expected and I also made a pull request to the 
>> tiddlywiki.com repo [1] to clarify the docs (I'll make some more 
>> suggestions later, the description definitely should be refactored to 
>> simplify the process for beginners).
>>
>> Best regards,
>> Yakov.
>>
>> [1] https://github.com/TiddlyWiki/tiddlywiki.com/pull/29
>>
>> вторник, 19 декабря 2017 г., 1:52:32 UTC+3 пользователь Jeremy Ruston 
>> написал:
>>>
>>> Hi Tobias
>>>
>>> Was there a particular necessity why the TWC build process involves 
>>> recipes and also phantom.js?
>>>
>>>
>>> The recipe files have been part of the TWC build process since 2005; 
>>> they're implemented in TW5 via the "classictools” plugin.
>>>
>>> We integrated Phantom.js sometime between 4 and 8 years ago. The final 
>>> 

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hi guys, happy new year :)

I've successfully modified a couple of tests and will make a pull request 
once I build a complete set of tests for extended slices, now I think I can 
become a maintainer, although there's a number things to learn still (most 
notably, how to update classic.tiddlywiki.com once a new version is ready). 
Jeremy, let me know how should I proceed for this.

Another thing to note is I've found a probable source of those multiple 
TypeError: 
Cannot read property 'formatterRegExp' of null errors when tests.html is 
opened. Since I've faced this error before in a plugin where the problem 
was formatter is built before plugins are loaded and the plugin used 
getPageTitle, I've suspected tests are launched before main – and it looks 
so: first, the accepted answer at [1] suggests that window.onload (which, 
as [2] suggests, is the same as ) fires later than 
jQuery(document).ready(..); second, if (in tests.html) in

test("generateRss: feed for an empty store", function() {

I put

alert('1');
alert(formatter);
var rss = generateRss();
alert('2');

instead of just var rss = generateRss();, I see the '1' alert before all of 
those error alerts, second alert indicates that formatter is actually null, 
then 5 of those errors are shown and then goes '2'.

It is tempting to use the same hack I've used in the plugin I've mentioned 
before: substitute

problematicFunctionThatNeedsFormatterToBeBuilt();

with

formatter = new Formatter(config.formatters);
problematicFunctionThatNeedsFormatterToBeBuilt();
formatter = null;

but I'm not sure yet if that can trick some tests and it feels like there 
should be a more consistent approach to this. Any suggestions? By the way, 
if I extend the example above like this:

alert('1');
var formatterCash = formatter;
formatter = new Formatter(config.formatters);
var rss = generateRss();
formatter = formatterCash;
alert('2');

all error messages between '1' and '2' alerts go away and all the "3. 
GenerateRss" tests are passed.

Best regards,
Yakov.

[1] https://stackoverflow.com/a/3698214/3995261
[2] https://stackoverflow.com/a/191318/3995261

среда, 27 декабря 2017 г., 18:52:15 UTC+3 пользователь Yakov написал:
>
> Hi Jeremy,
>
> I wanted to write once I manage to correct at least one test and be ready 
> to become a maintainer of TWc, but as a short note: yeap, now building 
> works somewhat as expected and I also made a pull request to the 
> tiddlywiki.com repo [1] to clarify the docs (I'll make some more 
> suggestions later, the description definitely should be refactored to 
> simplify the process for beginners).
>
> Best regards,
> Yakov.
>
> [1] https://github.com/TiddlyWiki/tiddlywiki.com/pull/29
>
> вторник, 19 декабря 2017 г., 1:52:32 UTC+3 пользователь Jeremy Ruston 
> написал:
>>
>> Hi Tobias
>>
>> Was there a particular necessity why the TWC build process involves 
>> recipes and also phantom.js?
>>
>>
>> The recipe files have been part of the TWC build process since 2005; 
>> they're implemented in TW5 via the "classictools” plugin.
>>
>> We integrated Phantom.js sometime between 4 and 8 years ago. The final 
>> stage of the build process is to run TWC under Phantom.js in order to 
>> generate the index.xml RSS file.
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>> Especially the former appear to complicate things a lot and make it 
>> somewhat less intuitive to build custom wikis.
>>
>> best -tb
>>
>> -- 
>> 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 tiddlywikide...@googlegroups.com.
>> To post to this group, send email to tiddly...@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/d48692bc-a6d1-4fd2-b5d1-9fbef95657ef%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>

-- 
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/92ae0b9e-e194-4a0c-81e4-dd34f27e02ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hi Jeremy,

I wanted to write once I manage to correct at least one test and be ready 
to become a maintainer of TWc, but as a short note: yeap, now building 
works somewhat as expected and I also made a pull request to the 
tiddlywiki.com repo [1] to clarify the docs (I'll make some more 
suggestions later, the description definitely should be refactored to 
simplify the process for beginners).

Best regards,
Yakov.

[1] https://github.com/TiddlyWiki/tiddlywiki.com/pull/29

вторник, 19 декабря 2017 г., 1:52:32 UTC+3 пользователь Jeremy Ruston 
написал:
>
> Hi Tobias
>
> Was there a particular necessity why the TWC build process involves 
> recipes and also phantom.js?
>
>
> The recipe files have been part of the TWC build process since 2005; 
> they're implemented in TW5 via the "classictools” plugin.
>
> We integrated Phantom.js sometime between 4 and 8 years ago. The final 
> stage of the build process is to run TWC under Phantom.js in order to 
> generate the index.xml RSS file.
>
> Best wishes
>
> Jeremy
>
>
> Especially the former appear to complicate things a lot and make it 
> somewhat less intuitive to build custom wikis.
>
> best -tb
>
> -- 
> 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 tiddlywikide...@googlegroups.com .
> To post to this group, send email to tiddly...@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/d48692bc-a6d1-4fd2-b5d1-9fbef95657ef%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
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/0c84a7b0-c1f2-4d06-880b-29eb003da5ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Jeremy Ruston]

Hi Tobias

> Was there a particular necessity why the TWC build process involves recipes 
> and also phantom.js?

The recipe files have been part of the TWC build process since 2005; they're 
implemented in TW5 via the "classictools” plugin.

We integrated Phantom.js sometime between 4 and 8 years ago. The final stage of 
the build process is to run TWC under Phantom.js in order to generate the 
index.xml RSS file.

Best wishes

Jeremy

> 
> Especially the former appear to complicate things a lot and make it somewhat 
> less intuitive to build custom wikis.
> 
> best -tb
> -- 
> 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/d48692bc-a6d1-4fd2-b5d1-9fbef95657ef%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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/121E453B-6EE6-44D5-95B9-A8697BBD6E9C%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Tobias Beer]

@Jeremy,

Was there a particular necessity why the TWC build process involves recipes 
and also phantom.js?

Especially the former appear to complicate things a lot and make it 
somewhat less intuitive to build custom wikis.

best -tb

-- 
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/d48692bc-a6d1-4fd2-b5d1-9fbef95657ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Tobias Beer]

Hi Jeremy / Yakov,

I managed to build TWC, I believe...
BUT the number of failing tests in tests.html,
and the continued popups informing me of this error:

TypeError: Cannot read property 'formatterRegExp' of null

...are quite irritating, for now.

best -tb

-- 
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/9d7d6813-08b2-41af-b6df-7a316a5ceed2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Jeremy Ruston]

Hi Yakov

my bad, I thought that the update you were talking about was some time ago
> and haven't checked the repo. Now I've updated my forks and tried bld.bat
> and got much nicer results but still somewhat incomplete.
>

Great stuff, I'm very pleased you are still working on this.


> So what's nice is that in somedir\tiddlywiki.com_and_builders\test I now
> got cooked index.2.9.1.html which is classic.tiddlywiki.com file with the
> new core. Same file is inside the somedir\tiddlywiki.com_and_bui
> lders\cooked\2.9.1\ folder (named index.html; I've compared them, texts
> are identical).
>
> What's not that nice:
>
>- empty.2.9.1.html is not cooked (no present in both cooked/2.9.1/ and
>test/ subfolders of somedir\tiddlywiki.com_and_builders\
>
> It sounds like PhantomJS needs to be installed - http://phantomjs.org/

It enables the batch file to invoke TiddlyWiki itself to generate the empty
file and the RSS index file.


The script suggests that you'll need to set the environment variable
BROWSER to point to the phantomjs executable.


>
>- bld.bat output still contains an error; it's another one, though:
>now in the 4th block, see the log below. Looks like the
>tiddlywiki_externaljs_tiddlyspace.html.recipe was deleted
>
> 
>but the building tools still try to use it (I've made git fetch origin
>master and have checked git status for them, looks like I'm
>up-to-date).
>
> I've removed the obsolete build steps I missed before:


https://github.com/TiddlyWiki/tiddlywiki.com/commit/60d32efadec15fb13ef5ede4b201e3fbd874fed1


>
>- there are many errors in tests.html. I've tried to build both
>current TWc core and my updated core
>, I've got only one
>new test failed and over 10 others are failed with the current core.
>There's definitely a number of tests which should be rewritten (for
>instance, slice names no longer can't have space in their name), they are
>located (defined) in TiddlyWiki/test/ , right?
>
> That certainly makes sense, do feel free to adjust the tests as required.


>
>- when I run building, still phantom_driver.js is opened in browser
>instead of anything helpful. Any ideas?
>
> Best regards,
> Yakov.
>

See above.


Good luck, and let me know how you get on,


Best wishes


Jeremy


>
> The full output:
> BUILD: clearing target folder: "cooked/2.9.1"
> - - - - - - - - - - - - - - -
> BUILD: assembling INDEX.HTML (v2.9.1)
> Boot log:
>   Startup task: load-modules
>   Startup task: info after: load-modules before: startup
>   Startup task: startup after: load-modules
>   Startup task: story after: startup
>   Startup task: commands platforms: node after: story
> Executing command: load ./index.html.recipe
> Executing command: rendertiddler $:/core/templates/tiddlywiki2.template.html
> D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/index.html
> text/plain
> - - - - - - - - - - - - - - -
> BUILD: assembling TESTS.HTML (v2.9.1)
> Boot log:
>   Startup task: load-modules
>   Startup task: info after: load-modules before: startup
>   Startup task: startup after: load-modules
>   Startup task: story after: startup
>   Startup task: commands platforms: node after: story
> Executing command: load ../tiddlywiki/test/recipes/tests.html.recipe
> Executing command: rendertiddler $:/core/templates/tiddlywiki2.template.html
> D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/tests.html
> text/plain
> - - - - - - - - - - - - - - -
> BUILD: creating TIDDLYWIKI_EXTERNALJS.HTML (v2.9.1)
> Boot log:
>   Startup task: load-modules
>   Startup task: info after: load-modules before: startup
>   Startup task: startup after: load-modules
>   Startup task: story after: startup
>   Startup task: commands platforms: node after: story
> Executing command: load ../tiddlywiki/tiddlywiki_externaljs.html.recipe
> Executing command: rendertiddler $:/core/templates/tiddlywiki2.template.html
> D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\
> 2.9.1/tiddlywiki_externaljs.html text/plain
> - - - - - - - - - - - - - - -
> BUILD: creating TIDDLYWIKI_EXTERNALJS_TIDDLYSPACE.HTML (v2.9.1)
> Boot log:
>   Startup task: load-modules
>   Startup task: info after: load-modules before: startup
>   Startup task: startup after: load-modules
>   Startup task: story after: startup
>   Startup task: commands platforms: node after: story
> Executing command: load ../tiddlywiki/tiddlywiki_exter
> naljs_tiddlyspace.html.recipe
> Error: No tiddlers found in file "../tiddlywiki/tiddlywiki_exte
> rnaljs_tiddlyspace.html.recipe"
> - - - - - - - - - - - - - - -
> BUILD: creating TWCORE.JS (v2.9.1)
> Boot log:
>   Startup task: load-modules
>   Startup task: info after: load-modules before: startup
>   Startup task: startup after: load-modules
>   Startup 

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hi Jeremy,

my bad, I thought that the update you mentioned was done some time ago and 
haven't updated TWc core repo; now I've done that and got much nicer 
results but there's still several issues about them.

   - now in tiddlywiki.com_and_builders in cooked/2.9.1/ subfolder there's 
   index.html and in test/ there's index.2.9.1.html which is the same file 
   namely classic.tiddlywiki.com's index.html with updated core
   - still, there's no empty.2.9.1.html in both subfolders
   - the output of bld.bat still has an error; it's a different one, though 
   (see the full output below). Looks like 
   tiddlywiki_externaljs_tiddlyspace.html.recipe was deleted 
   

 
   in TiddlyWiki repo, but building tools are not aware of it
   - when building, still phantom_driver.js is shown in browser instead of 
   anything helpful
   - there's a number of failed tests shown in cooked/2.9.1/tests.html. 
   I've rebuild with the current TWc core and can see that there's only one 
   block of tests that are failed after my changes, over 20 blocks are failed 
   with the current core. Tests are defined in TiddlyWiki/test/, right? 
   Looks it's time to rebuild them (for instance 76.15 shows that slices with 
   spaces in slice name should be ignored which is no longer the case), 
   although that requires some time.
   
Any suggestions?

Best regards,
Yakov.

PS after I wrote this reply and tried to submit it to the group, it got 
deleted (I haven't even got a mail notification about it), so I had to 
rewrite it again. Any ideas why could that happen?

Full bld.bat output:

BUILD: clearing target folder: "cooked/2.9.1"
- - - - - - - - - - - - - - -
BUILD: assembling INDEX.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ./index.html.recipe
Executing command: rendertiddler 
$:/core/templates/tiddlywiki2.template.html 
D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/index.html 
text/plain
- - - - - - - - - - - - - - -
BUILD: assembling TESTS.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ../tiddlywiki/test/recipes/tests.html.recipe
Executing command: rendertiddler 
$:/core/templates/tiddlywiki2.template.html 
D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/tests.html 
text/plain
- - - - - - - - - - - - - - -
BUILD: creating TIDDLYWIKI_EXTERNALJS.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ../tiddlywiki/tiddlywiki_externaljs.html.recipe
Executing command: rendertiddler 
$:/core/templates/tiddlywiki2.template.html 
D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/tiddlywiki_externaljs.html
 
text/plain
- - - - - - - - - - - - - - -
BUILD: creating TIDDLYWIKI_EXTERNALJS_TIDDLYSPACE.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load 
../tiddlywiki/tiddlywiki_externaljs_tiddlyspace.html.recipe
Error: No tiddlers found in file 
"../tiddlywiki/tiddlywiki_externaljs_tiddlyspace.html.recipe"
- - - - - - - - - - - - - - -
BUILD: creating TWCORE.JS (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ../tiddlywiki/tiddlywikinosaver.html.recipe
Executing command: rendertiddler 
$:/core/templates/tiddlywiki2.externaljs.template.html 
D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/twcore.js 
text/plain
- - - - - - - - - - - - - - -
BUILD: copying TIDDLYSAVER.JAR
- - - - - - - - - - - - - - -
BUILD: copying JQUERY.JS
- - - - - - - - - - - - - - -
BUILD: copying JQUERY.TWSTYLESHEET.JS
- - - - - - - - - - - - - - -
BUILD: creating EMPTY.HTML and INDEX.XML from INDEX.HTML
- - - - - - - - - - - - - - -
BUILD: copying INDEX.HTML to TEST/INDEX.2.9.1.HTML
BUILD: copying EMPTY.HTML to TEST/EMPTY.2.9.1.HTML
- - - - - - - - - - - - - - -
BUILD: done

суббота, 11 ноября 2017 г., 21:12:18 UTC+3 пользователь Yakov написал:
>
> Hello Jeremy,
>
> I've played a bit with these tools and got a number of questions (and 

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hi Jeremy,

my bad, I thought that the update you were talking about was some time ago 
and haven't checked the repo. Now I've updated my forks and tried bld.bat 
and got much nicer results but still somewhat incomplete.

So what's nice is that in somedir\tiddlywiki.com_and_builders\test I now 
got cooked index.2.9.1.html which is classic.tiddlywiki.com file with the 
new core. Same file is inside the 
somedir\tiddlywiki.com_and_builders\cooked\2.9.1\ folder (named index.html; 
I've compared them, texts are identical).

What's not that nice:

   - empty.2.9.1.html is not cooked (no present in both cooked/2.9.1/ and 
   test/ subfolders of somedir\tiddlywiki.com_and_builders\
   - bld.bat output still contains an error; it's another one, though: now 
   in the 4th block, see the log below. Looks like the 
   tiddlywiki_externaljs_tiddlyspace.html.recipe was deleted 
   

 
   but the building tools still try to use it (I've made git fetch origin 
   master and have checked git status for them, looks like I'm up-to-date).
   - there are many errors in tests.html. I've tried to build both current 
   TWc core and my updated core 
   , I've got only one new 
   test failed and over 10 others are failed with the current core. There's 
   definitely a number of tests which should be rewritten (for instance, slice 
   names no longer can't have space in their name), they are located (defined) 
   in TiddlyWiki/test/ , right?
   - when I run building, still phantom_driver.js is opened in browser 
   instead of anything helpful. Any ideas?

Best regards,
Yakov.

The full output:
BUILD: clearing target folder: "cooked/2.9.1"
- - - - - - - - - - - - - - -
BUILD: assembling INDEX.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ./index.html.recipe
Executing command: rendertiddler 
$:/core/templates/tiddlywiki2.template.html 
D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/index.html 
text/plain
- - - - - - - - - - - - - - -
BUILD: assembling TESTS.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ../tiddlywiki/test/recipes/tests.html.recipe
Executing command: rendertiddler 
$:/core/templates/tiddlywiki2.template.html 
D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/tests.html 
text/plain
- - - - - - - - - - - - - - -
BUILD: creating TIDDLYWIKI_EXTERNALJS.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ../tiddlywiki/tiddlywiki_externaljs.html.recipe
Executing command: rendertiddler 
$:/core/templates/tiddlywiki2.template.html 
D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/tiddlywiki_externaljs.html
 
text/plain
- - - - - - - - - - - - - - -
BUILD: creating TIDDLYWIKI_EXTERNALJS_TIDDLYSPACE.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load 
../tiddlywiki/tiddlywiki_externaljs_tiddlyspace.html.recipe
Error: No tiddlers found in file 
"../tiddlywiki/tiddlywiki_externaljs_tiddlyspace.html.recipe"
- - - - - - - - - - - - - - -
BUILD: creating TWCORE.JS (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ../tiddlywiki/tiddlywikinosaver.html.recipe
Executing command: rendertiddler 
$:/core/templates/tiddlywiki2.externaljs.template.html 
D:\data\based_here\code\tiddlywiki.com_and_builders\cooked\2.9.1/twcore.js 
text/plain
- - - - - - - - - - - - - - -
BUILD: copying TIDDLYSAVER.JAR
- - - - - - - - - - - - - - -
BUILD: copying JQUERY.JS
- - - - - - - - - - - - - - -
BUILD: copying JQUERY.TWSTYLESHEET.JS
- - - - - - - - - - - - - - -
BUILD: creating EMPTY.HTML and INDEX.XML from INDEX.HTML
- - - - - - - - - - - - - - -
BUILD: copying INDEX.HTML to TEST/INDEX.2.9.1.HTML
BUILD: copying EMPTY.HTML to TEST/EMPTY.2.9.1.HTML
- - - - - - - - - - - - - - -
BUILD: done

суббота, 11 ноября 2017 г., 21:12:18 UTC+3 пользователь Yakov 

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hello Jeremy,

I've played a bit with these tools and got a number of questions (and also 
notes regarding how the .md file [1]).

What I have done already:

   - downloaded WinDiff, pulled TiddlyWiki/TiddlyWiki to somedir\TiddlyWiki, 
   TiddlyWiki/tiddlywiki.com to somedir\tiddlywiki.com_and_builders, 
   Jermolene/TiddlyWiki5 to somedir\TiddlyWiki5.
  - actually, somedir\TiddlyWiki was somedir\TiddlyWiki Classic core at 
  first, but running somedir\tiddlywiki.com_and_builders\bld.bat showed 
  some errors and I've figured (judging by the bld.bat code) that path 
  to the TiddlyWiki Classic repo must be ..\TiddlyWiki relatively to 
  bld.bat and is not configurable
  - (haven't downloaded curl and phantomjs since the .md says the 
  former is needed to retrieve content from TiddlySpace and the latter is 
  only used by the OS X/Linux batch files; and haven't pulled 
  TiddlyWiki/tiddlywiki.github.com since I'm not publishing the build 
  to tiddlywiki.com yet)
  - edited somedir\tiddlywiki.com_and_builders\setenv.bat namely:
  - TIDDLYWIKI_RELEASE=2.9.1
  - TIDDLYWIKI5_DIR=%CD%\..\TiddlyWiki5
  - SET BROWSER="C:\\vivaldi.exe"
  - SET DIFF="\WinDiff.exe" 
  - run bld.bat from the somedir\tiddlywiki.com_and_builders. What 
   happens:
  - somedir\tiddlywiki.com_and_builders\cooked\2.9.1 is cleared as 
  expected.
  - what is created inside \2.9.1:
 - jquery.js
 - jQuery.twStylesheet.js
 - tests.html
 - TiddlySaver.jar
 - tiddlywiki_externaljs.html
 - tiddlywiki_externaljs_tiddlyspace.html
 - twcore.js
 - however, despite the .bat reports ... creating EMPTY.HTML and 
  INDEX.XML from INDEX.HTML ... copying INDEX.HTML to TEST/INDEX.2.9.1.HTML 
  ... copying EMPTY.HTML to TEST/EMPTY.2.9.1.HTML, there's no 
  INDEX.2.9.1.HTML and EMPTY.2.9.1.HTML inside the 
  somedir\tiddlywiki.com_and_builders\test\ folder
  - in browser (Vivaldi): 
  somedir\tiddlywiki.com_and_builders\phantom_driver.js is opened and 
  nothing else (no html)
  - full output of bld.bat is below
  - I'm puzzled: is there something I haved missed? Where should I look 
   for the built TWc file? Can I build it before any tests just to see what's 
   built? (the process description suggests that it should work this way but 
   it seems something went wrong)
   
Some notes and questions regarding the .md file:

   - it wasn't obvious that I have to pull tiddlywiki/tiddlywiki.com and 
   look for setenv.bat and bld.bat there (not in TW5 repo)
   - the repo describes the recommended directory structure but doesn't 
   mention that it is required that the TWc repo must have path 
   ../tiddlywiki relatively to bld.bat 
   - there's 2 sections headed "Building classic.tiddlywiki.com on 
   Windows". What's the difference? The first one is actually needed for both 
   building TWc file and classic.tiddlywiki.com which is somewhat confusing 
   (I'd change to Building classic.tiddlywiki.com and TiddlyWiki Classic on 
   Windows)
   - the overall hierarchy of sections/headers is somewhat confusing, too, 
   but I'll be ready to propose distinct changes after I successfully build 
   TWc, I think
   

Best regards,
Yakov.

[1] https://github.com/TiddlyWiki/tiddlywiki.com/blob/master/README.md
full output of bld.bat (with the paths substituted with ):
BUILD: clearing target folder: "cooked/2.9.1"
- - - - - - - - - - - - - - -
BUILD: assembling INDEX.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load ./index.html.recipe
fs.js:642
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), 
mode);
 ^

Error: ENOENT: no such file or directory, open '\tiddlywiki\content\split.recipe'
at Error (native)
at Object.fs.openSync (fs.js:642:18)
at Object.fs.readFileSync (fs.js:510:33)
at processRecipe ($:/plugins/tiddlywiki/classictools/recipe.js:63:34)
at exports.text/vnd.tiddlywiki2-recipe 
($:/plugins/tiddlywiki/classictools/recipe.js:71:2)
at $tw.Wiki.deserializeTiddlers (
\TiddlyWiki5\boot\boot.js:1249:23)
at $tw.loadTiddlersFromFile (\TiddlyWiki5\boot\boot.js:1480:23)
at $tw.loadTiddlersFromPath (\TiddlyWiki5\boot\boot.js:1530:22)
at Command.execute ($:/core/modules/commands/load.js:33:21)
at Commander.executeNextCommand ($:/core/modules/commander.js:115:14)
- - - - - - - - - - - - - - -
BUILD: assembling TESTS.HTML (v2.9.1)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
Executing command: load 

Re: [twdev] Build Process for TiddlyWiki Classic

[Jeremy Ruston]

Hi Yakov

I've made a number of updates that should get the TW2 build process working
again:

1. Fixing a regression in TW5 that had broken the "classictools" TW5 plugin
that we use for the build process
2. Removing the old code associated with pulling the content down from
TiddlySpace, and instead storing the content in the tiddlywiki repo
3. Working around the removal of the editions/tw2 edition from TW5

https://github.com/Jermolene/TiddlyWiki5/commit/95b84dd0ca34d7ae4019d0f3c20a55eb5318096e
https://github.com/TiddlyWiki/tiddlywiki/commit/c5d5c85eb7337a4f052f0d0151de0679be72e0ed
https://github.com/TiddlyWiki/tiddlywiki.com/commit/46daaa4397d143b467bb5ba2deb938bd817ca642
https://github.com/TiddlyWiki/tiddlywiki/commit/5a53e55d80d33db12599203e1847c14de456a837

Anyhow, things are working for me now under Mac OS X. I haven't tested
under Windows.

The instructions for the build process can be found here:

https://github.com/tiddlywiki/tiddlywiki.com

Hopefully now Eric and I between us should be able to help you get up and
running,

Best wishes

Jeremy


On Thu, Nov 2, 2017 at 3:22 PM, Yakov 
wrote:

> Hi Jeremy,
>
> I'm not familiar with Ruby, too, and I have no preferences among the two
> ways, actually I'm looking for an "at least this works" way. However, I'm
> not familiar with the unit testing system used for TWc core and have no
> idea if building with TW5 supports that. Also, I need some how-to
> guide/help since I haven't found any. TiddlyWikiDev space [1] gives links
> to [2] where I haven't found any instructions and to [3] which seems to be
> an instruction to build classic.tiddlywiki.com and which looks quite
> complicated (I can try to extract a recipe of how to build TWc from there,
> but if there's something more brief, it will be lovely to know). Also
> please keep in mind that for now I'm not very familiar with TW5.
>
> Best regards,
> Yakov.
>
> [1] http://yakovl.bplaced.net/TW/TS_backups/TiddlyWikiDev.
> tiddlyspace.com%20(31.12.2016).html#Build
> [2] http://tiddlywiki.com/dev/
> [3] https://github.com/TiddlyWiki/tiddlywiki.com/blob/master/README.md
>
> четверг, 2 ноября 2017 г., 14:12:22 UTC+3 пользователь Jeremy Ruston
> написал:
>>
>> Hi BJ
>>
>> what version of the core can be used to build TWC?
>>
>>
>> One might need to do a git bisect to find the last working build. Some of
>> the code is pretty hacky so may be better to slightly re-engineer.
>>
>> The current code is written as a deserialiser, but needs the file path of
>> the file. The old hack for that no longer works. I think better to rewrite
>> as a “load-classic-recipe” command
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>> On Wednesday, November 1, 2017 at 6:03:54 PM UTC+1, Jeremy Ruston wrote:
>>>
>>> Hi Yakov
>>>
>>> Apologies for the late response.
>>>
>>> I'm afraid I can't help with cook/ginsu; I always found them difficult
>>> to use because I'm not familiar with Ruby. That was what drove me to
>>> rewrite the TWC build process with TW5 back in 2011.
>>>
>>> I've just tried to get the TW5-based build process running and found
>>> that it is currently broken due to a minor change in TW5 since it was last
>>> used.
>>>
>>> I'm happy to get things fixed up again, or should I wait to see how you
>>> get on with cook/ginsu?
>>>
>>> Best wishes
>>>
>>> Jeremy.
>>>
>>>
>>>
>>>
>>> On Sun, Oct 29, 2017 at 11:40 PM, Yakov  wrote:
>>>
 Hello everyone,

 not sure if it's worthy to post here since the thread is very old;
 still it seems to have almost every reference I've found so far, so...

 I'm on Windows (10) and I'd like to build TWc core. I've pulled
 TiddlyWiki Classic repo (my branch
  that I'd like to
 build and test), installed Ruby (v2.4.2 x64), pulled
 https://github.com/TiddlyWiki/cooker to a separate folder, tried run
 to biuld and got an error that takes place even if I just run cook.rb
 -h:

 /Ruby_2_4__x64/l
 ib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require':
 cannot load such file -- recipe (LoadError)
 from /Ruby_2_4__x64/l
 ib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
 from /cook.rb:7:in `'

 Can anybody help me with that? I'd like to take maintainance of TWc,
 but for that (and for my own needs) I have to learn how to build TWc core!

 Guidance regarding building TWC with TW5 is also appreciated, but it
 seems that using cook should be quite simple and there's either something
 that's broken or I'm missing some simple detail. I have no knowledge of
 Ruby yet, though.

 Best regards,
 Yakov.

 суббота, 9 марта 2013 г., 14:24:06 UTC+3 пользователь Jeremy Ruston
 написал:
>
> Hi Tobias
>
> I've made a couple of pull requests that get the TW2 tests running
> with the new build environment:
>
> 

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hi Jeremy,

I'm not familiar with Ruby, too, and I have no preferences among the two 
ways, actually I'm looking for an "at least this works" way. However, I'm 
not familiar with the unit testing system used for TWc core and have no 
idea if building with TW5 supports that. Also, I need some how-to 
guide/help since I haven't found any. TiddlyWikiDev space [1] gives links 
to [2] where I haven't found any instructions and to [3] which seems to be 
an instruction to build classic.tiddlywiki.com and which looks quite 
complicated (I can try to extract a recipe of how to build TWc from there, 
but if there's something more brief, it will be lovely to know). Also 
please keep in mind that for now I'm not very familiar with TW5.

Best regards,
Yakov.

[1] 
http://yakovl.bplaced.net/TW/TS_backups/TiddlyWikiDev.tiddlyspace.com%20(31.12.2016).html#Build
 

[2] http://tiddlywiki.com/dev/
[3] https://github.com/TiddlyWiki/tiddlywiki.com/blob/master/README.md

четверг, 2 ноября 2017 г., 14:12:22 UTC+3 пользователь Jeremy Ruston 
написал:
>
> Hi BJ
>
> what version of the core can be used to build TWC?
>
>
> One might need to do a git bisect to find the last working build. Some of 
> the code is pretty hacky so may be better to slightly re-engineer.
>
> The current code is written as a deserialiser, but needs the file path of 
> the file. The old hack for that no longer works. I think better to rewrite 
> as a “load-classic-recipe” command
>
> Best wishes
>
> Jeremy
>
>
> On Wednesday, November 1, 2017 at 6:03:54 PM UTC+1, Jeremy Ruston wrote:
>>
>> Hi Yakov
>>
>> Apologies for the late response.
>>
>> I'm afraid I can't help with cook/ginsu; I always found them difficult to 
>> use because I'm not familiar with Ruby. That was what drove me to rewrite 
>> the TWC build process with TW5 back in 2011.
>>
>> I've just tried to get the TW5-based build process running and found that 
>> it is currently broken due to a minor change in TW5 since it was last used.
>>
>> I'm happy to get things fixed up again, or should I wait to see how you 
>> get on with cook/ginsu?
>>
>> Best wishes
>>
>> Jeremy.
>>
>>
>>
>>
>> On Sun, Oct 29, 2017 at 11:40 PM, Yakov  wrote:
>>
>>> Hello everyone,
>>>
>>> not sure if it's worthy to post here since the thread is very old; still 
>>> it seems to have almost every reference I've found so far, so...
>>>
>>> I'm on Windows (10) and I'd like to build TWc core. I've pulled 
>>> TiddlyWiki Classic repo (my branch 
>>>  that I'd like to build 
>>> and test), installed Ruby (v2.4.2 x64), pulled 
>>> https://github.com/TiddlyWiki/cooker to a separate folder, tried run to 
>>> biuld and got an error that takes place even if I just run cook.rb -h:
>>>
>>> >> installations>/Ruby_2_4__x64/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
>>>  
>>> `require': cannot load such file -- recipe (LoadError)
>>> from >> installations>/Ruby_2_4__x64/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
>>>  
>>> `require'
>>> from /cook.rb:7:in `'
>>>
>>> Can anybody help me with that? I'd like to take maintainance of TWc, but 
>>> for that (and for my own needs) I have to learn how to build TWc core!
>>>
>>> Guidance regarding building TWC with TW5 is also appreciated, but it 
>>> seems that using cook should be quite simple and there's either something 
>>> that's broken or I'm missing some simple detail. I have no knowledge of 
>>> Ruby yet, though.
>>>
>>> Best regards,
>>> Yakov.
>>>
>>> суббота, 9 марта 2013 г., 14:24:06 UTC+3 пользователь Jeremy Ruston 
>>> написал:

 Hi Tobias

 I've made a couple of pull requests that get the TW2 tests running with 
 the new build environment:

 https://github.com/TiddlyWiki/tiddlywiki/pull/119 - updates the test 
 recipe and tiddler format to the latest versions understood by the new 
 tools

 https://github.com/TiddlyWiki/tiddlywiki.com/pull/10 - adds a line to 
 bld.sh to build the tests.html file

 (I also made some changes to TW5 to get things working, so you'll need 
 the latest version of that too).

 At the moment you can run the tests by opening tests.html in the 
 browser. The next step is to use phantom.js to run the tests automatically.

 Best wishes

 Jeremy



 On Thu, Mar 7, 2013 at 11:26 PM, Tobias Beer  
 wrote:

> Thanks Jeremy,
>
> I'll try to...
>
>- dig into this
>- see if I can get to set up my machine and build the thing
>   - perhaps using both, the old and new process
>- see what I can bring over to TiddlyWikiDev 
>   - I like things at one place (less scattered)
>
> Cheers, Tobias.
>



 -- 
 Jeremy Ruston
 mailto:jeremy...@gmail.com

>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> 

Re: [twdev] Build Process for TiddlyWiki Classic

[Jeremy Ruston]

Hi BJ

> what version of the core can be used to build TWC?

One might need to do a git bisect to find the last working build. Some of the 
code is pretty hacky so may be better to slightly re-engineer.

The current code is written as a deserialiser, but needs the file path of the 
file. The old hack for that no longer works. I think better to rewrite as a 
“load-classic-recipe” command

Best wishes

Jeremy

> 
>> On Wednesday, November 1, 2017 at 6:03:54 PM UTC+1, Jeremy Ruston wrote:
>> Hi Yakov
>> 
>> Apologies for the late response.
>> 
>> I'm afraid I can't help with cook/ginsu; I always found them difficult to 
>> use because I'm not familiar with Ruby. That was what drove me to rewrite 
>> the TWC build process with TW5 back in 2011.
>> 
>> I've just tried to get the TW5-based build process running and found that it 
>> is currently broken due to a minor change in TW5 since it was last used.
>> 
>> I'm happy to get things fixed up again, or should I wait to see how you get 
>> on with cook/ginsu?
>> 
>> Best wishes
>> 
>> Jeremy.
>> 
>> 
>> 
>> 
>>> On Sun, Oct 29, 2017 at 11:40 PM, Yakov  wrote:
>>> Hello everyone,
>>> 
>>> not sure if it's worthy to post here since the thread is very old; still it 
>>> seems to have almost every reference I've found so far, so...
>>> 
>>> I'm on Windows (10) and I'd like to build TWc core. I've pulled TiddlyWiki 
>>> Classic repo (my branch that I'd like to build and test), installed Ruby 
>>> (v2.4.2 x64), pulled https://github.com/TiddlyWiki/cooker to a separate 
>>> folder, tried run to biuld and got an error that takes place even if I just 
>>> run cook.rb -h:
>>> 
>>> >> installations>/Ruby_2_4__x64/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
>>>  `require': cannot load such file -- recipe (LoadError)
>>> from >> installations>/Ruby_2_4__x64/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
>>>  `require'
>>> from /cook.rb:7:in `'
>>> 
>>> Can anybody help me with that? I'd like to take maintainance of TWc, but 
>>> for that (and for my own needs) I have to learn how to build TWc core!
>>> 
>>> Guidance regarding building TWC with TW5 is also appreciated, but it seems 
>>> that using cook should be quite simple and there's either something that's 
>>> broken or I'm missing some simple detail. I have no knowledge of Ruby yet, 
>>> though.
>>> 
>>> Best regards,
>>> Yakov.
>>> 
>>> суббота, 9 марта 2013 г., 14:24:06 UTC+3 пользователь Jeremy Ruston написал:
 
 Hi Tobias
 
 I've made a couple of pull requests that get the TW2 tests running with 
 the new build environment:
 
 https://github.com/TiddlyWiki/tiddlywiki/pull/119 - updates the test 
 recipe and tiddler format to the latest versions understood by the new 
 tools
 
 https://github.com/TiddlyWiki/tiddlywiki.com/pull/10 - adds a line to 
 bld.sh to build the tests.html file
 
 (I also made some changes to TW5 to get things working, so you'll need the 
 latest version of that too).
 
 At the moment you can run the tests by opening tests.html in the browser. 
 The next step is to use phantom.js to run the tests automatically.
 
 Best wishes
 
 Jeremy
 
 
 
> On Thu, Mar 7, 2013 at 11:26 PM, Tobias Beer  wrote:
> Thanks Jeremy,
> 
> I'll try to...
> dig into this
> see if I can get to set up my machine and build the thing
> perhaps using both, the old and new process
> see what I can bring over to TiddlyWikiDev
> I like things at one place (less scattered)
> Cheers, Tobias.
 
 
 
 -- 
 Jeremy Ruston
 mailto:jeremy...@gmail.com
>>> 
>>> -- 
>>> 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 tiddlywikide...@googlegroups.com.
>>> To post to this group, send email to tiddly...@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/44bd4148-caf3-44b4-b552-1f82d641bf86%40googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> 
>> 
>> -- 
>> Jeremy Ruston
>> mailto:jeremy...@gmail.com
> 
> -- 
> 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/31de5d30-70bb-484a-a94e-6990e04ea447%40googlegroups.com.
> For more options, visit 

Re: [twdev] Build Process for TiddlyWiki Classic

[BJ]

what version of the core can be used to build TWC?

On Wednesday, November 1, 2017 at 6:03:54 PM UTC+1, Jeremy Ruston wrote:
>
> Hi Yakov
>
> Apologies for the late response.
>
> I'm afraid I can't help with cook/ginsu; I always found them difficult to 
> use because I'm not familiar with Ruby. That was what drove me to rewrite 
> the TWC build process with TW5 back in 2011.
>
> I've just tried to get the TW5-based build process running and found that 
> it is currently broken due to a minor change in TW5 since it was last used.
>
> I'm happy to get things fixed up again, or should I wait to see how you 
> get on with cook/ginsu?
>
> Best wishes
>
> Jeremy.
>
>
>
>
> On Sun, Oct 29, 2017 at 11:40 PM, Yakov  > wrote:
>
>> Hello everyone,
>>
>> not sure if it's worthy to post here since the thread is very old; still 
>> it seems to have almost every reference I've found so far, so...
>>
>> I'm on Windows (10) and I'd like to build TWc core. I've pulled 
>> TiddlyWiki Classic repo (my branch 
>>  that I'd like to build 
>> and test), installed Ruby (v2.4.2 x64), pulled 
>> https://github.com/TiddlyWiki/cooker to a separate folder, tried run to 
>> biuld and got an error that takes place even if I just run cook.rb -h:
>>
>> > installations>/Ruby_2_4__x64/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
>>  
>> `require': cannot load such file -- recipe (LoadError)
>> from > installations>/Ruby_2_4__x64/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
>>  
>> `require'
>> from /cook.rb:7:in `'
>>
>> Can anybody help me with that? I'd like to take maintainance of TWc, but 
>> for that (and for my own needs) I have to learn how to build TWc core!
>>
>> Guidance regarding building TWC with TW5 is also appreciated, but it 
>> seems that using cook should be quite simple and there's either something 
>> that's broken or I'm missing some simple detail. I have no knowledge of 
>> Ruby yet, though.
>>
>> Best regards,
>> Yakov.
>>
>> суббота, 9 марта 2013 г., 14:24:06 UTC+3 пользователь Jeremy Ruston 
>> написал:
>>>
>>> Hi Tobias
>>>
>>> I've made a couple of pull requests that get the TW2 tests running with 
>>> the new build environment:
>>>
>>> https://github.com/TiddlyWiki/tiddlywiki/pull/119 - updates the test 
>>> recipe and tiddler format to the latest versions understood by the new tools
>>>
>>> https://github.com/TiddlyWiki/tiddlywiki.com/pull/10 - adds a line to 
>>> bld.sh to build the tests.html file
>>>
>>> (I also made some changes to TW5 to get things working, so you'll need 
>>> the latest version of that too).
>>>
>>> At the moment you can run the tests by opening tests.html in the 
>>> browser. The next step is to use phantom.js to run the tests automatically.
>>>
>>> Best wishes
>>>
>>> Jeremy
>>>
>>>
>>>
>>> On Thu, Mar 7, 2013 at 11:26 PM, Tobias Beer  wrote:
>>>
 Thanks Jeremy,

 I'll try to...

- dig into this
- see if I can get to set up my machine and build the thing
   - perhaps using both, the old and new process
- see what I can bring over to TiddlyWikiDev 
   - I like things at one place (less scattered)

 Cheers, Tobias.

>>>
>>>
>>>
>>> -- 
>>> Jeremy Ruston
>>> mailto:jeremy...@gmail.com
>>>
>> -- 
>> 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 tiddlywikide...@googlegroups.com .
>> To post to this group, send email to tiddly...@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/44bd4148-caf3-44b4-b552-1f82d641bf86%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Jeremy Ruston
> mailto:jeremy...@gmail.com 
>

-- 
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/31de5d30-70bb-484a-a94e-6990e04ea447%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[PMario]

On Wednesday, November 1, 2017 at 6:03:54 PM UTC+1, Jeremy Ruston wrote:
>
> I'm happy to get things fixed up again, 
>

please do!
 

> or should I wait to see how you get on with cook/ginsu?
>

-1 IMO needs unnecessary bloat.

-m

-- 
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/e79b740a-85dc-4411-b082-4efccb12b089%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Jeremy Ruston]

Hi Yakov

Apologies for the late response.

I'm afraid I can't help with cook/ginsu; I always found them difficult to
use because I'm not familiar with Ruby. That was what drove me to rewrite
the TWC build process with TW5 back in 2011.

I've just tried to get the TW5-based build process running and found that
it is currently broken due to a minor change in TW5 since it was last used.

I'm happy to get things fixed up again, or should I wait to see how you get
on with cook/ginsu?

Best wishes

Jeremy.




On Sun, Oct 29, 2017 at 11:40 PM, Yakov 
wrote:

> Hello everyone,
>
> not sure if it's worthy to post here since the thread is very old; still
> it seems to have almost every reference I've found so far, so...
>
> I'm on Windows (10) and I'd like to build TWc core. I've pulled TiddlyWiki
> Classic repo (my branch 
> that I'd like to build and test), installed Ruby (v2.4.2 x64), pulled
> https://github.com/TiddlyWiki/cooker to a separate folder, tried run to
> biuld and got an error that takes place even if I just run cook.rb -h:
>
>  installations>/Ruby_2_4__x64/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
> `require': cannot load such file -- recipe (LoadError)
> from /Ruby_2_4__x64/
> lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> from /cook.rb:7:in `'
>
> Can anybody help me with that? I'd like to take maintainance of TWc, but
> for that (and for my own needs) I have to learn how to build TWc core!
>
> Guidance regarding building TWC with TW5 is also appreciated, but it seems
> that using cook should be quite simple and there's either something that's
> broken or I'm missing some simple detail. I have no knowledge of Ruby yet,
> though.
>
> Best regards,
> Yakov.
>
> суббота, 9 марта 2013 г., 14:24:06 UTC+3 пользователь Jeremy Ruston
> написал:
>>
>> Hi Tobias
>>
>> I've made a couple of pull requests that get the TW2 tests running with
>> the new build environment:
>>
>> https://github.com/TiddlyWiki/tiddlywiki/pull/119 - updates the test
>> recipe and tiddler format to the latest versions understood by the new tools
>>
>> https://github.com/TiddlyWiki/tiddlywiki.com/pull/10 - adds a line to
>> bld.sh to build the tests.html file
>>
>> (I also made some changes to TW5 to get things working, so you'll need
>> the latest version of that too).
>>
>> At the moment you can run the tests by opening tests.html in the browser.
>> The next step is to use phantom.js to run the tests automatically.
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>>
>> On Thu, Mar 7, 2013 at 11:26 PM, Tobias Beer  wrote:
>>
>>> Thanks Jeremy,
>>>
>>> I'll try to...
>>>
>>>- dig into this
>>>- see if I can get to set up my machine and build the thing
>>>   - perhaps using both, the old and new process
>>>- see what I can bring over to TiddlyWikiDev
>>>   - I like things at one place (less scattered)
>>>
>>> Cheers, Tobias.
>>>
>>
>>
>>
>> --
>> Jeremy Ruston
>> mailto:jeremy...@gmail.com
>>
> --
> 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/44bd4148-caf3-44b4-b552-1f82d641bf86%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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/CAPKKYJaNLBhSyzENY7BjGNdYhVLHPvCg7WR9Z8HtP9KJr0abzw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Yakov]

Hello everyone,

not sure if it's worthy to post here since the thread is very old; still it 
seems to have almost every reference I've found so far, so...

I'm on Windows (10) and I'd like to build TWc core. I've pulled TiddlyWiki 
Classic repo (my branch  
that I'd like to build and test), installed Ruby (v2.4.2 x64), pulled 
https://github.com/TiddlyWiki/cooker to a separate folder, tried run to 
biuld and got an error that takes place even if I just run cook.rb -h:

/Ruby_2_4__x64/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
 
`require': cannot load such file -- recipe (LoadError)
from /Ruby_2_4__x64/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
 
`require'
from /cook.rb:7:in `'

Can anybody help me with that? I'd like to take maintainance of TWc, but 
for that (and for my own needs) I have to learn how to build TWc core!

Guidance regarding building TWC with TW5 is also appreciated, but it seems 
that using cook should be quite simple and there's either something that's 
broken or I'm missing some simple detail. I have no knowledge of Ruby yet, 
though.

Best regards,
Yakov.

суббота, 9 марта 2013 г., 14:24:06 UTC+3 пользователь Jeremy Ruston написал:
>
> Hi Tobias
>
> I've made a couple of pull requests that get the TW2 tests running with 
> the new build environment:
>
> https://github.com/TiddlyWiki/tiddlywiki/pull/119 - updates the test 
> recipe and tiddler format to the latest versions understood by the new tools
>
> https://github.com/TiddlyWiki/tiddlywiki.com/pull/10 - adds a line to 
> bld.sh to build the tests.html file
>
> (I also made some changes to TW5 to get things working, so you'll need the 
> latest version of that too).
>
> At the moment you can run the tests by opening tests.html in the browser. 
> The next step is to use phantom.js to run the tests automatically.
>
> Best wishes
>
> Jeremy
>
>
>
> On Thu, Mar 7, 2013 at 11:26 PM, Tobias Beer  > wrote:
>
>> Thanks Jeremy,
>>
>> I'll try to...
>>
>>- dig into this
>>- see if I can get to set up my machine and build the thing
>>   - perhaps using both, the old and new process
>>- see what I can bring over to TiddlyWikiDev 
>>   - I like things at one place (less scattered)
>>
>> Cheers, Tobias.
>>
>
>
>
> -- 
> Jeremy Ruston
> mailto:jeremy...@gmail.com 
>

-- 
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/44bd4148-caf3-44b4-b552-1f82d641bf86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[Jeremy Ruston]

Hi Tobias

I've made a couple of pull requests that get the TW2 tests running with the
new build environment:

https://github.com/TiddlyWiki/tiddlywiki/pull/119 - updates the test recipe
and tiddler format to the latest versions understood by the new tools

https://github.com/TiddlyWiki/tiddlywiki.com/pull/10 - adds a line to
bld.sh to build the tests.html file

(I also made some changes to TW5 to get things working, so you'll need the
latest version of that too).

At the moment you can run the tests by opening tests.html in the browser.
The next step is to use phantom.js to run the tests automatically.

Best wishes

Jeremy



On Thu, Mar 7, 2013 at 11:26 PM, Tobias Beer beertob...@gmail.com wrote:

 Thanks Jeremy,

 I'll try to...

- dig into this
- see if I can get to set up my machine and build the thing
   - perhaps using both, the old and new process
- see what I can bring over to TiddlyWikiDev
   - I like things at one place (less scattered)

 Cheers, Tobias.




-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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 http://groups.google.com/group/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[twdev] Build Process for TiddlyWiki Classic

[Tobias Beer]

Hi everyone,

I currently cannot run the TW build process on my Win8 machine.

Although desireable, figuring out how to set this up and using any test 
tools involves a bit too much effort out of the blue.

*What I know is...*

   1. there is an old build process (cook, ginsu, ruby)
   2. there is a new build process (node.js)
   3. there are some tests
   4. there is TinyTiddlyWiki

*What I don't know is...*

   1. is the old build process still relevant and why
   2. how to set up the old build process
   3. how to run tests using the old build process and how to verify the 
   results
   4. how to set up the new build process on node.js
   5. is the new build process complete
   6. are the tests complete
   7. how to run tests using the new build process and how to verify the 
   results
   8. how to build a TinyTiddlyWiki (old? / new? / tests?)

I would appreciate if we could get all of the above documented in the 
@TiddlyWikiDev space.
http://tiddlywikidev.tiddlyspace.com/#Build

I'll also gladly put it there if someone would post it here...

Cheers, Tobias.

-- 
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 http://groups.google.com/group/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [twdev] Build Process for TiddlyWiki Classic

[Jeremy Ruston]

Hi Tobias

I currently cannot run the TW build process on my Win8 machine.

 Although desireable, figuring out how to set this up and using any test
 tools involves a bit too much effort out of the blue.

 *What I know is...*

1. there is an old build process (cook, ginsu, ruby)

 the old build tools live at https://github.com/tiddlywiki/cooker


1. there is a new build process (node.js)

 there are two parts to this: the capabilit

The TW5 documentation for the ability to build TW2 documents is here:

http://five.tiddlywiki.com/static/Building%20classic%20TiddlyWiki%20with%20TiddlyWiki5.html

The build scripts for using TW5 to build tiddlywiki.com are here:

https://github.com/tiddlywiki/tiddlywiki.com/


1. there are some tests

 The new build process doesn't run the tests. It probably should.


1.
2. there is TinyTiddlyWiki

 *What I don't know is...*

1. is the old build process still relevant and why

 The new build process isn't 100% backwards compatible with the old
cook/ginsu tools, and so the old tools may be necessary for some legacy
operations. The desire is to upgrade the new tools vigorously - a recent
example is the work just done on using phantomjs to script the saving of
TiddlyWiki's release versions:

https://github.com/jermolene/tiddlywiki.com



1. how to set up the old build process
2. how to run tests using the old build process and how to verify the
results
3. how to set up the new build process on node.js


The readme.md in github.com/tiddlywiki/tiddlywiki.com should have
everything you need to know


1. is the new build process complete

 There are certainly improvements I'd like to see (eg the ability to use
http: URLs in recipe files)



1. are the tests complete
2. how to run tests using the new build process and how to verify the
results
3. how to build a TinyTiddlyWiki (old? / new? / tests?)

 I would appreciate if we could get all of the above documented in the
 @TiddlyWikiDev space.
 http://tiddlywikidev.tiddlyspace.com/#Build


It's worth noting that Eric has been maintaining this kind of information
in a standalone TiddlyWiki here:

http://tiddlywiki.com/dev/

Best wishes

Jeremy





 I'll also gladly put it there if someone would post it here...

 Cheers, Tobias.

 --
 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 http://groups.google.com/group/tiddlywikidev?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.






-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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 http://groups.google.com/group/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [twdev] Build Process for TiddlyWiki Classic

[Tobias Beer]

Thanks Jeremy,

I'll try to...

   - dig into this
   - see if I can get to set up my machine and build the thing
  - perhaps using both, the old and new process
   - see what I can bring over to TiddlyWikiDev
  - I like things at one place (less scattered)
   
Cheers, Tobias.

-- 
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 http://groups.google.com/group/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.