From: Sean O'Halpin <sean.ohalpin@...>
Date: 2010-08-31T04:57:40+09:00
Subject: Re: ffi-ncurses 0.3.3

On Mon, Aug 30, 2010 at 5:54 PM, Rahul Kumar <sentinel1879@gmail.com> wrote:
> Sean O'halpin wrote:
>
>> 0.4.2: ruby-ncurses compatibility layer (investigating)
>>
>> Regards,
>> Sean
>
> I noticed in ncurses-example.rb that you've created a module and WINDOW
> classes that makes your example exactly like the ruby-ncurses one, so no
> change is required in the user's code. That was great.
> However, should that class not go into the main project at some time ?

Yes, it will but it's not exactly quite there yet.
I need to convert the functions which take booleans, e.g. keypad.
For example, in ffi-ncurses at the moment, you write:

  keypad stdscr, 1 # or FFI::NCurses::TRUE which is extra fugly

I'll be changing that so you write

  keypad stdscr, true

That will break backward compatibility, but I think it's worth it.
It means I won't have to add translation functions for the ruby ncurses layer.
I think it's also more in the spirit of ffi type handling.

Thank you for rbcurse - it's one of the things spurring me on to
improve ffi-ncurses.

Regards,
Sean