How to manage the image-output / image-tools node conflict (split topic)

[Steve-Mcl]

@BartButenaers

Jimp vs Jimp-compact : you are completely right that this library indeed might stop following jimp in the future. However the viewer only needs the most basic jimp functionality: we only need to be able to resize and load a Jimp object. All other (new) Jimp functionality won't be needed for the viewer, so don't think it is a problem if that gets upgraded in the future. Is that correct?

This is true but its not the problem. If I were to switch image-tools to jimp-compact and jimp-compact fell behind Jimp, I would want to switch back to original Jimp - so I prefer to keep image-tools with original Jimp version.

That basically means if a user has both image-tools and image-output -AND- we dont use same library, then the installation is larger (jimp and jimp-compact wont be de-duplicated by NPM)

Not a huge problem.

@BartButenaers

output enable button : that is one of my favorite features, because now I can keep my image viewer nodes in the flow, even when I don't need them at the moment. No data will be transferred anyway ...

I agree - a good feature.

@BartButenaers

no output pin : Oh what a bummer... That is indeed VERY useful to avoid cloning. However I don't think this can be combined with the output enable button. Damn. Don't know a solution for this

Actually, you can have a button AND an output (it isn't pretty - but it works)

@BartButenaers

full data url and missing mime type : Ok that indeed should be fixed.

Yeah, including Image URL

@BartButenaers

Am I correct that the output pin is the major bottleneck to be able to merge both nodes?
Or do you see other major problems to merge them?

Current hurdles for me are...

1. Must be able to handle full Data URLs
2. Must be able to handle full Image URLs (you get this for free when you fix No.1)
3. Must be able to handle filenames (easy now you have Jimp)
   (All of this is handled in image-tools if you wish to save on dev time)

Current sticky point (but not a problem for me personnaly)

• I greatly prefer NOT to switch to jimp-compact so either image-output changes to jimp OR we do nothing (NPM doesnt dedupe, user has larger install - but everything continues to work)