Hey guys,
I have reworked everything and made a bitshares payment gateway (called it Bitshares Checkout)... I implemented the ecwid cart implementation but the checkout system will be standalone so anyone can integrate with it.. they just have to follow the "API" and implement the 4 or 5 php files I put in the integration folder. I will reuse it to do the rest of the carts, so look and feel will be the same on all implementations.
here is the source again for the ecwid: https://github.com/sidhujag/bitshares-ecwid
here is the demo: http://bitshares.ecwid.com
Go ahead and create a fake order then it will take you to the checkout for bitshares... you can pay via BTS and will be credited for BitUSD orders for testing. I will send all coins back anyways.
Eventually, it would be nice to have a seed list of public bitshares api clients the same way the native clients do it. I planning to implement this in JavaScript. We will need everyone to consider a new bitshares_client configuration parameter to enable CORS. I think this will greatly simplify your plugins.
Ive expressed this to bm about cors already on the http port. CORS would allow us to load the wallet via the web... can we do everything safely in jslib? You have other usecases in mind?
The plugin must run on the client computer because it will access their wallet to poll for transactions.. did you try the demo?
It's been awhile since I've been in this game, but am quite familiar with the cross domain request problem. Plugins typically operate in a more restrictive environment. Is that the primary reason ajax methods can't be used to accomplish what you can with CORS, or is it a matter of a more convenient and flexible API?
I just reviewed the state of the bitshares.org website (Still wish it used the safe as the image for security and something else for profit, like an image easily related to Wall Street for example). More to the point I also popped over and looked at some of the javascript code there.
I love javascript and scripting languages in general. Back in the day when Microsoft's ASP was the predominant web implementation and everyone and their brother used vbs to create websites, I loathed VB/VBS so I did it all (frontend and backend) in javascript. I also started using jquery in 2009; what a godsend that library is for browser programming! I prefer it over mootools for sure. It's the default client library for the Joomla CMS now, tho I was using it with Joomla long before that was the case.
Never took the time to learn python, ruby or ruby on rails, tho I could see they had strong merits. I keep saying I'm going to take the time to get familiar with python but haven't yet, tho I see it's used heavily now in many applications including an ever increasing role in Linux.
Now I see javascript has essentially been replaced with coffeeScript. Ah how the pace of technology accelerates!