Re: I really like Ioke. How can I help?

["Carlos Villela" <cv@lixo.org>]

> Especially starting to think about
> how distribution and so on could be done would be lovely.

You mean distribution as something like RubyGems?

> There are also lots of holes in the core libraries.

Yup, which is probably a good thing -- someone else gets to play! :)

> Patches for useful core methods are really appreciated. To guide the
> thinking, look more towards the Ruby library then the Io library. If it's
> possible to implement without Java, that's great too.

I'm favourable towards using named parameters a la Smalltalk /
ObjectiveC, or DSL-ish chains, whenever a call is likely to get a
bunch of parameters that don't read like english. To exemplify:

Bad:

c = Color rgb(1.0, 1.0, 0.5)

Good:

c = Color(red: 1.0, green: 1.0, blue: 0.5)

Awesome:

c = Color red(1.0) green(1.0) blue(0.5)
c = Color red(1.0) ;; green and blue aren't set, so == 0.0
c = Color alpha(0.8) ;; 80% alpha black

This is possibly off-topic, but another thing that's tricky to get my
head around are the subtleties between macro, dmacro, lecro, lecrox,
fn and fnx. This might just be me being unused to the Great LISP Way,
but I reckon if the idea is making Ioke look and feel like a super
powerful Ruby, these gotchas have to be well explained or more obvious
in the code.

Does that go with your current thinking, Ola?

Cheers!

- Carlos