Skip to main content

Posts

Showing posts from October, 2018

Familiarity and workflow

Blender is a 3D design software with a built-in video editor and a powerful compositor, among other relatively hidden gems. The advantage of these tools in a 3D design app might not be obvious to some but it saves from having to learn workflows of multiple apps. Once a user is comfortable with Blender's basic workflow and key commands, it's much easier to learn other parts of the software. Rather than exporting rendered videos to edit in another software, they can use the workflow they're already familiar with to edit within Blender.

To be forthright, Blender has a steep learning curve. It takes time to get acquainted with it. The reward being increased productivity through familiarity with an intuitive and fast workflow. Once that time is taken, the same workflow can be applied to other aspects of design like video editing and compositing.

What we want is a workflow that's far easier to learn than Blender's. Notepad for Windows provides our base experience. Anyone…

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.
Prospractically all designers now know CSSit's vastly capable Conscan'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.
Benefitswe have the full flexibility of CSS for all appswe have the full speed of native apps if needed

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 basicall…

Markdown vs HTML

Markdown converts to HTML. It’s designed to do that. But it’s drastically simpler in form than HTML. What if we could replace HTML altogether?
Right now, Markdown is built to support HTML directly. So to support Markdown is to support all of HTML as well. What if we just remove the HTML support and build Markdown as the language the browser understands natively?
Benefits:
Markdown is far easier to read than HTML.It’s far faster to parse, no open/close tags.Smaller file size; since there are no open/close tags. Tying in with the proposal to code in English, Markdown would provide a familiar, written form to compliment the English language.
CSS and JavaScript Both CSS and JavaScript can be included using code blocks.
body {background: white;} console.log('This will be executed.'); Further Consideration Various projects already exist to simplify use of Markdown either within HTML or by using an HTML page for boilerplate and Markdown file(s) for content.
Consider this: https://news…

OpenGL Everything

Recent terminals like Alacritty and Kitty have proved OpenGL is the fastest way to handle text rendering. Xray, the potential next generation of Atom text editor rightly seems to follow suit. Meanwhile, Linux distros like Ubuntu have long been using OpenGL for general rendering to great success as seen with compositors like Compiz.It seems OpenGL might be the best technology for any and all rendering needs. If an OS is built on and uses OpenGL for everything, the consistency could yield great results. Text editing, image manipulation and even office apps would be as fast as possible.

The Text Editor

Text editing comprises the core of an operating system. Every OS ever provides some way to edit text. Even the terminal or commandline is a text editing experience. We should build the best possible text editing experience into the OS.Temple OS as inspirationIn Temple OS, the text editor is everything. The commandline is actually a programming experience since commands are compiled as they’re entered. Meanwhile, a special document format (DolDoc) lets users structure text for easy navigation similar to HTML but better because of the way it links to other documents. That’s all part of the same core text editing experience. And that experience distinguishes Temple OS. The text editing experience is all its focus.Markdown for powerIf we use Markdown for structured documents similar to Temple OS’s DolDoc format, we can advance it steps further by allowing code execution via code blocks. Code blocks are executed when documents are opened for viewing. We can use that same concept for any an…

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.

Code in English

Code from programming languages ultimately gets compiled or translated down to some sort of digital code that a human would have difficulty reading.
The languages exist so humans aren’t required to read or write at the machine level. <- Lisp facilitates reasoning rather than attempting to be readable.
If the goal of programming languages is readability, why not have a single, human readable language? And why not just make it an actual language? Early languages like BASIC and COBOL were mostly based on English. We now have means to significantly advance that idea.
Let’s program using plain English.
Advantages:
Most of the world knows English so most of the world would know how to program (no need to learn a language).If code is universally in English, it’s re-usable across all platforms.Addresses concerns and frustrations with code comments. Comments aren’t much needed when code is in plain English. Markdown as a starting pointMarkdown, at least for now, provides an excellent startin…

Scripting and Storytelling

People wouldn't generally see a link between programming and storytelling but if programming involves taking a user through a guided experience using code, it's fundamentally the same. At its core, programming would involve a colorless and purely logical experience. But it's still an experience. Graphics and sound would tend to make the storytelling process more evident. In the case of game development, the storytelling process is probably clearest. But even where a programmer is just composing a sequence of commands to be repeated, potentially endlessly, that series of commands is nonetheless an experience. Optimization is likely the highest goal, to be the fastest and most efficient. So the experience they're crafting is one of ease for the end user. The end user wouldn't worry about their machine overheating due to inefficient code nor would they wait needlessly for the machine to complete its task. We want to build a software that most empowers programmers to…

Make it Easy

The easiest way to get an idea recorded is the best way. You can teach a child to write sheet music but if there's a faster, easier path to recording musical ideas, that path is better. Sheet music is beautiful, no doubt. But the underlying musical ideas are the true beauty, whereas the written form is a reflection. The method that most expedites recording those ideas empowers the composer to capture the most beauty. We endeavor toward that optimal method and thus may discover a more beautiful expression of it. At the very least, we can return to the historical beauty of sheet music upon discovering it's greater than we first realized.

The Higher Goal

With our focus on storytelling, it should quickly become clear that we're poised to tell the most enthralling story of all; the story of our creator. There can be no greater success in storytelling than to tell the greatest story in the greatest way. And that is our lofty goal. With that defined, we have the best possible intention in working toward the best possible end.

Storytelling

Storytelling seems to underlie all media. Video production, music composition, writing. Whether for a bland, fact-based documentary or an animated cartoon, all these artistic tasks involve a process of storytelling. We must create the optimal experience for storytelling through software, remembering even this process of building software is one of storytelling. We know the resolution, the creation of a software that best facilitates storytelling. Working toward that goal, we should consider all we do, even these very words, as key to success. If we begin building with the focus on storytelling through written language, we can later add elements to handle specifics such as audio and video meanwhile providing an encompassing base capable of dealing with every conflict.