MMM-ProfileSwitcher, A Profile/User/Layout Switching Module

tosti007

@strawberry-3-141 thank you for helping @Mar

@All @Mar I didn’t know that that browser doesn’t support those features. I will rewite those parts so then it should work out of the box.

tosti007

@all I pushed a small update so that older browers should also be able to use this module.
@Mar They are the same changes that you made.

Mar

@tosti007 Thanks for updating your module so quickly! and obviously thanks for taking the time to respond and maintain.

tosti007

@all Thanks to @roramirez we now have Spanish translations! :D

mortenbirkelund

@tosti007 When switching between profiles, there is a short timespan where both the modules of the old profile and of the new profile, is present at the screen at the same time. Is there a way to ensure that the old modules fadeout first, and once they are gone, the new modules will fade in?

tosti007

@mortenbirkelund Yes there is, however that would mean that the code has to loop over the modules twice, which isn’t a great thing to do performance wise. I will write a bit of code that does it for you and post it here soon.

Edit: here is the code, all you need to do it replace the whole set_profile function inside the MMM-ProfileSwitcher.js file.

The code:

// Change the current layout into the new layout given the current profile
set_profile: function (useEveryone) {
    var self = this;

    var options = {};
    if (self.config.useLockStrings) {
        options.lockString = self.identifier;
    }

    MM.getModules().exceptWithClass(self.config.ignoreModules).enumerate(function (module) {
        if (!self.isVisible(self, useEveryone, module.data.classes)) {
            module.hide(self.config.animationDuration, function () {
                Log.log(module.name + " is hidden.");
            }, options);
        }
    });

    MM.getModules().exceptWithClass(self.config.ignoreModules).enumerate(function (module) {
        if (self.isVisible(self, useEveryone, module.data.classes)) {
            module.show(self.config.animationDuration, function () {
                Log.log(module.name + " is shown.");
            }, options);
        }
    });
},

Note: Once again this is not so great performance wise, but I dont think you will notice much of it

mortenbirkelund

@tosti007 Thank you very much. Very kind of you to create the code for me.

I am new to using Git. How do i alter your my copy of your module, without risking that it will be overwritten on an update? Or is that not something that i should be concerned about?

mortenbirkelund

@tosti007 In case anybody is interested, the block of codes that enables the modules, should be altered a bit in order to take the animationDuration into account.

		setTimeout(function() {			
			MM.getModules().exceptWithClass(self.config.ignoreModules).enumerate(function (module) {
				if (self.isVisible(self, useEveryone, module.data.classes)) {
					module.show(self.config.animationDuration, function () {
						Log.log(module.name + " is shown.");
					}, options);
				}
			});			
		}, self.config.animationDuration);

tosti007

@mortenbirkelund By altering the code git won’t allow you to pull the new updates, in case of an update you will have to clone it manually again. And thank you for sharing the timeout :)

tosti007

Another side note I just realised, if you do use that setTimeout and you swap between profiles in rapid succession I am not sure and cannot quarantee that some of the modules will be shown properly