Hi Arc
I've gone ahead and created a new further 1.0alpha14 that uses local
storage in older versions of Firefox. I'd be grateful if you could give it
a go and see how you get on,
Many thanks,
Jeremy
On Mon, Apr 22, 2013 at 8:32 PM, Jeremy Ruston jeremy.rus...@gmail.comwrote:
Hi Arc
G'day
I used to use the GTD tiddlywiki for years - left it a while back because I
stopped using one computer - and am now coming back to the concept.
Tiddlyspot is cool - and I love the look, feel and speed of tiddlywiki5,
but I have two questions
a) is tiddlywiki5 under active development?
I used to use the GTD tiddlywiki for years - left it a while back because
I stopped using one computer - and am now coming back to the concept.
Tiddlyspot is cool - and I love the look, feel and speed of tiddlywiki5,
but I have two questions
a) is tiddlywiki5 under active development? It
I noticed that it adds an span whenever you have a blank line in the html.
This was messing up some styling I had done on my tiddly wiki so I modified
the function to remove the empty spans and thought I'd share it. If anyone
knows a way to keep it from surrounding everything in spans in the
I noticed that it adds an span whenever you have a blank line in the html.
Please read the plugin documentation regarding the handling of
newlines. By default, embedded newlines are treated as TW-formatted
content and are retained in the output. If you don't want newlines to
be retained (i.e.,
I had the newlines hidden by putting
config.options.chkHTMLHideLinebreaks=true; in a tiddler with the
systemConfig tag. It still creates empty spans when it encounters
newlines. This throws off the :last-child selector unless you have no
newline between the last element and the /html tag in
Firefox 18,19,20,21,22,23 :
On every load/start this window shows up:
https://lh3.googleusercontent.com/-RWnY21JJlc4/UXbqED78A2I/AHw/mdBW2pECnCE/s1600/2013-04-23_130731.png
Outside of that everything seems to be working like normal. Wikis can
save/export/make backups and the normal
Hi Arc
Thanks, I've uploaded a new version which should fix that extraneous alert.
As things stand, users will have to re-enable permissions for each TW that
they use at the point that they upgrade Firefox to version 23. I'll have a
think about strategies for avoiding that.
Best wishes
Jeremy.
All looks good!
Re-enabling permissions per TW file isn't really bad, though if I may add a
small request on this front:
It would be awesome if there was someway to prevent being asked for
permission for permalinks.
Where as currently and for as long as I've been using TiddlyFire I have to
All looks good!
Re-enabling permissions per TW file isn't really bad, though if I may add a
small request on this front:
It would be awesome if there was someway to prevent being asked for
permission for permalinks.
Where as currently and for as long as I've been using TiddlyFire I have to
10 matches
Mail list logo
