Skip to main content

Everything Text

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.

Comments

Popular posts from this blog

CSS sans DOM

CSS is amazing, but the HTML DOM isn't. It's just so heavy. Maybe if JSON or some similar format could replace HTML/XML, it could be made lighter? Better, I think, would be to use a human readable format like Eno . It's as terse but much easier to read than JSON.

Compile CSS

CSS is arguably the best means of UI customization. Consider an example of graphic-editing of UI elements: https://initialaudio.com/how-to-skin-sektor/ Using CSS, all elements in that project could potentially be done without graphics. Pros practically all designers now know CSS it's vastly capable Cons can't really decouple CSS from HTML whereas HTML is the biggest performance bottleneck (we'll solve this using different means) The Problem Unfortunately, CSS can get incredibly bulky. So what if we could design using CSS in a way that could feasibly be compiled to a local app? In general, everything would be styled using CSS, in the same bulky way it exists in browsers. But when compiled, it's no longer bulky. Benefits we have the full flexibility of CSS for all apps we have the full speed of native apps if needed

Why English

English is not superior to all other languages. It's just pervasive, enough so that many propgramming languages have English constructs built into them. If we're designing a system that uses natural language as a programming language, English is optimal since it's the most familiar.