#Textastic bluetooth keyboard how to
#Textastic bluetooth keyboard update
#Textastic bluetooth keyboard pro
#Textastic bluetooth keyboard code
#Textastic bluetooth keyboard mac

Personally, figuring out the GUI interactions has always been the most challenging aspect to designing the scripts. The limitations for me are my own limited programming experience but fortunately Mozaic is well documented, there’s Textastic, Ki’s work, threads like this, and the many working script examples on that enable me to create scripts of my own. I’ve had a similar experience with using Textastic and ’s extension which works great. Two taps is all it takes to jump to any event in Textastic with ‘s extension. CMD + any old pair of related symbols would work.

That time that is better spend on developing new stuff which brings in fresh money and said:Īnd/or some quick way to jump back and forth through any lines. That doesn‘t mean i don‘t have wishes for language extensions, but i understand that the structural changes needed to implement them would take time to develop and test - and probably bring new bugs to stuff that already worked well. In my eyes, Mozaic is a very complete, round package.

#Textastic bluetooth keyboard code

So a redesign of the elements and rewrite of the already optimized drawing code would be needed even for this seemingly simple task. And you can’t combine 16 pads with the XY as there is not enough space. If one would combine for instance 10 faders with 4 knobs this would result in a gap (since the XY is about 2.5 knobs wide). Pads, knobs, faders and XY have the same dimensions on all layouts. Perhaps not even new fixed layouts, as i assume the possible combinations are already there.Īll gui elements currently use fixed sizes.

#Textastic bluetooth keyboard update

I also don‘t think that we get an update with adjustable or configurable layouts. The current editor is good enough for medium sized scripts and one can easily use external editors with more features if scripts get longer. Text would be needed to be parsed on typing, not only on ‚update‘

Syntax highlighting would require a mayor rewrite of the text box that is currently used.

Adding search/replace or other edit functions would require a new buttons, which need a gui redesign.

Then I'd move the script over to IOS using think an update of the internal editor is unlikely.

#Textastic bluetooth keyboard mac

So I could write and test Streambyter scripts on the Mac using a nice keyboard. StreamByter code can run on IOS and also on a Mac using the Mac 'MidiFire' app. If we could just export the IOS screen onto the Mac and use cut and paste between the Mac and an IOS app I'd live on my Mac. I also wanted to write on my Mac but I find using files and iCloud or file passing mechanisms were just to slow for me.

He doesn't write an app before he has a designed the GUI for example.

#Textastic bluetooth keyboard pro

When I have a version to publish I save it in Textastic with a useful version number extension and upload that script file into the PatchStorage a total pro and writes the best Mozaic code you'll find to read. So, cut and paste between editor and Mozaic code windows are the most productive method for me. I generally add some new feature and test it. There's also a Textastic App for Macs so you can make syntax checking/highlighting work in that editor as well as the Sublime Editor I think. If you come from a Windows world Textastic might be more to your tastes. Never learned Emacs but maybe there's an app for that.

Textastic has a find/replace capability that I've learned to use for navigating around the code when it gets really large but Vi is supreme for that type of coding flow.

#Textastic bluetooth keyboard how to

I wrote a lot of scripting tools in Vi over the years and I love its features for find, replace and moving blocks of text around so I might start using the Vi editor since I was given a clue on how to make the apps font larger so I might value editing productivity over syntax high-lighting. There's a Vi Editor app for IOS if Vi is your thing. Look for the comment/video on of the big Mozaic thread: I do some runtime testing and I might fix small changes in the Mozaic text window for speed sake but eventually I 'select all' and paste the code back into the Textastic Editor before adding any significant amount of additional created a Mozaic syntax highlighter/checker for Textastic so I bought it. Debugging in Mozaic can sometimes be too frustrating if you can't find your logic flaw. That can be useful to rollback if some new feature just seems to be breaking things. I immediate save the script and add versioning numbers to the files I save periodically name98, name99, etc. Periodically I 'select all' in that editor and paste the whole code segment into the Mozaic code window displacing the prior text completely. I use a Bluetooth Keyboard and Mouse on the iPad and enter syntax checked text into the Textastic app.