comment on

The primary reason to not right a generic one is the suspicion that someone else has already written one that is good enough, which is why I'm here asking about it.

I also did an analysis of using our custom solutions as a base to create a generic solution. The result would need to be installed in under an hour and be flexible in other ways: it would need to easily support different designs, different shipping options, and different payment processor options.

I estimated this would take about 75 developer hours to create that software in-house.

When OScommerce takes 15 minutes to install a free, feature-laden stable store which generally meets my criteria, I think it merits heavy consideration versus spending a lot more time to have /exactly/ what I want.

The OSCommerce data model looks solid. I suspect that I wanted to extend it, it would be fairly easy to use Perl and talk to the same database directly.

Mark Stosberg

In reply to Re^4: recommendations for cookie cutter e-commerce toolkits? by markjugg
in thread recommendations for cookie cutter e-commerce toolkits? by markjugg

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks