It’s camel case because that’s how React does inline styling, as far as I know. I don’t know if there’s an easy way to translate between them; you might be able to approximate the correct results with CaseFormat if you’re trying to do something programmatic.
Note for some styles you will have to add !important, transform is one of those styles that will need it.
You can only really figure out which by inspecting the browser element… (or memorizing all the igntion default styles ((dont do this lol))
You can make empty classes and reference them in your theme file, so that you can still apply the style to components by adding that style class to them.
You’ll need to add psc- in front of the class name in the theme file.
Well, I never tried it, never needed to, but I can’t see a reason why it wouldn’t work.
@PGriffith How about direct access, from the designer, to the theme file ?
One interesting thing here is that it’s not a resource the same way we consider everything else to be a resource because it’s gateway based and not project based. When the tags eventually make their way into being a gateway based file resource, it will really enable the ability to create editors for gateway based resources like this. Right now it would require some workarounds since it’s not technically a “resource” the way styles are. Someone savvy enough could create a client-side designer module that enables this, but it would be relatively hacky since it wouldn’t leverage true Project Resources.
It's actually not that hard to create a screen in perspective that allows you to do this. Just read the directory into a tree and open each file in a text area component. I made one for the project I'm working on right now. Maybe I'll export it when I'm in the office tomorrow and post it, if I remember.
We're currently working on a first-party solution where we provide a stylesheet resource which is editable in the Designer and which can be used to configure CSS between themes and Named Styles. Should hopefully be available in 8.1.22, but no promises.
This is actually pretty useful as it saves having to RDP into the server to modify theme files, and can also be used to edit other resources as well thanks for sharing!
Might be something to consider adding to the Exchange.
One suggestion though, would be to convert it from a coord container into flex containers
That is a good idea. I hadn't really intended for it to be used by anyone else... hence only accounting for one screen size. If I have time I'll spruce it up a bit and add it to the exchange. I also don't know how well it'll work on non-windows gateways.
I wonder if you can set the owner to all 3 of us so we can all make changes in the future if needed? I wouldn't mind editing it to allow modifying other project resources (JSON) as well (in a structured manner)