Codea 2.0 Beta

Hey guys - sorry, been buried with work (building out 2 new datacenters, been doing 60+ hour weeks arguing with Cisco and Netapp and VMWare, oh my!), but glad to see a new beta coming down the pipe. I’ll try to monkey with it soon - I actually have it in my head to do some lua bindings and use it to remote-control my vmware stuff (that should scare the piss out of some of our security guys!). My job used to take 20% of my brain - and I could devote the rest to hobby stuff. It’s taking 99% now, sigh. It’s good - learning crazy stuff - but whoa, busy.

Quick question while I’m here - any concept of supporting ios7 controllers? I honestly don’t know the API, I’m hoping just hooks to the events would be sufficient. This is what put it in my mind: http://www.idownloadblog.com/2014/01/19/controllers-for-all-a-must-have-tweak-that-brings-ps3-controller-compatibility-to-ios/

Simeon - anything that makes projects more sharable is 100% good. Indeed - some way to export a project including all dependencies (not just shaders, but other local files and graphics) would be useful - It brings me back around to the “Codea Player” concept you had before (Codea without the editor - basically, drop project bundles into it, ideally universal, my iphone needs love). NO idea if Apple would flip their gourd or not about that nowadays. I don’t know if the runtime release derailed that or not, but the learning curve to making an app with xcode is a deterrent, as is the whole get-it-released thing.

Bugs:

  • Tabs don’t highlight red when there’s an error there
  • Tab with bluetooth keyboard does not indent multiple lines
  • Small issue, but you can’t see the “x” when adding a new tab in the dark theme
    Other than that, you fixed all the bugs I had on my bug list I had not reported.
    Thanks!
    About Codea Play, I would love to see that project come back. Just some ideas: You have the same projects, and you can play with the code (but it doesn’t save), or you can run code off your clipboard, or you can use AirCode. But I know that’s a ways off.
    Thanks!

Thanks @Zoyt, I hadn’t intended tab on a BT keyboard to indent multiple lines, but I can probably add it. Normally the key command for indent / back-indent is Cmd+] / Cmd+[ — so I might use those instead.

Highlighting tabs with errors will come back soon. Same with the Shader Lab.

By the way, is there someone using iPad 2 that is getting a lot of crashes (I see about 6 in TestFlight). If you could tell me what Lua code is causing your crash it would be much appreciated.

Probably me, it seem there is too things, bluetooth keyboard and print output. I came back with more details asap.

I’m assuming you have plans to restyle side panel while playing the app? Also, I personally thing that the backgrounds of project icons should be dated.
Thanks!

@Zoyt side panel will be redesigned soon, date on the project icons is interesting and something to think about.

@toffer if you could tell me more about your issues with BT keyboards and print output, that would be great.

Oh, haha. (I’m on a Windows tablet right now, so it has horrible auto correct.) That was actually a typo. I meant to say something along the lines of the background of the project icons should match the new icon theme, but you probably have that planned. Thanks!

parameter.watch doesn’t work at all now. It just prints the string with nothing else. So parameter.watch("stuff") just shows the word stuff without showing the value of stuff.

Sorry @Andrew_Stacey, I broke it while debugging its behaviour.

@Simeon - Here is the project that crash often beta 2.10 : https://www.dropbox.com/s/j7bbfx6v6m2zjq8/parameters_menu.lua.

  • keyboard issue : using type2phone to from my desktop to act as a bluetooth keyboard (never experienced this issue with previous Codea version). It starts with non working tab key and Cmd/Alt-Arrows followed a freeze and a crash.

  • print issue: crash when I scroll output panel (even with small stack) or when I print from a loop (from ~20 iterations)

from the same project, when I create new tab before Main and delete it, the editor switch to the second tab (it main be the first) and this one display the content of the third tab, after that, I can’t reach the first tab.
Hope it’s help.

@Simeon I have the same issue as @toffer with print. If I print any amount of data, a fast scroll to the bottom will close codea. If I scroll very slowly then Codea keeps running.

Sorry about the crash issue with the output/parameter panes. I think the newest build (11) solves it (and a bunch of other stuff). Please let me know if you still experience this issue.

Here’s a selection issue:

  1. Hide keyboard
  2. Tap on a line number to select that line
  3. Move the end of the selection

The result is that the start of the selection will jump to the start of the tab instead of staying where it is.

Also, I’d really, really like to be able to use the select key to start a selection. That is, if I have the cursor where I want it then I like to be able to tap the side of that key to start the selection from that point (in the corresponding direction). I miss that a lot.

Ah, I will have to fix that selection issue. The menu also doesn’t appear (making selections at that point a bit useless).

Regarding the selection key, I will be putting the tap behaviour back in soon. However you should be able to touch and drag it left or right to form a selection from the current cursor position. Is this what you mean?

E.g.,

(Cursor is |)


self.|foo

Touch and drag selection key right:

self.|foo|
      ^^^ - selected

Touch and drag selection key left:

|self.|foo
 ^^^^^ - selected

Just a quick look.
New shortcuts are great addition ! Unfortunately, I can’t use the ones with ] because my keyboard is french mapped.

It seem that the comment uncomment shortcut with multiline selection remove the lines while keeping the comment block.

@toffer on a French keyboard it looks like the ^ and $ keys are in the same place as [ ]. We could localize the keyboard shortcuts, but I think perhaps creating alternate versions with Latin characters would work better: cmd+I and cmd+O

I agree for latin characters, if that’s don’t bother anyone else :slight_smile:

Can anyone tell me how their autocomplete works, for example:

If you type math. (i.e., math dot), do you then get a list of completions?

Or do you only get a list of completions when you type math.<letter> (e.g., “math” dot “a”).

The former is correct behaviour (and happens for me), the latter is happening for at least one tester. I’d like to understand how widespread this is.

@Simeon math. gives me the full list of completions. They do go off the screen and they are not scrollable, but i do not believe they were intended to be scrollable. So working as intended for me.

Thanks @Briarfox