[jira] Created: (OFBIZ-298) Updated viewprofile for ecommerce
Locked
[jira] Created: (OFBIZ-298) Updated viewprofile for ecommerce
 
|
Updated viewprofile for ecommerce
--------------------------------- Key: OFBIZ-298 URL: http://issues.apache.org/jira/browse/OFBIZ-298 Project: OFBiz (The Open for Business Project) Issue Type: Improvement Components: ecommerce Affects Versions: SVN trunk Reporter: Marco Risaliti I have taken a crack at trying to make the ecommerce profile screen more user friendly for end users. What I did was simplified the UI by removing parts that didn't add value for the end user, and changing how addresses, credit cards, eft accounts, and gift cards are created, and updated. The largest change is what happens on the edit screens when the "save" button is clicked. Instead of redisplaying the page, it will forward to the page it came from (via DONE_PAGE). Attached are two files. One describing the changes to each file, and the patch file. The code is current as of revision 6276. Comments, suggestions welcome. Matt All Comments Work Log Change History Sort Order: Comment by Matt Kasubaski [08/Dec/05 01:02 PM] [ Permlink ] Patch file of changes Comment by Matt Kasubaski [08/Dec/05 01:03 PM] [ Permlink ] Detailed description of changes Comment by Si Chen [13/Dec/05 09:32 AM] [ Permlink ] Thanks for sending these in. I think they are all good changes. If nobody objects, I will test and commit them. Comment by David E. Jones [13/Dec/05 11:10 AM] [ Permlink ] If you're going to look at committing this please look at it closely Si. Reading through the changes I'm not sure I like some of the features that are removed here.... Some of these simplifications (like removing purposes...) could perhaps be options controller by indicators on the ProductStore, but in general the ecommerce templates should err on the side of including too much rather than including not enough. It is much easier to comment out something you don't want than it is to add something you do want. Also for different types of stores these things may make more or less sense, so removing them without knowing how they might be used (which is impossible being short of omniscient) is not really wise given the objectives we have for the ecommerce and other apps. Comment by Matt Kasubaski [13/Dec/05 12:14 PM] [ Permlink ] I do agree with David that this does reduce functionality for some applications. The overall goal of the change is to simplify the profile administration of registered accounts. The change is geared towards retail e-commerce where the end user is "grandma". There are other areas in the ecommerce app that could use some fine tuning for retail use as well. (split shipping comes to mind) As a suggestion, rather than having a runtime/database setting on how to behave, a new directory is created called ecommerce_retail (or similar) that levages the ecommerce tool set but focuses on selling products to end users (IE: grandma). Another idea would be to split these changes into their own screens and have an advance vs basic view profile. Comment by Si Chen [13/Dec/05 12:33 PM] [ Permlink ] David, I did read through Matt's original change list when I first commented, and I agree it would reduce some functionality. However, I thought that they are nevertheless good changes because they would make the ecommerce application closer to what a user organization would want. I also recalled that you had mentioned on the mailing list that you would like the user interfaces of the ofbiz applications to be rather generic in nature with all the fields and options available to the user, even if the screens become less intuitive to a user in a particular role (http://lists.ofbiz.org/pipermail/dev/2005-November/009439.html) That's why I said that I would wait for others' comments before I actually did anything, even though I liked the changes myself. I guess the real question with respect to the ecommerce (or any other ofbiz application) is whether it's meant to be close to something usable out of the box with minimum customization or a template for a developer to work with and create a completely custom one. Either way I'm fine with it, since I don't actually use this application myself. I'm just trying to help out. :) Si Comment by Marco Risaliti [13/Sep/06 01:40 AM] [ Permlink ] Is this issue can be closed ? Thanks Marco -- 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 |
[jira] Updated: (OFBIZ-298) Updated viewprofile for ecommerce
|
|
[ http://issues.apache.org/jira/browse/OFBIZ-298?page=all ]
Marco Risaliti updated OFBIZ-298: --------------------------------- Attachment: changedesc.txt profilepatch.txt > Updated viewprofile for ecommerce > --------------------------------- > > Key: OFBIZ-298 > URL: http://issues.apache.org/jira/browse/OFBIZ-298 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: ecommerce > Affects Versions: SVN trunk > Reporter: Marco Risaliti > Attachments: changedesc.txt, profilepatch.txt > > > I have taken a crack at trying to make the ecommerce profile screen more user friendly for end users. > What I did was simplified the UI by removing parts that didn't add value for the end user, and changing how addresses, credit cards, eft accounts, and gift cards are created, and updated. The largest change is what happens on the edit screens when the "save" button is clicked. Instead of redisplaying the page, it will forward to the page it came from (via DONE_PAGE). > Attached are two files. One describing the changes to each file, and the patch file. The code is current as of revision 6276. > Comments, suggestions welcome. > Matt > > > All Comments Work Log Change History Sort Order: > Comment by Matt Kasubaski [08/Dec/05 01:02 PM] [ Permlink ] > Patch file of changes > Comment by Matt Kasubaski [08/Dec/05 01:03 PM] [ Permlink ] > Detailed description of changes > Comment by Si Chen [13/Dec/05 09:32 AM] [ Permlink ] > Thanks for sending these in. I think they are all good changes. If nobody objects, I will test and commit them. > Comment by David E. Jones [13/Dec/05 11:10 AM] [ Permlink ] > If you're going to look at committing this please look at it closely Si. Reading through the changes I'm not sure I like some of the features that are removed here.... > Some of these simplifications (like removing purposes...) could perhaps be options controller by indicators on the ProductStore, but in general the ecommerce templates should err on the side of including too much rather than including not enough. It is much easier to comment out something you don't want than it is to add something you do want. Also for different types of stores these things may make more or less sense, so removing them without knowing how they might be used (which is impossible being short of omniscient) is not really wise given the objectives we have for the ecommerce and other apps. > Comment by Matt Kasubaski [13/Dec/05 12:14 PM] [ Permlink ] > I do agree with David that this does reduce functionality for some applications. > The overall goal of the change is to simplify the profile administration of registered accounts. The change is geared towards retail e-commerce where the end user is "grandma". > There are other areas in the ecommerce app that could use some fine tuning for retail use as well. (split shipping comes to mind) As a suggestion, rather than having a runtime/database setting on how to behave, a new directory is created called ecommerce_retail (or similar) that levages the ecommerce tool set but focuses on selling products to end users (IE: grandma). > Another idea would be to split these changes into their own screens and have an advance vs basic view profile. > Comment by Si Chen [13/Dec/05 12:33 PM] [ Permlink ] > David, > I did read through Matt's original change list when I first commented, and I agree it would reduce some functionality. However, I thought that they are nevertheless good changes because they would make the ecommerce application closer to what a user organization would want. > I also recalled that you had mentioned on the mailing list that you would like the user interfaces of the ofbiz applications to be rather generic in nature with all the fields and options available to the user, even if the screens become less intuitive to a user in a particular role (http://lists.ofbiz.org/pipermail/dev/2005-November/009439.html) That's why I said that I would wait for others' comments before I actually did anything, even though I liked the changes myself. > I guess the real question with respect to the ecommerce (or any other ofbiz application) is whether it's meant to be close to something usable out of the box with minimum customization or a template for a developer to work with and create a completely custom one. Either way I'm fine with it, since I don't actually use this application myself. I'm just trying to help out. :) > Si > Comment by Marco Risaliti [13/Sep/06 01:40 AM] [ Permlink ] > Is this issue can be closed ? > Thanks > Marco -- 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 |
[jira] Commented: (OFBIZ-298) Updated viewprofile for ecommerce
|
|
In reply to this post by Nicolas Malin (Jira)
[ http://issues.apache.org/jira/browse/OFBIZ-298?page=comments#action_12434811 ]
Marco Risaliti commented on OFBIZ-298: -------------------------------------- Hi Matt Kasubaski, I have seen that the attached pacthes are too old and it cannot be review to understand what they do. So if you want that this issue will progress you have to attach a new patch otherwise it will be closed (incomplete). Thanks Marco > Updated viewprofile for ecommerce > --------------------------------- > > Key: OFBIZ-298 > URL: http://issues.apache.org/jira/browse/OFBIZ-298 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: ecommerce > Affects Versions: SVN trunk > Reporter: Marco Risaliti > Attachments: changedesc.txt, profilepatch.txt > > > I have taken a crack at trying to make the ecommerce profile screen more user friendly for end users. > What I did was simplified the UI by removing parts that didn't add value for the end user, and changing how addresses, credit cards, eft accounts, and gift cards are created, and updated. The largest change is what happens on the edit screens when the "save" button is clicked. Instead of redisplaying the page, it will forward to the page it came from (via DONE_PAGE). > Attached are two files. One describing the changes to each file, and the patch file. The code is current as of revision 6276. > Comments, suggestions welcome. > Matt > > > All Comments Work Log Change History Sort Order: > Comment by Matt Kasubaski [08/Dec/05 01:02 PM] [ Permlink ] > Patch file of changes > Comment by Matt Kasubaski [08/Dec/05 01:03 PM] [ Permlink ] > Detailed description of changes > Comment by Si Chen [13/Dec/05 09:32 AM] [ Permlink ] > Thanks for sending these in. I think they are all good changes. If nobody objects, I will test and commit them. > Comment by David E. Jones [13/Dec/05 11:10 AM] [ Permlink ] > If you're going to look at committing this please look at it closely Si. Reading through the changes I'm not sure I like some of the features that are removed here.... > Some of these simplifications (like removing purposes...) could perhaps be options controller by indicators on the ProductStore, but in general the ecommerce templates should err on the side of including too much rather than including not enough. It is much easier to comment out something you don't want than it is to add something you do want. Also for different types of stores these things may make more or less sense, so removing them without knowing how they might be used (which is impossible being short of omniscient) is not really wise given the objectives we have for the ecommerce and other apps. > Comment by Matt Kasubaski [13/Dec/05 12:14 PM] [ Permlink ] > I do agree with David that this does reduce functionality for some applications. > The overall goal of the change is to simplify the profile administration of registered accounts. The change is geared towards retail e-commerce where the end user is "grandma". > There are other areas in the ecommerce app that could use some fine tuning for retail use as well. (split shipping comes to mind) As a suggestion, rather than having a runtime/database setting on how to behave, a new directory is created called ecommerce_retail (or similar) that levages the ecommerce tool set but focuses on selling products to end users (IE: grandma). > Another idea would be to split these changes into their own screens and have an advance vs basic view profile. > Comment by Si Chen [13/Dec/05 12:33 PM] [ Permlink ] > David, > I did read through Matt's original change list when I first commented, and I agree it would reduce some functionality. However, I thought that they are nevertheless good changes because they would make the ecommerce application closer to what a user organization would want. > I also recalled that you had mentioned on the mailing list that you would like the user interfaces of the ofbiz applications to be rather generic in nature with all the fields and options available to the user, even if the screens become less intuitive to a user in a particular role (http://lists.ofbiz.org/pipermail/dev/2005-November/009439.html) That's why I said that I would wait for others' comments before I actually did anything, even though I liked the changes myself. > I guess the real question with respect to the ecommerce (or any other ofbiz application) is whether it's meant to be close to something usable out of the box with minimum customization or a template for a developer to work with and create a completely custom one. Either way I'm fine with it, since I don't actually use this application myself. I'm just trying to help out. :) > Si > Comment by Marco Risaliti [13/Sep/06 01:40 AM] [ Permlink ] > Is this issue can be closed ? > Thanks > Marco -- 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 |
[jira] Updated: (OFBIZ-298) Updated viewprofile for ecommerce
|
|
In reply to this post by Nicolas Malin (Jira)
[ http://issues.apache.org/jira/browse/OFBIZ-298?page=all ]
Jacopo Cappellato updated OFBIZ-298: ------------------------------------ Priority: Minor (was: Major) > Updated viewprofile for ecommerce > --------------------------------- > > Key: OFBIZ-298 > URL: http://issues.apache.org/jira/browse/OFBIZ-298 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: ecommerce > Affects Versions: SVN trunk > Reporter: Marco Risaliti > Priority: Minor > Attachments: changedesc.txt, profilepatch.txt > > > I have taken a crack at trying to make the ecommerce profile screen more user friendly for end users. > What I did was simplified the UI by removing parts that didn't add value for the end user, and changing how addresses, credit cards, eft accounts, and gift cards are created, and updated. The largest change is what happens on the edit screens when the "save" button is clicked. Instead of redisplaying the page, it will forward to the page it came from (via DONE_PAGE). > Attached are two files. One describing the changes to each file, and the patch file. The code is current as of revision 6276. > Comments, suggestions welcome. > Matt > > > All Comments Work Log Change History Sort Order: > Comment by Matt Kasubaski [08/Dec/05 01:02 PM] [ Permlink ] > Patch file of changes > Comment by Matt Kasubaski [08/Dec/05 01:03 PM] [ Permlink ] > Detailed description of changes > Comment by Si Chen [13/Dec/05 09:32 AM] [ Permlink ] > Thanks for sending these in. I think they are all good changes. If nobody objects, I will test and commit them. > Comment by David E. Jones [13/Dec/05 11:10 AM] [ Permlink ] > If you're going to look at committing this please look at it closely Si. Reading through the changes I'm not sure I like some of the features that are removed here.... > Some of these simplifications (like removing purposes...) could perhaps be options controller by indicators on the ProductStore, but in general the ecommerce templates should err on the side of including too much rather than including not enough. It is much easier to comment out something you don't want than it is to add something you do want. Also for different types of stores these things may make more or less sense, so removing them without knowing how they might be used (which is impossible being short of omniscient) is not really wise given the objectives we have for the ecommerce and other apps. > Comment by Matt Kasubaski [13/Dec/05 12:14 PM] [ Permlink ] > I do agree with David that this does reduce functionality for some applications. > The overall goal of the change is to simplify the profile administration of registered accounts. The change is geared towards retail e-commerce where the end user is "grandma". > There are other areas in the ecommerce app that could use some fine tuning for retail use as well. (split shipping comes to mind) As a suggestion, rather than having a runtime/database setting on how to behave, a new directory is created called ecommerce_retail (or similar) that levages the ecommerce tool set but focuses on selling products to end users (IE: grandma). > Another idea would be to split these changes into their own screens and have an advance vs basic view profile. > Comment by Si Chen [13/Dec/05 12:33 PM] [ Permlink ] > David, > I did read through Matt's original change list when I first commented, and I agree it would reduce some functionality. However, I thought that they are nevertheless good changes because they would make the ecommerce application closer to what a user organization would want. > I also recalled that you had mentioned on the mailing list that you would like the user interfaces of the ofbiz applications to be rather generic in nature with all the fields and options available to the user, even if the screens become less intuitive to a user in a particular role (http://lists.ofbiz.org/pipermail/dev/2005-November/009439.html) That's why I said that I would wait for others' comments before I actually did anything, even though I liked the changes myself. > I guess the real question with respect to the ecommerce (or any other ofbiz application) is whether it's meant to be close to something usable out of the box with minimum customization or a template for a developer to work with and create a completely custom one. Either way I'm fine with it, since I don't actually use this application myself. I'm just trying to help out. :) > Si > Comment by Marco Risaliti [13/Sep/06 01:40 AM] [ Permlink ] > Is this issue can be closed ? > Thanks > Marco -- 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 |
[jira] Updated: (OFBIZ-298) Updated viewprofile for ecommerce
|
|
In reply to this post by Nicolas Malin (Jira)
[ http://issues.apache.org/jira/browse/OFBIZ-298?page=all ]
Jacopo Cappellato updated OFBIZ-298: ------------------------------------ Description: From Matt Kasubaski =========================================================== I have taken a crack at trying to make the ecommerce profile screen more user friendly for end users. What I did was simplified the UI by removing parts that didn't add value for the end user, and changing how addresses, credit cards, eft accounts, and gift cards are created, and updated. The largest change is what happens on the edit screens when the "save" button is clicked. Instead of redisplaying the page, it will forward to the page it came from (via DONE_PAGE). Attached are two files. One describing the changes to each file, and the patch file. The code is current as of revision 6276. Comments, suggestions welcome. Matt All Comments Work Log Change History Sort Order: Comment by Matt Kasubaski [08/Dec/05 01:02 PM] [ Permlink ] Patch file of changes Comment by Matt Kasubaski [08/Dec/05 01:03 PM] [ Permlink ] Detailed description of changes Comment by Si Chen [13/Dec/05 09:32 AM] [ Permlink ] Thanks for sending these in. I think they are all good changes. If nobody objects, I will test and commit them. Comment by David E. Jones [13/Dec/05 11:10 AM] [ Permlink ] If you're going to look at committing this please look at it closely Si. Reading through the changes I'm not sure I like some of the features that are removed here.... Some of these simplifications (like removing purposes...) could perhaps be options controller by indicators on the ProductStore, but in general the ecommerce templates should err on the side of including too much rather than including not enough. It is much easier to comment out something you don't want than it is to add something you do want. Also for different types of stores these things may make more or less sense, so removing them without knowing how they might be used (which is impossible being short of omniscient) is not really wise given the objectives we have for the ecommerce and other apps. Comment by Matt Kasubaski [13/Dec/05 12:14 PM] [ Permlink ] I do agree with David that this does reduce functionality for some applications. The overall goal of the change is to simplify the profile administration of registered accounts. The change is geared towards retail e-commerce where the end user is "grandma". There are other areas in the ecommerce app that could use some fine tuning for retail use as well. (split shipping comes to mind) As a suggestion, rather than having a runtime/database setting on how to behave, a new directory is created called ecommerce_retail (or similar) that levages the ecommerce tool set but focuses on selling products to end users (IE: grandma). Another idea would be to split these changes into their own screens and have an advance vs basic view profile. Comment by Si Chen [13/Dec/05 12:33 PM] [ Permlink ] David, I did read through Matt's original change list when I first commented, and I agree it would reduce some functionality. However, I thought that they are nevertheless good changes because they would make the ecommerce application closer to what a user organization would want. I also recalled that you had mentioned on the mailing list that you would like the user interfaces of the ofbiz applications to be rather generic in nature with all the fields and options available to the user, even if the screens become less intuitive to a user in a particular role (http://lists.ofbiz.org/pipermail/dev/2005-November/009439.html) That's why I said that I would wait for others' comments before I actually did anything, even though I liked the changes myself. I guess the real question with respect to the ecommerce (or any other ofbiz application) is whether it's meant to be close to something usable out of the box with minimum customization or a template for a developer to work with and create a completely custom one. Either way I'm fine with it, since I don't actually use this application myself. I'm just trying to help out. :) Si Comment by Marco Risaliti [13/Sep/06 01:40 AM] [ Permlink ] Is this issue can be closed ? Thanks Marco was: I have taken a crack at trying to make the ecommerce profile screen more user friendly for end users. What I did was simplified the UI by removing parts that didn't add value for the end user, and changing how addresses, credit cards, eft accounts, and gift cards are created, and updated. The largest change is what happens on the edit screens when the "save" button is clicked. Instead of redisplaying the page, it will forward to the page it came from (via DONE_PAGE). Attached are two files. One describing the changes to each file, and the patch file. The code is current as of revision 6276. Comments, suggestions welcome. Matt All Comments Work Log Change History Sort Order: Comment by Matt Kasubaski [08/Dec/05 01:02 PM] [ Permlink ] Patch file of changes Comment by Matt Kasubaski [08/Dec/05 01:03 PM] [ Permlink ] Detailed description of changes Comment by Si Chen [13/Dec/05 09:32 AM] [ Permlink ] Thanks for sending these in. I think they are all good changes. If nobody objects, I will test and commit them. Comment by David E. Jones [13/Dec/05 11:10 AM] [ Permlink ] If you're going to look at committing this please look at it closely Si. Reading through the changes I'm not sure I like some of the features that are removed here.... Some of these simplifications (like removing purposes...) could perhaps be options controller by indicators on the ProductStore, but in general the ecommerce templates should err on the side of including too much rather than including not enough. It is much easier to comment out something you don't want than it is to add something you do want. Also for different types of stores these things may make more or less sense, so removing them without knowing how they might be used (which is impossible being short of omniscient) is not really wise given the objectives we have for the ecommerce and other apps. Comment by Matt Kasubaski [13/Dec/05 12:14 PM] [ Permlink ] I do agree with David that this does reduce functionality for some applications. The overall goal of the change is to simplify the profile administration of registered accounts. The change is geared towards retail e-commerce where the end user is "grandma". There are other areas in the ecommerce app that could use some fine tuning for retail use as well. (split shipping comes to mind) As a suggestion, rather than having a runtime/database setting on how to behave, a new directory is created called ecommerce_retail (or similar) that levages the ecommerce tool set but focuses on selling products to end users (IE: grandma). Another idea would be to split these changes into their own screens and have an advance vs basic view profile. Comment by Si Chen [13/Dec/05 12:33 PM] [ Permlink ] David, I did read through Matt's original change list when I first commented, and I agree it would reduce some functionality. However, I thought that they are nevertheless good changes because they would make the ecommerce application closer to what a user organization would want. I also recalled that you had mentioned on the mailing list that you would like the user interfaces of the ofbiz applications to be rather generic in nature with all the fields and options available to the user, even if the screens become less intuitive to a user in a particular role (http://lists.ofbiz.org/pipermail/dev/2005-November/009439.html) That's why I said that I would wait for others' comments before I actually did anything, even though I liked the changes myself. I guess the real question with respect to the ecommerce (or any other ofbiz application) is whether it's meant to be close to something usable out of the box with minimum customization or a template for a developer to work with and create a completely custom one. Either way I'm fine with it, since I don't actually use this application myself. I'm just trying to help out. :) Si Comment by Marco Risaliti [13/Sep/06 01:40 AM] [ Permlink ] Is this issue can be closed ? Thanks Marco > Updated viewprofile for ecommerce > --------------------------------- > > Key: OFBIZ-298 > URL: http://issues.apache.org/jira/browse/OFBIZ-298 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: ecommerce > Affects Versions: SVN trunk > Reporter: Marco Risaliti > Priority: Minor > Attachments: changedesc.txt, profilepatch.txt > > > From Matt Kasubaski > =========================================================== > I have taken a crack at trying to make the ecommerce profile screen more user friendly for end users. > What I did was simplified the UI by removing parts that didn't add value for the end user, and changing how addresses, credit cards, eft accounts, and gift cards are created, and updated. The largest change is what happens on the edit screens when the "save" button is clicked. Instead of redisplaying the page, it will forward to the page it came from (via DONE_PAGE). > Attached are two files. One describing the changes to each file, and the patch file. The code is current as of revision 6276. > Comments, suggestions welcome. > Matt > > > All Comments Work Log Change History Sort Order: > Comment by Matt Kasubaski [08/Dec/05 01:02 PM] [ Permlink ] > Patch file of changes > Comment by Matt Kasubaski [08/Dec/05 01:03 PM] [ Permlink ] > Detailed description of changes > Comment by Si Chen [13/Dec/05 09:32 AM] [ Permlink ] > Thanks for sending these in. I think they are all good changes. If nobody objects, I will test and commit them. > Comment by David E. Jones [13/Dec/05 11:10 AM] [ Permlink ] > If you're going to look at committing this please look at it closely Si. Reading through the changes I'm not sure I like some of the features that are removed here.... > Some of these simplifications (like removing purposes...) could perhaps be options controller by indicators on the ProductStore, but in general the ecommerce templates should err on the side of including too much rather than including not enough. It is much easier to comment out something you don't want than it is to add something you do want. Also for different types of stores these things may make more or less sense, so removing them without knowing how they might be used (which is impossible being short of omniscient) is not really wise given the objectives we have for the ecommerce and other apps. > Comment by Matt Kasubaski [13/Dec/05 12:14 PM] [ Permlink ] > I do agree with David that this does reduce functionality for some applications. > The overall goal of the change is to simplify the profile administration of registered accounts. The change is geared towards retail e-commerce where the end user is "grandma". > There are other areas in the ecommerce app that could use some fine tuning for retail use as well. (split shipping comes to mind) As a suggestion, rather than having a runtime/database setting on how to behave, a new directory is created called ecommerce_retail (or similar) that levages the ecommerce tool set but focuses on selling products to end users (IE: grandma). > Another idea would be to split these changes into their own screens and have an advance vs basic view profile. > Comment by Si Chen [13/Dec/05 12:33 PM] [ Permlink ] > David, > I did read through Matt's original change list when I first commented, and I agree it would reduce some functionality. However, I thought that they are nevertheless good changes because they would make the ecommerce application closer to what a user organization would want. > I also recalled that you had mentioned on the mailing list that you would like the user interfaces of the ofbiz applications to be rather generic in nature with all the fields and options available to the user, even if the screens become less intuitive to a user in a particular role (http://lists.ofbiz.org/pipermail/dev/2005-November/009439.html) That's why I said that I would wait for others' comments before I actually did anything, even though I liked the changes myself. > I guess the real question with respect to the ecommerce (or any other ofbiz application) is whether it's meant to be close to something usable out of the box with minimum customization or a template for a developer to work with and create a completely custom one. Either way I'm fine with it, since I don't actually use this application myself. I'm just trying to help out. :) > Si > Comment by Marco Risaliti [13/Sep/06 01:40 AM] [ Permlink ] > Is this issue can be closed ? > Thanks > Marco -- 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 |
[jira] Updated: (OFBIZ-298) Updated viewprofile for ecommerce
|
|
In reply to this post by Nicolas Malin (Jira)
[ http://issues.apache.org/jira/browse/OFBIZ-298?page=all ]
Jacopo Cappellato updated OFBIZ-298: ------------------------------------ Description: Copy of http://jira.undersunconsulting.com/browse/OFBIZ-626 from Matt Kasubaski =========================================================== I have taken a crack at trying to make the ecommerce profile screen more user friendly for end users. What I did was simplified the UI by removing parts that didn't add value for the end user, and changing how addresses, credit cards, eft accounts, and gift cards are created, and updated. The largest change is what happens on the edit screens when the "save" button is clicked. Instead of redisplaying the page, it will forward to the page it came from (via DONE_PAGE). Attached are two files. One describing the changes to each file, and the patch file. The code is current as of revision 6276. Comments, suggestions welcome. Matt All Comments Work Log Change History Sort Order: Comment by Matt Kasubaski [08/Dec/05 01:02 PM] [ Permlink ] Patch file of changes Comment by Matt Kasubaski [08/Dec/05 01:03 PM] [ Permlink ] Detailed description of changes Comment by Si Chen [13/Dec/05 09:32 AM] [ Permlink ] Thanks for sending these in. I think they are all good changes. If nobody objects, I will test and commit them. Comment by David E. Jones [13/Dec/05 11:10 AM] [ Permlink ] If you're going to look at committing this please look at it closely Si. Reading through the changes I'm not sure I like some of the features that are removed here.... Some of these simplifications (like removing purposes...) could perhaps be options controller by indicators on the ProductStore, but in general the ecommerce templates should err on the side of including too much rather than including not enough. It is much easier to comment out something you don't want than it is to add something you do want. Also for different types of stores these things may make more or less sense, so removing them without knowing how they might be used (which is impossible being short of omniscient) is not really wise given the objectives we have for the ecommerce and other apps. Comment by Matt Kasubaski [13/Dec/05 12:14 PM] [ Permlink ] I do agree with David that this does reduce functionality for some applications. The overall goal of the change is to simplify the profile administration of registered accounts. The change is geared towards retail e-commerce where the end user is "grandma". There are other areas in the ecommerce app that could use some fine tuning for retail use as well. (split shipping comes to mind) As a suggestion, rather than having a runtime/database setting on how to behave, a new directory is created called ecommerce_retail (or similar) that levages the ecommerce tool set but focuses on selling products to end users (IE: grandma). Another idea would be to split these changes into their own screens and have an advance vs basic view profile. Comment by Si Chen [13/Dec/05 12:33 PM] [ Permlink ] David, I did read through Matt's original change list when I first commented, and I agree it would reduce some functionality. However, I thought that they are nevertheless good changes because they would make the ecommerce application closer to what a user organization would want. I also recalled that you had mentioned on the mailing list that you would like the user interfaces of the ofbiz applications to be rather generic in nature with all the fields and options available to the user, even if the screens become less intuitive to a user in a particular role (http://lists.ofbiz.org/pipermail/dev/2005-November/009439.html) That's why I said that I would wait for others' comments before I actually did anything, even though I liked the changes myself. I guess the real question with respect to the ecommerce (or any other ofbiz application) is whether it's meant to be close to something usable out of the box with minimum customization or a template for a developer to work with and create a completely custom one. Either way I'm fine with it, since I don't actually use this application myself. I'm just trying to help out. :) Si Comment by Marco Risaliti [13/Sep/06 01:40 AM] [ Permlink ] Is this issue can be closed ? Thanks Marco was: From Matt Kasubaski =========================================================== I have taken a crack at trying to make the ecommerce profile screen more user friendly for end users. What I did was simplified the UI by removing parts that didn't add value for the end user, and changing how addresses, credit cards, eft accounts, and gift cards are created, and updated. The largest change is what happens on the edit screens when the "save" button is clicked. Instead of redisplaying the page, it will forward to the page it came from (via DONE_PAGE). Attached are two files. One describing the changes to each file, and the patch file. The code is current as of revision 6276. Comments, suggestions welcome. Matt All Comments Work Log Change History Sort Order: Comment by Matt Kasubaski [08/Dec/05 01:02 PM] [ Permlink ] Patch file of changes Comment by Matt Kasubaski [08/Dec/05 01:03 PM] [ Permlink ] Detailed description of changes Comment by Si Chen [13/Dec/05 09:32 AM] [ Permlink ] Thanks for sending these in. I think they are all good changes. If nobody objects, I will test and commit them. Comment by David E. Jones [13/Dec/05 11:10 AM] [ Permlink ] If you're going to look at committing this please look at it closely Si. Reading through the changes I'm not sure I like some of the features that are removed here.... Some of these simplifications (like removing purposes...) could perhaps be options controller by indicators on the ProductStore, but in general the ecommerce templates should err on the side of including too much rather than including not enough. It is much easier to comment out something you don't want than it is to add something you do want. Also for different types of stores these things may make more or less sense, so removing them without knowing how they might be used (which is impossible being short of omniscient) is not really wise given the objectives we have for the ecommerce and other apps. Comment by Matt Kasubaski [13/Dec/05 12:14 PM] [ Permlink ] I do agree with David that this does reduce functionality for some applications. The overall goal of the change is to simplify the profile administration of registered accounts. The change is geared towards retail e-commerce where the end user is "grandma". There are other areas in the ecommerce app that could use some fine tuning for retail use as well. (split shipping comes to mind) As a suggestion, rather than having a runtime/database setting on how to behave, a new directory is created called ecommerce_retail (or similar) that levages the ecommerce tool set but focuses on selling products to end users (IE: grandma). Another idea would be to split these changes into their own screens and have an advance vs basic view profile. Comment by Si Chen [13/Dec/05 12:33 PM] [ Permlink ] David, I did read through Matt's original change list when I first commented, and I agree it would reduce some functionality. However, I thought that they are nevertheless good changes because they would make the ecommerce application closer to what a user organization would want. I also recalled that you had mentioned on the mailing list that you would like the user interfaces of the ofbiz applications to be rather generic in nature with all the fields and options available to the user, even if the screens become less intuitive to a user in a particular role (http://lists.ofbiz.org/pipermail/dev/2005-November/009439.html) That's why I said that I would wait for others' comments before I actually did anything, even though I liked the changes myself. I guess the real question with respect to the ecommerce (or any other ofbiz application) is whether it's meant to be close to something usable out of the box with minimum customization or a template for a developer to work with and create a completely custom one. Either way I'm fine with it, since I don't actually use this application myself. I'm just trying to help out. :) Si Comment by Marco Risaliti [13/Sep/06 01:40 AM] [ Permlink ] Is this issue can be closed ? Thanks Marco > Updated viewprofile for ecommerce > --------------------------------- > > Key: OFBIZ-298 > URL: http://issues.apache.org/jira/browse/OFBIZ-298 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: ecommerce > Affects Versions: SVN trunk > Reporter: Marco Risaliti > Priority: Minor > Attachments: changedesc.txt, profilepatch.txt > > > Copy of http://jira.undersunconsulting.com/browse/OFBIZ-626 from Matt Kasubaski > =========================================================== > I have taken a crack at trying to make the ecommerce profile screen more user friendly for end users. > What I did was simplified the UI by removing parts that didn't add value for the end user, and changing how addresses, credit cards, eft accounts, and gift cards are created, and updated. The largest change is what happens on the edit screens when the "save" button is clicked. Instead of redisplaying the page, it will forward to the page it came from (via DONE_PAGE). > Attached are two files. One describing the changes to each file, and the patch file. The code is current as of revision 6276. > Comments, suggestions welcome. > Matt > > > All Comments Work Log Change History Sort Order: > Comment by Matt Kasubaski [08/Dec/05 01:02 PM] [ Permlink ] > Patch file of changes > Comment by Matt Kasubaski [08/Dec/05 01:03 PM] [ Permlink ] > Detailed description of changes > Comment by Si Chen [13/Dec/05 09:32 AM] [ Permlink ] > Thanks for sending these in. I think they are all good changes. If nobody objects, I will test and commit them. > Comment by David E. Jones [13/Dec/05 11:10 AM] [ Permlink ] > If you're going to look at committing this please look at it closely Si. Reading through the changes I'm not sure I like some of the features that are removed here.... > Some of these simplifications (like removing purposes...) could perhaps be options controller by indicators on the ProductStore, but in general the ecommerce templates should err on the side of including too much rather than including not enough. It is much easier to comment out something you don't want than it is to add something you do want. Also for different types of stores these things may make more or less sense, so removing them without knowing how they might be used (which is impossible being short of omniscient) is not really wise given the objectives we have for the ecommerce and other apps. > Comment by Matt Kasubaski [13/Dec/05 12:14 PM] [ Permlink ] > I do agree with David that this does reduce functionality for some applications. > The overall goal of the change is to simplify the profile administration of registered accounts. The change is geared towards retail e-commerce where the end user is "grandma". > There are other areas in the ecommerce app that could use some fine tuning for retail use as well. (split shipping comes to mind) As a suggestion, rather than having a runtime/database setting on how to behave, a new directory is created called ecommerce_retail (or similar) that levages the ecommerce tool set but focuses on selling products to end users (IE: grandma). > Another idea would be to split these changes into their own screens and have an advance vs basic view profile. > Comment by Si Chen [13/Dec/05 12:33 PM] [ Permlink ] > David, > I did read through Matt's original change list when I first commented, and I agree it would reduce some functionality. However, I thought that they are nevertheless good changes because they would make the ecommerce application closer to what a user organization would want. > I also recalled that you had mentioned on the mailing list that you would like the user interfaces of the ofbiz applications to be rather generic in nature with all the fields and options available to the user, even if the screens become less intuitive to a user in a particular role (http://lists.ofbiz.org/pipermail/dev/2005-November/009439.html) That's why I said that I would wait for others' comments before I actually did anything, even though I liked the changes myself. > I guess the real question with respect to the ecommerce (or any other ofbiz application) is whether it's meant to be close to something usable out of the box with minimum customization or a template for a developer to work with and create a completely custom one. Either way I'm fine with it, since I don't actually use this application myself. I'm just trying to help out. :) > Si > Comment by Marco Risaliti [13/Sep/06 01:40 AM] [ Permlink ] > Is this issue can be closed ? > Thanks > Marco -- 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 |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |