Ruby anyone?

[Dema]

Hi there,

I'd like to know if there is anyone intending to implement Ruby
bindings for this project.

I'd like to help on that path if I may.

Best regards,
Demetrius

[Kenton Varda]

Yes, Ilya (cc'd) mentioned it yesterday, and I just realized I had forgotten to respond.  Sorry, Ilya!

Ruby support would be great.  Please let me know how I can help.  I'm not familiar with Ruby personally, but I imagine the same design used with Python -- namely, something based on metaclasses -- may work well with Ruby.

[Demetrius Nunes]

Ok Kenton, great. I am pretty proficient with Ruby, but I might need
help with the C/C++ part. So how can we start? Is it possible to just
checkout the code from SvN and start working?

Anyway, I'm gonna take a good look at the Python design and source
code to see how they did it there.

Cheers,
Dema

--
____________________________
http://www.demetriusnunes.com

[Kenton Varda]

On Tue, Jul 8, 2008 at 10:45 AM, Demetrius Nunes <demetri...@gmail.com> wrote:

Ok Kenton, great. I am pretty proficient with Ruby, but I might need
help with the C/C++ part. So how can we start? Is it possible to just
checkout the code from SvN and start working?

We're going to get SVN running soon (the masses have spoken!).  However, the compiler is designed such that support for other languages can be developed as separate projects.  The compiler front-end is available as a library (libprotoc); check out the compiler::CommandLineInterface class:

http://code.google.com/apis/protocolbuffers/docs/reference/cpp/google.protobuf.compiler.command_line_interface.html

So, my thought has been that the most efficient way for people to work on supporting other languages would be to create separate physical projects on code.google.com for it.  On the other hand, I don't want people to feel like they are not part of the main project just because their code is in a separate repository.  What do you think of this plan?  I'd of course be happy to link to any such projects from the protobuf docs and help in any way I can.

If we want to put everything in a single SVN repository, things may be more cumbersome as we'll need to synchronize releases and negotiate about SVN commit rights, but I'm open to debate on this.  Let me know what you think would work best.
 

Anyway, I'm gonna take a good look at the Python design and source
code to see how they did it there.

Note that the Python code is somewhat incomplete at the moment (missing some advanced features), so you should take a look at the Java or C++ code a bit as well.

[Demetrius Nunes]

On Tue, Jul 8, 2008 at 3:46 PM, Kenton Varda <ken...@google.com> wrote:

On Tue, Jul 8, 2008 at 10:45 AM, Demetrius Nunes <demetri...@gmail.com> wrote:

Ok Kenton, great. I am pretty proficient with Ruby, but I might need
help with the C/C++ part. So how can we start? Is it possible to just
checkout the code from SvN and start working?

We're going to get SVN running soon (the masses have spoken!).  However, the compiler is designed such that support for other languages can be developed as separate projects.  The compiler front-end is available as a library (libprotoc); check out the compiler::CommandLineInterface class:

http://code.google.com/apis/protocolbuffers/docs/reference/cpp/google.protobuf.compiler.command_line_interface.html

So, my thought has been that the most efficient way for people to work on supporting other languages would be to create separate physical projects on code.google.com for it.  On the other hand, I don't want people to feel like they are not part of the main project just because their code is in a separate repository.  What do you think of this plan?  I'd of course be happy to link to any such projects from the protobuf docs and help in any way I can.

If we want to put everything in a single SVN repository, things may be more cumbersome as we'll need to synchronize releases and negotiate about SVN commit rights, but I'm open to debate on this.  Let me know what you think would work best.

Yes, that sounds good. Let's do that and see how it goes. 

 

Anyway, I'm gonna take a good look at the Python design and source
code to see how they did it there.

Note that the Python code is somewhat incomplete at the moment (missing some advanced features), so you should take a look at the Java or C++ code a bit as well.

Great, thanks, I'll dive into that too.

Cheers,
Dema

--
____________________________
http://www.demetriusnunes.com