https://github.com/Berrysoft/gal/issues/21

We'd like to consider if the config.yaml could include other files. This will make the project easier to organize.

Consider this folder structure:

config.yaml
  └─paras
    ├─ja
    │ ├─start.yaml
    │ └─end.yaml
    └─zh-Hans
      ├─start.yaml
      └─end.yaml

However, we need to consider these problems:

• Is this structure forced or alternative?
  • If alternative, we need to extend YAML grammar, and it is not that easy.
• When are the files loaded?
  • If they are not all loaded at first, we need to refactor many APIs to async.

Related: #56

Add this features to all frontends.

The GUI will search for data.frfs, and then data.a.frfs to data.z.frfs. All existing files will be included.

From: ljlorljl [email protected] Topic: 请求解答一些疑惑

尊敬的王 宇逸学长： 很高兴能看到您在2022年11月5日发表的演讲：使用Rust开发的视觉小说引擎，因为您的引擎开发项目能够促使下一代视觉小说引擎的开发（目前大多数视觉小说要么使用老旧的吉里吉里，要么使用大才小用的unity），我十分赞赏您开发的Ayaka。我将您的演讲实况转载到了哔哩哔哩（视频链接：https://www.bilibili.com/video/BV1wM411m7oN ），同时在评论当中b站用户提出的问题我想请您解答一下： 你们思路有大问题，，，， “

1. 你为什么要引入新语言，你们有专门的调试器吗？有专门的文档吗？如果我是视觉小说作者，我要考虑的是上手成本

2. 为什么要引入Web？直接走DX或者Vulkan不好吗？一个视觉小说，最重要的是一定的效果表现力。如果说rust生态有局限，重写就没有意义，如果说课程要求，当我没说。live2d是个好选择，但有时候有没那么必要。

3. 在我看来，视觉小说应该注重资产管理，你们有没有资产管理的工具？有没有场景调试的工具？有没有预制一些动画特效和转场效果？

4. 视觉小说的对话树你们有吗？帮助大家简化设计的工具有吗？如果你是从根本上解决这些问题，拿熟悉的语言去重写一个引擎是有必要的，否则就是重复造轮子 “ 期待您的答复！

此致 LJL

We finally named this project Ayaka today. It is such an important day, because we finally stopped calling it gal.

About this project

Ayaka is currently a project for OSPP 2022. According to the rules, we should show our work with a merged PR. Here is all our work recently. Contributions are welcomed after this PR is merged.

About the name

The frontend is Ayaka. The runtime is Ayaka. The script is Ayaka. Just Ayaka.

What we've done

• A cross-platform visual noval (VN) runtime with rust
• A well-defined and easy-to-author VN config file format, based on YAML.
• An embedded custom script.
• CLDR-based i18n support.
• A flexible plugin system based on WebAssembly. It provides hooks of the runtime and interop functionalities with the script.
• A decoupled framework - the frontend, backend and plugins are decoupled.
• A CLI frontend to check grammar errors and debug quickly.
• A GUI frontend powered by Tauri and Vue.
• A proto LaTeX frontend to generate PDF from the config.

Non-goal byproducts

• stream-future, a helper crate, separated from this repo.
• A language matcher based on CLDR data in Rust. We need it to reduce the ICU dependency.

What we need to do before merging

• [x] Rename gal- to ayaka-. Rename gal binary to ayaka-check.
• [x] Separate fallback and locale out.
• [ ] Draw a new logo. We should not infringe the copyright of miHoYo/HoYoVerse, but we all love Ayaka.
• [x] Organize the docs, the book and the README.
• [x] Archive the old repo.
• [x] Write reports.

What we will do after merging

• Enable github actions & dependabot.
• Copy opened issues from the old repo.
• Publish the SDK to crates.io.
• Make some advertisements?
• ~~Write some GalGame.~~

Updates the requirements on wasmtime to permit the latest version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

https://github.com/Uni-Gal/Ayaka/blob/c01f74587a641377ff81222d3974379837609390/utils/ayaka-script/src/line.rs#L46

Ayaka Script 允许 | 和 || 算符的存在，要么换一个算符，要么就要写一个复杂的 parser。

/cc @LaoshuBaby

Ayaka Script 是完全没有国际化支持的。与之相关的资源文本虽然有国际化支持，但是在执行脚本时只是将当前语言的资源字典以及 fallback 传给了解释器。这相当于没有国际化支持。

同时，Ayaka Script 的嵌入方式非常自由，因此给国际化也带来了很大的压力。

我现在计划分离 Text 的 parsing 步骤，将 Action 分成两部分，一部分 ActionParams 是不变的属性与计算好的结果，不随语言变化；一部分 Action 在需要显示的时候即时获取，以保证所有的显示内容与当前语言匹配。但是由于 Ayaka Script 没有国际化支持，这个重构面临着某些强耦合。

代码示例1：

- \exec{ format.fmt(#r1, 123,456) }

提问：如果 r1 在不同的语言下有不同的值， format.fmt 在何时执行？

代码示例2：

- \exec{ format.fmt("{}", random.rnd(10)) }

提问：如何保证 random.rnd 只执行一次？

代码示例3：

- a = \exec{ $a }
- b = \exec{ $b += 1; $b }

提问：其它语言的文本怎么写？

我们也许需要一种新的语法来解决脚本语言的问题。

Fixes #3

• [x] Separated paragraphs
• [x] Separated resources
• [x] Adjust frontends
• [x] Adjust examples
• [x] ~~Lazy load paragraphs & resources~~
• [x] Fix bugs
• [x] Update Ayaka Book

Bumps pixi.js from 6.5.8 to 7.0.5.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Now we simplify put all files on the disk, and try to find them at runtime. It is not suitable for deployment.

We plan to take steps one by one.

• [x] Don't check files' existance through WASI fs. #57
• [x] Use tar as the pack format. #57
• [x] Resource override rules. #63
• [ ] Add compression?

Docs: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleinterval

Haven't modify npm check because frondend tech-stack dependency update frequently.