History of BitcommercePackage
We have started the bitcommerce project. This will be a large project. Almost as large as bitweaver itself. We have taken the Zencart application version 1.2.5d and are forking to a closely integrated application. The approach is just like the TikiWiki -> ReleaseZero -> ReleaseOne approach for bitweaver:
*First, port the architecture and maintain functionality
*Second, expand functionality and greatly improve modularity.
We have reverted all code to ADODB and have SQL running on multiple platforms. Try to get everything working "as-is" with a pristine Zencart 1.2.5d schema. Slowly migrate the tpl_ files to Smarty templates. sideboxes have been converted. Took about an hour a piece.
^(:arrow:)There is now a ~~#090:demo~~ at the [http://sandbox.bitweaver.org/commerce|sandbox]
user: __admin__
password: __qwer__
Check out the [http://sandbox.bitweaver.org/commerce/admin|bitcommerce admin too]^
!!Want code?
#((GetCode|Get the latest bitweaver)) - bitcommerce requires the latest HEAD branch (upcoming R2) from CVS. These do *NOT* include the bitcommerce package yet, since it is still under development.
#The only reliable way to get bitcommerce is from our CVS (there is no branch on bitcommerce yet): ^cvs -z3 -d:pserver:anonymous@cvs.sf.net:/cvsroot/bitweaver checkout _bit_commerce^
!!Want to know more?
*See bitcommerceChangelog for details and current progress.
*There is a [/blogs/17|bitcommerce blog]
*And a [/forums/viewforum.php?f=13|forum] for discussion about bitcommerce.
*Or stop by ((ConnectingToIrc|IRC)) and chat with us in real-time
!!Current Status
*A few sites have it running in production and processing live transactions (that's real cash. woo!) If you want to see bitcommerce running on postgres in live production environment, [http://www.viovio.com/shop|buy something from Viovio].
*The schema is considered to be cooled, though a few small changes are still occuring. Any future schema changes will only be permitted with extreme need.
*__MAIN TODO CHORE__: Port everything in commerce/pages to php & smarty .tpl pairs. This is a lot of work, and very risky due to the high possibility regressive bug introduction. About 10 of 70 pages have been completed.
*First, port the architecture and maintain functionality
*Second, expand functionality and greatly improve modularity.
We have reverted all code to ADODB and have SQL running on multiple platforms. Try to get everything working "as-is" with a pristine Zencart 1.2.5d schema. Slowly migrate the tpl_ files to Smarty templates. sideboxes have been converted. Took about an hour a piece.
^(:arrow:)There is now a ~~#090:demo~~ at the [http://sandbox.bitweaver.org/commerce|sandbox]
user: __admin__
password: __qwer__
Check out the [http://sandbox.bitweaver.org/commerce/admin|bitcommerce admin too]^
!!Want code?
#((GetCode|Get the latest bitweaver)) - bitcommerce requires the latest HEAD branch (upcoming R2) from CVS. These do *NOT* include the bitcommerce package yet, since it is still under development.
#The only reliable way to get bitcommerce is from our CVS (there is no branch on bitcommerce yet): ^cvs -z3 -d:pserver:anonymous@cvs.sf.net:/cvsroot/bitweaver checkout _bit_commerce^
!!Want to know more?
*See bitcommerceChangelog for details and current progress.
*There is a [/blogs/17|bitcommerce blog]
*And a [/forums/viewforum.php?f=13|forum] for discussion about bitcommerce.
*Or stop by ((ConnectingToIrc|IRC)) and chat with us in real-time
!!Current Status
*A few sites have it running in production and processing live transactions (that's real cash. woo!) If you want to see bitcommerce running on postgres in live production environment, [http://www.viovio.com/shop|buy something from Viovio].
*The schema is considered to be cooled, though a few small changes are still occuring. Any future schema changes will only be permitted with extreme need.
*__MAIN TODO CHORE__: Port everything in commerce/pages to php & smarty .tpl pairs. This is a lot of work, and very risky due to the high possibility regressive bug introduction. About 10 of 70 pages have been completed.