gulix / ofelia Goto Github PK

Right now, the random part of the maze generation is totally random.

It could be good to add a "seed function", optional, that could be used to (re)generate multiple times the same pattern.

Check the position.

Set a min/max size for a path (to be taken into effect, to be visualized).

Currently, the mask feature is a "applied-once" feature. It cannot be replayed, it cannot be played with (like, for example, inverted).
It could be good to have a dedicated class.

The paths are "one-way" only.
What about branches? A path separating in two branches at some point ?
What about loops, with path getting back on itself ?

Generation of the image applying textures on post process

Setting a path to start later (one a specific point is reached, after X loops...)

In order to decorate drawings, logo or else, we have to be able to set some "positions" as not available from the start.

Why not use something like the python logo ? Round angle, head for the path.

Adding a visualizer/generator that makes a SVG file of the paths

Working on a better project organization, by following guidelines.

Right now, the image generation makes linear paths.
What about round one ? Or not linear ones ?

A visualizer should be disconnected from the maze generation (loop, paths, size...).

It could be dependent on some configuration (my visualizer cannot render loop, for example).
The idea is that the project is clearly two phases, with an open link between the twos.

Externalize the color management, with a dedicated class that could be inherited or filled with parameters.

Having some logs in generation (time to generate, loops...)
Also, getting some stats about a plane : number of paths, length, ...

Making animated gif of various generation modes.

Like the gif is generated, why not export to video ?

Right now, the gif generation replays the construction "step by step".

It could be useful to speed up (and limit the number frames, which can break the process) by skipping some steps (2by2, 4by4...) on large images.

Set how the path is generated (full random, likeness to change direction...)

In order to make future operations, tags will be added to path : group by tag (from the same origin ? with the same rules ?), by "age"

Using a known palette format, compatible with package of palette.

Ideas :
https://github.com/jiffyclub/palettable
https://jiffyclub.github.io/palettable/cubehelix/
https://github.com/BlakeRMills/MetBrewer
https://github.com/dzhu8/pyNationalParkPalettes
https://github.com/jakelawlor/PNWColors

Keeping the colorManager, but find how to use these palettes (format, loading)

Having some paths being able to get "under" others, if a "tunnel" is available to get under.

Bring about new structures : hexagons, square but with 8 exit points (diagonals).
Obviously, any visualizer would need to decide if it can (or not) run a type of structures or not.

% of appearance/occurence
Size of loops
number of loops in a path ?

Linked to #12