Very cool! I hadn't looked at the SF codebase yet...guess
I'll have to go tinker! :)
Regards,
Eric Longman
Atl-Connect Internet Services
+-------------------------------------------------------+
| Atl-Connect Internet Services http://www.atlcon.net |
| 3600 Dallas Hwy Ste 230-288 770 590-0888 |
| Marietta, GA 30064-1685 [EMAIL PROTECTED] |
+-------------------------------------------------------+
----- Original Message -----
From: "Paul Sisson" <[EMAIL PROTECTED]>
To: "WebWiz" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, September 07, 2001 12:33 PM
Subject: Re: Re[2]: Wish List
On Friday 07 September 2001 06:41, WebWiz wrote:
> FWIW, Items #1 and #2 are great ideas, and something that
> *should* be implemented by OSRS
> > > 1) Move all unique configuration to a user.conf file so that
> > > we don't have to re-edit so much on each upgrade
> > > 2) Remove appropriate formatting from the html so that we can
> > > use css etc
The opensrs-sf code on sourceforge
(http://www.sourceforge.net/projects/opensrs-sf) includes this
functionality.
> (a) Resellers will, by design, make many modifications to
> the basic client code, and
The opensrs-sf codebase is designed in a modular format and by using
"hooks" no changes to the client code should be necessary.
> (b) Every new release includes many modifications sprinkled
> throughout the code, requiring significant effort to
> merge the two codebases.
With the modular format (and hooks) you can upgrade the codebase while
leaving your additions and local config options untouched.
>> This applies to the .cgis as well as the HTML templates.
Template changes must occur if functional changes are made to the
codebase, however now that the HTML is removed from the code and CSS
has been implemented, the changes should not be so painful.
> #3 and #4, in my opinion, would address tasks that would
> differ wildly from RSP to RSP and should be built by the
> individual resellers.
>>>3) [snip...] we only need to handle payment the processing parts.
> > > A money spinning opportunity for Tucows or Resellers to sell the
> > > payment processor add-ins and a high confidence that the shopping
> > > cart would always work with the registration engine.
The opensrs-sf codebase includes base components for payment processing
and adds support for Authroize.Net and Processing.Net. Processing code
can easily be added using "hooks" and will not be affected by an
upgrade.
-bfn,
Paul Sisson
