I'm using the node server version of TW5
As an experiment I thought I could just drop new .tid files into the
tiddlers sub-directory but the system does not seem to find these files.
1) I made a tiddler called Hello
This gets saved in the tiddlers directory in a file Hello.tid
2) I copi
> I'm using the node server version of TW5
>
>
> As an experiment I thought I could just drop new .tid files into the
> tiddlers sub-directory but the system does not seem to find these files.
>
>
> 1) I made a tiddler called Hello
>
>
> This gets saved in the tiddlers directory in a file Hello.
oh, sorry! I didn't read you're post well enough
--
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 gro
my last guess: the node process should be restarted
I like using pm2 for that (npm -g install pm2 or how you do it on your
machine)
pm2 gracefulReload yourprocess is very handy
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe f
On Friday, 2 March 2018 18:16:55 UTC+1, Simon Huber wrote:
>
>
> I'm using the node server version of TW5
>>
>>
>> As an experiment I thought I could just drop new .tid files into the
>> tiddlers sub-directory but the system does not seem to find these files.
>>
>>
>> 1) I made a tiddler called
On Friday, 2 March 2018 18:20:04 UTC+1, Simon Huber wrote:
>
> my last guess: the node process should be restarted
>
Yes - silly me - I should have thought of that.
I guess the node server assumes that nobody else will muck around with the
tiddlers sub directory while it is running - a restar
Can I keep all old versions of a tiddler in TW5?
Would this be a good idea?
(Why? because I made a Wiki a few years ago that did this - and the
overheads were quite small - if you diff and compress the files)
/Joe
--
You received this message because you are subscribed to the Google Groups
"
Hi Joe
> Yes - silly me - I should have thought of that.
>
> I guess the node server assumes that nobody else will muck around with the
> tiddlers sub directory while it is running - a restart did the job.
The original plan was indeed to support external modifications to the file
system repres
Hi Joe
> Can I keep all old versions of a tiddler in TW5?
It isn’t supported at the moment. (The TiddlyWeb API does support revisions,
but the TW5 client and server just implement minimalist change count tracking
to support synchronising).
> Would this be a good idea?
Yes! It’s been on the r
Do you
1) Put all your tiddlers in one name space (ie one TW)
2) Put them into different namespaces (one TW per project)
Tiddlers should be small (in order to make them reusable)
If they are (say) on average c. 300 bytes
we could get 3 tiddlers per KB of 3K tiddlers / MB
or 3M tiddlers per GB
So
On Friday, 2 March 2018 18:52:22 UTC+1, Jeremy Ruston wrote:
>
> Hi Joe
>
> Can I keep all old versions of a tiddler in TW5?
>
>
> It isn’t supported at the moment. (The TiddlyWeb API does support
> revisions, but the TW5 client and server just implement minimalist change
> count tracking to su
On Friday, 2 March 2018 18:45:31 UTC+1, Jeremy Ruston wrote:
>
> Hi Joe
>
> Yes - silly me - I should have thought of that.
>
> I guess the node server assumes that nobody else will muck around with the
> tiddlers sub directory while it is running - a restart did the job.
>
>
> The original plan
I was wondering about attachments in the node/server version of TW5
It might be me but I find the act of attaching a file to TW5 overly
complicated,
and I still haven't figured out how to do this :-(
What I'd like:
In the TW file system there is a directory called 'attachments'
(parallel to ti
Yes, you can/must have an icon per plugin. The icon is shown in the control
panel’s plugin list.
Here is one of the more colourful examples:
https://tid.li/tw5/plugins.html#%24%3A%2FControlPanel
Good luck!
Thomas
--
You received this message because you are subscribed to the Google Groups
"T
Hi Stephan
Concerning your original question: Here is what I did in my plugin ToDoNow. It
depends on another plugin of mine called Listreveal.
In the readme I test for the presence of the other plugin and display a hint
accordingly:
!!! ~ToDoNow needs Listreveal
ToDoNow extends the power of
Thanks thomas… My question was badly worded:
Can I have one and the same icon for all my plugins - without having to
include it into each plugin.
I guess the answer is "no".
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from
Yep. I came to the same conclusion.
--
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 ema
Hi Joe,
this is most definitely possible and something I think most people in
the community already use. The way I do it is to put these "external"
files into a "files/" directory in the node server directory and add a
tiddler with the "_canonical_uri" field set to the relative path to the
fi
Hi Joe,
On Friday, March 2, 2018 at 6:52:43 PM UTC+1, joearms wrote:
...
> Tiddlers should be small (in order to make them reusable)
> If they are (say) on average c. 300 bytes
>
Tiddlers internally do have a little bit of an overhead.
We use several invisible core fields, which also need a
That's a good idea. Thanks!
--
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 tid
Hi,
On Friday, March 2, 2018 at 6:52:43 PM UTC+1, joearms wrote:
>
> 1) Put all your tiddlers in one name space (ie one TW)
> 2) Put them into different namespaces (one TW per project)
>
... It depends :) I personally use several TWs.
If we imported large numbers of tiddlers with the same nam
About namespaces:
In TW everything is a tiddler. Eg: plugins.
A plugin is a tiddler, with a content-type: application/json and a field:
plugin-type:
plugin
This tiddler contains several other tiddlers. At startup, those "content"
tiddlers are extracted into ShadowTiddlers.
See: ControlPanel
As I wrote: Everything is a tiddler:
You can explore the core structure using: The right sidebar: More:
Explorer tab
see: https://tiddlywiki.com/#%24%3A%2Fcore%2Fui%2FMoreSideBar%2FExplorer
Clicking a "blue link" will open the tiddler and show the full name.
Clicking the "folder icons" will e
On Friday, March 2, 2018 at 6:52:43 PM UTC+1, joearms wrote:
>
> Any other distinction (say by project) is tricky - ie X could belong to
> project A or B
> or both - so where do we store it???
>
With TiddlySpace (discontinued) we did explore the possibility to "include"
one "space" into an other
24 matches
Mail list logo
