Re: [Ironruby-core] .NET Remoting with IronRuby 0.9.2

2009-11-27 Thread Patrick Brown
Hi Dong Unfortuantly not, it is an issue I am going to come back to and really want to get to work but I temporarily dropped it so I could move forward on learning the tools and language. Thanks, Patrick On Wed, Nov 25, 2009 at 11:41 PM, Dong Zhang wrote: > Hi Patrick > > did you find a sol

Re: [Ironruby-core] ListViewItem DataTemplate

2009-11-27 Thread Patrick Brown
Hi Thank you, this explanation is very helpful. I will start working on following the naming conventions, I have actually been purposefully avoiding them to this point as following the C# standards was helping me to map commonalities between the two languages and focus on learning the language

Re: [Ironruby-core] ListViewItem DataTemplate

2009-11-27 Thread Ivan Porto Carrero
Yeah sorry for that.. I guess I'm not a morning person keep sending questions, helps me to understand the areas people have trouble with :) --- Met vriendelijke groeten - Best regards - Salutations Ivan Porto Carrero Blog: http://flanders.co.nz Google Wave: portocarrero.i...@googlewave.com Twitter

[Ironruby-core] handling ruby types and CallSiteStorage in std library

2009-11-27 Thread Dylan McClung
I'm working on adding code to the OpenSSL extension of the standard library and I need to understand the design for invoking and typing Ruby code. I read the 'Modifying the sources' github page and it mentions using CallSiteStorage to call into Ruby code. Specifically, the Cipher ruby class has a

Re: [Ironruby-core] handling ruby types and CallSiteStorage in std library

2009-11-27 Thread Tomas Matousek
It depends whether the method is supposed to invoke Digest's methods dynamically or not. Does pkcs5_keyivgen method accept any Ruby object that implements the methods pkcs5_keyivgen calls? Or does it need to be an instance of Digest class? If the former is true than you need to use "object" as t

Re: [Ironruby-core] handling ruby types and CallSiteStorage in std library

2009-11-27 Thread Tomas Matousek
BTW: Since parts of the OpenSSL library are already written in Ruby (see ruby-1.8.6p368\lib\ruby\1.8\openssl directory) it might be easier to write the rest in Ruby as well. With calls to .NET implementation of the cryptographic algorithms, of course. If you chose to go that way you can add the