Hi Ryan,

As a non-programmer (yet), I was wondering if you would elaborate more on what the intention and/or roadmap is for the module and/or related modules?

I'm keen to use it to do some basic CRUD actions on my Freshbooks site using workflow/rules/actions and views. I've played around a little with curl and the API and and I've hacked the module (guesswork mainly) to prevent SSL cert issues on my local machine but when it comes to PHP programming or understanding what the module provides, I'm a bit lost. My programming is limited to tiny snippets used in calculated CCK fields and they're probably not very well done either. If I can spare some time, I may try to get to grips with my inadequacies and have a go at programming some stuff but it scares me a little. Some examples or documentation about what you've created would help me on my way immensely.

Many thanks (for this and the great work with UC)

Comments

4drian’s picture

Gave up on this but then saw http://drupal.org/node/293841 and got very excited again. Just been committed to Views 3 branch and patch appears to work with current stable views 2 release (2.5). Not investigated much further yet but are you thinking what I'm thinking?

t0xicCode’s picture

Issue summary: View changes
Status: Active » Closed (works as designed)

This is a pure API module. It provides the freshbook API for consumption by other drupal modules/code.