HN user

tshepom

137 karma

contact: twitter.com/tscepo tshepohlala@gmail.com

Posts15
Comments30
View on HN

I built this to make it easier to see what I’m making as I’m making it. No extra installations or extra import step. Create React components visually or pull in designs as code from Figma, right inside the IDE.

Ah I see, yeah the "double-click to select container child/text" ux is meant to mimic keynote's implicit grouping mechanism, which works the same way.

It's mostly to prevent empty "phantom" containers that people aren't aware are affecting their project layout.

I've been thinking about changing this to the straightforward, single click to select whatever's topmost and visible. Will have to if the current ux bothers people.

This all makes sense, and I've definitely been feeling the integration pain when I want to export code elsewhere – GitHub support coming soon!

Thanks! If double-clicking or pressing the enter key while the text element is selected doesn’t work, it’s likely a bug. Are you using Firefox by any chance? I just tested on chrome and safari.

Great questions! I’ve got upcoming features for version control – it’ll still involve conflict resolution in git, but much easier than current code export methods. So far I’ve focused on good code export readability to address integration into existing codebases.

Thanks! Yeah it’s exactly that - pure js and canvas element for custom drawing. No UI frameworks. It’s all custom so there’s no open source reference, but I plan to release some open source stuff.

It's built entirely from the ground up – no ui libraries. It's focused on simple, PowerPoint-like usability instead of Webflow's complex, Photoshop-like approach.

Thanks! Pricing will be freemium, resembling Figma where we charge teams per seat or for usage past a certain threshold. But it’s important to me to keep it virtually free for the casual individual.

Google, for your codebase. Search code using natural language with our vscode extension, Metacode. Let me know what you think!

Queries like 'user sign up', 'delete file' etc. work even if those specific keywords don't exist in the code. Example gif is Metacode searching linux kernel.

Ah, interesting! The difference between Metacode and something like AppleScript is that the artifact left over from using Metacode is still the rigorous programming language you're used to. If we retain a query log, you could even convert your natural language queries into code comments alongside your code to actually improve clarity.

Of course: the app draws from a database of thousands of snippets that are cleaned up and generalized with some scripting. Natural language queries are handled like search, with semantic matching over both natural language and code structures. Content within the snippet like naming, "subject"/"target", and values are dynamic (use # to modify those values) – but it still needs work. As for auto layout, I actually have a feature for that on the roadmap but wasn't sure it was a common problem – bumping up its priority!