Steve McKenzie's Drupal Sandbox code which fathered the Drupal Salesforce module and comprised its initial import, was composed of an install and module file, as well as a sub-directory of includes.
So, I have created the Drupal Salesforce module on the basis of Steve McKenzie's important work in this regard.
This blog entry, and other coming after it, I can imagine, deal with my experience getting the module operational and following the announced roadmap (see module description).
First, I posted the following feature request on drupal.org http://drupal.org/node/125030:
[Just thinking aloud here, that's what a blog is for, isn't it?]
I like use cases because they are great for modeling scope.
Once you have a use case, with its basic flow and alternative flows, then you can discover the most important paths through the basic and alternative flows, and clearly mark out the key scenarios.
Each one of these key scenarios corresponds to a single test case. So each use case has one or more key scenarios and the same number of test cases.
These test cases are what the customer and the developers must write together based on a user story which is going to be implemented.
I am having some trouble with jscalendar and the views date module, so I want to make sure I have the "latest cvs version" (of the DRUPAL-5 branch!).
This also shows how to set up a whole site with spanking new stable branch code. Source: Drupal Handbook page .
First check out Drupal itself:
cvs -d:pserver:anonymous:firstname.lastname@example.org:/cvs/drupal checkout -r DRUPAL-5 -d mysite drupal
Then check out any modules you want (actually, should put them in ./sites all, but this is just an example, here I am the date module in ./modules/date)