Chris,
sincerely speaking, I'd be a bit worried about the quality of the final
results since it seems to me that you don't have a clear understanding
of how the current *OFBiz* agreement stuff is designed and used.
Please, understand that this is not a lack of trust on your skills, but
such a big task (that will include existing data model, services and
user interface refactoring) would be a challenging task for everyone
(even for core contributors like, for example, Si, David and me).
I'd like to hear the opinions from others about this subject: do we
really need to refactor the agreement data model or can we complete and
refine the existing processes? what are the most urgent limitations in
the current agreement data model?
If you really need to perform this task, I'd suggest to implement it as
an alternative model instead of a replacement of existing
functionalities... maybe it would be easier to implement... but it is
obviously up to you.
Jacopo
Chris Howe wrote:
Who's priorities? I already offered to make the
necessary corrections. You insisted that we should
push forward with what is there instead of making the
corrections. Would you be okay with me making the
necessary corrections to make the agreements generic?
With a clear seperation between products and
agreements and only their join tables defining thier
relationship, price lists and other calculated prices
can more easily reuse current calculating services.
