![]() Notably, exported / embedded notebooks don’t show the cell editors. But you don’t get the whole Observable UI as part of that. You can download any notebook as a standalone module, which produces the same output (sandbox) results as you see on. It’s a trade-off, but I think improving the SQL experience on Observable is gonna require some of that, because SQL lends itself to more server intermediation than client-side web programming.Īnyway, bringing it back to export / embedding…!! That allows the notebook to hide some implementation details and synchronize some state. You don’t see all of the code that creates the table. In this sense the SQL cell’s results table is “privileged”, and more of a black box than other tables and visualizations you see on Observable. The SQL cell is different in that both the SQL code and the table of results (“input” and “output”) live entirely in the “editor” window (historically restricted to “input”). ![]() We have lots of “Inputs” components, but their state lives only in the “output” of the code, and there’s no (official) way to propagate it or persist it right now. If one slides a slider, it doesn’t slide for the other. The sandbox runs only on your own computer if two people are looking at the same notebook, they can see each other’s cursors in the editor, but each of them have their own personal private state in the sandbox. To produce a table, even in our official notebooks, we have to write code in the editor you can hide the code, but it’s still there. ![]() The editor is where you write code the sandbox displays the results, whether that’s a JavaScript object inspector or a DOM node, such a visualization or table. Historically these two windows have sorta corresponded to “input” (the editor) and “output” (the sandbox).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |