[darktable-devel] Details on multicore support for OsX

2014-06-17 Thread John Lehman
Sorry if this is an old question, but could someone please clarify the extent to which the Mac OS version of darktable supports multi-core processing? I am trying to choose the number of cores in a new Mac Pro, and so am interested in whether multiple cores would be used for vectorization, pipel

Re: [darktable-devel] print module

2014-06-17 Thread Pascal Obry
2014-06-17 12:52 GMT+02:00 Frederic Crozat : > Since Cairo is already part of Darktable "stack" (being pulled by > GTK), I would strongly advocate > for it (it is also used by all GNOME applications and Firefox) and not > add yet another external dependencies > like ImageMagick. Probably so, and I

Re: [darktable-devel] print module

2014-06-17 Thread Pascal Obry
And if we go the Gtk way we can probably even avoid CUPS completely. In fact Gtk+ comes with the following classes: - GtkPrinter - handles the printers - GtkPageSetup - everything about pages (hard margins, margins...) - GtkPaperSize - all about papers With this solution no other dependencies f

Re: [darktable-devel] print module

2014-06-17 Thread Frederic Crozat
2014-06-17 8:02 GMT+02:00 Pascal Obry : > > Following the IRC discussion last night. We agree that CUPS is the way > to go. But we need to discuss the technology(ies) that can be used to > *compose* the page to be printed. > > I have used Gutenprint API for this at this point but it seems desirable

Re: [darktable-devel] print module

2014-06-17 Thread Rob Z. Smith
Just a tiny bit of out of date experience? Reading that article it seems the way eventual success was obtained was to compose the image at native printer resolution and then dump it on CUPS and presumably Gutenprint drivers under that. This seems a sensible approach and the one taken also by Ph