Anixx,
like any other application-related macrolanguage (or script language) KM's one is the scripting way to manage the application not by GUI, but through scripts. Or macros.
Well we call 'macros' both the kmm-files and single 'command units' (I don't know how to call this correct - I'm not a coder) in this files that are responsive for some particular action.
These macros not only can change prefs or add menu items. They do interact with KM application itself, forcing it do some useful things - single, multiple, cascading, parallel, etc.
Every macrofile (*.kmm) is read on the startup and usually it adds some GUI element (menu item, button, hotkey) to interact with user, to give user new possibilities, new options and functions of browser. But also they may have no one - just defining the conditions to do something automatically.
Well, KM macros are that thing what you call 'addon' or 'extension' in other browsers.
But also some in-built basic functions of K-Meleon browser are implemented through macros too. So we can say KM is natively modular and extendable browser.
You can read more technical
info about KM macrolanguage here.
Edited 2 time(s). Last edit at 02/14/2017 09:51PM by rodocop.