Pixi was originally designed to only handle image importing, but Pixi's functionality has expanded to importing other files as well.
As a direct result, Pixi needs to be remodeled and refactored to make support for new filetypes easier.
The refactored code should satisfy the following requirements:
Optimised structure importing (less/no freezing during import)
I'm picturing a loading process something like this.
Without blueprint interception:
PixiCommand “filename” -> determine filetype -> find filetype's conversion module -> get blocks to place from module -> place blocks
With blueprint interception:
PixiCommand “filename” -> determine filetype -> find filetype's conversion module -> get blueprints to place from module -> convert blueprints to blocks -> place blocks
Pixi was originally designed to only handle image importing, but Pixi's functionality has expanded to importing other files as well.
As a direct result, Pixi needs to be remodeled and refactored to make support for new filetypes easier.
The refactored code should satisfy the following requirements:
- Optimised structure importing (less/no freezing during import)
- Generic block placement (re-usable)
- Modular filetype importing (standard interface)
- Blueprint file loading & block conversion interception
I'm picturing a loading process something like this.
Without blueprint interception:
PixiCommand "filename" -> determine filetype -> find filetype's conversion module -> get blocks to place from module -> place blocks
With blueprint interception:
PixiCommand "filename" -> determine filetype -> find filetype's conversion module -> get blueprints to place from module -> convert blueprints to blocks -> place blocks
NGnius
added this to the v1.0 milestone 4 years ago
Pixi was originally designed to only handle image importing, but Pixi's functionality has expanded to importing other files as well. As a direct result, Pixi needs to be remodeled and refactored to make support for new filetypes easier.
The refactored code should satisfy the following requirements:
I'm picturing a loading process something like this.
Without blueprint interception:
PixiCommand “filename” -> determine filetype -> find filetype's conversion module -> get blocks to place from module -> place blocks
With blueprint interception:
PixiCommand “filename” -> determine filetype -> find filetype's conversion module -> get blueprints to place from module -> convert blueprints to blocks -> place blocks
This work has been completed in v1.0.0 (as of commit
1b126b69c0
)