TODOs

[zfengg]

Guide rules

• Performance matters while a successful implementation comes firsts.
• Simple to use while allow maximal flexibility.
• Increase modularity.
• Fit Julia ecosystem.

Check list

• [ ] matlab :arrow_right: julia
  • [ ] find an idea package to produce the smooth interactivity of matlab figure. candidates: Makie.jl
  • [ ] plot large number of polygons or shapes with high performance. candidates: classic methods of Plots.jl, GMT.jl
• [ ] Develop a package IFSs.jl as API to structs of IFS.
• [ ] Prepare a bunch of Pluto notebooks (for future possible presentations or tutorials).
• [ ] Host the Pluto notebooks on MyBinder when it is officially available, WIP like pluto on Binder!
• [ ] add support for the complex IFS
• [ ] ...

[johnnychen94]

I notice this package doesn't have CI enabled. Maybe you can take a look at julia-runtest for unit test, CompatHelper for automatic compatibility checks, TagBot for automatic release tag creation, and Documenter for documentation. People often just use https://github.com/invenia/PkgTemplates.jl to generate a "standard" julia package layout, which also includes an out-of-box CI setup.

Develop a package IFSs.jl as API to structs of IFS.

It's not recommended to use abbreviations as package names, how about the name IterativeFunctions? Many Julia packages use the plural form as package name, e.g., OffsetArrays implement an array type OffsetArray.

[zfengg]

@johnnychen94 Thanks a lot for the suggestions and I will consider the more expressive name IterativeFunctionSystems.jl.