Absolutely! I already have some working code (based on the examples in the plugin) to produce MECard or VCard Contact QRs to plug into a page template. I just didn't want to include functionality from a pre-release plugin. Once 5.1.16 is released, I will add it in.
I'll post the template code here a bit later if you are interested. /Mike On Tuesday, March 20, 2018 at 8:30:10 AM UTC-4, AlexHough wrote: > > Just a thought..... > > I wonder if the plugin could be used to produce QR labels from the QR > function in TW > > > Alex > > On 18 March 2018 at 12:39, @TiddlyTweeter <[email protected] > <javascript:>> wrote: > >> Ciao Mike >> >> Thanks for the detailed comments! They are useful to read. >> >> The area of accurate printing via CSS I think has quite a lot of >> "exception handling" you have to deal with. Your comments illustrate that >> well. >> >> I'm pretty sure its like that because, still, when browsers adopt new CSS >> rules, there is hardly any assessment of final printed output on testing >> the implementation. Its an area of CSS that has great potential--but is >> weak and inconsistent as soon as you start trying to create reliable >> precision. >> >> One advantage of printing to PDF, rather than printer, is its a way >> around some of the current problems. I assume that is why its used so >> widely? >> >> Best wishes >> Josiah >> >> Michael Wiktowy wrote: >>> >>> Some of the issues that I ran into: >>> 1) All the little margins and padding that get placed everywhere even >>> though you have not specified anything and it is just an "unprintable" and >>> "undisplayed" whitespace in the html drove me nuts. It isn't. Mostly solved >>> by setting font size and line heights to zero on the containing elements >>> and then resetting them to the size you want where you want them. Sometimes >>> solved in a case by case basis by html commenting out whitespace. It >>> weirdly works. >>> >>> 2) Also, there is a little bit of margin around the html body element >>> that causes a weird margin at the top (screwing up your pagination on the >>> first page only) and at the end (giving you an random extra page on >>> templates that fill up the top to bottom space like tent cards). I had to >>> force that to zero in the @media print rule. >>> >>> 3) @page rule is a wonderful concept for printing that is largely >>> ignored in Chrome. Chrome depends on manual print page margin setting which >>> makes it great for over-riding crappy print layouts but makes it impossible >>> to make things completely automatic. I got to the point where only the top >>> margin setting is needed and the rest should be zero. If you set all the >>> manual margins to zero in Firefox, the @page top margin is respected and >>> things line up automatically. I wanted to fake this using and n-up layout >>> within TiddlyWiki but could not figure out how or if it can process n list >>> items at a time. >>> >>> 4) I would have liked to have some automatic resizing/scaling of fonts >>> to fit each unit div but apparently that does not exist unless you hack it >>> up by iterating with javascript which is beyond my skill-set. My first >>> attempt as squeezing text in was to use the "condensed" version of a font >>> but whether the font that a browser chooses has a condensed variant is hit >>> or miss even with the same font-family specification. I ended up just >>> squeezing by changing the font size on the line that was assumed the >>> biggest but what is done with that checkmark is template specific. This >>> might turn into a slider or a +/- button in the future to allow some fine >>> tuning. >>> >> -- >> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <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/95d7328e-db95-4d4e-a782-e14010d428c1%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/95d7328e-db95-4d4e-a782-e14010d428c1%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 [email protected]. To post to this group, send email to [email protected]. 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/5f30d672-4a8c-4143-913c-5ef151a63ae2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
