Hi David, > The print module is obviously of significant interest to most of us. > If this branch has no impact on the general stability on the rest of dt, > would it be feasible to make an early merge with the current daily version to > allow more extensive testing?
I'm not in a position to do that. This is a decision to make by the core developers. But from my point of view it is still too early. I've fixed many issues today for example. Note that I keep my branch up-to-date with master (I rebase regularly) as this is a long living branch it will avoid merge conflicts. So the best way today to test this print module is to compile the branch yourself. Note that, as said in my previous message, all prints are currently sent to a PDF printer if installed. I just don't want to loose paper at this statge (even if on my side I have already tested on 2 different real printers). I'm doing my best to get this in shape for a real field testing. But do not expect this before the end of the year. Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
