I implemented #2 for Textastic 2.0 because I could use the same interface as for the FTP client.

I plan to add a feature that saves information about the used connection when you upload or download a file:

Say, you downloaded a file from your Dropbox. Textastic then saves the remote path and the connection used for the download. This creates a "link" between the local and the remote file.

You can then upload the file or download a newer version of the file with just one or two taps!

The cool thing is, that this works for Dropbox AND FTP and any other type of remote connection I might add in the future.

Yes, when you have a file opened in Textaxtic, you can tap on the "action" button (right-most button in the toolbar) and use the "Open In..." command to open the document in other apps registered for this file type.

Thanks for the detailed information. I'm sorry that you had to go through the trouble of reinstalling the app.

Although I can't reproduce it, I've limited this setting to a maximum value of 1000 for the next version.

This is now implemented for the next version.

Which iOS version are you running? I can't reproduce it on 4.2.
Did you try to restart the device?

See comments.

Have a look at http://feedback.textasticapp.com/feedback/7436-dropbox-support/ for a discussion of Dropbox support. Actually, I've already started the implementation (along with FTP support).

As for Flex MXML files, I'll add the extension to the list of XML extensions, as MXML is XML.

In the future, please create separate feedback entries for every issue.

Thanks for your feedback!

Interesting. But, I plan to implement both a WebDAV (also for iDisk) and a Dropbox client.

The next version of Textastic supports displaying of Chinese and Japanese text. Actually, most unicode characters will be supported. This version also supports input using the Japanese and Chinese keyboards in iOS.

There's only one drawback: the drawing of characters not found in the font selected in the app's settings take significantly longer to draw because I have to use CoreText to draw the characters in the correct color. But for normal html pages or source code files with some Japanese sentences there won't be much difference.