Entries For: February 2008

Non-code news

• First thing to mention is that we passed 400 downloads of the release candidate tarball! We have no way of knowing how many people are on buildout, but that adds to the growing number of users.
• Speaking of buildout...it's worth mentioning that there is now a handy tool/bundle to help Windows users get going with buildout! You can read about the "installer for buildout-ready Windows" here. Haven't used it, but glad to know that the windows users are getting exposed to more buildout goodness :)
• Google code added a sweet trac-ish-on-ajax code browser. Check out GetPaid's code here. 
• Anyone going to Plone Symposium East? There is still time to submit a proposal for a session on GetPaid (though that ends this Friday)! If you are interested, check it out.
  

Sprints

• There was mention of interest of GetPaid for the Sorrento sprint. If you are looking to hang out with great folks in lovely place, check out Sorrento sprint!
  
• There was even mention of a potential DocComm II sprint for this summer at Google again!
  

If you are interesting in organizing or leading GetPaid sprint activities, please do! Please also share your interest with others on our mailing list.

Code and related

• Big news lately was the merge of work done in a branch into the trunk. This brought in UPS integration, a backend for address books, and a refactored checkout wizard.
  
• Since the merge, several fixes and modifications have happened including, and there have been several points where the buildout was not in ideal condition, but things are looking up:
• Making xml dependency more sane: the buildout got a bit unwieldy with a dependency on lxml. Liam refactored that out (I believe it is just going to use elementtree). Several folks in the channel today agreed that we need to avoid making the buildout more difficult as a point of distribution. We want people using GetPaid...not fighting with the tool. 
• Javier and Perrito fixed compatibility of the new checkout wizard with Plone 2.5 after finding a problem with an import of IBrowserView failing
• Dunny did some externals cleanup on the anonymous buildout and Kapil updated the anonymous buildout also. This brings the anon buildout up to date with the merge and changes in the development version.
  
• Kapil made several modifications to the checkout wizard and its state handling.
• There is also a lot of stuff planned and at various stages of being worked on:
• UPS UI integration is well advanced. Please have a look, especially if you are able to help out.
  
• Inventory/warehouse management: Ability to turn this on for a product and site. Keep track of where your stuff is as well as how much of it you have.
  
• Reporting and storage of orders in relational database: Work is planned on storing orders in a relational (postgres) db and then providing new reports.
  
• Liam also reports that shipping using USPS (that's US Postal Service for those not in the US) will be easy building on the UPS integration module.
  
• UI refactoring: after some deployments, there is some frustration with UI and skinning GetPaid that can be overcome with a bit of UI love...
  
• Probably more goodies too...but I'll leave it at that for now :)

There has been a lot of work going on a branch called "kapil-dev", which includes shipping with UPS, an address book available in checkout, and a checkout wizard refactoring. Two main changes:

• the store settings are no longer stored in an adapter,  instead there in a utility. It's backwards compatible though for access, ie there is an adapter that retrieves the utility. and there is a migration step in place if you go the upgrade tool. Previous settings will work till then.
• the checkout wizard has been refactored in an attempt to make it more customizable. which is in getpaid.wizard. There are separate controllers (sequence of steps ), data managers ( manage all the data in the forms) and steps no longer have to get hardcoded to their order of execution. If you have made programmatic changes to the wizard, you will need to make changes to accomodate the new code. If you override the checkout entirely with your customizations, your changes should be fine.
  

These changes represent some great new features for GetPaid, yet also mean that the code base is going to change in some significant pieces...so there is going to be a transition that requires attention (note: this is vital for anyone running their site from buildout on the trunk of the product; if you are using the tarball or the RedOchre release branch (0.3), then you don't need to pay attention to this). 

If you are running off the trunk, then the next time you update the code base, you will need to perform a migration to fix some of the changes. The "upgrade" screen in GetPaid setup area will be helpful in this - just hit the upgrade button and your site will be fixed!