YAAW - Yet Another Argyll Wrapper

I agree that the mentioned 3D viewers wouldn' fit well into YAAW; I just mentioned them since 3D viewers are rather rare overall as stand alone programs. I cannot remember that Monaco Gamutworks ever had a Linux version. Gamutworks can display several image and/or profile files at the same time, the Color Inspector can deliver different views but only of one graphics file, I would like to work with a program which could do both.
 
Hallo Riclin,
I am for the fact that there would be a lot of software and alternatives. Please develop your project further.
I like your program better, and ChromIQ looks too overloaded.
 
df11 said:
Hallo Riclin,
I am for the fact that there would be a lot of software and alternatives. Please develop your project further.
I like your program better, and ChromIQ looks too overloaded.
Click to expand...
Thanks for your interest. I'd paused om developing YAAW further since it already seems to do most of what I need, and there seemed to be a resounding lack of interest from others. That said, I'm happy to add additional functionality providing it aligns with the core project objectives. What additional capabilities do you think would be useful?

r/
 
riclin said:
Thanks for your interest. I'd paused om developing YAAW further since it already seems to do most of what I need, and there seemed to be a resounding lack of interest from others. That said, I'm happy to add additional functionality providing it aligns with the core project objectives. What additional capabilities do you think would be useful?

r/
Click to expand...
The first thing that immediately came to mind and what I would like to see.
1. international support i18n
2. tooltips when hovering over a short explanation of a particular parameter for what it is needed.
3. for Windows users, I would compile everything in exe or msi(x). What would be installed as a regular Windows program. So that users just click on the yarls on the desktop or from the start menu and do not care about the python setpoints.
 
For Windows packaging, PyInstaller with a one-folder build is usually less fragile than one-file for apps that call external Argyll binaries; you’ll still need to bundle or locate Argyll separately and handle paths. For i18n, gettext is straightforward if strings are marked from the start. Tooltips are worth doing as parameter-level help sourced from one definitions file so they stay consistent with the docs. I’d prioritise tooltips and packaging before full i18n, since those reduce the most setup friction.
 
You must log in or register to reply here.

Latest posts

Back
Top