My biggest beef with most of the code editors out there is the lack of console logging and error reporting. Correct me if I'm wrong, somebody, but Firebug Lite just doesn't cut it when dealing with JS errors - you know, syntax errors, illegal tokens, undeclared variables, attempting to call a method on an undefined object (a pretty common error), etc.... All the javascript errors that Firebug or Chrome would normally catch on a desktop just aren't caught with FB Lite.

This app needs more robust, built-in error reporting beyond linking in an external library that is, itself, powered by Javascript and so presumably dies as soon as an actual JS error is thrown. What's the point of that? Coffeescript has a pretty robust error logger, and CodePad has a mediocre one, but at least they'll catch the errors in the following, whereas Textastic with Firebug Lite just does nothing at all. You're in good (bad) company: Koder and Kodiac both suffer from the same disease. See the error-ridden code below:

console.log("log");
alert("hey");
fffx(); // undefined function 
ggg.h() test $< // method on undefined function and then illegal tokens

Not to appear completely negative,the Navigator is epic, and your options for file interchange are best in class.

Just really surprised that you can't really use this app for JS development, since there's no way to report JavaScript errors. Am I mistaken?

I saw it on my old iPad 1 and my new iPad 2. Sometimes if I write something... closing the keyboard and selecting something, then the keyboard not pop up. 

I have an HTML file that includes a .less file and then the JavaScript less compiler. When I preview with textastic, Iit appears that none of the JavaScript has executed.

Are there limits on js execution in the preview?

Suggestion:
In ultraedit i have already the text files for the abb robot programing code( rapid) I missing this option in textasticapp!
Forseen that you have the option "others" in the syntax difinition list in textasticapp

then select the syntax text file , and your own code syntax is installing.


Thanks

Textastic doesn't apply them even if they are active system-wide.

Line numbers make an editor look cool, but their practical utility is near zero — no one uses them for anything except perhaps when dealing with bug reports. They do consume precious screen real estate, especially in vertical mode, and I can see less code because of them.