A new version of om-css is ready for testing with a new API: 1.1.0-SNAPSHOT. The docs are on the develop branch. This requires the latest Om version 1.0.0-beta1.

https://github.com/untangled-web/om-css/tree/develop

It has the following improvements: No need for a macro on your render. Eliminates CSS duplication when more than one component composes in the same subcomponent. Makes using your localized classes easier with a map destructuring syntax instead of a special key in the attrs.

Thanks to @timovanderkamp, who collaborated with me on the new design, and did most of the coding.

@claudiu I’d encourage you to try ^^^

so, kind of an odd question: in working through the dev guide i don't see any place mentioning a url or port in any of the server interactions - is untangled client just pulling it from config somewhere?

@adamvh So, depends on the example. Some of them use fake networking and local js code for the server. In the ones that use a real server: you have to start the server. Yes, it uses a port from a config file, and then you must load the page from that server’s host/port (localhost)

at that point, the comms just go back to where the page came from