StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I'd say start with the user interface. Think about how the user will use your IDE.</p> <p>Will it work like Xcode 3? Xcode 4? A simplified version of either? Another existing IDE? Something largely or completely original?</p> <p>Draw sketches, whether on paper or in your favorite image editor. Try different layouts. Sketch the same thing different ways and compare them.</p> <p>Think of the different things the user will need to do. How will they do it? Does one method come at the expense of another task? Is it worth it?</p> <p>Once you have an idea of how your user interface will work, you'll find that your model and your controller layout will follow from that.</p> <hr> <p>It sounds like you've thought about at least some of this already, so I'll address only a couple of your specific items:</p> <blockquote> <ul> <li>Have a simple editor, text-view-based, for example, without syntax coloring, check, highlighting; however to design it in such a way to allow future development of syntax coloring/ check, via a NSScanner, for example;</li> </ul> </blockquote> <p>Parsing C code with NSScanner will be a bag of hurt. There may be a suitable text view/syntax-colorer already existing that you could use; I, for one, would do a good thorough search before embarking on such a task myself. If I had to write something like this from scratch, I'd look into <a href="http://clang.llvm.org/features.html#libraryarch" rel="nofollow">what Clang can do for me</a>.</p> <blockquote> <ul> <li>Having the project packaged into folder-like project files, with NSFileWrapper for example (that will include the main.c file, additional header, the autogenerated Makefile and a plist for project settings etc);</li> </ul> </blockquote> <p>Beware: NSFileWrapper used to not understand .svn directories. That was a big complaint about Interface Builder back in the 2.x days. They fixed it in IB years ago, but I'm not sure NSFileWrapper ever got the fix.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload