[tw5] Re: Compression of embedded images

[Mal]

Tony,

Thanks for your additional comments.

To answer some of your points: 

   - Yes, maintaining single file format is important - this makes it much 
   easier to access on various device types.
   - Yes, these wikis need to be kept private.

My previous batch approach was to process images that have already imported 
into the wiki, convert png images to jpg and retain whichever is smaller.  
However, the streamlined workflow you mentioned would help to get the 
images optimised at the start.

Regards,

Mal


On Sunday, 10 November 2019 16:25:28 UTC+10, TonyM wrote:
>
> Mal
>
> Actual screen shots, without photographic style images included, Actualy 
> compress very well in jpg since a lot of the image is block colours. If you 
> extract the images you would import and try some bulk converters you can 
> get a quick idea if they are small enough in total to import or if you must 
> go the external route. 
>
> If you go for external images you may loose the single file portability. I 
> suppose it depends if its one or more users, needs to be private or not, 
> needs to work off line etc that will determine the best solution. You could 
> host images somewhere and reference them, the trick would be making an easy 
> capture, save, reference workflow and this starts with how are the images 
> acquired 
>
>

-- 
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.com/d/msgid/tiddlywiki/4f5f4720-6bf6-4299-990e-10522cc9414a%40googlegroups.com.

[tw5] Re: Compression of embedded images

[TonyM]

Mal

Actual screen shots, without photographic style images included, Actualy 
compress very well in jpg since a lot of the image is block colours. If you 
extract the images you would import and try some bulk converters you can get a 
quick idea if they are small enough in total to import or if you must go the 
external route. 

If you go for external images you may loose the single file portability. I 
suppose it depends if its one or more users, needs to be private or not, needs 
to work off line etc that will determine the best solution. You could host 
images somewhere and reference them, the trick would be making an easy capture, 
save, reference workflow and this starts with how are the images acquired 

-- 
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.com/d/msgid/tiddlywiki/c1012fe6-ae2b-475b-8b26-8b0f8c9b5d3a%40googlegroups.com.

[tw5] Re: The-book. Weekly report

[TonyM]

Luis,

Great stuff, I will review in more detail and provide feedback if you want.


   - The one thing I just noticed is you use the word unlinear which does 
   not exist - use nonlinear.
   - You say "tag bubbles" but the standard is "tag pill"

Do you want us to point good document sources to you?

Regards
Tony

On Friday, November 8, 2019 at 9:12:31 PM UTC+11, Luis Gonzalez wrote:
>
> The-book is growing!! Look its Repository. 
> 
> The most important chapter is near: filters. Understanding filters is 
> essential to get the most out of Tiddlywiki. The next weeks I will start 
> writing it.
>
>
>
> This week:
>
>- Chapter 4
>   - Adding new buttons at the toolbars.
>   - Adding global shortcuts.
>   - Adding a left menu.
>- Mindmap of the CSS main core tiddlywiki classes on page 36
>- Table with the roles a tiddler can have on page 38
>- Wikitext mindmap on page 42
>- Chapter 8. Starting.
>- Describing variables
>
>
>
>

-- 
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.com/d/msgid/tiddlywiki/b365da1f-0501-4706-9dd2-fe017a9b0fda%40googlegroups.com.

[tw5] Re: Compression of embedded images

[Mal]

Mario / Mark / TT,

Thanks for all the helpful comments.

Mario, your post is a great reference - it's a pity this stuff tends to get 
buried in GG.

In my application, I think we are mostly dealing with screen shots and 
pretty much only view the wikis on screens, ranging from desktops to 
mobiles, so no need for printing.

I will look further into a suitable image manipulation application that 
will allow for a simple workflow to get from the screen capture through 
image optimisation to copying into Tiddlywiki.

Thanks again.

Regards,

Mal




On Sunday, 10 November 2019 04:42:28 UTC+10, @TiddlyTweeter wrote:
>
> Mal, partly backing up PMario & Mark but with a sharper intent ... :-)
>
> It would definitely be easiest to use an external image editor with bulk 
> functions to prepare images. Change resolution, palette color numbers & 
> output format for LOWEST NICE LOOKING SIZE (do that interactively in the 
> program). There are lots of them.
>
> On Windows https://www.irfanview.net/ is a good free one to try. There 
> are many others on all platforms.
>
> Underlining your OP: You need make sure image resolutions are not higher 
> than the viewport. Match them to the max resolution you'd display. That is 
> the biggest issue.
>
> Best wishes
> TT
>

-- 
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.com/d/msgid/tiddlywiki/f9bf0bdc-cfc7-452a-84c7-990ab578b0f3%40googlegroups.com.

[tw5] Ipfs with TiddlyWiki

[TonyM]

Xavier

Thanks very much for sharing. I will look into this soon. It may be helpful for 
you to add to this threads original post, using the Google forum and provide an 
acronym free explanation of what ipfs and this implementation offers. Basic 
benefits are requirements are more likely to catch peoples eyes.

Great contribution thanks.

Regards
Tony

-- 
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.com/d/msgid/tiddlywiki/26d7dc1e-3bc2-4120-9db5-4a8e11b3d71b%40googlegroups.com.

[tw5] Re: More math: standard-metric converter

[HansWobbe]

@ A_Gloom

I am not sure people would understand, in spite of the fact that the 
TiddlyWiki community is much more inclined to accept Symbols, especially as 
Tags.  One of the frequent complaints about APL was "all of those funny 
symbols are too hard to understand".  That being said, the trade off was 
that is was possible to create a function that summed a variable, be it a 
vector or a higher-order structure, in only 7 keystrokes (as opposed to 
needing 100+ in COBOL.  The primitive functions were powerful !!


re: ...

I was thinking of using APL symbols since they're in extended unicode, was 
needing short buttons labels (why I used Pi and Σ) but if I add an actual 
Pi/π key (3.14) I may switch  to +/ for the sum key but I believe there's 
also a shrunken sum unicode... think ppl would understand +/?
 

-- 
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.com/d/msgid/tiddlywiki/b5792e9a-1117-4ba6-b2a5-7e99add517ef%40googlegroups.com.

[tw5] Re: Compression of embedded images

[@TiddlyTweeter]

Mal, partly backing up PMario & Mark but with a sharper intent ... :-)

It would definitely be easiest to use an external image editor with bulk 
functions to prepare images. Change resolution, palette color numbers & 
output format for LOWEST NICE LOOKING SIZE (do that interactively in the 
program). There are lots of them.

On Windows https://www.irfanview.net/ is a good free one to try. There are 
many others on all platforms.

Underlining your OP: You need make sure image resolutions are not higher 
than the viewport. Match them to the max resolution you'd display. That is 
the biggest issue.

Best wishes
TT

-- 
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.com/d/msgid/tiddlywiki/5618631b-c70b-41aa-a821-e50ce7e14a86%40googlegroups.com.

[tw5] Re: Compression of embedded images

['Mark S.' via TiddlyWiki]

I guess step one would be to locate any open-source, javascript-only code 
sources for converting PNG to JPG. 

On Friday, November 8, 2019 at 9:34:58 PM UTC-8, Mal wrote:
>
> Tiddlywiki Folks,
>
> I have a non-technical Tiddlywiki user with large (30-40MB) wikis of study 
> notes containing lots of embedded images.  Ideally, I would like to provide 
> a simple method of optimising these images during the process of dragging 
> and dropping into the wiki.  Are there any good ideas out there for 
> streamlining this process?
>
> I know there are various on-line sites for image conversion and 
> optimisation, like https://image.online-convert.com/convert-to-webp, and 
> browsers also have some in-built image manipulation capability.
>
> A plugin that automatically converted images when dropped into tiddlywiki 
> would be ideal, but I fear this is a bit above my level of browser, 
> javascript and Tiddlywiki knowledge.
>
> In the past, I have used a simple bash script to run through the image 
> files in a node.js implementation of the wikis and convert png images to 
> jpg.  This provides some substantial reductions in Tiddlywiki file sizes.  
> However, it would be much cleaner to do the optimisation at the point of 
> adding the images to the wiki, preferably with some options related to 
> resulting quality and size.
>
> I would love to read your thoughts on this.
>
> Regards,
>
> Mal
>
>
>
>

-- 
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.com/d/msgid/tiddlywiki/a8d82e5e-d8df-47b6-9504-8e20fee81901%40googlegroups.com.

[tw5] Re: Compression of embedded images

[PMario]

Hi Mal, 

Image processing is a highly advanced art and libraries that can handle it 
in a sophisticated way are huge in size. .. So I _don't_ think it will ever 
be convenient to add an image processing library to the TW core. ... To 
deal with imperfections would be a maintenance nightmare. 

IMO working with TW and images always depends on the "*target group*" you 
want to reach. 

*Print target)*
As soon as you want to print the content, you'll need "full" 
resolution, to get good results. ... So I would completely *exclude *the "
*print*" *target* group, if I would work with *embedded images*. If you 
need to print something I think you will _have_ to work with "external 
images ". 

*Computer screen shots)*
I still think, that GIF  is still a 
format to go here. GIF was very popular in 1990 to 2000 but it had a really 
BAD problem. LZW lossless compression, which GIF uses was patented. In 2004 
the relevant *patents expired *and since then GIF IMO is still a image 
format to go for screen-shots. 

The nice thing is, it doesn't need any settings, when you save it. It 
always uses lossless compression. The only problem it has is the colour 
range it can handle. ... So if you have an image background ... forget 
about it. If you have a monochrome background (as I prefer) it's still a 
good format. 

PNG  was developed 
in the 2000th because of the GIF patent wars. IMO it's a bit better for 
handling modern colour palettes for screenshots, but it also has a bigger 
file size. _and_ it has a compression setting. :/ which has the potential 
to be set wrong by users. 

With the screenshot I did create from my workspace the setting 9 creates a 
smaller image as setting 6. Where 9 is better quality. :/ The file size 
difference between PNG and GIF is about 150kByte. GIF (557k), PNG (703k 
c9)(710k c6 :/)

JPG should _NOT_ be used for computer screenshots. If you set quality to 
100% it produces much bigger images as PNG. In my case 1016kByte instead of 
703kByte for PNG

If 80% setting is used the jpg is 388kByte BUT it already produces very bad 
JPG-artefacts  with 
text. Which can be seen if the screen-shot is ever printed. It doesn't look 
professional. ... ever. 

*Images)*
IMO JPEG is the format to go here. WEBP isn't supported by Apple, so 
chances are high, it produces problems, if embedded. JPG is already 
compressed and can _not_ be zipped. The second problem with images today is 
size. 

Modern mobile pones easily create 5000x3000 pixel images. That's OK, 
because we want "good quality" and jpg always uses a "lossy compression 
" format, even if set to 
100%!

The problem is, that those images already need 4-7MByte, depending on the 
content details. ... So if we want to embed JPG we need to do some 
"pre-processing". 

IMO googles Squoosh-app  is a 
nice way to play with different possibilities, that fits your needs. _but_ 
interested users should read this info 
first,
 
to know what's going on. WebApp is: https://squoosh.app


Optimizing according to the usecase is nice ... BUT ... embedding images 
into TW converts them into base64 encoding 
, which throws a lot of the 
optimizations out of the window by blowing it up by 100%


*SVGs)*

For SVGs optimization we can use: https://jakearchibald.github.io/svgomg/ 


just some thoughts
have fun!

mario

-- 
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.com/d/msgid/tiddlywiki/0c2f48e3-75dd-450d-bdfa-73a634984f26%40googlegroups.com.

[tw5] Re: CSS: A sidebar for mobile

[@TiddlyTweeter]

Ciao Scott

Update.

I was struck by the simplicity of this. I been playing around with it with 
different "breakpoints". I have no improvement over your demo yet but will 
work more with the general idea.

FYI, unrelated, there is one issue on moblie sizes that Telmiger did 
solve.  Its the "wiggle width". On Android, at least, even if you think you 
scale properly, the tiddlers sometimes need scrolling right a bit. The 
problem is likely somewhere in the Vanilla CSS. Not quite sure where. We 
could ask Thomas?

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e08db3bb-4716-4b8e-b37b-5095f9e8615a%40googlegroups.com.

[tw5] Re: The-book. Weekly report

[@TiddlyTweeter]

Ciao on the Google Group I added the tags "announcement", "resource", 
"update" ... like this ...

[image: Annotation 2019-11-09 144248.jpg]


Its worth taking the time to do so when you post. It makes the posts more 
easily findable.

Best wishes
TT

On Friday, 8 November 2019 11:12:31 UTC+1, Luis Gonzalez wrote:
>
> The-book is growing!! Look its Repository. 
> 
> The most important chapter is near: filters. Understanding filters is 
> essential to get the most out of Tiddlywiki. The next weeks I will start 
> writing it.
>
>
>
> This week:
>
>- Chapter 4
>   - Adding new buttons at the toolbars.
>   - Adding global shortcuts.
>   - Adding a left menu.
>- Mindmap of the CSS main core tiddlywiki classes on page 36
>- Table with the roles a tiddler can have on page 38
>- Wikitext mindmap on page 42
>- Chapter 8. Starting.
>- Describing variables
>
>
>
>

-- 
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.com/d/msgid/tiddlywiki/1ef0782d-bd74-4bfb-9a6f-9be088c6b75b%40googlegroups.com.

[tw5] Re: The-book. Weekly report

[David Gifford]

Great! Congratulations on the progress!

On Friday, November 8, 2019 at 4:12:31 AM UTC-6, Luis Gonzalez wrote:
>
> The-book is growing!! Look its Repository. 
> 
> The most important chapter is near: filters. Understanding filters is 
> essential to get the most out of Tiddlywiki. The next weeks I will start 
> writing it.
>
>
>
> This week:
>
>- Chapter 4
>   - Adding new buttons at the toolbars.
>   - Adding global shortcuts.
>   - Adding a left menu.
>- Mindmap of the CSS main core tiddlywiki classes on page 36
>- Table with the roles a tiddler can have on page 38
>- Wikitext mindmap on page 42
>- Chapter 8. Starting.
>- Describing variables
>
>
>
>

-- 
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.com/d/msgid/tiddlywiki/d5eb365b-f3cb-437c-b5da-7015b50c125f%40googlegroups.com.

[tw5] Ipfs with TiddlyWiki

[Xavier Maysonnave]

Dear Friends,

I just published a new version v0.2.6 of Ipfs with TiddlyWiki.

You can save your wikis and their attachments over Ipfs, attachment 
encryption is also supported.
The only open free server I know is https://infura.io otherwise for a 
faster and more personal experience your need the tandem Ipfs Companion and 
Ipfs Desktop.

This version supports the following feature:
- Ipfs
- Ipns
- Unpin previous version
- Encrypt and Unencrypt attachments
- Ens, It means that the plugin is able to update your Ens domain to 
provide a better experience.

The official web site is reachable @
https://bluelightav.eth if you have an Ens capable browser or
https://bluelightav.eth.link
This web site provides a full documentation.

As a test case I also published the official https://tidllywiki.com over 
Ipfs @
https://maatech.eth
https://maatech.eth.link

Bug reports and enhancement requests should be done on GitHub @

https://github.com/xmaysonnave/tiddlywiki-ipfs

Warmly

-- 
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.com/d/msgid/tiddlywiki/3f769bce-6c08-451b-a558-05398d79bbb2%40googlegroups.com.