If the connector is enabled by the prompt or via a UI interaction, it calls your MCP server. They have created some meta fields your tool can respond with, one of which is something about producing a widget along with a field for html.
In the current implementation, it makes an iframe (or webview on native) that loads a sandboxed environment which then gets another iframe with your html injected. Your html can include meta field whitelisted remote resources.
Fully charged show did an episode on this car (or maybe just this era.) either way, I found it interesting to see the similarities in design to todays evs considering how early so many of these concepts were.
I would like to see comparisons for things in the same price category too. Especially for something like usb-c cables where it's hard to know if you are just paying for a brand or actual quality.
Most of the time when you buy Apple you are buying a better engineered product and maybe these scans are just proving that it's actually hard to match their quality for the price.
Exact same thought here but with their Caseta lineup. It is one of the most easy to configure and reliable smart home things I have in the house.
I still use HA on a RPi4 for other things, typically via Zigbee, but the Casetas always work like you'd expect from a light switch while also enabling smart stuff like voice control or automations.
Couldn't agree more. I have no problem paying for tools, especially when they will save me time.
That said, don't I need to know how to use devtools (chrome/ff/safari) to do my job in the first place? It feels like this product is trying to inject itself into a process that isn't super refined but works fine.
The real problem is the dependency it creates. If I only know how to do frontend work with handheld UI controls, then I have to use them and am locked into this product. It doesn't promote me learning the css rules or understanding how to actually fix things, so then I'm back to the devtools and why am I using this?
A bit pessimistic though right? Carbon capture through both natural and engineered methods is a thing that could have more investment/incentive if that were the case which counters the idea that just because CO2 hangs around a long time doesn't mean there's nothing to be done about it.
Obviously, it'd be great to limit the production of more CO2 going forward but I don't believe that everyone will collectively just give up.
In the current implementation, it makes an iframe (or webview on native) that loads a sandboxed environment which then gets another iframe with your html injected. Your html can include meta field whitelisted remote resources.