@pjkersten > > For the payment generator, I followed the exact specification, which is > written in Dutch, so no English class names... Every class however represents > a tree branch or record type of the specification used. I imagine your > specification (which is probably not ClieOp) has similar rules. Following the > specs exactly enhances traceability (and decreases readability when in a > foreign language).
I do have not seen the one for Clieop, but it is a bit frustrating to imagine that specification specifies internal class names. Usually only the output format is specified, so if you follow the strict rules how the format should look like, you meat the spec - how it is being done inside your "kitchen" it is usually up to your own conscience. Probably it is a wishlist, but some dummy example export module "in English", would do the trick. :) So it seems, that we will stay with our original export module, not porting it to framework, until we have such example. > There is definitely work to do on the generator part. This is just a start. > Again, this is intended to be a community effort, so please join me. Well we should probably focus on those problems we have discovered, if we would fix them, framework would be much more usable than original banking. Kaspars ----------------------------- http://kndati.lv -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=50543#50543 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
