[ 
http://issues.apache.org/jira/browse/OFBIZ-510?page=comments#action_12459105 ] 
            
Chris Howe commented on OFBIZ-510:
----------------------------------

It makes it a lot easier to review issues/patches if the patches are submitted 
to the issue that they belong.  If an issue is blocking the progress of another 
issue bring it to the committers attention.  I'm looking at  CustomerEvents.xml 
and custsettings.ftl now because they seem to be OFBIZ-512.  If I can figure it 
out, I'll post my reply there.

My point on the async call is that you're not gaining anything for this case 
over an approach that loads the data the first time around.  You're simply 
complicating the issue in order to use a buzzword.  If and when you do come 
across a scenario that would benefit from the async call, I think it would be 
more efficient to use the approach in OFBIZ-411 in whether or not to make 
dojo.js available to a page.

If you're itching to use dojo for the checkout screens, I would think the 
wizzard widget would be a much cleaner and user friendly route to take.

Do you think it would be possible for you to outline what actual issue each 
file that is changed is in regards to?  This would make it a lot faster to get 
through.

> 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

        

Reply via email to