US3 - Multiple Input Elements

[chris-kuehn]

Value proposition

As a user, I would like to make adjustments in the art generator to create my own custom artwork.

Description

Acceptance criteria

• [ ] the background color slider changed to an overall slider in order to change the color of the background and the artwork
• [ ] you find a rotation slider to rotate the artwork
• [ ] you find a slider to change the amount of outlines of the artwork
• [ ] you find a variation button to create variations of the outline element's line width

Tasks

• [ ] add input elements type range
• [ ] add a variation button
• [ ] define useStates for the input-Elements
• [ ] implement a loop to draw the outline elements
• [ ] implement an array wich stores the randomized line-width-values in order to use the amount-of-outline-slider independently from the line-width-randomizer
• [ ] change the state variables with the input elements

Size L

[CJAkkuec]

Re: VP

As a user who has already used the art generator I would like to see an archive page where I can see the artwork I have already created, in order to store all the artworks I have created in one place and view them again

As a user I want to be able to store the images I've created using the generator so that I can view them again.

Best to keep it concise. ;)

Re: Acceptance Criteria

a new page called archive is created

Not an acceptance criteria, unless you want to express that the user can access it.

Re: Tasks

creae

*create :D

add the CanvasOne component to the page

I'm not sure that's what you want to do. Shouldn't you want to be able to save the image you created rather than displaying the canvas again?

[CJAkkuec]

Re: Acceptance Criteria

minimum two more input-elements to customize the art work

Please state a fixed number of inputs. Please also state what they do.

the artwork should change by using the input-elements or by using a re-render-button

The "expected" behavior would be that the artwork changes with every increment the handler is moved in either direction - think: color pickers, etc. If you want the user to move the handlers and then submit a new artwork "request" based on the given specifications, then you need the button. You need to state what the behavior should be, otherwise the AC can't be met.

Re: Tasks Your tasks are going to be quite different based on how you define the approach mentioned above.

create branch "multiple Input Elements"

I'd prefer you name it something like feature/customization.

[chris-kuehn]

Thanks for your feedback. I have adjusted my user story.