On Wed, Sep 3, 2008 at 10:56 AM, _why <[EMAIL PROTECTED]> wrote: > On the note of sandboxing, I think Chrome has made me ditch my prior > ideas about how I want to handle security in Shoes. (Because that's > the big problem here, not a bunch of little platform bugs.) I don't > think I'm going to use the sandbox extension after all. It's too > experimental for right now and not generic enough should I end up > supporting Rubinius of Ruby 1.9 or anything else.
Sorry this is kind of off topic but are there any tips for using a freaky freaky sandbox from within shoes? I made a brief attempt at it last week but failed completely. It seemed Shoes doesn't come with the exposed rb_syserr_tbl which you have to patch into the ruby source. And furthermore, the rb_syserr_tbl patch didn't seem to work for me with ruby 1.8.7. Does patching the ruby source on your system to expose it make it exposed when you build shoes? I've got some really cool ideas floating around in my head about using shoes + sandbox as kind of a multi-irb-ruby-editor type thing. -Garret Buell
