I would like to see a section in the custom class editor for transition and transform, plus CSS animation.
4 Likes
I would like these too (but there are a lot of options). At least an easier coding solution, like using our own editors, so we can make use of the tab key 
and take advantage of their features.
Then cmd + s syncs it with Blocs. (I know another app that does this).
Its a âwish listâ.
2 Likes
The current options in the side panel are fine for basics but not as efficient or flexible as I would like for more advanced usage.
1 Like
+1 used a code editor that syncs with the main app, too. Liked that feature for adding handwritten css.
Canât agree more. A little bit of 
for the âPlusâ version would be welcome.
3 Likes
While I can see why this would make sense, I donât agree that such features should be in the Plus version.
For example, I wrestled with the thought of purchasing Blocs Plus but I donât need WP capabilities (at least not at this time), but I would like to have the image editing capabilities - since itâs a lot more convenient that spinning up an image editor just to do basic changes. Yet I would be forced to pay full price just for that convenience.
I feel that Blocs Plus is best for features that cater to niche needs, not something that benefit all users. I donât mind paying for added features but if Blocs goes in that direction, it would (or could) be doing itself and itâs user base an injustice by forcing users to buy a Plus version for which they would only use a small percentage of.
I think these kinds of features should be in a upgrade rather than a Plus version.
But⌠I do agree that this feature would be awesome to have.
The fact is all updates from 4.0 upto 4.4.1b2 have been for all users. As a Blocs Plus user I (may) expect after 4 major, regular, updates some upgrades in advanced features added to the âPlusâ version. Easier coding solutions would perfectly fit into this.
Just my two cents on this beautiful Saturday 
2 Likes
I hear you @Jerry. Since I donât have Blocs Plus, I assumed the Plus version is a plug-in (like adding brics). But based on your comments, I guess Blocs Plus is a complete Blocs app all to itself, the only difference being the added stuff like WP, etc⌠And so in that regard, I can understand your stance.
Regardless, I feel this should be separate, so that users can upgrade while retaining the option to pay for niche needs. But those are my thoughts. Otherwise Blocs & Blocs plus would each have to be compiled to include these feature, or fork the future of Blocs to include WP and all future features as an upgrade for all.
1 Like
Some will go for the plus version because they want something specific like WP theme development, while others will upgrade for a balance of extras or just wanting the full package, even if they wonât use everything.
I guess there has to be some point of separation and this gives Blocs users some choice. When I posted the original point I didnât specifically imagine it as a plus user feature, but I think it would most likely be wanted by plus users.
Just as an example, if I look at something like a series of styled buttons and decide I would like them to fade in with a lazy animation after a delay I can currently do that in the side panel, but if there are 10 such buttons I have to repeat the steps 10 times, which is thirty separate selections.
This is slow and opens the door mistakes when the dog is barking or the phone rings. It would be far more efficient if that animation could be added to an existing custom class and applied everywhere in one step.
1 Like
Exactly. Thatâs why I felt that it shouldnât be part of one version or another. Features like these are universal in the world of web design. I couldnât imagine a web designer feeling that basic image editing and advance design tools would be of no use to them, unlike features like WP, where not every web designer needs it.
But if it were more of a plug-in(meaning WP), all would retain the option to pay for that specific tool when the need arises. Considering that there are two versions of Blocs, why would features like advanced tools be made available to just one version? If thatâs the case I think users would be better served if all features were just one upgrade even if not all features are needed.
Thatâs besides the point of this thread though. I do think that your idea is a valid one and should be in both versions. 
In a case like this I suspect a plugin might be too fiddly to add. There will be many users who are perfectly happy to work with animations in the side panel and would continue to do so, even if custom class options existed.
The side panel has always been the area for broad general changes like you see with padding, while custom classes are for more precise control and at the moment we donât have that precise control in this area.
I think it would turn Blocs into a much more flexible tool and also help with something like Volt if it could add custom classes with animations that could then be applied inside the CMS by the site user offering them much finer control.
1 Like
I also try to avoid mixing sidebar and classes. Actually I very seldom use the side bar to set any style. It avoids confusion later on.
I agree and either do one or the other. Sometimes itâs just easier using the side bar, but custom classes have so much more control and when carefully planned far more efficient.