MegaPint: Rework

The MegaPint Package is getting a massive rework.

At the moment the package includes all functionality and resources in one package which increases the needed disk space.
In addition the package so far is build with unity’s old EditorGUI system.

To reduce unwanted disk usage in your project and to increase stability as well as making it easier to work on the project in the future
MegaPint is started from scratch with a new system.

 

Improved Package System

From now on every feature will be released and updated as it’s own separate package.
These packages are all hosted on gitHub.

In order to use any of those packages you need to have the MegaPint base package installed. Afterwards you could either install all wanted packages into your project via gitHub or use the newly implemented MegaPint internal packageManager.

The packageManager will automatically import and setup the packages if you install them through there. Every version of the MegaPint base package will include bug fixes or new functions in their own packages. This means if a package was launched with MegaPint 1.1.2 it is not accessible in MegaPint 1.1.1, but available in all newer versions.

 

Switching to Unity’s UI-Toolkit

MegaPint was build on the old UI-system, which is quite harsh to handle and can cause problems.
Since Unity already released new UI-systems MegaPint will now use the UI-Toolkit. This will allow for a much smoother development and makes it possible for MegaPint to receive a visual overhaul in the future.

 

The Plan Going Forward

MegaPint 1.0.0 is still quite a bit away and until then will not be usable without issues.
Since MegaPint 1.0.0 will not immediatly include all functionality the current MegaPint has, the current version will remain until all functions are transfered onto the new system.

MegaPint 1.0.0 will include

• Internal PackageManager
• Validatable MonoBehaviours
• Scene-AutoSave