I'll buy maracas and some voodoo/pixie dust then :)
- Dylan
On Fri, Oct 2, 2009 at 2:06 PM, Laurent Sansonetti wrote:
> Hi Dylan,
>
> You can still start your project today and use the JIT during development,
> then once the template is in place, you can activate it. If you need to ship
> your pr
Hi Dylan,
You can still start your project today and use the JIT during
development, then once the template is in place, you can activate it.
If you need to ship your product before the template is available we
can help you compiling your app (but it will require some command-line
magic)
Thanks!
Mostly I'm looking at doing some real commercial development here and it
helps to know the timeline and how you feel about the stability. Certainly
beats the daylights out of bracket soup. But in order to do that I basically
need to keep my code from being editable and readable by anyone wh
0.5 is scheduled for the end of the year, with a set of beta releases
before. We didn't set a date in stone yet because we want to ship it
when it's really ready :)
Laurent
On Oct 2, 2009, at 12:02 AM, Dylan wrote:
Good to know :)
Hate to ask since I can never answer this question myself:
Good to know :)
Hate to ask since I can never answer this question myself: do you have
a loose timeline for the release ?
-Dylan
On Oct 2, 2009, at 1:54 AM, Laurent Sansonetti
wrote:
Hi Dylan,
The AOT compilation of an Xcode project is still not finalized. It's
technically possible
Hi Dylan,
The AOT compilation of an Xcode project is still not finalized. It's
technically possible to do it with the current macrubyc on the command
line but it's kind of hard and we still have problems with #require
statements. We will introduce an Xcode target that does it
automaticall
I'm a bit of a newbie when it comes to command line compilation.
Is there an easy way for me to basically just say: compile everything
recursively, starting at this directory ? Given that, what would be the best
way to then integrate that with an Xcode project as part of a target ?
Also, is this f