toretore
commented
12 years ago Not a bad idea, it would solve the "problem" you describe where there's no good way to indicate what libraries an outputter depends on. Though, I fear it could be a little messy. There are barcode symbologies with external dependencies too, which means such an approach would mean each of those would have to be a separate gem as well..
For now I think the status quo is the best balance between the convenience of having everything in one gem while still being lightweight by not loading anything but the bare minimum by default. But it's not ideal, as you've experienced, and it's certainly something to think about.
On Jun 4, 2012, at 18:58, Ryan Johnson wrote:
Trying to use 'barby/outputter/png_outputter' threw a dependency error for chunky_png. Obviously you don't want to include every possible dependency into barby for each outputter, because they may not be used. Rather than requiring EVERY possible gem that the outputters require, why not split each outputter into its own gem with its own dependencies (barby being the first and foremost)?
Reply to this email directly or view it on GitHub: https://github.com/toretore/barby/issues/20
Trying to use 'barby/outputter/png_outputter' threw a dependency error for chunky_png. Obviously you don't want to include every possible dependency into barby for each outputter, because they may not be used. Rather than requiring EVERY possible gem that the outputters require, why not split each outputter into its own gem with its own dependencies (barby being the first and foremost)?