[tw5] Re: Copying TW customization and configuration

2024-01-29 Thread duche...@gmail.com 
Thank you Scott, and feel free to move this discussion to  
https://talk.tiddlywiki.org if it's better there.

Here is what I did:

   1. Converted my nodejs wiki to a single file; (I tried the two methods 
   shown at 
   
https://tiddlywiki.com/static/Generating%2520Static%2520Sites%2520with%2520TiddlyWiki.html).
 

   2. Converted this single file to 5.3.3 using 
   https://tiddlywiki.com/upgrade.
   3. Loaded the upgrade file into my new 5.3.3 nodejs Tiddlywiki with: 
   /usr/local/bin/tiddlywiki mywiki --load mywiki/upgrade.html

Everything worked fine but the end result is that my 602 tiddlers are now 
merged into a single one in my new wiki.  I thought the load process would 
split the single file into different tiddlers but this is not the case.  

Am I doing something wrong or impossible?

Thank again.

Normand.

Le dimanche 28 janvier 2024 à 23:03:05 UTC-5, scott@gmail.com a écrit :

> Note that most of the tiddlywiki discussion these days takes place on 
> https://talk.tiddlywiki.org.
>
> My technique would be to save a copy of your wiki as a single-file wiki, 
> use the upgrade page at https://tiddlywiki.com/upgrade to create an 
> updated wiki, and then use the TW-node `--load` to load this into your 
> existing or (probably safer) a new node wiki. 
>
> ```text
> tiddlywiki path/to/new/wiki --init server
> tiddlywiki path/to/new/wiki --load path/to/upgrade.htm
> tiddlywiki path/to/new/wiki --listen port=6789
> ```
>
> On Sunday, January 28, 2024 at 4:23:01 PM UTC-5 Normand Duchesne wrote:
>
>> I am running TW 5.2.2. on nodejs and created a new (docker) TW nodes 
>> service running 5.3.3.  I copied the tiddlers from the original env. to the 
>> new one without issues but I would like to also copy all the customizations 
>> I did in the 5.2.2 to the new one.  I searched this group and the web 
>> unsuccessfully.  Any one could help?
>>
>> Thanks.
>>
>>
>> Normand Duchesne
>> duche...@gmail.com
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5f1dca1f-332f-4743-93ec-2437bf7c449an%40googlegroups.com.

[tw5] Edit tiddly shortcut on Firefox Mac

2021-01-03 Thread duche...@gmail.com 
Tiddlywiki 5.1.23 on nodejs.
Firefox (84.0.1) on Mac Big Sur.

Hi,

Anyone knows how to enable a shortcut to edit a tiddler?  I know about the 
ctrl-D as well as the shift-alt-D but none works.  I also tried to change 
it in the Control panel for ctrl-W, still without success.

Also, I noticed that crtl-D and shift-alt-D don't work either in Safari.

Any help will be appreciated.

Thank you.

Normand.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d09db507-5e51-485f-a223-c2dbdc9a9a9dn%40googlegroups.com.

[tw5] Re: Drag-and-drop plugins under node

2021-01-03 Thread duche...@gmail.com 
Crystal clear!  Thank you Jeremy and Mark,

Le samedi 2 janvier 2021 à 13:41:11 UTC-5, Mark S. a écrit :

> Many (most?) 3rd party plugins (including SideEditor) have not been set up 
> as node.js plugins. So you just drag and drop them to update.
>
> Third party plugins that have been set up for node.js can be placed inside 
> your node TW directory structure like this
>
> MyTiddlyWiki 
>   tiddlywiki.info 
>   tiddlers 
> (a bunch of tiddlers)
>   *plugins *
>  *myfavoriteplugin *
> *   plugin.info <http://plugin.info> (required file)*
>tiddler.td
>tiddler2.tid
>...
>  myotherfavoriteplugin 
>plugin.info (required file)
>tiddler.tid
>    ...
>
>
>
> On Saturday, January 2, 2021 at 6:13:18 AM UTC-8 duche...@gmail.com wrote:
>
>> I have the exact same case as dieg: I used tiddlywiki for a while under 
>> nodejs and importing plugins via drag and drop.
>>
>> Now with 5.1.23 I wanted like to install them the recommended way 
>> <https://tiddlywiki.com/static/Installing%2520a%2520plugin%2520from%2520the%2520plugin%2520library.html>,
>>  
>> so I added some of the officials plugins to my tiddlywiki.info file, 
>> restarted my tiddlywiki and it worked fine.
>>
>> However I missed how to install custom plugins 
>> <https://tiddlywiki.com/static/Installing%2520custom%2520plugins%2520on%2520Node.js.html>.
>>   
>> Just adding them to the .info file is obviously not sufficient and *I 
>> wonder how to download them*.  Per instance SideEditor?
>>
>> Thank you.
>> Le mercredi 30 décembre 2020 à 10:22:26 UTC-5, sil...@gmail.com a écrit :
>>
>>> You can't have your cake and eat it too ;)
>>> (just discover this translate proposal of french expression "avoir le 
>>> beurre et l'argent du beurre").
>>>
>>> Since you run Node.js server, plugins are typically served by server. 
>>> And when you update from 5.1.22 to 5.1.23, official plugins are updated 
>>> too. If you use drag, you can't benefit from this behaviour and stay 
>>> with old plugin (since it's not deal by Node.js).
>>>
>>> Sylvain
>>>
>>>
>>> Le mardi 29 décembre 2020 à 16:36:13 UTC+1, dieg...@gmail.com a écrit :
>>>
>>>>
>>>> Hello all,
>>>>
>>>> Ive been using TW on node for a while. Ive always just installed 
>>>> plugins by dragging and dropping, effectively ignoring anything having to 
>>>> do with tiddlywiki.info files.
>>>>
>>>> Today, I decided to do a "fresh install" of 5.1.23, essentially 
>>>> abandoning all of my configurations and only import my "content" tiddlers 
>>>> into a fresh server. 
>>>>
>>>> I now see the official plugin library is disabled, in favor of using 
>>>> the tiddlywiki.info file to install official plugins. Also, custom 
>>>> plugin installation is now an order of magnitude more complicated than 
>>>> previously. 
>>>>
>>>> In checking the docs there is the following: "Note that including a 
>>>> plugin as an ordinary tiddler (e.g. by dragging and dropping a plugin into 
>>>> the browser) *will result in the plugin only being active in the 
>>>> browser, and not available under Node.js*."
>>>>
>>>> What does the bold part mean? Specifically the "not available under 
>>>> node"? I only use node to run one TW instance locally. 
>>>>
>>>> I find plugin dragging and dropping to be the absolute easiest way to 
>>>> install plugins, and I would love to keep this ability under node. 
>>>>
>>>> Thanks!
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4dfe641b-0f9d-40e9-bfc0-002835c949dbn%40googlegroups.com.

[tw5] Re: Drag-and-drop plugins under node

2021-01-02 Thread duche...@gmail.com 
I have the exact same case as dieg: I used tiddlywiki for a while under 
nodejs and importing plugins via drag and drop.

Now with 5.1.23 I wanted like to install them the recommended way 
,
 
so I added some of the officials plugins to my tiddlywiki.info file, 
restarted my tiddlywiki and it worked fine.

However I missed how to install custom plugins 
.
  
Just adding them to the .info file is obviously not sufficient and *I 
wonder how to download them*.  Per instance SideEditor?

Thank you.
Le mercredi 30 décembre 2020 à 10:22:26 UTC-5, sil...@gmail.com a écrit :

> You can't have your cake and eat it too ;)
> (just discover this translate proposal of french expression "avoir le 
> beurre et l'argent du beurre").
>
> Since you run Node.js server, plugins are typically served by server. And 
> when you update from 5.1.22 to 5.1.23, official plugins are updated too. If 
> you use drag, you can't benefit from this behaviour and stay with old 
> plugin (since it's not deal by Node.js).
>
> Sylvain
>
>
> Le mardi 29 décembre 2020 à 16:36:13 UTC+1, dieg...@gmail.com a écrit :
>
>>
>> Hello all,
>>
>> Ive been using TW on node for a while. Ive always just installed plugins 
>> by dragging and dropping, effectively ignoring anything having to do with 
>> tiddlywiki.info files.
>>
>> Today, I decided to do a "fresh install" of 5.1.23, essentially 
>> abandoning all of my configurations and only import my "content" tiddlers 
>> into a fresh server. 
>>
>> I now see the official plugin library is disabled, in favor of using the 
>> tiddlywiki.info file to install official plugins. Also, custom plugin 
>> installation is now an order of magnitude more complicated than previously. 
>>
>> In checking the docs there is the following: "Note that including a 
>> plugin as an ordinary tiddler (e.g. by dragging and dropping a plugin into 
>> the browser) *will result in the plugin only being active in the 
>> browser, and not available under Node.js*."
>>
>> What does the bold part mean? Specifically the "not available under 
>> node"? I only use node to run one TW instance locally. 
>>
>> I find plugin dragging and dropping to be the absolute easiest way to 
>> install plugins, and I would love to keep this ability under node. 
>>
>> Thanks!
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/565df4c7-4e8c-4b9b-97ec-5002583a0a79n%40googlegroups.com.

[tw5] Re: TiddlyWiki node update-issue

2021-01-01 Thread duche...@gmail.com 
Hi Torax,

I had the same issue as you and fixed it with:

*sudo* npm -g update tiddlywiki
sudo systemctl restart tiddlywiki

and then refresh your tiddlywiki page in your browser.

N.

Le vendredi 1 janvier 2021 à 11:07:52 UTC-5, PMario a écrit :

> Hi, 
> Can you try: tiddlywiki --version in the command line?
>
> Then you need to _restart_ your server. ... The control panel should 
> change now.
>
> -m
>
> On Friday, January 1, 2021 at 1:53:36 PM UTC+1 torax...@googlemail.com 
> wrote:
>
>> Hi!
>>
>> at first hapyp new year.
>>
>> I tried the update from 5.1.22 => 5.1.23 with the descriped procedure via
>>
>> `npm -g update tiddlywiki`
>>
>> A short `npm -g list` shows the successfiul update in the npm-repository. 
>> But still in the control panel a version of 5.1.22 is displayed. What do I 
>> miss?
>>
>> Thanks and for a reply.
>>
>> Cheers
>> ToraxMalu
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6cf17478-88c7-453e-a30d-72ae7dd04f1an%40googlegroups.com.

[tw5] Re: What are $__StoryList_ ?

2020-12-14 Thread duche...@gmail.com 
Hi,

I use Tiddlywiki 5.1.22 on node.js v12.14.1.

I deleted them all without impact so far.  I'll watch if they reappear.

Any idea why they were created?

Thank you.

Le dimanche 13 décembre 2020 à 14:19:28 UTC-5, PMario a écrit :

> Hi,
> You can safely delete all of them! ... Then tell us, if they come back. .. 
> There may be a problem with your server setup. 
>
> So which versions do you use? TW, OS, node, ... ?
>
> -mario
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2612ef74-5993-4b79-99a0-408790bf3d53n%40googlegroups.com.

[tw5] What are $__StoryList_ ?

2020-12-13 Thread duche...@gmail.com 
Tiddlywiki 5.1.22 on node.js v12.14.1

I have 111 tiddlers named '*$__StoryList_**number'.  *I know that StoryList 
stores the river of opened tiddlers but why do I have some many created?

Thank you.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/061a07de-7157-43d6-bae5-7a12de6b9d9an%40googlegroups.com.

[tw5] Re: Twtube

2020-12-10 Thread duche...@gmail.com 
Re my last paragraph above I now understand that '' 
> from TwTube Github page 
> <https://thediveo.github.io/TwTube/output/twtube.html> suggests?
>
> Thanks again digit!
>
> Le mercredi 9 décembre 2020 à 20:07:12 UTC-5, digit...@gmail.com a écrit :
>
>> So I don't think it will work this way - trying to access it by tw 
>> import.  You have to think of it this way - *nginx is serving the file* 
>> within tiddlywiki.  nginx has to be able to serve the file separately on 
>> its own.  Here is the code I put in for the video you see in my wiki:
>>
>> ```
>> <$videojs controls="controls" fluid="fluid" width="800">
>>   https://digitalap3.com/christinemessages_0.mp4; 
>> type="video/mp4">
>> 
>> ```
>>
>> So I put the video in a place that I can directly access it from nginx if 
>> I copy paste the address in the src into the address bar.  It is the same 
>> for external images.  External images or any files are not imported 
>> directly into tiddlywiki.  Nginx is serving the file to the browser inside 
>> of tiddlywiki.  This is what makes relative addresses as your src tricky.  
>> Nginx is looking relative to the webroot in the website's config file.
>>
>> On Wednesday, December 9, 2020 at 10:42:06 AM UTC-5 duche...@gmail.com 
>> wrote:
>>
>>> I'm getting closer!
>>>
>>> One thing I missed was to import the videos using tiddlywiki import, 
>>> rather than just copying them from the server file system into mywiki 
>>> directory.  So I was missing the .meta file.
>>>
>>> Now if I put this imported name within the >> src="BigBuckBunny_SampleVideo_1280x720_1mb.mp4" type="video/mp4"/> 
>>> statement, I get an error message.
>>> If I just put the imported video name within {{ }} then I can play it, 
>>> but without any controls of the visual.js / Twtube plugin, see below.
>>> BTW I can play without issue your video that I copied into my test 
>>> tiddler, probably because this is a network location rather than a server 
>>> file.
>>>
>>> So all of this seems to lead to a file location or permission problem.  
>>> I'll have to play with Firefox Web Developer tools to find the address / 
>>> file location that is asked.
>>>
>>>
>>>
>>>>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5394a587-8ec5-43a1-89c6-134fc2a3e5f2n%40googlegroups.com.

[tw5] Re: Twtube

2020-12-10 Thread duche...@gmail.com 
Yes, it works that way, i.e. when I input the url of a file located on my 
ngnix server to the 'source src=' .

However I thought that I could also address a video located within the 
tiddlywiki folder, as we do with images.  And Tiddlywiki shows right such a 
video as it does for an image using the transclusion syntax: 
{{video.mp4}}.  The only problem is that the plugin isn't used hence no 
control on the size of it.  

Isn't it what the  statement '  ' 
from TwTube Github page 
<https://thediveo.github.io/TwTube/output/twtube.html> suggests?

Thanks again digit!

Le mercredi 9 décembre 2020 à 20:07:12 UTC-5, digit...@gmail.com a écrit :

> So I don't think it will work this way - trying to access it by tw 
> import.  You have to think of it this way - *nginx is serving the file* 
> within tiddlywiki.  nginx has to be able to serve the file separately on 
> its own.  Here is the code I put in for the video you see in my wiki:
>
> ```
> <$videojs controls="controls" fluid="fluid" width="800">
>   https://digitalap3.com/christinemessages_0.mp4; 
> type="video/mp4">
> 
> ```
>
> So I put the video in a place that I can directly access it from nginx if 
> I copy paste the address in the src into the address bar.  It is the same 
> for external images.  External images or any files are not imported 
> directly into tiddlywiki.  Nginx is serving the file to the browser inside 
> of tiddlywiki.  This is what makes relative addresses as your src tricky.  
> Nginx is looking relative to the webroot in the website's config file.
>
> On Wednesday, December 9, 2020 at 10:42:06 AM UTC-5 duche...@gmail.com 
> wrote:
>
>> I'm getting closer!
>>
>> One thing I missed was to import the videos using tiddlywiki import, 
>> rather than just copying them from the server file system into mywiki 
>> directory.  So I was missing the .meta file.
>>
>> Now if I put this imported name within the > src="BigBuckBunny_SampleVideo_1280x720_1mb.mp4" type="video/mp4"/> 
>> statement, I get an error message.
>> If I just put the imported video name within {{ }} then I can play it, 
>> but without any controls of the visual.js / Twtube plugin, see below.
>> BTW I can play without issue your video that I copied into my test 
>> tiddler, probably because this is a network location rather than a server 
>> file.
>>
>> So all of this seems to lead to a file location or permission problem.  
>> I'll have to play with Firefox Web Developer tools to find the address / 
>> file location that is asked.
>>
>>
>>
>>>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/da11e72e-2d77-4892-aabe-7e88bf514f21n%40googlegroups.com.

[tw5] Re: Twtube

2020-12-07 Thread duche...@gmail.com 

The idea to test it first on a standalone wiki is a good one so I did so 
and was very happy to see that it worked!

Unfortunately the install on my node server is still a failure and I can't 
find what I'm doing wrong.

Few questions for you (if you don't mind):


   1. Do you start the media server with '*npm start*' from the '*TheDiveO*' 
   directory?  Do you get any message like the ones I have in my print screen 
   above?  Is the media server using the same port (8080) than your tiddlywiki 
   instance (not me)?
   2. I am using a dedicated linux user (non-sudo) owning the Tiddlywiki 
   directory, is the same for you?
   3. My tiddlywiki is behind a proxy (nginx), forwarding port 443 to 
   Tiddlywiki listening on port 8080.  I didn't configure any port on the 
   proxy for the media server (on port 8090).  Do you I have to?  If so, how 
   different the server name would be  from the Tiddlywiki one?
   4. I have the current folder structure:

user@server:/mnt/VHD/mywiki/plugins/TheDiveO$ ll
total 2.1M
drwxrwxr-x  4 user user 4.0K Dec  1 18:48 editions
-rw-rw-r--  1 user user  21K Dec  1 18:48 LICENSE.md
drwxrwxr-x  2 user user 4.0K Dec  7 09:17 media
drwxrwxr-x 29 user user 4.0K Dec  1 18:49 node_modules
-rw-rw-r--  1 user user 1.2K Dec  7 10:08 package.json
-rw-rw-r--  1 user user 9.1K Dec  1 18:49 package-lock.json
-rw-rw-r--  1 user user 3.3K Dec  1 18:48 README.md
drwxrwxr-x  3 user user 4.0K Dec  1 18:48 src
-rw-rw-r--  1 user user5 Dec  7 10:09 tw.pid
-rw-rw-r--  1 user user  407 Dec  1 18:48 twtube.js
-rw-r--r--  1 user user 2.0M Dec  2 10:09 twtube.tid

Thanks again for helping out, much appreciated!  (BTW, funny video you put 
as an example!)
Le dimanche 6 décembre 2020 à 00:17:36 UTC-5, digit...@gmail.com a écrit :

> Okay I went ahead and just did it on my nodejs server.  Did just like I 
> said below and again it worked fine, as you can see here 
> <https://mainwiki.digitalap3.com/#Joe%20and%20Donald%20Grooving>
>
>
>
>
> On Thursday, December 3, 2020 at 3:24:23 PM UTC-5 duche...@gmail.com 
> wrote:
>
>>
>> I'm running Tiddlywiki 5.1.22 on node.js v12.14.1 and trying to install 
>> Twtube plugin from https://github.com/TheDiveO/TwTube.
>>
>> Sorry I'm far from being a js developer and probably missing basic js and 
>> node knowlegge.
>>
>> After I git cloned the directory above, cd into it and ran install I try 
>> to start it with "npm start".
>>
>> The media server seems to start but then issue an error message about an 
>> undefined property "addroute", see the attached image.
>>
>> Any help will be appreciated.  Thank you.[image: twtube npm start.png]
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9fceca87-56f7-4fea-8ace-2ebd73b77e9an%40googlegroups.com.