Skip to content

Latest commit

 

History

History
120 lines (101 loc) · 4.77 KB

DEVELOPERS.md

File metadata and controls

120 lines (101 loc) · 4.77 KB
Raw

Fox's Magisk Module Manager (Developer documentation)

Note: This doc assume you already read the official Magisk module developer guide

Note: official repo do not accept new modules anymore, submit here instead.

Index:

Properties

In addition to the following required magisk properties

# Magisk supported properties
id=<string>
name=<string>
version=<string>
versionCode=<int>
author=<string>
description=<string>

(Note: The Fox's mmm will not show the module if theses values are not filled properly)

This the manager support these new optional properties

# Fox's Mmm supported properties
minApi=<int>
maxApi=<int>
minMagisk=<int>
support=<url>
donate=<url>
config=<package>

(Note: All urls must start with https://, or else will be ignored)

  • minApi and maxApi tell the manager which is the SDK version range the module support
    (See: Codenames, Tags, and Build Numbers)
  • minMagisk tell the manager which is the minimum Magisk version required for the module (Often for magisk xx.y the version code is xxyzz, zz being non 00 on canary builds)
  • support support link to direct users when they need support for you modules
  • donate donate link to direct users to where they can financially support your project
  • config package name of the application that configure your module (Note: The icon won't appear in the module list if the module and target app is not installed)

Note: Fox's Mmm use fallback here for some modules
Theses values are only used if not defined in the module.prop files
So the original module maker can still override them

Installer commands

The Fox's Mmm also allow better control over it's installer interface

Fox's Mmm define the variable MMM_EXT_SUPPORT to expose it's extensions support

All the commands start with it #!, by default the manager process command as log output unless #!useExt is sent to indicate that the app is ready to use commands

Commands:

  • useExt: Tell the manager you would like to use commands
    (Note: Any command executed before this one will just appear as log in the console)
  • addLine <arg>: Add line to the terminal, this commands can be useful if you want to display text that start with #! inside the terminal
  • setLastLine <arg>: Set the last line of text displayed in the terminal
    (Note: If the terminal is empty it will just add a new line)
  • clearTerminal: Clear the terminal of any text, making it empty
  • scrollUp: Scroll up at the top of the terminal
  • scrollDown: Scroll down at the bottom of the terminal
  • showLoading <max>: Show an indeterminate progress bar (Note: Status bar is indeterminate if 0 is provided)
  • setLoading <progress>: Set loading progress if the bar is not indeterminate.
  • hideLoading: Hide the indeterminate progress bar if previously shown
  • setSupportLink <url>: Set support link to show when the install finish
    (Note: Modules installed from repo will not show the config button if a link is set)

Variables:

  • MMM_EXT_SUPPORT declared if extensions are supported
  • MMM_USER_LANGUAGE the current user selected language
  • MMM_APP_VERSION display version of the app (Ex: x.y.z)
  • MMM_TEXT_WRAP is set to 1 if text wrapping is enabled

Note: The current behavior with unknown command is to ignore them, I may add or remove commands/variables in the future depending of how they are used

A wrapper script to use theses commands could be

if [ -n "$MMM_EXT_SUPPORT" ]; then
  ui_print "#!useExt"
  mmm_exec() { 
    ui_print "$(echo "#!$@")"
  }
else
  mmm_exec() { true; }
fi

And there is an instance of it in use

# mmm_exec only take effect if inside the loader
mmm_exec showLoading
ui_print "The installer doesn't support mmm_exec"
mmm_exec setLastLine "The installer support mmm_exec"
# Wait to simulate the module doing something
sleep 5
mmm_exec hideLoading
mmm_exec setSupportLink https://github.com/Fox2Code/FoxMagiskModuleManager

You may look at the example module code or download the module zip and try it yourself

Have fun with the API making the user install experience a unique experience

Also there is the source of the app icon here .