In order to achieve this, we would appreciate any and all feedback on challenges encountered when using Textastic.
Please also have a look at the manual.
Be sure to vote for the features you want to see implemented!
The editor interface is great, but file creation flow for the remote server is too slow. We need to first create a file locally, then edit it, then upload manually onto the server. Why don't just support *Link* for folders? When I download a folder from a server, it should be linked to the remote server and any new files I add into the folder should just be automatically uploaded into the same folder in the server.
I'm looking for a way to keep some highly sensitive information on my iPad. I'm thinking about files being encrypted by an individual password on the iPad from within Textastic. The file should be encrypted when it its closed (probably asks for an explicit "close the file now" button). The password must be entered to decrypt the file when it is opened in Textastic. Encrypted files would stay encrypted even when sent to other places (cloud, mail, dropbox, WebDav, etc.).
It would be great if you could implement something like cocoa http server instead of using a file path so when we're building web pages we can use the likes of less, angular, backbone which all currently won't work because of being a file path protocol and not a local web server.
To clarify further, having this ability also gives us the opportunity to have something similar to Codea's "Aircode" and to run Ajax requests in page, it will throw a security error at the moment because of not being a http protocol.
Right now I am learning XML and trying to create a schema for Balsamiq (unofficial schema for my workflow), but I have to fire up VS 2012 RTM on my laptop and I need to constantly flip between a schema that works with intellisense and one that still has issues, not to mention having a tutorial page open to learn the specs. As I have described, you can imagine I have limited visibility of either schema, which means I need to constantly adjust the size of the window panes. This has another problem, there is no scrolling synch (unlike Word 2007-2013), which makes it extremely difficult to spot differences.
Why do I still use this method?
Intellisense is the reason, being allowed to reference known Schemas makes my job a little easier.
1. Add ability to reference Schemas, so that autocomplete works with XML and other XML related languages (XAML, YAML, XSL, XSLT, etc).
2. Add ability to store custom Schemas and reference them with other Schemas.
3. Implement a synchronized scrolling feature that allows users to spot differences between 2 documents (similar to the Notepad++ diff plugin or Word 2010 if you want to wait to add diff).
(feature request copied from an email by Jon Edlund)
Customer support service by UserEcho