Océane Patiny
Océane Patiny
> Not super convincing indeed but I don't think we should spend more time on this for now. Ok, I'll still need for @targos' feedback then
> Feedback on what? I agree with you the result is ugly Considering what @lpatiny said, should I try to fix this or not? > Not super convincing indeed but...
Current state of the `strokeWidth` branch - `drawRectangle` was modified to use `lineWidth` but the `out` option doesn't work - plenty of tests don't pass because the implementation of `lineWidth()`...
A better way of enhancing performance would be: - Draw the contour first - Find one point inside of the polygon - Make a `floodFill` using the previous point as...
Here is a first draft of an API to implement stacks in `image-js-ts`. Any feedback @stropitek , @targos , @lpatiny ? ```js export class Stack { /** * The number...
> There could be a method that normalize them so that they have the same properties. What would you expect from a function normalizing the images? - resize all images...
> Should all images of the stack have the same properties (dimensions, bidDepths, etc) ? I agree with @lpatiny that the images could have different dimensions, which could be made...
Would it be interesting to add a method allowing to read all images from a folder and directly create a stack with the images?
I've used the following script to verify wether it is the function itself or the test environment that make it slow. ```js const { readSync, ImageColorModel } = require('./lib/index.js'); console.time('a');...
Crosscheck was implemented in image-js/image-js-typescript#199