an autotit-based script to handle compressed 7z km extensions
KEM is available in 2 versions
for 9x systems(95, 98, me):
http://kmext.sourceforge.net/keih/kmextman9x.7z
for NT systems(2000,xp, vista):
http://kmext.sourceforge.net/keih/kmextmanNT.7z
KEM has 4 functions:
1- displays extensions in an array
2- online(web) installer
3- local installer
4- ext uninstaller
how it works:
the online installer first executes through a macro, to access the installer..right click on a kmext 7z link and select km extension
KEITH (part of KEM) will download the extension, decompresses it and extracts all files/folders in their designated destinations in kmeleon's folder.
please note, that the km extension menu command will always be greyed out(disabled) and will only be active on kmext.sf.net, this precaution is for 2 reasons:
1- ensuring the extension is in 7z format
2- ensuring the extension has the necessary uninstall ini for KEM
as an extensions manager, you can access KEM from the tools menu
clicking the drop down menu displays a list of the installed extensions
selecting the extension(by it's uninstall ini) and clicking uninstall
the ext install button triggers the KEIH local file extension installer
KEIH function's installing procedure is identical to KEITH only just for local files
note..that installing(web/local) and uninstalling extensions will close k-meleon and restart it. the functions also support kmeleons running with a loader.exe and additionally they will always delete compreg.dat and xpti.dat upon either installing or uninstalling ensuring that the components are always registered properly.
for an extension/macro to be supported by KEM, it must include an ini file containing instructions for the files that will be removed upon an uninstall..that ini file is naturally deleted as well.
for now, there are few extensions that are supported by KEM.. i've updated and uploaded about 20 or so but we have around 230 extensions and macros so updating all of them will take a while but hopefull will be done by this weekend
for now, if you'd like to test KEM.. you can download/install those extensions which have been updated
adblockplus
blockfall (game)
archive edit
capture plus
_---------------------------------------------------------------------------------
for ext/macro writers
to enable uninstall support, the package in 7z should include a folder called: "kmextensions"
inside kmextensions will be the ini file with all the necessary info for KEM to parse
here's an example of the
adblock uninstall ini:
[macros]
1=adblockplus.kmm
[chrome]
1=adblockplus.jar
2=adblockplus.manifest
[components]
1=nsAdblockPlus.js
[kplugins]
1=adblockplus.dll
[plugins]
[pref]
1=adblockplus.js
2=adblockplus_extra.js
[locales]
[tools]
[scripts]
[skins]
[stylesheets]
[profile]
1=adblockplus
[root]
[strings]
this ini instructs KEM of the adblockplus files/folders that are included with the extension and must be removed upon an uninstall.
fields where the extension does not have files can be left empty without problems
explaining the fields
[macros]the extension may contain up to 5 macros .kmm or folders location: root\macros
1=
2=
3=
4=
5=
[chrome]support up to 4 files in the chrome folder.. 2 jars and 2 manifests location: root\chrome
1=
2=
3=
4=
[components]support up to 8 component files location: root\components
1=
2=
3=
4=
5=
6=
7=
8=
[kplugins]support for 1 k-plugin for each extension location: root\k-plugins
1=
[plugins]support for 4 plugins location: root\plugins
1=
2=
3=
4=
[pref]support for 2 pref files per extension location: root\defaults\pref
1=
2=
[locales]support for up to 7 locales (kml) for each extension location: root\locales
1=(e.g.) es-ES\blockfall.kml
2=others\blockfall.kml
3=
4=
5=
6=
7=
[tools]support for 5 files and or folders per extension location root\tools
1=(e.g.)bogus-extension\tutu.exe (file)
2=bugus-extension (folder)
3=bugbog\beebee.au3 (file)
4=
5=
[scripts]support for 1 script (js) per extension location: root\scripts
1=
[skins]support for 4 bitmaps per extension location: root\skins\default
1=
2=
3=
4=
[stylesheets]support for 5 stylesheets(css) per ext. location: root\styles
1=
2=
3=
4=
5=
[profile]support for 3 files and/or folders per ext in the profile folder location: active profile directory
1=
2=
3=
[root]support for 3 files in root location: root
1=
2=
3=
[strings](not implemented) active profile
special conditions; for macro, tools and profile directory locations.. the ini may contain folders (without an ext suffix) for those 3 locations only KEM can delete folders as well as files listed in those places. for example if you have an extension that is created in a subdirectory in the tools folder..no need to list all the files in that folder and simply just add the folder name which will be deleted along with any files in that folder.
Edited 1 time(s). Last edit at 10/03/2009 07:20PM by disrupted.