Initialization method define background and text colors not randomgly about evo-poster HOT 4 CLOSED

I create a script named ColorGenerator.js for creating colour palettes based on a random base colour. I used the 'simpler-color.js' library to support the generation. I created four methods that blend multiple strategies: (i) generate colour pallete that comprises the complement colour of the base colour and another analogous colour, (ii) create triad pallete; (iii) generate a colour pallete that comprises a complementing colour of the base colour and one triad colour, and (iv) generate a "harmonious" colour palette based on a default method of simple-colour.js library.

By empirical observation, we selected the first one. Genetic operators are also modified.

from evo-poster.

What user story does this refer to? Is this needed in a minimally viable product?

from evo-poster.

You suggest it in our last meeting, i think. We talk about be necessary to find a way to make colour generation less “random” (ensuring that all the colours work well together). Personally, I think that totally makes sense.

While this is not directly connected to any specific user story, it aligns with the overall objective of enhancing the system’s exploratory capabilities, which is a key aspect referred to in the user stories. Due to the exploratory characteristics of the system (stories #1, #23 and #5). It makes sense be part of MVP since it enhance the value of the first version of product, compared to other similar systems.

from evo-poster.

You suggest it in our last meeting, i think. We talk about be necessary to find a way to make colour generation less “random” (ensuring that all the colours work well together). Personally, I think that totally makes sense.

Makes sense, but the whole point of working with minimally viable products is prioritizing the features with strong interconnection.

While this is not directly connected to any specific user story, it aligns with the overall objective of enhancing the system’s exploratory capabilities, which is a key aspect referred to in the user stories. Due to the exploratory characteristics of the system (stories #1, #23 and #5). It makes sense be part of MVP since it enhance the value of the first version of product, compared to other similar systems.

Well, if it's a restriction it's more exploitatory than exploratory... This is why some user history and description of the problem are needed...

from evo-poster.