Hi Julien, Of course you're right. I failed to recend the link with the suggested work-flow, sorry. http://orion.freehost.gr/gsoc-sane-workflow#B What I meant above, was replacing the call at step (5)a with a call to a new get_icc_profile(). That call is made by the oyranos backend. The frontend would get the icc data from oyranos. I'm just trying to make sure that I didn't miss a possibility for making this work with the least disturbance on the sane codebase.
Yiannis Julien BLACHE wrote ... > And how would the frontend actually get the ICC data if it isn't aware > of the get_icc_profile() call? > > You want to send the ICC profile over the network, so that means > someone has to request it. The frontend doesn't know it's using the > net backend; it's using the dll backend and doesn't even know the net > backend exists. So it can't issue this request. > > > If that won't happen, do you see any other way of getting a remote > > profile without having to update every backend to a new version of the > > sane api? > > My take on this is that it should be handled out of band and by the > frontend only. The frontend should have all the information needed to > determine which ICC profile applies. > > JB.
