I don't use Firefox; most of the corps [I work with at least] disallow
firefox, no sense falling in love with something at home that I cannot
reliably use elsewhere.
Chrome yes, and no crashes in 5.1.13, but operationally its very subpar to
how things work in IE. Saving: "Thou cannot savest
Hi Brian,
better to start a new thread so that people with experience of using IE can
respond.
all the best
BJ
On Sunday, January 29, 2017 at 6:46:36 PM UTC+1, Brian McMullan wrote:
>
> First post, sorry for the intrusion in existing thread. Using TW for
> about four years, love it, moreover
Hi Brian,
Do you experience the same issues in Chrome or Firefox?
No matter what version of TiddlyWiki, Internet Explorer has never been a
well supported browser.
Personally, I'm very much for not even trying.
Best wishes,
Tobias.
--
You received this message because you are subscribed to
First post, sorry for the intrusion in existing thread. Using TW for about
four years, love it, moreover DEPEND on it. Jeremy you are a mad genius is
all I can say. But, I am experiencing significant "crashes" since 5.1.13.
Even using an empty_5.1.13 shell, navigating around and editing a
Also any logs from the server NodeJS would be helpful. Would more than one
person be editing at the same time?
On Jan 17, 2017 09:27, "Russell Cosway" wrote:
> I have started to suffer this now. I am on a MacMini running MacOS Sierra
> 10.12.2. I use Firefox 50.1.0
It sounds like server details would be good. This sounds like it could be
related to the sync mechanism somehow, but we would need to know how the
server is setup.
On Jan 17, 2017 09:27, "Russell Cosway" wrote:
> I have started to suffer this now. I am on a MacMini
I have started to suffer this now. I am on a MacMini running MacOS Sierra
10.12.2. I use Firefox 50.1.0 and autosave is enabled; I only used Firefox
for TW work. TW version is 5.1.13 and is on a node.js hosted on AWS - I
didn't set that up but could get the server setup details is needed.
I
Ok, I added the electron.js file that I pass to electron as the first
argument.
https://gist.github.com/Arlen22/45f1a460c9e348fa50ad
On Mon, Dec 26, 2016 at 7:00 PM, Arlen Beiler wrote:
> It may be a bug, and we may need to look into it.
>
> See my link in the last post,
It may be a bug, and we may need to look into it.
See my link in the last post, or quoted below, showing how to use NodeJS
data folders with Electron so it saves correctly.
Please do take all reasonable precautions in using this as well, and I
can't warrent that it is perfect, but it's for your
I see dropping modified tiddler as a bug.
I am intensively working with PBWorks at the moment (while preparing
transfer to TW in future).
PBWorks gives you all indicators of the processes taking place. I know, for
example, that saving finished when a URL with no "edit" appeared. Then,
it's
I just had an idea. The way the NodeJS server currently works is
asynchronous. It syncs with the server and then returns to the browser.
Then the server syncs to the file system and returns. If there would have
been a time where you closed your draft, waited for the check mark to turn
grey, and
Not necessarily a bug in TW per se. No one ever promised (that I know of)
that it would work on Electron. Definitely no one promised that it would
work with a custom version of Electron and if it's on a custom branch of
TW5 that depends on sensing its platform --- all bets are off.
Just
Nevertheless, this is a bug. TiddlyWiki should never lose changes no matter
how big the Tiddler is. Thanks for the info, though. I hope we can find any
problems that are causing it.
I have frankly never just used the draft idea before, I always save the
Tiddler when I am done writing. And I would
Yes it was.
On Monday, 12 December 2016 19:46:54 UTC+1, Mark S. wrote:
>
> But, was all that work -- 3 to 5 pages -- in a single tiddler?
>
> Mark
>
> On Monday, December 12, 2016 at 9:13:45 AM UTC-8, Bruno Loff wrote:
>>
>> Tiddlywiki was running on electron v1.4 on Arch Linux; the server side
But, was all that work -- 3 to 5 pages -- in a single tiddler?
Mark
On Monday, December 12, 2016 at 9:13:45 AM UTC-8, Bruno Loff wrote:
>
> Tiddlywiki was running on electron v1.4 on Arch Linux; the server side was
> running on electron's server (a node.js process), and the webpage was
>
Tiddlywiki was running on electron v1.4 on Arch Linux; the server side was
running on electron's server (a node.js process), and the webpage was
running on electron's chromium process. So all of it was localhost.
I was working on a slightly modified fork
(https://github.com/bloff/TiddlyWiki5),
You still haven't told us anything about your set-up. What browser are you
using? What operating system? Is node.js running on the same machine or a
different machine than the machine where you are working?
You say that you've lost 14 hours worth of work. But from your description,
it sounds
Hi Bruno,
Some questions:
- Which OS do you use on your client-browser? OS and Version?
- electron version?
- Is there a network connection in between, or is it localhost?
- Where does the node.js server run? OS, V?
that's it for the moment.
-m
--
You received this message
Sorry for the angry vent, that was uncalled for. I was really upset.
The bug, wherever it lies, is hard to reproduce.
I am running a node.js instance, and accessing it via the browser (actually
via a custom-made electron app which I had eventually planned to release
publicly).
When I usually
Hi,
That sucks. I've been there. Have you tried the Classic version? I
personally prefer that one and it has options that you can set to auto-save
any changes and to create backups. It is located here:
http://classic.tiddlywiki.com
-- There are also a lot of plugins and themes already out
20 matches
Mail list logo