Lazy loading is working well so far, thank you very much!
On Wednesday, November 7, 2018 at 12:33:47 AM UTC, Mark S. wrote:
>
>
> TW isn't indexed like a database and doesn't scale up well. I try to keep
> it below 10M for compatibility with devices. 30-40 Megs is the upper range
> on my
Mark,
Some thoughts on what you just said.
- Turmux allows you to run nodeJS, On Top of NodeJS is TiddlyServer,
although Arlen has packaged it so you do not need to install nodeJS, I
believe you can install it into Node JS yourself, the same works for Bob.
- If you cant get Termux
Yes, tiddlyserver does this -- that's one of the main reasons to use it
instead of node.js. Do you happen to know it ts runs on Termux?
Unfortunately, my 4.2 devices can't run termux.
You can certainly use some a separate server to serve up images, etc. But
if you do the addresses will not be
I know this is off Topic, please forgive me
Mark,
You say " they have to be served up via a web-like address" and that is
exactly where I am coming from. Personally I can dump images on the
internet (my host) and reference them as URL's and load them as needed.
However for local only wikis,
As long as you're using node.js (plain), it won't solve the problem. The
browser won't let a server serve up local files -- they have to be served
up via a web-like address.
You could, of course, have a local instance of TW, and then iframe (or
_canonical_uri, or ) will allow you to use local
Sorry, let me clarify,
Place the images elsewhere and display them on demand and or from an iframe
- this means the images and the device need to be online, but they will be
pulled into the device browser cache when needed and not before.
Regards
Tony
On Wednesday, November 7, 2018 at
I'm not sure what you mean by "valid". Using iframes won't fix the node.js
image/document server problem.
One thing you can do with iframe (and probably "embed" as well) is to put
it in a macro that specifies the first part of an object path. Then when
you change to a different locale, where
Mark,
Do you think using iframes is valid ?
Regards
Tony
On Wednesday, November 7, 2018 at 11:33:47 AM UTC+11, Mark S. wrote:
>
>
> TW isn't indexed like a database and doesn't scale up well. I try to keep
> it below 10M for compatibility with devices. 30-40 Megs is the upper range
> on my
TW isn't indexed like a database and doesn't scale up well. I try to keep
it below 10M for compatibility with devices. 30-40 Megs is the upper range
on my desk-top machine.
The solution is to put images, PDF's, etc. into sub-directories.
Unfortunately plain node.js won't serve up images, etc.
It might be worth trying to keep certain kinds of content separate from or
external to the wiki. My wife has a lot of pictures she uses in her wiki,
but he keeps them in a directory next to her static html file and just
links to them instead. This keeps her html file fairly small, and the
John,
As Jeremy says, use the special address 0.0.0.0 in launching tiddlywiki and
then you can access the Wiki at the devices IP address on your local
network. Do keep in mind that the IP address is usually obtained by using a
DHCP server on the local network to issue the address. If your
Alternatively, you can use 0.0.0.0 to listen on all available network addresses.
Best wishes
Jeremy.
> On 6 Nov 2018, at 17:35, 'Mark S.' via TiddlyWiki
> wrote:
>
> How are you launching node.js/TiddlyWiki ? You need to specify the full IP
> number in order to open it to the network.
How are you launching node.js/TiddlyWiki ? You need to specify the full IP
number in order to open it to the network. Something like:
--server 8080 $:/core/save/all text/plain text/html "" "" 192.168.0.245
where 192.168.0.245 is the IP of your "server" device.
Good luck!
-- Mark
On Tuesday,
Hi John,
TiddlyWiki's node daemon defaults to listening on the 127.0.0.1 address
only - if you want to access it from other devices, you'll need to tell the
server to listen on a different address.
However, I must caution you - I think that having a server open to other
network clients on
14 matches
Mail list logo
