Quote from: Dr. at Jun 17, 2008, 09:49 PM
I have restarted work on TC2. I ran into some pretty significant roadblocks that I was able to overcome. There are a lot of good suggestions in this forum, and I am open to every suggestion.
Some key features of what I am working on right now:
There will be no separate module for product administration.
each item is a MODx document. Product attributes (price, quantity, shipping options, etc...) are set in TVs.
"ViewCart" contents will be customizable via chunk. Default functionality will be to open a new page to view the cart with an easy option to use an included javascript modal window or to roll your own javascript view.
Focus for TC2 will be on the API.
Payment options (PayPal, Google Checkout, Authorize.net, 2Checkout, etc...) will be a modular extension. Any developer can add a new payment method by extending the TreasureChestPayment framework class:
...stripped...
I am (as usual) working on this in my spare time. As soon as I get a workable public alpha, I will subversion it to encourage collaboration from the community.
-sD-
Dr. Scotty Delicious, DFPA
Hi there Scotty.
These are some really welcome additions, and I say this just because I needed to r*pe your TC totally to get a client happy - and by saying totally, I mean totally
There are but a few methods left in the TC class I didn’t meddle thru to customise the cart for my clients needs, eventhough the chunks remained the same.
My goal was originally just to implement a simple mailer instead of having direct paypal money transfers, but wanted to leave the option there, so it could just be "toggled" on and off at will, from the module
- well to achieve this, I had to simulate the paypal payment procedure, alter the paypal-gw to point to my own servers if sandbox on (used this for the mailing-toggle) and with no prior paypal api knowledge, it was a heavy trial and error case what the script wanted as response for the requests, like fake transaction id’s, creating the order detail forms etc etc.
Now if that wasn’t enough, I learned that my client used Mootools as their clientside JS Framework, and of course you had packed&obfuscated the JS, so I needed to rewrite the whole js-part of TC into using mootools
Well after 2 weeks of guessing what your functions were, I finally got the sh*t together, without a single error and everything working, even as a butt-ugly-hack-TC.
So to the point of my rant, if you got this far

;
I’m volunteering to write you an alternative JS solution for clientside - the Mootools version - going alongside the jQuery (which would’ve worked perfectly if MT wouldn’t’ve clashed - yes even with the noConflict namespacing) if you like
So If you’re interested, just drop me a pm or email me: jabis @ pumppumedia.com
Yours truly,
Jabis Sevón
ps. the site I re-coded this chenanebang-ding-dong-TC isn’t online yet, for other productional hassles, but I’ll bump here when it is launched.
pps. thanks for the great
(piece of) work