Discussion:
[tw] [TW5] Prerelease of v5.1.14
(too old to reply)
Jeremy Ruston
2016-10-18 13:01:07 UTC
Permalink
There’s been a rash of updates to v5.1.14 in the last 10 days, making it a good time to have a look at the prerelease at http://tiddlywiki.com/prerelease <http://tiddlywiki.com/prerelease>

I’d like to highlight the new QR code generator plugin (installed in the prerelease so that you can try it out easily). I had little idea about QR codes before the recent correspondence here on the mailing list, but am now a convert. If you don’t have a QR code reader on your smartphone I’d highly recommend installing one to play with the prerelease.

Basically, QR codes can be used to transfer any block of text that isn’t too long/complicated to fit. There are conventions for passing URLs, contact information, wifi details etc., but there is complete freedom; one can make a QR code of JSON if you want (actually a bad idea as the special characters appear to compress badly).

The QR code plugin adds a generic macro for generating a QR code from a string, and also adds a couple of pre-built ways to use it:

* A new view toolbar button that displays the current tiddler as a QR code. You can choose from the URL of the tiddler, the raw text, or the rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes

Once I’d found the library, getting the plugin up and running was surprisingly easy — I had the first operational version within 30 minutes of starting work. A good illustration of the excellent returns on the effort involved in integrating existing JavaScript components.

There’s a full list of changes in the release note, but I’d highlight the following bigger changes:

* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
* Improved access to plugin information:
** New “Plugins” tab in the “More” sidebar tab, listing all installed plugins
** Better display of plugin tiddlers themselves, duplicating the gadget used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings according to HTML encoding, URI encoding, regexp escaping and JavaScript string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files Files within TiddlyWikiFolders

I’d like to get v5.1.14 released in the next couple of weeks, so any feedback/thoughts/questions are much appreciated at this point.

As ever, thanks to everyone listed in the release note for their contributions to this release.

Best wishes

Jeremy.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/AF2B9AB9-0E8A-4A96-9FF5-981A3B78B239%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Sylvain Naudin
2016-10-18 19:10:26 UTC
Permalink
Hi Jeremy,

It's a good idea for QrCode, thanks for this improvement.

I've see the new print icon, how use it ? I've see WidgetMessage: tm-print,
but don't help me ;)


Regards,
Sylvain
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/be58a35a-f208-4720-ba70-7e49100c71ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thomas Elmiger
2016-10-18 20:59:10 UTC
Permalink
Hi Jeremy

I played a bit with MECARD and the QR plugin. It seems to generate about
the same codes as the Google API (I did not compare pixels), great stuff!

Most of the scanners on my iPhone (Scan, NeoReader, i-nigma, RedLaser) lose
some content of my test card (either the birthday, the second email address
the second phone number or the postal address), *NeoReader* is the only one
that gets it all right. So the MECARD reception/transfer is much worse than
vcard. But the most important information from my point of view is the URL
– and this goes through in every app I have. Would you consider to add the
URL to your example, please?

Here’s an anonymized version of my test content:

MECARD:N:Tester,Thomas;TEL:+99443099090;TEL:+99795678906;EMAIL:***@example.com;EMAIL:***@example.com;NOTE:Test
Content;BDAY:19160812;ADR:Husacherstrasse
303,Wallisellen-ZÃŒrich,,8910;Schweiz;URL:http://thomas-elmiger.ch;

Advantages of MECARD in my eyes: it has a nice compact format, not far away
from dictionary tiddlers 
 and there were no problems with German umlauts.

Thanks again and good luck!
Thomas
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/eb96bd8d-4c8a-4f94-875e-794ac175a844%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
'Mark S.' via TiddlyWiki
2016-10-19 14:37:55 UTC
Permalink
On my aging Samsung tablet, using the eponymous "Barcode Scanner" by zxing,
I was able to read all your contact data generated by TW from the computer
screen. Were you scanning a computer screen, a printed page, or another
small screen? Does it help if you change the error correction level?

Good luck,
Mark
Post by Sylvain Naudin
Hi Jeremy
I played a bit with MECARD and the QR plugin. It seems to generate about
the same codes as the Google API (I did not compare pixels), great stuff!
Most of the scanners on my iPhone (Scan, NeoReader, i-nigma, RedLaser)
lose some content of my test card (either the birthday, the second email
address the second phone number or the postal address), *NeoReader* is
the only one that gets it all right. So the MECARD reception/transfer is
much worse than vcard. But the most important information from my point of
view is the URL – and this goes through in every app I have. Would you
consider to add the URL to your example, please?
MECARD:N:Tester,
Content;BDAY:19160812;ADR:Husacherstrasse
303,Wallisellen-ZÃŒrich,,8910;Schweiz;URL:http://thomas-elmiger.ch;
Advantages of MECARD in my eyes: it has a nice compact format, not far
away from dictionary tiddlers 
 and there were no problems with German
umlauts.
Thanks again and good luck!
Thomas
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c1ff955d-e999-4176-a720-89b5e1ff56b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thomas Elmiger
2016-10-19 15:25:48 UTC
Permalink
Hi Mark, if your questions are adressed to me: I was scanning with an
iPhone SE (HiRes Camera) from a HiRes-Screen (Retina MacBook). So the
QR-reader apps are the problem. I will check if there are updates
available.

Cheers, Thomas
Were you scanning a computer screen, a printed page, or another small
screen? Does it help if you change the error correction level?
Good luck,
Mark
Post by Sylvain Naudin
Hi Jeremy
I played a bit with MECARD and the QR plugin. It seems to generate about
the same codes as the Google API (I did not compare pixels), great stuff!
Most of the scanners on my iPhone (Scan, NeoReader, i-nigma, RedLaser)
lose some content of my test card (either the birthday, the second email
address the second phone number or the postal address), *NeoReader* is
the only one that gets it all right. So the MECARD reception/transfer is
much worse than vcard. But the most important information from my point of
view is the URL – and this goes through in every app I have. Would you
consider to add the URL to your example, please?
MECARD:N:Tester,Thomas;TEL:+99443099090;TEL:+99795678906;EMA
Content;BDAY:19160812;ADR:Husacherstrasse 303,Wallisellen-ZÃŒrich,,8910;S
chweiz;URL:http://thomas-elmiger.ch;
Advantages of MECARD in my eyes: it has a nice compact format, not far
away from dictionary tiddlers 
 and there were no problems with German
umlauts.
Thanks again and good luck!
Thomas
--
You received this message because you are subscribed to a topic in the
Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/tiddlywiki/sKv57A9-eCk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/
msgid/tiddlywiki/c1ff955d-e999-4176-a720-89b5e1ff56b3%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/c1ff955d-e999-4176-a720-89b5e1ff56b3%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CALXLrTjBxJp6xFdTksCwuD-hoAn4Tc%2BeugO1PAHs%3D-ktiOcc7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Greg Davis
2016-10-19 01:51:11 UTC
Permalink
Hi Jeremy,

Quick look, loading some of my favorite plugins and didn't notice any
problems. Neat that QR codes work offline. Here is a quick example of a QR
Bookmark TW: http://qrbookmark.tiddlyspot.com

More exploring to do.

Best,
Greg
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/214bc0a1-5197-4cc3-8da2-ff92b083e9f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
'Mark S.' via TiddlyWiki
2016-10-19 14:32:27 UTC
Permalink
Hi Jeremy,

Cool stuff. A single line showing the invocation of the macro would be
helpful as well. I know it may seem obvious to you, but it won't be to
everyone.

My proposed use case for QR is to take books (like files, but made of wood
pulp) and put them in a box. A QR code on the box creates a URL that leads
to a web site with images of the books (currently shared Evernote pages,
but that could change to a TW subdirectory), so I can quickly verify if the
box has what I'm looking for. This would be useful on moving day as well.
The list of books is in a tiddler as well, so that I can find the box in
the first place.

Thanks!
Mark
Post by Jeremy Ruston
There’s been a rash of updates to v5.1.14 in the last 10 days, making it a
good time to have a look at the prerelease at
http://tiddlywiki.com/prerelease
I’d like to highlight the new QR code generator plugin (installed in the
prerelease so that you can try it out easily). I had little idea about QR
codes before the recent correspondence here on the mailing list, but am now
a convert. If you don’t have a QR code reader on your smartphone I’d highly
recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t
too long/complicated to fit. There are conventions for passing URLs,
contact information, wifi details etc., but there is complete freedom; one
can make a QR code of JSON if you want (actually a bad idea as the special
characters appear to compress badly).
The QR code plugin adds a generic macro for generating a QR code from a
* A new view toolbar button that displays the current tiddler as a QR
code. You can choose from the URL of the tiddler, the raw text, or the
rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was
surprisingly easy — I had the first operational version within 30 minutes
of starting work. A good illustration of the excellent returns on the
effort involved in integrating existing JavaScript components.
There’s a full list of changes in the release note, but I’d highlight the
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed
plugins
** Better display of plugin tiddlers themselves, duplicating the gadget
used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a
filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings
according to HTML encoding, URI encoding, regexp escaping and JavaScript
string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files
Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any
feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their
contributions to this release.
Best wishes
Jeremy.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/e70d116c-05b1-420b-b564-82b854ee4191%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Mat
2016-10-19 18:18:00 UTC
Permalink
QR - very cool! But I must admit I must do some more thinking on what to
actually use it for :-)

@Jeremy
Could it be that the QR plugin has dependencies that are not stated? I
suspect this because a simple test here <http://testingqr.tiddlyspot.com/> ,
i.e an empty TW into which I merely dragged only the QR plugin, does give
QR codes but they don't function properly. An identical tiddler in the
prerelease does function.

<:-)
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/03c19dfc-2910-456c-90b9-491d28381223%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jeremy Ruston
2016-10-19 19:38:52 UTC
Permalink
Hi Mat

The QR code plugin is part of the 5.1.14 prerelease, and won't work with older versions like 5.1.13,

Remember that this is not the time to adopt 5.1.14 for regular work, of course.

Best wishes

Jeremy

--
Jeremy Ruston
***@jermolene.com
http://jermolene.com
QR - very cool! But I must admit I must do some more thinking on what to actually use it for :-)
@Jeremy
Could it be that the QR plugin has dependencies that are not stated? I suspect this because a simple test here , i.e an empty TW into which I merely dragged only the QR plugin, does give QR codes but they don't function properly. An identical tiddler in the prerelease does function.
<:-)
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/03c19dfc-2910-456c-90b9-491d28381223%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/F5D6F6B9-0A14-4C2C-BD65-A0972594A1A9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Greg Davis
2016-10-19 23:39:39 UTC
Permalink
Hi,

@Mat

In ver. 5.1.13 the tiddler toolbar does not seem to work but it can
generate a good QR code. Tried a few and seemed to work for URL links. As
Jeremy implied, no guarantees on earlier versions. Example:


<Loading Image...>
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/714d699e-ab2a-4a3d-986b-3a96271f2342%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Mat
2016-10-20 08:38:38 UTC
Permalink
Jeremy thanks for reply

I would suggest that all plugin dependencies are explicitly stated (as they
often are). In this case I guess it would be "requires 5.1.14". A reason
for this can be illustrated with a case of my own; I have at least one TW
where my tweaks (mostly page layout) conflict with later updates so it is
"stuck" at 5.1.10, which is OK in this case as it works well enough for its
purpose. I assume this is not a typical use case but still not totally
uncommon. I'd thnk that people leaving the newbie stage and passing onto
more advanced tweaking trying to e.g integrate a TW with some other system
etc might end up in this. Just guessing. Anyway, for these cases it is
valuable to know a plugins backward compatibility and other dependencies.
...

Apropos QR in general, they remind me of Identicons link1
<https://en.wikipedia.org/wiki/Identicon> link2 <http://identicon.net/>.
Possibly this is a use case for TWederation and twCards. (BTW I currently
don't have the needed time to devote to TWederation dev but will, of
course, proceed at some future date.)

Again, thanks for a cool plugin! And overall thanks for yet more power in
our little baby.


@Greg - I found the generated qr image for e.g the url did not work
properly in 5.1.13. When it does work properly, my qr reader (android "QR
Scanner") automatically visits the url, but the qr image from 5.1.13 merely
shows e.g "#testingtesting" and not the full url.


<:-)
Post by Greg Davis
Hi,
@Mat
In ver. 5.1.13 the tiddler toolbar does not seem to work but it can
generate a good QR code. Tried a few and seemed to work for URL links. As
<https://lh3.googleusercontent.com/-l607ewoKlms/WAgDNbD3xZI/AAAAAAAAAEI/SeRrkeaScyYKUVpwB4Cj8ChHmbrIxQC1QCLcB/s1600/Test_Plugin_%25E2%2580%2594_5.1.13.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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/0cdd3cc1-4638-4f1d-b6e9-d69031ba19ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jeremy Ruston
2016-10-20 08:43:18 UTC
Permalink
Hi Mat
I would suggest that all plugin dependencies are explicitly stated (as they often are). In this case I guess it would be "requires 5.1.14". A reason for this can be illustrated with a case of my own; I have at least one TW where my tweaks (mostly page layout) conflict with later updates so it is "stuck" at 5.1.10, which is OK in this case as it works well enough for its purpose. I assume this is not a typical use case but still not totally uncommon. I'd thnk that people leaving the newbie stage and passing onto more advanced tweaking trying to e.g integrate a TW with some other system etc might end up in this. Just guessing. Anyway, for these cases it is valuable to know a plugins backward compatibility and other dependencies.
The core plugins and the TiddlyWiki core itself are in lockstep. There is no support for backporting plugins to earlier versions. You can experiment at your own risk, of course.

There is a partially implemented mechanism for plugins to enforce a minimum core version number. If we switched it on it would make life harder for the people who do want to experiment with backporting.
Apropos QR in general, they remind me of Identicons link1 <https://en.wikipedia.org/wiki/Identicon> link2 <http://identicon.net/>. Possibly this is a use case for TWederation and twCards. (BTW I currently don't have the needed time to devote to TWederation dev but will, of course, proceed at some future date.)
Well, a QR code could be a means of federating a tiddler, but of course it would only work for very short tiddlers.


Best wishes

Jeremy
Again, thanks for a cool plugin! And overall thanks for yet more power in our little baby.
@Greg - I found the generated qr image for e.g the url did not work properly in 5.1.13. When it does work properly, my qr reader (android "QR Scanner") automatically visits the url, but the qr image from 5.1.13 merely shows e.g "#testingtesting" and not the full url.
<:-)
Hi,
@Mat
<https://lh3.googleusercontent.com/-l607ewoKlms/WAgDNbD3xZI/AAAAAAAAAEI/SeRrkeaScyYKUVpwB4Cj8ChHmbrIxQC1QCLcB/s1600/Test_Plugin_%25E2%2580%2594_5.1.13.png>
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
Visit this group at https://groups.google.com/group/tiddlywiki <https://groups.google.com/group/tiddlywiki>.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/0cdd3cc1-4638-4f1d-b6e9-d69031ba19ae%40googlegroups.com <https://groups.google.com/d/msgid/tiddlywiki/0cdd3cc1-4638-4f1d-b6e9-d69031ba19ae%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout>.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/5F01C786-C780-4122-B9FF-B403E108789E%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Mat
2016-10-20 09:11:58 UTC
Permalink
Jeremy,

The core plugins and the TiddlyWiki core itself are in lockstep.
Makes sense but it is not explicitly stated so how would a user know this?
In the case of the QR plugin, it *seems *to work in 5.1.13 but doesn't
fully.


There is a partially implemented mechanism for plugins to enforce a minimum
Post by Jeremy Ruston
core version number.
Yea, enforcing it is beyond what I'd suggest but that detection mechanism
sounds like it could be used to inform the user about the discrepancy.

<:-)
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/637633f1-f6e1-42d1-b3cc-6e8e3eea48ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jeremy Ruston
2016-10-20 09:20:23 UTC
Permalink
Hi Mat
Makes sense but it is not explicitly stated so how would a user know this? In the case of the QR plugin, it seems to work in 5.1.13 but doesn't fully.
Fair point. To me it seems obvious that one can’t drop a bit of Windows 10 into a Windows 8 installation and expect it to work, but obviously my perspective is warped by being a developer.

But documenting it doesn’t feel sufficient (partly because people often don’t read documentation).
There is a partially implemented mechanism for plugins to enforce a minimum core version number.
Yea, enforcing it is beyond what I'd suggest but that detection mechanism sounds like it could be used to inform the user about the discrepancy.
Yes, but none of it feels like much of a priority to be honest. If somebody does come along and try a new plugin against an old core, if it works they’re happy, and if not, there’s a teachable moment about software compatibility :)

Best wishes

Jeremy
<:-)
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
Visit this group at https://groups.google.com/group/tiddlywiki <https://groups.google.com/group/tiddlywiki>.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/637633f1-f6e1-42d1-b3cc-6e8e3eea48ae%40googlegroups.com <https://groups.google.com/d/msgid/tiddlywiki/637633f1-f6e1-42d1-b3cc-6e8e3eea48ae%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout>.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8948785D-4EE6-4A1C-AC77-37ED194AA08B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Jeremy Ruston
2016-10-20 09:23:47 UTC
Permalink
Hi Everyone

Thanks for the feedback. Some specific comments:

John - yes, the built-in toolbar button to produce a “URL of the current tiddler” produces the same permalink that you’d get clicking the “permalink” button, linking directly to the tiddler in question. It’s a URL to the tiddler, not the wiki.

Mark - I’ve updated the QR code plugin docs with some examples

Thomas - are you suggesting that we provide a vCard example instead or alongside the MECARD example?

Sylvain - I’ve added a proper page control button for the print function

I’ll update the prerelease later today after some further updates,

Best wishes

Jeremy.
Post by Jeremy Ruston
Hi Mat
I would suggest that all plugin dependencies are explicitly stated (as they often are). In this case I guess it would be "requires 5.1.14". A reason for this can be illustrated with a case of my own; I have at least one TW where my tweaks (mostly page layout) conflict with later updates so it is "stuck" at 5.1.10, which is OK in this case as it works well enough for its purpose. I assume this is not a typical use case but still not totally uncommon. I'd thnk that people leaving the newbie stage and passing onto more advanced tweaking trying to e.g integrate a TW with some other system etc might end up in this. Just guessing. Anyway, for these cases it is valuable to know a plugins backward compatibility and other dependencies.
The core plugins and the TiddlyWiki core itself are in lockstep. There is no support for backporting plugins to earlier versions. You can experiment at your own risk, of course.
There is a partially implemented mechanism for plugins to enforce a minimum core version number. If we switched it on it would make life harder for the people who do want to experiment with backporting.
Apropos QR in general, they remind me of Identicons link1 <https://en.wikipedia.org/wiki/Identicon> link2 <http://identicon.net/>. Possibly this is a use case for TWederation and twCards. (BTW I currently don't have the needed time to devote to TWederation dev but will, of course, proceed at some future date.)
Well, a QR code could be a means of federating a tiddler, but of course it would only work for very short tiddlers.
Best wishes
Jeremy
Again, thanks for a cool plugin! And overall thanks for yet more power in our little baby.
@Greg - I found the generated qr image for e.g the url did not work properly in 5.1.13. When it does work properly, my qr reader (android "QR Scanner") automatically visits the url, but the qr image from 5.1.13 merely shows e.g "#testingtesting" and not the full url.
<:-)
Hi,
@Mat
<https://lh3.googleusercontent.com/-l607ewoKlms/WAgDNbD3xZI/AAAAAAAAAEI/SeRrkeaScyYKUVpwB4Cj8ChHmbrIxQC1QCLcB/s1600/Test_Plugin_%25E2%2580%2594_5.1.13.png>
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
Visit this group at https://groups.google.com/group/tiddlywiki <https://groups.google.com/group/tiddlywiki>.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/0cdd3cc1-4638-4f1d-b6e9-d69031ba19ae%40googlegroups.com <https://groups.google.com/d/msgid/tiddlywiki/0cdd3cc1-4638-4f1d-b6e9-d69031ba19ae%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout>.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/E0C6C2AF-FA03-4596-84DD-5F0DC9AF6F84%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Thomas Elmiger
2016-10-20 12:13:14 UTC
Permalink
Hi Jeremy

When I think over it, a vCard example alongside would be great. In my eyes
the "workflow" for vCards is very straightforward: drop a .vcf file on your
TW, import, go to the imported tiddler, open QR, scan. Maybe you want to
mention this in the docs?
My second suggestion would be to add a URL input field to the MECARD
example (as this would be the most important field for me and it worked
flawlessly in my tests).
Post by Jeremy Ruston
Thomas - are you suggesting that we provide a vCard example instead or
alongside the MECARD example?
Thanks a lot!
Thomas
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CALXLrTjN5QF_%2B2x_CkD6hTTZNV7OoeannbuWp1aVLXFKzxs%2BEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
John Newell
2016-10-20 09:19:10 UTC
Permalink
Excited about checking out the new release....
I am quite a fan of QR codes -
they have the ability to be read "on the fly" = off shop windows, building
entrances, exhibition stands, billboard signage - from close up to quite
some distance.
they also have the capacity to be great for virtual business card delivery,
web addresses, delivery of documentation ( eg link to a hosted PDF ) - and
instant "on-mobile" opening of prepared email sends, etc etc

The HUGE advantage for a hosted TW file delivering a tiddler QR code is the
time saving in having all these options prepared IN A TIDDLER, then quickly
converted to a QRCode.( a simple "create" tiddler - then QR code - then
distribute.


There is one desirable I would prompt - for times when the TW is hosted :
Assuming a complete TW.html file is hosted at : 1234wxyz.com.
Creating a tiddler "PurpleRain" would deliver that tiddler via URL -
http://1234wxyz.com/#PurpleRain
IF the QR code could create THAT ADDRESS - THAT is very convenient for
online / hosted tiddlers that deliver :

- embedded video or audio
- embedded social media accounts
- a customer to the URL for your website, order page or social media
accounts
- a text message - of thanks / directions / important information
- a discount coupon / and invitation etc
- an embedded Google Map wrapped within your business info on-page
- your price list
- additional product / service informatiom
- a pocket offline edition of your website ( full TW file )
- "share' links to social media accounts to encourage co-propomotion (
especially as they are holding a phone / camera / comm-device!


So, my question at the end of this is - can the links to an online delivery
of both a complete TW file
or an exported TW page ( tiddler ) be produced?

cheers
John
Post by Jeremy Ruston
There’s been a rash of updates to v5.1.14 in the last 10 days, making it a
good time to have a look at the prerelease at
http://tiddlywiki.com/prerelease
I’d like to highlight the new QR code generator plugin (installed in the
prerelease so that you can try it out easily). I had little idea about QR
codes before the recent correspondence here on the mailing list, but am now
a convert. If you don’t have a QR code reader on your smartphone I’d highly
recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t
too long/complicated to fit. There are conventions for passing URLs,
contact information, wifi details etc., but there is complete freedom; one
can make a QR code of JSON if you want (actually a bad idea as the special
characters appear to compress badly).
The QR code plugin adds a generic macro for generating a QR code from a
* A new view toolbar button that displays the current tiddler as a QR
code. You can choose from the URL of the tiddler, the raw text, or the
rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was
surprisingly easy — I had the first operational version within 30 minutes
of starting work. A good illustration of the excellent returns on the
effort involved in integrating existing JavaScript components.
There’s a full list of changes in the release note, but I’d highlight the
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed
plugins
** Better display of plugin tiddlers themselves, duplicating the gadget
used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a
filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings
according to HTML encoding, URI encoding, regexp escaping and JavaScript
string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files
Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any
feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their
contributions to this release.
Best wishes
Jeremy.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3c577350-90be-402a-923c-006f7ed16225%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
PMario
2016-10-20 12:27:58 UTC
Permalink
Post by John Newell
Assuming a complete TW.html file is hosted at : 1234wxyz.com.
Creating a tiddler "PurpleRain" would deliver that tiddler via URL -
http://1234wxyz.com/#PurpleRain
You may want to use https://www.example.com/ for examples. example.com is
designed to be used like this.
The above URLs may point to valid domains, if someone registers them.

Just a thought.
-m
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/a7eb69f0-1427-4d5e-b45a-ac5869b12f5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
John Newell
2016-10-21 04:44:53 UTC
Permalink
Good thought - thanks for that advice ( first I knew of an actual
www.example.com page ) cheers
Post by PMario
Assuming a complete TW.html file is hosted at : 1234wxyz . com.
Creating a tiddler "PurpleRain" would deliver that tiddler via URL -
http:// 1234wxyz . com/#PurpleRain
You may want to use https://www.example.com/ for examples. example.com
is designed to be used like this.
The above URLs may point to valid domains, if someone registers them.
Just a thought.
-m
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/690a879d-36cc-4b1a-ba64-e00a3157cbdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
jwd
2016-10-21 01:34:20 UTC
Permalink
Not to be a wet blanket but ...
Post by Jeremy Ruston
Basically, QR codes can be used to transfer any block of text that isn’t
too long/complicated to fit.

And that, of course, leads to the downsides of QR codes, e.g.,
https://www.owasp.org/index.php/Qrljacking - the misuse of QR Codes to do
not so nice things.

It seems to me that folks who use them on TW sites that allow federated
content are going to be implicitly trusting every other person with write
access to that federated content. Even static TW's on public sites are
going to have the same implications. It does not seem that there is
anything keeping from me putting a QR Code in a tiddler claiming to be my
contact info but instead sending the unsuspecting user to a phishing web
site first, or a Rick Roll. Or it might not be me but someone who simply
has obtained my login information to that publicly accessible content.
Maybe using Qrljacking.

The TW community seems to be a very helpful one. But with its popularity
and capabilities increasing I am not sure that will remain universally true
indefinitely. A google of 'qr code vulnerabilities' mentions might give you
pause.
--
Jonathan
Post by Jeremy Ruston
There’s been a rash of updates to v5.1.14 in the last 10 days, making it a
good time to have a look at the prerelease at
http://tiddlywiki.com/prerelease
I’d like to highlight the new QR code generator plugin (installed in the
prerelease so that you can try it out easily). I had little idea about QR
codes before the recent correspondence here on the mailing list, but am now
a convert. If you don’t have a QR code reader on your smartphone I’d highly
recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t
too long/complicated to fit. There are conventions for passing URLs,
contact information, wifi details etc., but there is complete freedom; one
can make a QR code of JSON if you want (actually a bad idea as the special
characters appear to compress badly).
The QR code plugin adds a generic macro for generating a QR code from a
* A new view toolbar button that displays the current tiddler as a QR
code. You can choose from the URL of the tiddler, the raw text, or the
rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was
surprisingly easy — I had the first operational version within 30 minutes
of starting work. A good illustration of the excellent returns on the
effort involved in integrating existing JavaScript components.
There’s a full list of changes in the release note, but I’d highlight the
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed
plugins
** Better display of plugin tiddlers themselves, duplicating the gadget
used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a
filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings
according to HTML encoding, URI encoding, regexp escaping and JavaScript
string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files
Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any
feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their
contributions to this release.
Best wishes
Jeremy.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8a7817c2-159d-4c5c-8fd9-d53d92443207%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
John Newell
2016-10-21 04:53:45 UTC
Permalink
Not trying too much to throw a blanket over the "wet blanket" post - but :

Whilst your observations are mostly valid - DANGER really only (possibly)
applies if the TW file is editable by people other than the original author.
If YOU are the only person adding QR codes - you should know what you're
delivering.

In order to keep the QR codes valid and safe - it is up to the author to
RE-ASSURE the reader and provide some basic details that assist in that
trust -
you can find more information on this link *http://bit.ly/QRcodes1
<http://badqr.pen.io>* along with an example and an APP to provide you the
information about the end result of activating the QR redirection - by
showing you what to expect. The NORTON App is free and well-respected.
Post by jwd
Not to be a wet blanket but ...
Post by Jeremy Ruston
Basically, QR codes can be used to transfer any block of text that isn’t
too long/complicated to fit.
And that, of course, leads to the downsides of QR codes, e.g.,
https://www.owasp.org/index.php/Qrljacking - the misuse of QR Codes to do
not so nice things.
It seems to me that folks who use them on TW sites that allow federated
content are going to be implicitly trusting every other person with write
access to that federated content. Even static TW's on public sites are
going to have the same implications. It does not seem that there is
anything keeping from me putting a QR Code in a tiddler claiming to be my
contact info but instead sending the unsuspecting user to a phishing web
site first, or a Rick Roll. Or it might not be me but someone who simply
has obtained my login information to that publicly accessible content.
Maybe using Qrljacking.
The TW community seems to be a very helpful one. But with its popularity
and capabilities increasing I am not sure that will remain universally true
indefinitely. A google of 'qr code vulnerabilities' mentions might give you
pause.
--
Jonathan
Post by Jeremy Ruston
There’s been a rash of updates to v5.1.14 in the last 10 days, making it
a good time to have a look at the prerelease at
http://tiddlywiki.com/prerelease
I’d like to highlight the new QR code generator plugin (installed in the
prerelease so that you can try it out easily). I had little idea about QR
codes before the recent correspondence here on the mailing list, but am now
a convert. If you don’t have a QR code reader on your smartphone I’d highly
recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t
too long/complicated to fit. There are conventions for passing URLs,
contact information, wifi details etc., but there is complete freedom; one
can make a QR code of JSON if you want (actually a bad idea as the special
characters appear to compress badly).
The QR code plugin adds a generic macro for generating a QR code from a
* A new view toolbar button that displays the current tiddler as a QR
code. You can choose from the URL of the tiddler, the raw text, or the
rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was
surprisingly easy — I had the first operational version within 30 minutes
of starting work. A good illustration of the excellent returns on the
effort involved in integrating existing JavaScript components.
There’s a full list of changes in the release note, but I’d highlight the
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed
plugins
** Better display of plugin tiddlers themselves, duplicating the gadget
used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a
filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings
according to HTML encoding, URI encoding, regexp escaping and JavaScript
string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files
Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any
feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their
contributions to this release.
Best wishes
Jeremy.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/f573c0b0-0860-4d42-97f8-ca850f169308%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jeremy Ruston
2016-10-21 07:45:45 UTC
Permalink
Hi Jonathan
Not to be a wet blanket but 

Not at all, it’s a good discussion to have.
Post by Jeremy Ruston
Basically, QR codes can be used to transfer any block of text that isn’t too long/complicated to fit.
And that, of course, leads to the downsides of QR codes, e.g., https://www.owasp.org/index.php/Qrljacking - the misuse of QR Codes to do not so nice things.
Most of that article is about a specific usage of QR codes to contain login credentials for an online service.

But really all the risks that are discussed are the risks associated with links to malware. The problem is trusting hyperlinks, and it doesn’t matter whether those links are distributed via email, a website, a QR code, Bluetooth, or some other means.

In the particular case of QR codes, the biggest risks are associated with reader software that automatically navigates to URLs; that’s as bad as an email app that renders untrusted HTML content.
It seems to me that folks who use them on TW sites that allow federated content are going to be implicitly trusting every other person with write access to that federated content.
A critical point to grasp about federation is that there is no requirement for shared access to a common server. Every participant publishes on their own server, and the client software retrieves the distributed fragments of a discussion, and threads them together for reading.
Even static TW's on public sites are going to have the same implications. It does not seem that there is anything keeping from me putting a QR Code in a tiddler claiming to be my contact info but instead sending the unsuspecting user to a phishing web site first, or a Rick Roll. Or it might not be me but someone who simply has obtained my login information to that publicly accessible content. Maybe using Qrljacking.
As noted above, this is no different than the risks of clicking on an ordinary HTML hyperlink.
The TW community seems to be a very helpful one. But with its popularity and capabilities increasing I am not sure that will remain universally true indefinitely. A google of 'qr code vulnerabilities' mentions might give you pause.
I did google that phrase, and think the results are actually pretty misleading. Security is a complex business, and these articles evoke the overly simple idea that QR codes have intrinsic vulnerabilities.

Best wishes

Jeremy
--
Jonathan
There’s been a rash of updates to v5.1.14 in the last 10 days, making it a good time to have a look at the prerelease at http://tiddlywiki.com/prerelease <http://tiddlywiki.com/prerelease>
I’d like to highlight the new QR code generator plugin (installed in the prerelease so that you can try it out easily). I had little idea about QR codes before the recent correspondence here on the mailing list, but am now a convert. If you don’t have a QR code reader on your smartphone I’d highly recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t too long/complicated to fit. There are conventions for passing URLs, contact information, wifi details etc., but there is complete freedom; one can make a QR code of JSON if you want (actually a bad idea as the special characters appear to compress badly).
* A new view toolbar button that displays the current tiddler as a QR code. You can choose from the URL of the tiddler, the raw text, or the rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was surprisingly easy — I had the first operational version within 30 minutes of starting work. A good illustration of the excellent returns on the effort involved in integrating existing JavaScript components.
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed plugins
** Better display of plugin tiddlers themselves, duplicating the gadget used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings according to HTML encoding, URI encoding, regexp escaping and JavaScript string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their contributions to this release.
Best wishes
Jeremy.
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
Visit this group at https://groups.google.com/group/tiddlywiki <https://groups.google.com/group/tiddlywiki>.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8a7817c2-159d-4c5c-8fd9-d53d92443207%40googlegroups.com <https://groups.google.com/d/msgid/tiddlywiki/8a7817c2-159d-4c5c-8fd9-d53d92443207%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout>.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2494DA1F-33FC-487E-A31E-F26B87A37B7A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Jed Carty
2016-10-21 12:08:47 UTC
Permalink
As far as security goes, as my work on federation has reminded me over and
over again, security is nuanced. QR codes don't pose any security risk to
anyone, the problem is that many QR code readers don't do any sort of
sanitation and often lack basic security features. Just about all of the
trouble from QR codes comes from naive developers assuming that nothing bad
can come from a QR code, and users trusting them.

Please don't make the mistake of confusing the statement 'there are
security concerns associated with using QR codes' with 'QR codes are a
security concern'. The horror that is browser security standards is full of
places where those two ideas have been confused and it makes developing the
federation things for tiddlywiki very annoying when it doesn't have to be.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1e8d9beb-ea64-4c23-b839-ff7d048cc8aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Atul Grover
2016-10-27 11:16:59 UTC
Permalink
Hi Jeremy,

Kudos for bringing QR and XLSX to TW5.

I was struggling with with .xls to csv to json conversion. I found .json
import responded differently (at least sometimes...even when I am not
drunk!!!) in firefox and crome.
It is great to have the xlsx plugin for TW5.

Also, would it be advisable to have 'CUSTOM CONTENT' as an option in QR
dropdown?
In my use case some tiddlers are referring to a external pdf (from another
website).
QR code linking to that pdf would enable direct download on to the
learner's phone/tablet.

We could have another column for QR (besides title, text, tag....) which
will be the custom content shown on the QR code (for that particular
tiddler). What do you think?

Regards
AG
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/41d2ae79-2865-4ecb-b9fc-2fb719b4462c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Atul Grover
2016-10-27 11:44:57 UTC
Permalink
We could also do with a smaller size of the QR image (to fit appropriately
on mobile devices).
I can ctrl(-) to make the QR image smaller on my laptop, but no such luck
on my phone.
Regards
Ag
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/68804d82-0e08-44f1-bb81-4f3eb910ce46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
'Mark S.' via TiddlyWiki
2016-12-16 23:14:06 UTC
Permalink
While the QR code is neat, could it's icon be move to the left of the
closing icon? All my instincts are to always look for the closing icon in
the upper right hand corner. Having the QR code, an occasional activity,
take over the position of the closing action, an always-needed activity,
breaks up the work flow.

Thanks for listening,
Mark
Post by Jeremy Ruston
There’s been a rash of updates to v5.1.14 in the last 10 days, making it a
good time to have a look at the prerelease at
http://tiddlywiki.com/prerelease
I’d like to highlight the new QR code generator plugin (installed in the
prerelease so that you can try it out easily). I had little idea about QR
codes before the recent correspondence here on the mailing list, but am now
a convert. If you don’t have a QR code reader on your smartphone I’d highly
recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t
too long/complicated to fit. There are conventions for passing URLs,
contact information, wifi details etc., but there is complete freedom; one
can make a QR code of JSON if you want (actually a bad idea as the special
characters appear to compress badly).
The QR code plugin adds a generic macro for generating a QR code from a
* A new view toolbar button that displays the current tiddler as a QR
code. You can choose from the URL of the tiddler, the raw text, or the
rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was
surprisingly easy — I had the first operational version within 30 minutes
of starting work. A good illustration of the excellent returns on the
effort involved in integrating existing JavaScript components.
There’s a full list of changes in the release note, but I’d highlight the
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed
plugins
** Better display of plugin tiddlers themselves, duplicating the gadget
used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a
filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings
according to HTML encoding, URI encoding, regexp escaping and JavaScript
string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files
Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any
feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their
contributions to this release.
Best wishes
Jeremy.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/aae6d6f8-5467-4956-acdb-1543c5638639%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jeremy Ruston
2016-12-17 08:37:28 UTC
Permalink
Hi Mark
While the QR code is neat, could it's icon be move to the left of the closing icon? All my instincts are to always look for the closing icon in the upper right hand corner. Having the QR code, an occasional activity, take over the position of the closing action, an always-needed activity, breaks up the work flow.
Just to be clear, the QR code plugin is included in the prerelease to make it easier for people to try it out, but it won’t be included when 5.1.14 is released.

I’ll change the button ordering,

Best wishes

Jeremy
Thanks for listening,
Mark
There’s been a rash of updates to v5.1.14 in the last 10 days, making it a good time to have a look at the prerelease at http://tiddlywiki.com/prerelease <http://tiddlywiki.com/prerelease>
I’d like to highlight the new QR code generator plugin (installed in the prerelease so that you can try it out easily). I had little idea about QR codes before the recent correspondence here on the mailing list, but am now a convert. If you don’t have a QR code reader on your smartphone I’d highly recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t too long/complicated to fit. There are conventions for passing URLs, contact information, wifi details etc., but there is complete freedom; one can make a QR code of JSON if you want (actually a bad idea as the special characters appear to compress badly).
* A new view toolbar button that displays the current tiddler as a QR code. You can choose from the URL of the tiddler, the raw text, or the rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was surprisingly easy — I had the first operational version within 30 minutes of starting work. A good illustration of the excellent returns on the effort involved in integrating existing JavaScript components.
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed plugins
** Better display of plugin tiddlers themselves, duplicating the gadget used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings according to HTML encoding, URI encoding, regexp escaping and JavaScript string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their contributions to this release.
Best wishes
Jeremy.
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
Visit this group at https://groups.google.com/group/tiddlywiki <https://groups.google.com/group/tiddlywiki>.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/aae6d6f8-5467-4956-acdb-1543c5638639%40googlegroups.com <https://groups.google.com/d/msgid/tiddlywiki/aae6d6f8-5467-4956-acdb-1543c5638639%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout>.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/F6B7AB85-21E8-4260-9A91-1584466DD9A4%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Thomas Elmiger
2016-12-27 18:30:37 UTC
Permalink
Hi Jeremy

I just tried to look into $:/plugins/tiddlywiki/qrcode/ViewToolbarButton/Rendered
<http://tiddlywiki.com/prerelease/#%24%3A%2Fplugins%2Ftiddlywiki%2Fqrcode%2FViewToolbarButton%2FRendered>
first from the plugin (contents tab) then from the advanced search (Shadows
tab).

All my preferred browsers throw JS errors at me (Safari, FF, Chrome on Mac).

Uncaught RangeError: Maximum call stack size exceeded

*Skript: http://tiddlywiki.com/prerelease/ line 25874 > eval:137* (FF)

Is this due to an error or to the many browser tabs I have in all of my
browsers?

Kind regards,
Thomas

PS: Writing this I wondered about case differences in contents / Shadows
(first letter uppercase) is there a logic I am not aware of?
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b31465fd-5e6f-422d-9e5f-fa8035fabfed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
'Mark S.' via TiddlyWiki
2016-12-27 18:45:08 UTC
Permalink
When I click on your link I get a recursion error. I can clear the error,
but then I can't edit the tiddler.

Mark
Post by Sylvain Naudin
Hi Jeremy
I just tried to look into $:/plugins/tiddlywiki/qrcode/ViewToolbarButton/Rendered
<http://tiddlywiki.com/prerelease/#%24%3A%2Fplugins%2Ftiddlywiki%2Fqrcode%2FViewToolbarButton%2FRendered>
first from the plugin (contents tab) then from the advanced search
(Shadows tab).
All my preferred browsers throw JS errors at me (Safari, FF, Chrome on Mac).
Uncaught RangeError: Maximum call stack size exceeded
*Skript: http://tiddlywiki.com/prerelease/
<http://tiddlywiki.com/prerelease/> line 25874 > eval:137* (FF)
Is this due to an error or to the many browser tabs I have in all of my
browsers?
Kind regards,
Thomas
PS: Writing this I wondered about case differences in contents / Shadows
(first letter uppercase) is there a logic I am not aware of?
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2a09e28d-3781-4840-8cdb-a010f995f143%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Josiah
2016-12-27 19:13:02 UTC
Permalink
there are LOT of RED flags in it when you try look at stuff.
Post by Sylvain Naudin
Hi Jeremy
I just tried to look into $:/plugins/tiddlywiki/qrcode/ViewToolbarButton/Rendered
<http://tiddlywiki.com/prerelease/#%24%3A%2Fplugins%2Ftiddlywiki%2Fqrcode%2FViewToolbarButton%2FRendered>
first from the plugin (contents tab) then from the advanced search
(Shadows tab).
All my preferred browsers throw JS errors at me (Safari, FF, Chrome on Mac).
Uncaught RangeError: Maximum call stack size exceeded
*Skript: http://tiddlywiki.com/prerelease/
<http://tiddlywiki.com/prerelease/> line 25874 > eval:137* (FF)
Is this due to an error or to the many browser tabs I have in all of my
browsers?
Kind regards,
Thomas
PS: Writing this I wondered about case differences in contents / Shadows
(first letter uppercase) is there a logic I am not aware of?
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/9b47db82-8d75-426c-bd20-2c6ca408c173%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tobias Beer
2016-12-28 12:31:57 UTC
Permalink
Hi Josiah,
Post by Josiah
there are LOT of RED flags in it when you try look at stuff
Please be specific, otherwise your comment is of little help.

Best wishes,

Tobias.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/f1daaefc-ff09-4937-85eb-989db7c61785%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Josiah
2016-12-29 18:47:31 UTC
Permalink
Ciao Tobias

The QR Code generator plugin. I was not clear enough I was referring to
earlier posts.

$:/plugins/tiddlywiki/qrcode/ViewToolbarButton/Rendered
<http://www.google.com/url?q=http%3A%2F%2Ftiddlywiki.com%2Fprerelease%2F%23%2524%253A%252Fplugins%252Ftiddlywiki%252Fqrcode%252FViewToolbarButton%252FRendered&sa=D&sntz=1&usg=AFQjCNH_S3UKQ82WZaoO56u_7BAQ0IPxSw>

When clicked gives either a recursion error. After that all the rest give
JavaScript node not found errors.

The link above seems deadly. For me not only does it gives a red error, it
also freezes the browser.

Best wishes
Josiah
Post by Tobias Beer
Hi Josiah,
Post by Josiah
there are LOT of RED flags in it when you try look at stuff
Please be specific, otherwise your comment is of little help.
Best wishes,
Tobias.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2e09f8ad-82a0-46eb-9c50-9f3c0bdaa622%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tobias Beer
2016-12-29 20:29:42 UTC
Permalink
Hi Josiah,
Post by Josiah
The QR Code generator plugin. I was not clear enough I was referring to
earlier posts.
$:/plugins/tiddlywiki/qrcode/ViewToolbarButton/Rendered
<http://www.google.com/url?q=http%3A%2F%2Ftiddlywiki.com%2Fprerelease%2F%23%2524%253A%252Fplugins%252Ftiddlywiki%252Fqrcode%252FViewToolbarButton%252FRendered&sa=D&sntz=1&usg=AFQjCNH_S3UKQ82WZaoO56u_7BAQ0IPxSw>
Ah, thanks for clarifying. I got the idea you were talking about something
different.

Best wishes,

Tobias.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/6b527b86-e175-48a1-b339-11aebcbe526a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jeremy Ruston
2016-12-30 15:36:28 UTC
Permalink
Hi Thomas
I just tried to look into $:/plugins/tiddlywiki/qrcode/ViewToolbarButton/Rendered  <http://tiddlywiki.com/prerelease/#%24%3A%2Fplugins%2Ftiddlywiki%2Fqrcode%2FViewToolbarButton%2FRendered>
first from the plugin (contents tab) then from the advanced search (Shadows tab).
All my preferred browsers throw JS errors at me (Safari, FF, Chrome on Mac).
There are, sadly, a bunch of shadow tiddlers in the core that are not safe to view directly; they are templates designed to be used in specific circumstances, and they run into problems when viewed in the context of the story river.

I think the best solution would have been to have arranged things so that system tiddlers are always shown as raw text, rather than rendered text. It’s too late to change things now for all shadow tiddlers, but I have experimented with a patch that displays raw text for all system tiddlers that have more than one forward slash in their titles, allowing $:/ControlPanel etc to be displayed as usual.

I think at the moment our only other recourse is to fix each individual template. The example you’ve mentioned has the following content:

\define image()
<img src=<<makeqr text:"""$(content)$""" size:"350">>/>
\end

<$wikify name="content" text={{!!text}} type="text" mode="block" output="formattedtext">
<<image>>
</$wikify>

The problem occurs because when you view this tiddler in the story river, the current tiddler will be the tiddler itself (rather than a target tiddler for which we are generating a QR code), thus triggering the recursion.

In this case, we could fix things with a protective reveal widget that detects that the tiddler is being viewed in the story river, and suppresses the main content. The trouble is that all of that extra mechanism will impact performance, adding an overhead to every template in the system.

Best wishes

Jeremy
Uncaught RangeError: Maximum call stack size exceeded
Skript: http://tiddlywiki.com/prerelease/ line 25874 > eval:137 (FF)
Is this due to an error or to the many browser tabs I have in all of my browsers?
Kind regards,
Thomas
PS: Writing this I wondered about case differences in contents / Shadows (first letter uppercase) is there a logic I am not aware of?
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
Visit this group at https://groups.google.com/group/tiddlywiki <https://groups.google.com/group/tiddlywiki>.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b31465fd-5e6f-422d-9e5f-fa8035fabfed%40googlegroups.com <https://groups.google.com/d/msgid/tiddlywiki/b31465fd-5e6f-422d-9e5f-fa8035fabfed%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout>.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/EEC7B56B-8572-4CD7-BD15-68D28D7C8776%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Josiah
2016-12-29 18:58:27 UTC
Permalink
A small point on the editor's behaviour. When you click on any action that
has a pop-up you then decide you don't want it you have to click OUTSIDE
the editable area to dismiss it. Its not intuitive (to me at least) to have
to do that.

Best wishes
Josiah
Post by Jeremy Ruston
There’s been a rash of updates to v5.1.14 in the last 10 days, making it a
good time to have a look at the prerelease at
http://tiddlywiki.com/prerelease
I’d like to highlight the new QR code generator plugin (installed in the
prerelease so that you can try it out easily). I had little idea about QR
codes before the recent correspondence here on the mailing list, but am now
a convert. If you don’t have a QR code reader on your smartphone I’d highly
recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t
too long/complicated to fit. There are conventions for passing URLs,
contact information, wifi details etc., but there is complete freedom; one
can make a QR code of JSON if you want (actually a bad idea as the special
characters appear to compress badly).
The QR code plugin adds a generic macro for generating a QR code from a
* A new view toolbar button that displays the current tiddler as a QR
code. You can choose from the URL of the tiddler, the raw text, or the
rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was
surprisingly easy — I had the first operational version within 30 minutes
of starting work. A good illustration of the excellent returns on the
effort involved in integrating existing JavaScript components.
There’s a full list of changes in the release note, but I’d highlight the
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed
plugins
** Better display of plugin tiddlers themselves, duplicating the gadget
used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a
filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings
according to HTML encoding, URI encoding, regexp escaping and JavaScript
string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files
Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any
feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their
contributions to this release.
Best wishes
Jeremy.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/28b56a37-8c1b-49c5-9142-cdf9d33a2e16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jeremy Ruston
2016-12-30 15:39:07 UTC
Permalink
Hi Josiah
A small point on the editor's behaviour. When you click on any action that has a pop-up you then decide you don't want it you have to click OUTSIDE the editable area to dismiss it. Its not intuitive (to me at least) to have to do that.
The problem there is that the new editor uses an iframe for the text. Meanwhile, the main page is listening for mouse clicks to trigger the removal of the popup. However, the main page doesn’t get mouse click events for clicks within the iframe. So, I think the only fix would be to create a whole new mechanism for a click within the iframe to send a message to the main page to cancel any outstanding popups.

Best wishes

Jeremy
Best wishes
Josiah
There’s been a rash of updates to v5.1.14 in the last 10 days, making it a good time to have a look at the prerelease at http://tiddlywiki.com/prerelease <http://tiddlywiki.com/prerelease>
I’d like to highlight the new QR code generator plugin (installed in the prerelease so that you can try it out easily). I had little idea about QR codes before the recent correspondence here on the mailing list, but am now a convert. If you don’t have a QR code reader on your smartphone I’d highly recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t too long/complicated to fit. There are conventions for passing URLs, contact information, wifi details etc., but there is complete freedom; one can make a QR code of JSON if you want (actually a bad idea as the special characters appear to compress badly).
* A new view toolbar button that displays the current tiddler as a QR code. You can choose from the URL of the tiddler, the raw text, or the rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was surprisingly easy — I had the first operational version within 30 minutes of starting work. A good illustration of the excellent returns on the effort involved in integrating existing JavaScript components.
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed plugins
** Better display of plugin tiddlers themselves, duplicating the gadget used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings according to HTML encoding, URI encoding, regexp escaping and JavaScript string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their contributions to this release.
Best wishes
Jeremy.
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
Visit this group at https://groups.google.com/group/tiddlywiki <https://groups.google.com/group/tiddlywiki>.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/28b56a37-8c1b-49c5-9142-cdf9d33a2e16%40googlegroups.com <https://groups.google.com/d/msgid/tiddlywiki/28b56a37-8c1b-49c5-9142-cdf9d33a2e16%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout>.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/F39D6C36-4A5E-415F-B635-6F622AA67738%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Josiah
2016-12-30 18:38:40 UTC
Permalink
Ciao Jeremy
Post by Jeremy Ruston
The problem there is that the new editor uses an iframe for the text.
Meanwhile, the main page is listening for mouse clicks to trigger the
removal of the popup. However, the main page doesn’t get mouse click events
for clicks within the iframe.

It seems like too much work to do that. How difficult would it be to add a
top right corner "x" closer instead? Could that be a a viable alternative?
In reality I don't think its a major issue. It would probably confound a
few newbies at first until they clicked around.

Best wishes
Josiah
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/4f37eac0-8c0f-415c-8209-9a39c044be83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
'Mark S.' via TiddlyWiki
2016-12-29 21:26:49 UTC
Permalink
The new "Heavier" theme seems to only make the stuff that is already big
(titles, headlines, bold text) bigger. The ordinary text stays the same
size. For my poor eyes, it's the small stuff that needs to get bigger.
Perhaps it works differently on other browsers?

Mark (Windows 7, Firefox 47)
Post by Jeremy Ruston
There’s been a rash of updates to v5.1.14 in the last 10 days, making it a
good time to have a look at the prerelease at
http://tiddlywiki.com/prerelease
I’d like to highlight the new QR code generator plugin (installed in the
prerelease so that you can try it out easily). I had little idea about QR
codes before the recent correspondence here on the mailing list, but am now
a convert. If you don’t have a QR code reader on your smartphone I’d highly
recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t
too long/complicated to fit. There are conventions for passing URLs,
contact information, wifi details etc., but there is complete freedom; one
can make a QR code of JSON if you want (actually a bad idea as the special
characters appear to compress badly).
The QR code plugin adds a generic macro for generating a QR code from a
* A new view toolbar button that displays the current tiddler as a QR
code. You can choose from the URL of the tiddler, the raw text, or the
rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was
surprisingly easy — I had the first operational version within 30 minutes
of starting work. A good illustration of the excellent returns on the
effort involved in integrating existing JavaScript components.
There’s a full list of changes in the release note, but I’d highlight the
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed
plugins
** Better display of plugin tiddlers themselves, duplicating the gadget
used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a
filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings
according to HTML encoding, URI encoding, regexp escaping and JavaScript
string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files
Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any
feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their
contributions to this release.
Best wishes
Jeremy.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c30e0ce2-491a-4b4c-988b-b3d8235bde37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jeremy Ruston
2016-12-30 15:40:42 UTC
Permalink
Hi Mark
The new "Heavier" theme seems to only make the stuff that is already big (titles, headlines, bold text) bigger. The ordinary text stays the same size. For my poor eyes, it's the small stuff that needs to get bigger. Perhaps it works differently on other browsers?
The “Heavier” theme doesn’t actually change the size of any of the text, it just changes the font weight. That’s intentional, but perhaps what you really want is a “Bigger” theme that bumps up the font sizes of everything. The reason that I didn’t bother to create such a theme is that I assumed that people would use the browser font size controls. Do they not do the job for you?

Best wishes

Jeremy
Mark (Windows 7, Firefox 47)
There’s been a rash of updates to v5.1.14 in the last 10 days, making it a good time to have a look at the prerelease at http://tiddlywiki.com/prerelease <http://tiddlywiki.com/prerelease>
I’d like to highlight the new QR code generator plugin (installed in the prerelease so that you can try it out easily). I had little idea about QR codes before the recent correspondence here on the mailing list, but am now a convert. If you don’t have a QR code reader on your smartphone I’d highly recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t too long/complicated to fit. There are conventions for passing URLs, contact information, wifi details etc., but there is complete freedom; one can make a QR code of JSON if you want (actually a bad idea as the special characters appear to compress badly).
* A new view toolbar button that displays the current tiddler as a QR code. You can choose from the URL of the tiddler, the raw text, or the rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was surprisingly easy — I had the first operational version within 30 minutes of starting work. A good illustration of the excellent returns on the effort involved in integrating existing JavaScript components.
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed plugins
** Better display of plugin tiddlers themselves, duplicating the gadget used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings according to HTML encoding, URI encoding, regexp escaping and JavaScript string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their contributions to this release.
Best wishes
Jeremy.
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
Visit this group at https://groups.google.com/group/tiddlywiki <https://groups.google.com/group/tiddlywiki>.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c30e0ce2-491a-4b4c-988b-b3d8235bde37%40googlegroups.com <https://groups.google.com/d/msgid/tiddlywiki/c30e0ce2-491a-4b4c-988b-b3d8235bde37%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout>.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/419B2064-C050-446A-9DD2-3842EF440BD4%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Josiah
2016-12-30 18:42:53 UTC
Permalink
Ciao Mark & Jeremy

FWIW I agree with Jeremy. Browser zoom, as far as I understand it, is a
universal facility in all bowsers now?

Best wishes
Josiah
Post by Thomas Elmiger
Hi Mark
The new "Heavier" theme seems to only make the stuff that is already big
(titles, headlines, bold text) bigger. The ordinary text stays the same
size. For my poor eyes, it's the small stuff that needs to get bigger.
Perhaps it works differently on other browsers?
The “Heavier” theme doesn’t actually change the size of any of the text,
it just changes the font weight. That’s intentional, but perhaps what you
really want is a “Bigger” theme that bumps up the font sizes of everything.
The reason that I didn’t bother to create such a theme is that I assumed
that people would use the browser font size controls. Do they not do the
job for you?
Best wishes
Jeremy
Mark (Windows 7, Firefox 47)
Post by Jeremy Ruston
There’s been a rash of updates to v5.1.14 in the last 10 days, making it
a good time to have a look at the prerelease at
http://tiddlywiki.com/prerelease
I’d like to highlight the new QR code generator plugin (installed in the
prerelease so that you can try it out easily). I had little idea about QR
codes before the recent correspondence here on the mailing list, but am now
a convert. If you don’t have a QR code reader on your smartphone I’d highly
recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t
too long/complicated to fit. There are conventions for passing URLs,
contact information, wifi details etc., but there is complete freedom; one
can make a QR code of JSON if you want (actually a bad idea as the special
characters appear to compress badly).
The QR code plugin adds a generic macro for generating a QR code from a
* A new view toolbar button that displays the current tiddler as a QR
code. You can choose from the URL of the tiddler, the raw text, or the
rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was
surprisingly easy — I had the first operational version within 30 minutes
of starting work. A good illustration of the excellent returns on the
effort involved in integrating existing JavaScript components.
There’s a full list of changes in the release note, but I’d highlight the
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed
plugins
** Better display of plugin tiddlers themselves, duplicating the gadget
used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a
filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings
according to HTML encoding, URI encoding, regexp escaping and JavaScript
string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files
Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any
feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their
contributions to this release.
Best wishes
Jeremy.
--
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
<javascript:>.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/c30e0ce2-491a-4b4c-988b-b3d8235bde37%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/c30e0ce2-491a-4b4c-988b-b3d8235bde37%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/4e0c658b-26ff-4967-930a-01879252b07d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
'Mark S.' via TiddlyWiki
2016-12-30 18:59:40 UTC
Permalink
It doesn't seem to change the font weight of the smaller text. I'm just
trying to understand what the point is of a theme that makes the
easy-to-read stuff even bigger/heavier and easier-to-read, but ignores the
small stuff. All I can say is, wait until you need reading
glasses/bifocals. ;-)

Changing the font-size from the menu, or any of the other settings for that
matter, is awkward because the fonts change WHILE you are typing, meaning
you can easily lose your place. I've got a configuration tiddler that I
want to post that will let you dial-in fonts and and width settings and
then save the configuration.

Merry Holiday Seasons Greetings,
Mark
Post by Thomas Elmiger
Hi Mark
The new "Heavier" theme seems to only make the stuff that is already big
(titles, headlines, bold text) bigger. The ordinary text stays the same
size. For my poor eyes, it's the small stuff that needs to get bigger.
Perhaps it works differently on other browsers?
The “Heavier” theme doesn’t actually change the size of any of the text,
it just changes the font weight. That’s intentional, but perhaps what you
really want is a “Bigger” theme that bumps up the font sizes of everything.
The reason that I didn’t bother to create such a theme is that I assumed
that people would use the browser font size controls. Do they not do the
job for you?
Best wishes
Jeremy
Mark (Windows 7, Firefox 47)
Post by Jeremy Ruston
There’s been a rash of updates to v5.1.14 in the last 10 days, making it
a good time to have a look at the prerelease at
http://tiddlywiki.com/prerelease
I’d like to highlight the new QR code generator plugin (installed in the
prerelease so that you can try it out easily). I had little idea about QR
codes before the recent correspondence here on the mailing list, but am now
a convert. If you don’t have a QR code reader on your smartphone I’d highly
recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t
too long/complicated to fit. There are conventions for passing URLs,
contact information, wifi details etc., but there is complete freedom; one
can make a QR code of JSON if you want (actually a bad idea as the special
characters appear to compress badly).
The QR code plugin adds a generic macro for generating a QR code from a
* A new view toolbar button that displays the current tiddler as a QR
code. You can choose from the URL of the tiddler, the raw text, or the
rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was
surprisingly easy — I had the first operational version within 30 minutes
of starting work. A good illustration of the excellent returns on the
effort involved in integrating existing JavaScript components.
There’s a full list of changes in the release note, but I’d highlight the
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed
plugins
** Better display of plugin tiddlers themselves, duplicating the gadget
used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a
filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings
according to HTML encoding, URI encoding, regexp escaping and JavaScript
string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files
Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any
feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their
contributions to this release.
Best wishes
Jeremy.
--
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
<javascript:>.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/c30e0ce2-491a-4b4c-988b-b3d8235bde37%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/c30e0ce2-491a-4b4c-988b-b3d8235bde37%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/dea02a73-620a-4ed1-85fb-c4cbe22367b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jeremy Ruston
2017-01-05 09:38:32 UTC
Permalink
Hi Mark
Post by 'Mark S.' via TiddlyWiki
It doesn't seem to change the font weight of the smaller text.
The smaller text gets heavier on the Mac on all browsers I’ve tried. I think the problem may be that your system that doesn’t support the same range of distinct font weights.

Try this wikitext:

<div style="font-weight:100;">Font weight 100</div>
<div style="font-weight:200;">Font weight 200</div>
<div style="font-weight:300;">Font weight 300</div>
<div style="font-weight:400;">Font weight 400</div>
<div style="font-weight:500;">Font weight 500</div>
<div style="font-weight:600;">Font weight 600</div>
<div style="font-weight:700;">Font weight 700</div>
<div style="font-weight:800;">Font weight 800</div>
<div style="font-weight:900;">Font weight 900</div>
<div style="font-weight:1000;">Font weight 1000</div>

Here’s what it looks like for me on Chrome:



Here, there are 5 distinct weights. You may be able to make out that 200 and 300 are rendered with the same weight, and from 600 to 900 (and 1000 isn’t supported).

The Heavier theme switches the weight of the body text from the browser default of 400 to 500.

Best wishes

Jeremy
Post by 'Mark S.' via TiddlyWiki
I'm just trying to understand what the point is of a theme that makes the easy-to-read stuff even bigger/heavier and easier-to-read, but ignores the small stuff. All I can say is, wait until you need reading glasses/bifocals. ;-)
Changing the font-size from the menu, or any of the other settings for that matter, is awkward because the fonts change WHILE you are typing, meaning you can easily lose your place. I've got a configuration tiddler that I want to post that will let you dial-in fonts and and width settings and then save the configuration.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/811471A4-2E55-442A-A9B9-72E7944AE4EE%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
wimm
2017-01-22 23:51:26 UTC
Permalink
Hi Jeremy
I think I found a small export tiddler bug, the popup menu for tiddlers
containing two double quotes in their titles e,g, New Tiddler "test"

<Loading Image...>
shows part of the export macro instead of the options like export tiddler
CSV file, JSON file
see blue area in attached image

as a result the export of the tiddlers does not work.

*work around*: remove double quotes from tiddler title (one " is no problem)

BTW this is also present in the current 5.1.13

KR wimm
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/315815c2-64b8-4e99-9a8d-46b889ce2dbd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tobias Beer
2017-01-23 07:28:33 UTC
Permalink
Hi Wimm
Post by wimm
I think I found a small export tiddler bug, the popup menu for tiddlers
containing two double quotes in their titles e,g, New Tiddler "test"
The problem lies in how TiddlyWiki parses widget attributes, in this case
specifically this line:

https://github.com/Jermolene/TiddlyWiki5/blob/master/core/wiki/macros/export.tid#L24

Any tiddle title ending in quotes will break the pattern which I believe
means that in a case like this, TiddlyWiki should never use macro
parameters, but always use variables.

Best wishes,

Tobias.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/e6749b9a-73a5-45c4-8dba-b7ca217c95a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tobias Beer
2017-01-25 20:38:24 UTC
Permalink
Hi wimm,

I think I found a small export tiddler bug, the popup menu for tiddlers
containing two double quotes in their titles e,g, *New Tiddler "test"*
With some much appreciated help from Pranav C Balan
<http://stackoverflow.com/questions/41845715/capture-with-single-quotes-in-triple-quoted-string>
I just made a pull request that hopefully fixes this issue for good:

*#2736 enables quotes in triple quotes as well as triple single quotes for
attributes and params*
https://github.com/Jermolene/TiddlyWiki5/pull/2736

Here's a demo:
http://2736.tiddlyspot.com

Best wishes,

Tobias.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b5e4e0c9-e8cf-4cdc-a5e3-7482adb40b79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
wimm
2017-01-27 17:43:24 UTC
Permalink
Hi Tobias

*#2736 enables quotes in triple quotes as well as triple single quotes for
Post by Tobias Beer
attributes and params*
https://github.com/Jermolene/TiddlyWiki5/pull/2736
http://2736.tiddlyspot.com
I tried your demo and some additional test cases, it works like a charm,
thank you! and Pranav C Balan via stackoverflow
I hope the pull request gets implemented
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3c2da45b-5a4a-4925-ae8a-47d27dcdfecf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Andrew Lister
2017-01-25 00:10:14 UTC
Permalink
I've been using those controls for presentation, and it's easy enough, but
it would be handy if there were a one-stop-shop switch to presentation
theme. At the moment I'm switching to "Hide Furniture" theme, plus
switching whatever-it's-called to "zoom-in", and then finally increasing
font size. If I haven't done it in a while I have to fuss for a bit to
figure it out again.

Plus on my tiddlers I still see the various edit toolbar buttons... Ok, I
need the "Punch" theme for that, I think.
Post by Thomas Elmiger
Hi Mark
The new "Heavier" theme seems to only make the stuff that is already big
(titles, headlines, bold text) bigger. The ordinary text stays the same
size. For my poor eyes, it's the small stuff that needs to get bigger.
Perhaps it works differently on other browsers?
The “Heavier” theme doesn’t actually change the size of any of the text,
it just changes the font weight. That’s intentional, but perhaps what you
really want is a “Bigger” theme that bumps up the font sizes of everything.
The reason that I didn’t bother to create such a theme is that I assumed
that people would use the browser font size controls. Do they not do the
job for you?
Best wishes
Jeremy
Mark (Windows 7, Firefox 47)
Post by Jeremy Ruston
There’s been a rash of updates to v5.1.14 in the last 10 days, making it
a good time to have a look at the prerelease at
http://tiddlywiki.com/prerelease
I’d like to highlight the new QR code generator plugin (installed in the
prerelease so that you can try it out easily). I had little idea about QR
codes before the recent correspondence here on the mailing list, but am now
a convert. If you don’t have a QR code reader on your smartphone I’d highly
recommend installing one to play with the prerelease.
Basically, QR codes can be used to transfer any block of text that isn’t
too long/complicated to fit. There are conventions for passing URLs,
contact information, wifi details etc., but there is complete freedom; one
can make a QR code of JSON if you want (actually a bad idea as the special
characters appear to compress badly).
The QR code plugin adds a generic macro for generating a QR code from a
* A new view toolbar button that displays the current tiddler as a QR
code. You can choose from the URL of the tiddler, the raw text, or the
rendered text
* Example forms for generating QR codes for contacts, wifi and generic codes
Once I’d found the library, getting the plugin up and running was
surprisingly easy — I had the first operational version within 30 minutes
of starting work. A good illustration of the excellent returns on the
effort involved in integrating existing JavaScript components.
There’s a full list of changes in the release note, but I’d highlight the
* Extended search mechanism to require the search string to be a minimum length
* New Hebrew translation, and preliminary support for RTL languages
** New “Plugins” tab in the “More” sidebar tab, listing all installed
plugins
** Better display of plugin tiddlers themselves, duplicating the gadget
used in control panel
* Fixed height of preview pane to use a scrollbar when fixed height layout is selected
* Improved modals and notifications so that global macros are available
* Extended the SetWidget to allow a single result to be selected from a
filtered result list
* Added new $:/info/url/* information tiddlers providing document location information
* Added several new filter operators for string encoding/decoding strings
according to HTML encoding, URI encoding, regexp escaping and JavaScript
string encoding
* Improved support for bulk loading tiddler files via tiddlywiki.files
Files within TiddlyWikiFolders
I’d like to get v5.1.14 released in the next couple of weeks, so any
feedback/thoughts/questions are much appreciated at this point.
As ever, thanks to everyone listed in the release note for their
contributions to this release.
Best wishes
Jeremy.
--
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
<javascript:>.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/c30e0ce2-491a-4b4c-988b-b3d8235bde37%40googlegroups.com
<https://groups.google.com/d/msgid/tiddlywiki/c30e0ce2-491a-4b4c-988b-b3d8235bde37%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
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+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/449bfe5b-d738-4615-b527-cea3ce89e98d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Continue reading on narkive:
Loading...