[ http://issues.apache.org/jira/browse/OFBIZ-510?page=comments#action_12459109 ] Chris Howe commented on OFBIZ-510: ----------------------------------
Tim, I feel you've completely missed my point and sentiment. My advice was to tackle one issue at a time. It's very difficult and time consuming for someone to review your efforts if we're chasing down how a particular change plays into it and then to find out after a half hour of chasing, that it doesn't. My contention on the order screens is not on whether you require different screen definitions to accomplish your goals. The contention is that other people use screens from the ecommerce component without utilizing the entirety of the ecommerce component. Renaming and removing of screen definitions is outside of the scope of your improvement and this manner of consolidating is not necessary to accomplish your improvement. As David mentioned in the ML, if this is a NEW checkout process it should be a parallel one and not a replacement one. New functionality should not break old code unless there is a real benefit in doing so. There are so many approaches that one can take to obtain both benefits. I was not slamming Anil or you for your choices of implementation. You agree, functionality that is gained by making this async call can be accomplished without it. The async call being made is much more complicated than the JS only solution. If that's true, then the only benefit that this patch gives is to be able to say that we use Dojo in OFBIZ. Is there another benefit that I'm missing? I have no doubt that OFBiz will take advantage of AJAX approaches, but again, it's not needed here. I am all for creating more ways to incorporate technology into OFBiz. But you need to remember that this is a community project and the KISS philosophy should prevail unless there is a real reason to complicate things. > Anonymous Checkout Refactoring [ ecommerce ] Part #2 > ---------------------------------------------------- > > Key: OFBIZ-510 > URL: http://issues.apache.org/jira/browse/OFBIZ-510 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Affects Versions: SVN trunk > Reporter: Tim Ruppert > Attachments: 3stepAnonCheckoutWithAjax.patch > > > So, now that we're close to completing the Anonymous Checkout Refactoring > Part #1, we are going on to the second phase out of three, which is intended > to make the checkout process even more succint. The final goal is to do > something like I did for one of my customers - http://twpinc.insourcery.com . > This is an old site and is being replaced, so don't worry about the other > functionality - just walk thru the checkout process. > Currently we have a long process that contains these functions / screens: > 1. Personal Info > 2. Shipping Address > 3. Shipping Options > 4. Payment Options > 5. Payment Information (and Billing Address) > 6. Review Order > 7. Order Confirmation > We are going to shorten it up this way: > 1. Personal Info / Shipping Address / Billing Address - with the appropriate > error handling and the check box & action Billing same as shipping) > 2. Shippint Options > 3. Payment Options (if necessary - skip if you only have credit card - or > only one option in general) > 4. Review & Place Order - enter the credit card right here - put error > handling here as well > 5. Order Confirmation > This would be the end of this patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
