As far as I could see, Phocus is mostly based on modules (like Darktable and Rawtherapee), and not adjustment layers, which makes the UI a bit easier to organise… also I doubt that it supports layer groups.
Another idea I am considering it to have the controls of the active layer shown below the layer list, instead of on a separate panel. This would save space for the preview image, and also limit the mouse movements.
Concerning the X-Y movement, it actually only makes sense for image layers or clone layers, and can be used for example to “clone” some portion of the image by translating a copy of it and then masking. I agree that this can be disabled for most of the tools, and thus simplify the UI.
I think it has adjustment layers, as shown at the bottom right of the included images and also see here for example, but probably with less flexibility than PhF. And I guess you’re right that it doesn’t support groups.
Sounds very good to me.
Between these two options, I’d still vote for having the controls of a layer expandable next to its name, but I think both of them are better than the separate panel with aggregated control boxes as it is today.
It needs to be added to the windows version as well, but that’s not a big deal (I’ve never had any request so far…). You’ll get a new test package very soon.
It looks nice.
I would try to save expensive vertical space by making the layers and control boxes more condensed. For example, by omitting the box title line (“V basic adjustments”) and by putting the sliders next to the control name This is a summary of suggestions. See the marked lines and arrows, and notice the relocated sliders of brightness/contrast/etc at the bottom left.):
I see two steps where the batch treatment is useful:
pre development where we can apply the basic raw treatment, with a default preset file. A pfi file is saved for every image with or without output image.
1.1. it could be interesting to have the option to save the pfi file in the same folder as the output image (instead of the source folder).
to produce the final image, resized, watermark, sharpened, …
Another small UI improvement, following a suggestion from @chroma_ghost: if more than one layer is selected when adding a new layer group, the layers get automatically moved inside the new group.
layers get automatically moved inside the new group.
macaroni, stracciatella, umpa lumpas, manga nera, consumismo, riot griot, OSS non SOS
That how the mice chant when they’re raving around these parts
Today I did try something different: loaded 3 raws (HDR) inside same project and kicked the hell out of PF.
The “bad” thing is that without HSV secondaries for opacity or other effects it takes time, too long.
The good things are that I really like how PF treats inserted raw images, it groups its components (raw loader and raw developer) automatically, nice! Other thing that I liked is that if gradients and/or paths masks are changed to darken or lighten, the work together; a bit cumbersome, but it’s useful. And for my surprise I kicked the hell out of the prog and it didn’t crush, NEAT!
A semi-sourer annoyance possible bug is that as the project gains more layers path masks and gradients tend to get lazy and don’t want to leave the viewer. If PF could align the shots and there was a way of using luminosity masks, I could also see PF as 1 stop, develop,blend and finish HDR shots… for the long distant future, when Logan wakes up. All and all, a lot of fun.
I don’t remember if it was like that before, but if so I hadn’t notice it: path can be moved directly in UI which is very nice. Improvement suggestion, something to toogle its wireframe on/off so the result can be reviewed (also individually), maybe for future also area affected visibility, mask, red would be pretty standard.
And when giving layers new names it takes way too long, sometimes only apearing after several layers have been created… by then the mice already ate the cheese {cannot believe there’s not an emoticon for cheese… mon dieu!!!}
Ha ha ha Mica you saved the from a very tough forced migration to Normandy, ha ha ha it was hidden after the sign that normally plays next song, so now all is good these for later, after getting rid of the snake
I have prepared updated packages of the current stable branch, which contain fixes for most of the issues recently pointed out by @chroma_ghost, namely:
the quality of the scaled-down preview has been greatly improved thanks to a better resizing algorithm
the changes in layer names are now immediately reflected in the layers list
the layout of several UI drop-down widgets has been improved
I am also in the process of doing some optimizations of the processing pipeline, which should hopefully bring some performance improvements…
yes it does as U said, in coming days more thourough punching. I keep collecting dumb ideas and moldy suggestions, but not for today, today enjoyment!!!
;
{cannot believe there’s not an emoticon for cheese… mon dieu!!!}
there most certainly is!
you saved the 
