I think he meant he was working on another api wrapper for ruby - he's
wrapping slimtimer, you're wrapping pownce. The similarity had to do with
you both thinking about turning your wrappers into gems.

Ian Serlin

On 12/29/07, eggie5 <[EMAIL PROTECTED]> wrote:
>
>
> I'm confused...What does pownce have to do with slimtimer?
>
> On Dec 29, 3:01 pm, "Nick Zadrozny" <[EMAIL PROTECTED]> wrote:
> > No, I'm not using ActiveResource because the authentication for the app
> I'm
> > using (SlimTimer) is token based and ActiveResource only really does
> HTTP
> > Basic. I'd love to see some kind of token-based support (or, heck, OAuth
> > while I'm dreaming) in ActiveResource.
> >
> > On Dec 29, 2007 11:39 AM, eggie5 <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > > Are you using active resource in your version? Do you have any
> > > comments on how their API is structured? From my perspective, I think
> > > it needs a good amount a refactoring...
> >
> > > Here's the google code page I have setup for now:
> >
> > >http://code.google.com/p/powncer/
> >
> > > Alex
> >
> > > On Dec 29, 11:23 am, "Nick Zadrozny" <[EMAIL PROTECTED]> wrote:
> > > > On Dec 28, 2007 10:36 PM, eggie5 <[EMAIL PROTECTED]> wrote:
> >
> > > > > I was thinking that this (the bindings) would be a good candidate
> for
> > > > > my first gem! The Pounce gem... This would also boost our working
> with
> > > > > rails authority.
> >
> > > > I think that's a great idea. I've got a similar idea for a new gem
> as
> > > well.
> >
> > > > > Oh and is this a good project to go into the new sd ruby google
> code
> > > > > svn?
> >
> > > > Totally. We have a new Rubyforge account as well, which would
> probably
> > > be
> > > > more useful for publishing gems. Patrick has the details on that.
> >
> > > > --
> > > > Nick Zadrozny * beyondthepath.com
> >
> > --
> > Nick Zadrozny * beyondthepath.com
> >
>


-- 
This message and all attachments are PRIVATE, and may contain
information that is CONFIDENTIAL and PRIVILEGED.
If you received this message in error, please notify the sender by reply
e-mail and delete the message immediately.

--~--~---------~--~----~------------~-------~--~----~
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
-~----------~----~----~----~------~----~------~--~---

Reply via email to