What's new in Advanced Themer 2.1

[@WebsiteStudiosOfficial]

This is huge towards complete control and customization. What a simplified way to manage development with the variable manager alone. But it never stops with just a huge update, there are always multitudes of little features that just increase QoL. Thanks Maxime!

[@mr.matt.eastwood]

Holy cow!! This is amazing. I'm about to start a new project so THE PLAYGROUND IS OPEN :-D Thanks so much!

[@petrovui]

Awesome.. New level!

[@DimitryChamy]

Truly amazing work so thoughtfully executed.

[@jugibur2117]

Wo, incredible work, you're talent and diligence are admirable! PS: @28:25 Maybe you could add a slight light border around the colors for better contrast? Do you think it's generally / technically possible to add a SASS compiler in the css editor? Especially for using own functions / mixins. May be the sources could just be files / libraries, because functions and mixins doesn't change frequently.

[@AdvancedThemer]

Yep it’s on my list 👍

[@IssaKhlief]

Great update, I always have this question in AT, if you created a border with clamp function as a variable, what you should put as a minimum and a maximum value? I saw you put (PX) but how about border color and style?

[@AdvancedThemer]

I never use clamp for border-width. I always use px for it. You could use different variables for border-color and border style, but Bricks border controls aren’t friendly for variables. I normally create a custom class for borders, and use my variables inside the custom css control.

[@AyDeeSandra]

👍. Is there a way to use “clamp” as opposed to using “min” and “max” for fluidity? e.g the headings. Edited: I see its doable with custom variables

[@AdvancedThemer]

Min and max fields inside the variable manager are used to calculate the clamp function already - there is no min() or max() css functions involved

[@AyDeeSandra]

@@AdvancedThemer Silly me. Just got to 14.00 and you just explained it. The ease at which you develop AT is incredible. The Oxygen and Breakdance community need to steal u for a while. 👀

[@spacevertex]

ACSS recently copied the right click contextual menu from Oxyprops and also copied the automatic BEM classes converter from Advanced Themer. Is it possible that in a year’s time either ACSS will eclipse AT or AT will eclipse ACSS in terms of functionality?

[@AdvancedThemer]

In terms of functionalities, AT is second to none. ;)

[@spacevertex]

@@AdvancedThemer I am rooting for AT, and I think it’s a great product offering. However, it lacks a framework option like ACSS/Oxyprops, with right click contextual menu, which I think is a genius idea - No typing, point and shoot. If AT offers something similar or better, then AT will rule the market I reckon, as currently one has to make a choice between installing both add-ons or choosing one over the other. Too many plugins = too many plugin conflicts. Let AT be a one stop solution for Bricks. Kindly consider it as a feature request.

[@AdvancedThemer]

@@spacevertex why would you choose one over the other? AT works well with any framework/bricks plugin.

[@I9Chris6I]

1. "recently copied from oxyprops" is not quite correct - the first demo of "plaster-plugin" - which acss aquired, was actually posted a few weeks before the release of the oxyprops context menus. Not that it matters, those features are awesome and should in fact be copied and improved, as they help users! 2. The "auto-bem" was called class converter in Advanced themer. And if you compare the first version to the current version, it is obvious that maxime took more inspiration from Acss's auto-bem than the other way around. Also - not judging here, and so shouldn't you. Its not like those features are patented or something. Copying the best things from one another makes both products better, which everyone is happy about.

[@maximebeguin4346]

@@I9Chris6Iyour second affirmation is just ridiculous…

[@stewartr7648]

Just updated, and the CSS Variable Picker has stopped working for me. I'm going to rollback to check everything was fine in the previous version. Anyone else having problems with the CSS Variable Picker? BTW - loving the update :-)

[@AdvancedThemer]

Make sure to send a support ticket to [e-mail] - I’m happy to have a look 👍

[@AdvancedThemer]

It has been fixed in 2.1.1

[@stewartr7648]

@@AdvancedThemer amazing support 🙏🏻

[@Flemming1980]

Can see that colors from the color manager now work, which is really nice. However, custom variables no longer work in editor mode.

[@AdvancedThemer]

Thanks for pointing that out. I’ll check it and release a fix in 2.1.1. Btw, to be sure bug reports don’t get lost on social media, please use the bug report on the website so I can easily track it 👍

[@AdvancedThemer]

It has been fixed in 2.1.1