|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Storm Documentation | Why?</title>
</head>
<body>
<h1>Why I created Storm</h1>
<p>
When I first started my IDE, Moonlite, seven months ago, I thought that creating
a syntax highlighter would be an easy task. After 3 months, I had figured out
that it was not. When I had first searched after a syntax highlighting
component, I found none that were good. So, four months ago I thought to myself
"there's absolutely no reason that everyone should go through this long process
just for making something as simple as a syntax highlighter."</p>
<p>
The result was Storm.</p>
<p>
When I decided to start Storm, I searched for something I could base my
TextEditor on. I found DotNetFireball's CodeEditor, which unfortunately had a
rather terrifying code. It was ugly, unstructured, filled with uncommented and
undocumentated code and worst of all, very inefficient. The only thing that
wasn't inefficient was the text rendering, which I later figured out that they
didn't make.</p>
<p>
So I started the task of making the code better. I realized too late that it
would've been faster just to make a TextEditor from scratch. When it was done, I
started the other Controls, and now that they're done, I'm presenting them to
use for your usage.</p>
</body>
</html>
|
By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.
If a file you wish to view isn't highlighted, and is a text file (not binary), please
let us know and we'll add colourisation support for it.
Submit an article or tip