$mdThemingProvider - registering a theme on the fly

[rgolea]

Hi there!
First of all, I love Angular Material. I think you guys are doing an excellent job. Keep it up.

Secondly, and the reason I'm starting this issue is because I want my users to be able to register a new theme by adding 3 colour palletes together. I would like to search that in the database... so I will have active just one theme but I would need it to work with an ajax function...
The question is... is there a way to do that? Will it? Could you add a resolve method just like the routes?

If you want to see what I would be using it for... just check this out... rgolea/angular-deployd-admin@3dd2a6f

I'm making an angular-material dashboard (free and open source for anyone who may need it). But in order to take full advantage of the angular-material capabilities I would need to do that option.

Thank you very much.

[ThomasBurleson]

@rgolea - I recommend add a snapshot of the [expected] UX to your the Angular-DepolyD-Admin README.

Meanwhile, let me discuss this with the team.

[rgolea]

Here is a snapshot... My users will change the different palletes and then set that setting as active. That will be the colour the app will have for all the users. Imagine the case scenarios where your users want to change colours in christmas, on birthdays or who knows... and you want them to get really creative and to choose the different palletes to make the theme they want. I don't think for this case scenario watching the theme would be a good idea but if you can adapt it... it would be way better.

Sorry you can't see the colours but I was using my mongodb with a more recent version of the project.

Thank you for answering.

[websirnik]

I'm looking into similar functionality or best practice to achieve that. For us it's user's corporate colors that needs to be changed on a fly.

[rgolea]

The thing is that I was trying to change the theme in the .run() method and use $mdThemingProvider like a service. I found out later that you can't because you can't inject a provider in the .run() function. :(

[ThomasBurleson]

So the feature request is to be use post-initialization processes [such as .run() or $timeout callbacks] to be able to call an API similar to $mdTheming.theme('default').primaryPalette('pink')

[rgolea]

Yes. I'm not sur what you mean with $timeout callbacks. But we need it to be on run because on .config() you can't use $http nor a factory. We need to do something like this:

$http.get([url_of_the_setting]).success(function(data){
     $mdTheming.theme([custom_name]).primaryPalette(data.primaryPalette); //with secondaryPalette, warnPalette and backgroundPalette too.
})

So basicaly, use it on .run() or to have a resolve method like the $routeProvider or $stateProvider. It should look something like this:

$mdThemingProvider.theme([custom_name]).resolve({
   primaryPalette: function($http, $q){
          var deffer = $q.defer();

         $http.get([url_of_the_setting]).success(function(data){
                deffer.resolve(data.primaryPalette);
         });
         return deffer.promise;
  }
});

Even if this scenario is way larger, we could use that too. Whatever you guys think it's easier for you to get it working.

[ThomasBurleson]

@rgolea - my point is that developers my need it not only at .run( ) times but also at other times during the app lifetime.

[rgolea]

Oh yeah! For sure! Thank you a lot @ThomasBurleson . Keep up the good work! I really think you guys are making this project be the new Twitter Bootstrap for angular. Thanks a lot!

[Frank3K]

+1

There was previously also some discussion around this functionality in another issue, see #1269 (comment).

[nolazybits]

+1
We need this functionality too...

[remcohaszing]

+1