On 01/09/2013 05:24 PM, Dale E. Moore wrote: > Hi Mike; > > Thanks for your hard work! This is not a big important question, but; > one I ponder sometimes. I've been guided by this community to never > change the base or community modules that are not my own, but; instead > to create a new module that inherits from (for example the point_of_sale > module) then revises the inherited module. I hear that minimizes upgrade > hassles in the future. > > I wonder if you had considered this alternative and if so, how did you > come to your decision to change the point_of_sale module?
Yes, normally that is what you should do, but I wasn't sure how to go about doing it for *this* particular module, since a lot of the logic is on the client side (in static javascript and css files). It is something that I will have to look at in the future. But for now the most important thing for me was the functionality that was missing. I made the announcement because the major goals that I set for the module have been met, and it is usable. It doesn't mean that the module is finished. Certainly this issue will have to be addressed before the module is considered "finished". Hope that clears things up. Ideally, I would like to see these changes integrated in to the official point_of_sale module. In that case a separate module would not be needed. Regards, Mike. _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
