Well, as long as you put a nice GUI around it, I will be delighted to use it. <div><br></div><div>And if you don't, I'm sure you will find someone else to run the necessary profiles. </div><div><br></div><div><br></div> <div>Edmund</div><div><br><div class="gmail_quote">On Thu, May 5, 2011 at 8:32 PM, Chris Murphy <span dir="ltr"><<a href="mailto:lists@colorremedies.com">lists@colorremedies.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im"><br> <br> On May 5, 2011, at 11:39 AM, James Cloos wrote:<br> <br> >>>>>> "er" == edmund ronald <<a href="mailto:edmundronald@gmail.com">edmundronald@gmail.com</a>> writes:<br> ><br> > er> I simply cannot envision printing targets from a command-line<br> > er> app. Sorry. At this point, if this is the decision taken here,<br> > er> I will resign from this endeavor.<br> ><br> > I really hope you mean you don't want cli to be the /only/ way to<br> > print targets, rather than that you want to exclude cli users<br> > from printing targets.<br> ><br> > You wording parses as the latter, exclusionist interpretation and<br> > not as the former, inclusionist interpretation. Hense this followup.<br> ><br> > Really, every print job which can be done from a gui also should be<br> > doable from a cli shell. And visa-versa.<br> <br> <br> </div>Yes. There's every reason to consider that the app be CLI with a GUI wrapper.<br> <font color="#888888"><br> <br> Chris Murphy<br> </font><div><div></div><div class="h5">_______________________________________________<br> openicc mailing list<br> <a href="mailto:openicc@lists.freedesktop.org">openicc@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/openicc" target="_blank">http://lists.freedesktop.org/mailman/listinfo/openicc</a><br> </div></div></blockquote></div><br></div>