Chris, Sounds like an interesting approach. I'd like to talk with you more about it offline. Mind if I email you sometime to chat about your thoughts and ideas? Would you be interested in helping out with completing a similar project, this time with a small team?
Tim -----Original Message----- From: snacktime [mailto:[email protected]] Sent: Monday, May 11, 2009 2:41 PM To: [email protected] Subject: Re: Ruby Port of Shindig Ya I'm one of those people. I abandoned my project a while ago but have had a couple of other people contact me about it. So I'm going to put an MIT license on it and put what I have up on github in case it's of use. I'll try to get that done tonight/tomorrow sometime. My codebase took a different approach then trying to do a class for class copy of shindig. The container itself is a rails app, with the opensocial api's in a rails plugin. The opensocial entities are all rails tableless models that don't use a database. Those entity models do callbacks into whatever class you want to get the real data (mappings are defined in a yaml file). Chris On Mon, May 11, 2009 at 7:49 AM, Chris Chabot <[email protected]> wrote: > I also remember a few cases where people said they had the intention > too; Might be worth digging up those posts and contacting them directly too? > Some > might not be subscribed to the shindig-dev list. > > & good luck! > > -- Chris > > On Mon, May 11, 2009 at 4:43 PM, Fisher, Tim <[email protected] > >wrote: > > > Would anyone out there be interested in contributing to a Ruby port > > of Shindig?? Scanning the mailing list and searching the web I > > notice that have been a few false starts at a Ruby implementation of > > Shindig. I'd like to get a small team together of developers > > interested in completing this project, a full Shindig implementation in Ruby. > > > > If your interested drop me a line... [email protected] > > > > Thanks, > > Tim > > The contents of this e-mail are intended for the named addressee > > only. It contains information that may be confidential. Unless you > > are the named addressee or an authorized designee, you may not copy > > or use it, or > disclose > > it to anyone else. If you received it in error please notify us > immediately > > and then destroy it. > > >
