Comment 4 for bug 448622
Revision history for this message
| Raphaël Valyi - http://www.akretion.com (rvalyi) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Hello Ferdinand,
I raised exactly this issue 2 days ago with Fabien. I said that Tiny is not going to have the power to rewrite it all alone, neither would it be good them carrying all the dev effort.
Ferdinand: as you can read here: https:/
I wanted quite the same thing as you: fetch the period on data change (see last patch). But because old wizard don't support on_change, I made the trade-off of dropping the period field completely...
My point is that, as you say, THE COMMUNITY CAN DO IT, but provided, Tiny will TEST AND INTEGRATE. old wizard also have other issues, like lack of extensibility by third party modules. Recently, for instance I could make the effort to refactor the partial picking wizard or the reconcile wizard, because I was needing too. But just because Tiny stated no clear contrib process for this and because trunk branches were abandoned and messed up, I didn't do this effort and went for yet one more ugly copy/paste.
BTW, sometimes (not here), it's not even required to move to osv_memory already, just moving code from old wizard code back to the real OOP business objects they belong too often solve the extensibility issue. So for stable 5.0, I advise doing this as often as possible rather than rewriting using osv_memory which would be better done in trunk. Of course, here this is one of those case where osv_memory might be justified even on 5.0 stable.
Please Ferdinand and vra, tell us how do you see the community doing that. Can we expect this to be committed in 5.0 stable? at least a shortlist of annoying wizards? How Tiny will test carefully?
You can also contact me on r-v-a-l-
Regards,