DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=41995>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41995 ------- Additional Comments From [EMAIL PROTECTED] 2007-04-04 07:50 ------- Jeremias, I should have made it clearer I never really expected the patch to be applied as it stands for the reason that it relies on forked bc4j code. I submitted the patch in the hope that it would prompt this discussion, when writing it I obviously had the issue of calculating the barcode dimensions which is exactly what Barcode4J does very well, so didn't want to re-solve that problem. My intention was not that that FOP would have a seperate set of barcode4j classes as I agree it would be a mainatenance nightmare. This is why I put in the barcode4j a seperate package, so that it could be reviewed as part of the patch and you could decide the best way to achieve this with your Barcode4j hat on. I'd like to see fop include barcode4j, but obviously it also stands on it's own for users who want to generate images. I am more than happy with your proposal and we can take it forward once you've finished the package refactor. However I think some kind of bridging pattern would be required so that the BCOCA attributes (to get the afp barcode type and modifier) can be obtained based on the barcode being rendered. (In reply to comment #4) > BTW, further advantages with my proposal: > - Less documentation overhead > - Same namespace as Barcode4J already uses (no special handling for AFP) > - Optimal rendering (native or Java2D) depending on what's already > implemented. > > Disadvantages: > - we cannot just use your patch, more development necessary > - we need to make sure that the FOP extension works with 0.93 until the next > release of FOP. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
