Still need to think how to handle it, it seems that the flux
architecture is something that can be Ok for us. The workers stores the
state, and the ui handle pulls and render the thing. This is exactly
what we want here.

We should reduce the risks of mis-uses of the API here.

- Borrowing llvm context, don't dispose of it
- Didn't init all the needed things for the JIT
- Incorrect buffer size for the random generator
- Log what's happening in the temp/lock file thing

Kubat a rédigé 1 year ago et Kubat a validé Il y a 8 mois

Vivy:
- Use upx to compress executable if possible
- Rename libvvs to libvivy as it is only inteded to be embeded into Vivy
  and not into the vvs runtime
- Compose every crate into the vvs_cli to parse, lower and set
  options/subtitle files

Script:
- Update VVS files
- Parse VVS files
- Base JIT initialization
- Use full_moon for the scripting things, we use a base of Lua for VVS

Misc:
- Correct samples + clippy + update
- Fix README
- Update example files for scripts
- Remove not really needed fonts from the repo and from being bundled into vvcc
- Fix qrc file + move the aux table out of the ass crate

Codegen/JIT crates:
- vvs_runtime: only the JIT runtime thingy, re-exports the types module
  of the vvs_runtime_types crate
- vvs_runtime_types: only the types that will be used in the generated
  code, usefull for the vvs_runtime crate and the vvs_codegen crate
  because we need to know the layout of the types to generate the code
- vvs_codegen: transform the Vivy Script AST into a LLVM module

Kubat a rédigé 1 year ago et Kubat a validé Il y a 8 mois

Also use bash explicitly for .bash scripts.

Will need to connect properties and factors to sliders to test what is
best easily

Use "_vv_" instead of "___" for special struct members

Search for openmp in find_package, to prevent fail at linkage if llvm
openmp is missing from system
Add explicit template specialization for QPair

No need to send content change as AssLinesModel retrieves it from the
LinePtr