[tw5] Re: Itty.bitty - a cousin to the tiddler?

It is an interesting issue. What one wants is the "easiest route". Give me A BUTTON, always. The itty.bitty thing goes through a server. It is a recomposition to HTML of a decomposition and concatenation of bits. Basically it is a compacted page of all elements present in render. I am SURE we

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Ciao Steve You can include IN email TW HTML quite easily. At the moment on the pre-release version, in editor, includes a "Raw HTML" preview. You just copy the code from that. To make is sweetly neat you need a browser add in like " https://markdown-here.com/"; that will convert a css styleset

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Does/Could/should it not occupy a similar space to the qrcode.. Press the hypothetical button to create a link for.. Much like the qrcode button does right now? I once tried to share a tiddlywiki as an html file via email as a thing to be read by someone else and they said they didn't know how

[tw5] Re: Itty.bitty - a cousin to the tiddler?

PMario wrote: > > It depends, what you mean with "snapshot". For me a snapshot also contains > CSS settings. So if you want to preserve a "pixel perfect" representation > of a tiddler you better go with a screenshot. > Absolutely right. But "snapshot" IS useful in that you can retain basic stu

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Ciao Mark How did you capture the CSS, and how did you inline it ? > The CSS is not extracted. Its simply a TW stylesheet tiddler with a few rules to format the Tiddler & this GG post so they look the same. I use the browse

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Hi TT, How did you capture the CSS, and how did you inline it ? Thanks! On Saturday, December 14, 2019 at 7:36:48 AM UTC-8, TiddlyTweeter wrote: > > TonyM wrote: >> >> >> ... snapshots are needed >> > > (Rendered HTML) snapshots are remarkably easy in TW. And flexible too. > > I think the underl

[tw5] Re: Itty.bitty - a cousin to the tiddler?

TonyM Part of the issue is "how much render do you need"? In TW we can access the HTML render of a tiddler, a group of tiddlers, or the whole tamale quite easily. The issues relate mostly to what is "inline" and what isn't for specific outputs types. Some outputs (email, GG posts) need inli

[tw5] Re: Itty.bitty - a cousin to the tiddler?

TonyM wrote: > > > ... snapshots are needed > (Rendered HTML) snapshots are remarkably easy in TW. And flexible too. I think the underlying issue is (a) documentation; (b) some recipes about how to do them for different objectives. For instance this GG post

[tw5] Re: Itty.bitty - a cousin to the tiddler?

TT See my response to Mario. I am responding to snapshots, not necessarily with itty.bitty. Please share your method to "copying the render level HTML in TW" and why should it not be simplified? Regards Tony On Friday, December 13, 2019 at 9:10:25 PM UTC+11, TiddlyTweeter wrote: > > TonyM w

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Mario, I am not sure itty.bitty is a full snapshot answer. but snapshots are needed I think snapshots with or without multiple versions can be used for the following 1. Effectively displaying a static tiddler result for complex or long tiddlers so it need not be re rendered on the sligh

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Mat wrote: > > Come ON! Is this a cousin to the tiddler?! > Cousins? Beware of inbreeding :-) > I'm in love at first glance but I'm not sure what to do with it! > Let us not be forced to analyse that too closely :-) TT -- You received this message because you are subscribed to the Google

[tw5] Re: Itty.bitty - a cousin to the tiddler?

TonyM wrote: > > Can itty.bitty built into tiddlywiki be used to take and preserve a > snapshot of a rendered tiddler? > No. Not in the sense it could locate all styling. Since you can already do a "snapshot" by simply copying the render level HTML in TW I'm struggling to know what is the adde

[tw5] Re: Itty.bitty - a cousin to the tiddler?

On Thursday, December 12, 2019 at 10:24:35 PM UTC+1, TonyM wrote: ... > Can itty.bitty built into tiddlywiki be used to take and preserve a > snapshot of a rendered tiddler? It depends, what you mean with "snapshot". For me a snapshot also contains CSS settings. So if you want to preserve a "p

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Now I am going to immediately put an argument opposite to my last. Can itty.bitty built into tiddlywiki be used to take and preserve a snapshot of a rendered tiddler? it would compress the result and allow review in a new tab or iframe. It could also generate static html pages where we can use

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Mario Thanks for considering that. In a similar way I see more value in a tool to use a filter to package tiddlers in a bookmarklet. Jeremy provided the wiki text recently to me. One drags the bookmarklet to the browser bookmarks and with a click it silently imports the tiddlers in the bookmark

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Ciao Mat & PMario PMario wrote... > 2) I don't see a real usecase ... Neither do I. The thing works via an online service in the default. It is a nice thing ... BUT ... "What has TW got to do with it?" What would be the benefit? TT -- You received this message because you are subscribed

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Hi Mat, I had a closer look at the implementation and it seems to be simple to implement into TW. Both the encoder and the decoder. There are some lzma libraries at github, which could be used. Minified code size may be about 50kByte ... BUT There are 2 concerns. 1) Security. See the last n

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Qr code* -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.c

[tw5] Re: Itty.bitty - a cousin to the tiddler?

But we already have a we code generator! -- 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+unsubscr...@googlegroups.com. To view this discussion on the w

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Ste, I imagine the algorithm for Ittybitty could be represented in TiddlyWiki, both encode and decode but I am curious how this can be put to use? [[Test|https: //itty.bitty.site/#/?XQI4AAAmGUqHVd09ZfxC16xLzC16aGEjdkZ7N++qsaejZeOh+pjIxMWiWgrUhIMz6VWHybyHUyNYIGvB///p02AA]] works on ti

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Hans, Did you come up with anything interesting for this? Tt, Good question. I guess we can't.. Even though we can isolate one tiddler it still comes as a file...tid/ Json etc. so then i guess the question becomes one of ease of sharing. link or e-mail attachment. Would an export to itty bitt

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Can't WE do this too? TT On Sunday, 22 September 2019 19:46:06 UTC+2, Mat wrote: > > @dubiousscript just shared > > something over at gh: > > Itty.bitty >

[tw5] Re: Itty.bitty - a cousin to the tiddler?

@Mat: Well, I can certainly say that it worked, as promised, "right out of the box". And, having spent less than 10 minutes with it so far, I think I have a few uses for it. It's quite intriguing. Thanks for sharing! Regards, Hans On Sunday, September 22, 2019 at 1:46:06 PM UTC-4, Mat wrot

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Mat, In a similar vein when this kind of sharing matures we can leverage these instead https://css-tricks.com/how-to-use-the-web-share-api/ and along with the fall back options perhaps someone can make a tiddlywiki widget for this? Similar to copy to clipboard of the permalink as a sharing mech

[tw5] Re: Itty.bitty - a cousin to the tiddler?

Mat, This is a quite interesting idea. I am yet to fully understand the implications and functionality especially as it relates to tiddlywiki but its worth investigating. It also made me think when it comes to desirable features in tiddlywiki we do need to look further afield as tiddlywiki can