would be a cool idea. But I assume some of those componenents are quite special and use non-public features? Not sure about that. At least thats how it appears to me in some cases. When looking at the browser source.
For the base settings you can always use the custom components. Thats what I start with normally. They have a lot sample code
I saved a few to Snippets Lab that I copied like for like for a couple components already. But just started another component that really should have everything in the kitchen sink included, and was like Urgggh
@Doobox That is just for page properties. But I do like the idea of us providing some more example components that use some of our control layouts making it easier for you.
If ever you need anything specific, just ask and we can post code snippets to help out
Nope, we’re only using the public API, nothing is private… anything we do in a component is available to you guys
Just clicking around in Elements reminded me of this discussion.
So before I forget (getting old), This seems like it might be fairly low hanging fruit when you guys get back onto the developer stuff.
Setting a “Use developer features” toggle in settings would enable, this and maybe more developer features like the debugger etc etc…
Then we’d get an extra context menu item here when right clicking a groups title bar “Copy Group”. Copies the groups json to the clipboard.
This would be super useful. Don’t know what other devs think, but I can’t imagine needing anything else, to aid development.
Sure eventually something in app with in app UI could be cooked up, but like I say. On the face of it, this seem like it just may be low hanging fruit in your codebase