Pixel and vectors, video and text. What if we built one editor that could handle all these cases and more? One editor using one human-readable text format for files. If we use Markdown, we can use code blocks to represent binary data, if needed. Besides being able to store binary data, we could create human-readable data sections using formats like Eno. We could even include executable code. With the flexibility of Markdown and its respective code blocks, we could store any type of data in a manageable way. So the file format for our all-purpose editor is plain text, Markdown.
We'll build our editor for text processing. But from the start, we must account for all editing needs. We're building a text editor that can do what Photoshop does, and what Premiere does. So first and foremost, everything those editors can do, our editor must be able to do using plain text. From there, we can create intuitive graphic interfaces to facilitate different workflows. Those UIs will basically utilize shortcuts to the plain text methods we've built into the core, the same way Gimp and Blender use Python for core processing needs. Ultimately, everything is based on plain text commands. UIs will provide intuitive shortcuts to those commands.
We'll build our editor for text processing. But from the start, we must account for all editing needs. We're building a text editor that can do what Photoshop does, and what Premiere does. So first and foremost, everything those editors can do, our editor must be able to do using plain text. From there, we can create intuitive graphic interfaces to facilitate different workflows. Those UIs will basically utilize shortcuts to the plain text methods we've built into the core, the same way Gimp and Blender use Python for core processing needs. Ultimately, everything is based on plain text commands. UIs will provide intuitive shortcuts to those commands.
Comments
Post a Comment