Codea Play

General
21

I was just about to say you can always bring it in LoveCodea and set the width and height on conf.lua to an iPhone screen size.

22

Has a release date for Codea Play been announced yet?

23

The competition deadline is Saturday, February 18. Don’t worry too much about time zones — we’ll allow some flexibility if it’s still Saturday wherever you are when you submit.

@Juggularity we can’t give a definite release date until Apple approves it. And it won’t be submitted for approval until the results of the competition are integrated, which will be a couple of days after the deadline.

24

@Simeon Just wondering… would you have any objection to the author of one of the winning games writing a non-Codea version of their game and releasing it as a standalone app/game on the App Store?

25

@frosty not at all. Though I’ve mentioned earlier that we’re releasing the engine portion of Codea soon as open source. It will be out shortly after Codea Play — so the Codea version could even be put on the App Store.

26

Wow! I Love the icon, Name and the Great Looking App. The only Thing for me is i have much to do in School. i already wrote a game in Case you start a competition, but you said it should have scoring, hah, but my game is a adventuregame… But the next competition will be Mine! Muhahahahah! Not. I’ll try to Set up something, and Enter the competition, but i dont think I’ll Get something acceptable till then… Thank you so much for this competition!!!

27

So… Is this kind of a Codea Viewer? I know you can send code to them and paste it in, but can the user save the project?

28

You basically have one tab to play with. It saves the code but you can’t create new tabs or new projects. So it lets you try out the features but isn’t practical at all for significant projects and you can only have one thing at a time.

29

Will users of Codea Play be able to access the source code to the winning entries in a single tab directly in the application?

Said another way, the winning entries will be like the examples in Codea. The users can copy them and edit them. But, they are limited to editing in one tab and they only have the choice between one copy tab of one example or one tab of their own experiments.

30

I agree with Ipda41001. That should be possible. Also, we should be able to save code as a runnable app, but not get the code so it acts as a Codea Viewer :slight_smile:

31

Sorry for all the questions

 also provide us with your name

Is that True Name or will an alias suffice?

http://en.wikipedia.org/wiki/True_name

Though, I make light of it, it’s a serious question.

32

An alias if you would like. However you would like the project credited.

33

Instead of adding a limited editor to it I would just add the feature to view the code.

34

@Ldsguy1 has a point. Then you don’t have to deal with the editor on the iPhone… Bit if it’s already done (which I’m assuming it’s fairly close), don’t bother.

35

Alright: Quetion roundup:

  1. Does the coding work on the iPhone.
  2. When we code something in the demo coder, will we be able to save it but not edit it?
  3. Will the examples be in the normal Codea?
  4. Will we be able to view the code of the projects?
  5. If there is an an iPhone coder in the demo, will it come to the full Codea?
    Thanks!
36

And related to that, will the buttons take up a similar footprint and be in the location as shown here

function draw() 
    displayMode(FULLSCREEN)
    background(123, 115, 30, 255)
    stroke(0,0,0,255)
    strokeWidth(5)
    noFill()
    rectMode(CENTER)
    rect(160,240,320,480)
    rect(240,160,480,320)
end
37

@Zoyt

  1. Yes. That’s the plan.
  2. It will save your edits, but you only have one project, with one “tab.”
  3. I would like to include them as examples in Codea.
  4. Probably not — if you want to do that you will be encouraged to get the full Codea.
  5. Maybe

@Ipda41001

The buttons will be exactly the same as those shown in displayMode(FULLSCREEN). That is the back, pause/play, reset, tweet, and capture buttons. So the same footprint that they have now.

I realise this takes some control away from your projects, but I’m in favour of giving the user complete control over the engine while they play your games. This allows them to see how the system works, to a very small extent.

38

Hmmm. I think there’s value, in the player, of allowing people to view the example code. It might be a good thing to show people how easy some of this actually is. I know the thing that tends to “sell me” on a new language is being able to see source of something I might actually want to do, to see how difficult it might be. Not that there’s not lua source floating around anyway.

I’m actually thinking you should be even more restrictive on the coding - one project, one tab, and maybe 100 or 200 lines total. People are gonna hack it, and if they can drop arbitrary projects into the directory, “one project” isn’t a big thing, and I think tabs are cosmetic only, aren’t they (I mean I could do all of my class definitions in the main tab, right?)

Then you give em source to the examples, but they’re all to big to run in the included editor. :slight_smile:

39

@Bortels tabs are technically not necessary to run complex projects, but they make complexity a lot more convenient to view. I wouldn’t dismiss them as cosmetic only — convenience is a very important function.

The main reason the code in the examples won’t be visible is because we won’t have the ability to show tabs on the iPhone’s tiny screen. Dumping all the code into one large buffer would look pretty crazy for the sorts of games that will be included with the app.

There’s nothing against letting them view the code, though. It could be put up on the web with a link inside the app.

40

Thanks for the answers Simeon. I was thinking that this could cover the Codea Viewer app and so someone could paste in code, save the code, but not edit it or get it back. That was my point. On #4, if you mistook me for being able to edit them, I didn’t mean that. Just viewing them. I also get your point about the limited iPhone space, but I really think that one of the amazing features of Codea is the lack of extra coding for some things. I think that might be relevant to trying to get users of the full Codea. Maybe make it so you can scroll to the side on the iPhone? And you might as well go for #5 if you do it in the free version, but I understand it’s more work for adding updates…
Thanks a lot! I’ll stop bothering you now.