Hi Guys,

I was just wondering what is the best way to load J Query onto websites I am working on in Textastic. I have heard that a specific file is needed to compensate for lack of mouse when coding on an iPad or iPhone. Otherwise I think that the app is brilliant.

Thanks,

Mark

Being able to edit files directly from dropbox without having to download them first. 

The app shuts down when I try to connect to my SharePoint WebDAV server. Seems like a great editor but I can't use it.

I work on my site in my public dropbox folder. So I download the files locally edit them and then upload them again to see results online. So if the work is good and I want to deploy it to the we server, how do I do that? Currently the upload button only does it with the dropbox, how can I take a file that I downloaded from dropbox and upload it to an ftp server?

Some keys on the sliding row get used more than others. It would be good to be able to adjust the sequence. For example i use (){} and ; a lot!

I've found that I'm missing the TextExpander and Additional Keys panel when entering text in the Find and Replace text boxes.

Any reason they're not active in that UI?
Is that easy to add?

Currently, Textastic interprets FTP file listings as UTF-8.

A user reported that this doesn't work for an FTP server which uses Korean (EUC_KR) character encoding. In this case, Textastic shows an empty file listing when there is at least one file with Korean characters in the directory.

There should be a way to choose the character encoding for each FTP connection.

This is mainly an issue with large files.

When device rotation occurs, the page position changes due to many lines becoming wrapped (or unwrapped). This in itself isn't a horrible problem, but what tends to happen is this: 

I am at line 5500, the file is 6200 lines. 

I rotate to portrait. It pegs me at the bottom of the file. This clamps the y-offset.

Now I rotate back to portrait in hopes of returning to line 5500. I am dropped off around line 4000.

This is... not... ideal. 

One great way to fix BOTH issues is to check the line# and return me to that position upon device rotation. 

Note also that having a cursor present will prevent this issue (which is probably why this has not been reported yet). However having a cursor makes over 1/3 of the screen consumed by a keyboard so I *ensure* the keyboard is put away when I use Textastic to read code (as it's hardly practical to do actual coding), but it causes this issue every time (when i am near the bottom of a file).

So since I am JB'd i would use tweaks that let me force specific apps to be portrait-locked, but it's just not ideal because sometimes I do need to go landscape when the line wrapping gets to be overwhelming.