(Tag names are freely interpreted ) I found a base64 en/decoder capable of processing utf-16 here YQBsAGUAcgB0AF8AYgB1AGIAYgBsAGUAXwB0AGkAbQBlAG8AdQB0AA= The settings are stored as base64-encoded utf-16 key-value pair strings. To enable the script manually, there must be a prefs.dat in the folder wuid-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx noted in the widget.dat, containing at least the following structure: Īdditionally to that, you may have to manually initialise the widget settings within the pstorage folder.
This usually happens through the javascript/extension engine during runtime. I think you'll understand the syntax yourself, it is quite self-explaining if you have some widgets installed.ĮDIT: I just found out that adding a new entry to widget.dat will install the extension to Opera, but it will be deactivated as it hasn't been initialised.
You will find a XML-file called widget.dat in the folder: C:\Users\%Username%\AppData\Local\Opera\Opera\widgetsĮach widget has an entry there. Opera extensions aren't installed via the registry. Opera 12 uses another extension architecture than the following Opera versions!
0 kommentar(er)
