🔼Upgrading from API v2.1
Follow the compatibility notes when upgrading your mods from API v2.1
Last updated
Follow the compatibility notes when upgrading your mods from API v2.1
Last updated
When upgrading your modification from the target of the later version of Nitrocid KS that declares itself to be from the API v2.1, you must make necessary changes to be able to use your mod in a Nitrocid KS version which you use to test your mod.
The following changes were listed sequentially as development went on.
This version was released to make groundbreaking additions and improvements.
Custom screensavers used to implement the ICustomSaver interface to implement the screensaver logic. Now, it has been removed in favor of the new screensaver class implementing the newer IScreensaver interface, BaseScreensaver.
This breaks all the existing screensavers that still use the old ICustomSaver interface. This has also resulted in the removal of the CustomCustom() function and reimplementation as ParseCustomSaver.
All new screensavers should use the BaseScreensaver class. All existing screensavers should migrate from ICustomSaver to BaseScreensaver.
As for the parser, it has been reimplemented to take only the screensaver DLL files.
CommandBase.Execute() was implemented to replace the above function, so we decided to remove the function as it only supported one command at a time, and you had to make a switch case statement for each command executed.
BaseCommand.Execute can be overridden in the below method signature:
Filesystem module was a god class
, so we decided to consolidate it to their own separate files to accomodate with the upcoming changes. However, you need to use their own namespace (for example, if you want to copy a file, import KS.Files.Operations
) to be able to use them.
We have also removed SetSizeParseMode()
as it's redundant and it was there for compatibility reasons.
The base Filesystem
module will stay so that path neutralization and invalid path detection routines will still be available under the same namespace in 0.0.24.0 and above.
Removed functions:
SetSizeParseMode()
New namespaces:
KS.Files.Attributes
KS.Files.Folders
KS.Files.LineEndings
KS.Files.Operations
KS.Files.PathLookup
KS.Files.Print
KS.Files.Querying
KS.Files.Read
Choose one of the above namespaces to select the kind of filesystem operation you're going to do. However, these namespaces were written at the time of the change commit date, so the API documentation always gets up-to-date.
This enumeration used to hold all the 255 console colors and their names for easier selection. It was just separated from the Color255 module to put it directly to the KS.ConsoleBase namespace
You can still use this enumeration in the ColorSeq library.
As Dictify got released, we decided to remove these functions and use them from the library.
You can still use these functions using the Dictify library.
We have moved all network transfer APIs to KS.Network.Transfer
to further organize the network APIs.
We have moved all color-related console APIs to KS.ConsoleBase.Themes
as it keeps getting expanded.
We have moved all input-related console APIs to KS.ConsoleBase.Inputs
as it keeps getting expanded.
These four progress position variables were used to indicate where the splash manager should write the progress percentage and progress report. Splashes are now responsible for these.
We advice you to assign these variables in your splash code instead of using these fields.
CommandPromptWrite()
CommandPromptWrite()
used to be the helper for UESH to write its own prompt, but it's eventually replaced by the more powerful WriteShellPrompt()
to accommodate all possible cases, like custom variables, and so on.
Your shell should use the PromptPresetBase class to define your own shell prompts.
The shell base has been divided to three types:
Aliases (namespace: KS.Shell.ShellBase.Aliases
)
Commands (namespace: KS.Shell.ShellBase.Commands
)
Shells (namespace: KS.Shell.ShellBase.Shells
)
Use the above namespaces if you want to perform operations in your own custom shell.
We didn't want to cause confusion between ProgressColor
in the FancyWriters
namespace and the actual ProgressColor
in the ColorTools
module, so we decided to extend the name of the progress bar writer module to ProgressBarColor
.
To utilize the progress bar writers, you need to use the KS.Misc.Writers.FancyWriters
namespace and use the ProgressBarColor
class methods.