fdb75017

4 ms·

1. 1.▲
   by fdb75017 2y ago

   Thanks for your feedback ! Well I'm proposing to have a workspace with everything structured indeed, where all the documents would be "programmable" and "queryable" and where unstructured data would simply be attach
2. 2.▲
   by fdb75017 2y ago

   OK I see. I think exporting to JSON Schema is a feature to implement. But again, there would be some situations where the 2 representations would not be reconcilable: you would not be able to stream out views & methods to JSON Schema, a
3. 3.▲
   by fdb75017 2y ago

   Thanks for your feedback ! It does not rely on JSON schema at all, the idea was to build a representation that binds together data structure, views and behavior in a self-contained way (like .xlsx does). There are a few tools that do enable
4. 4.▲
   by fdb75017 2y ago

   Thanks ! No, sorry, it's not yet open-source, but i think it will be at some point.
5. 5.▲
   by fdb75017 2y ago

   OK, thanks for your words !
6. 6.▲
   by fdb75017 2y ago

   By standalone web component do you mean like a React component that you can embed in your own app ? Or something more "bundled" like a VS Code extension ? In terms of scope, you are thinking of both the "Editor" and the
7. 7.▲
   by fdb75017 2y ago

   Many thanks for your feedback, very useful ! Yes you are right, the complexity at first sight is a problem. The onboarding journey should be clearer, and indeed there is too much jargon to digest before you can really start. That's als
8. 8.▲
   Show HN: Hyper Workspace – A no-code framework for JSON(hyper-workspace.onrender.com)

   19 points by fdb75017 2y ago|14 comments