[Beepcore-ruby-discuss] Decisions, decisions

[Jim G. <jg...@mi...>]

Greetings, all.  I'm Jim Greer, a fellow Ruby enthusiast who is
interested in BEEP, though I can't claim significant work using either.
I am interesting in contributing to this project.  I have a few
questions, though:

Q1) What is this project?

That is, what is the scope of the intended work?

A reference implementation of BEEP in Ruby? (correct)
The definitive core implementation of BEEP in Ruby? (correct & good)
A complete BEEP implementation in Ruby? (complete)


Q2) How will this project differ from other BEEP implemetations?

By language of implementation only? (Ruby)
By reflection of language idiom(s) for more natural expression of the
problem? (Rubyifed BEEP)


Q3) Have any of you thoughts about your initial and long-term design
and implementation strategies?

{ natural implications from above }
Candidate objects, anyone?

Use SWIG + reference C-BEEP, concentrating on integration level work?
Use SWIG + custom C-BEEP?
'Native' BEEP implementation?


Q4) Has anyone got a driver project that we can use to tout our
implementation?


Q5) Any ideas on timeline/goals?


Jim G

-- 
In a museum in Havana, there are two skulls of Christopher Columbus,
"one when he was a boy and one when he was a man."
		-- Mark Twain
Jim Greer (Jim <G>) <jg...@mi...> [expires: 2002-12-09]
5CE1 6822 5E85 38D5 0C5C  8FA8 9499 8A2C 3E8B A74F