Batch convert

[xnview]

What do you think?
I think to make it as a standalone app, to replace XnConvert

[oops66]

What do you think?
I think to make it as a standalone app, to replace XnConvert

+1, I agree, I usually really like standalone app. (for extra stuffs like: "Color picker", "XnView Media detector", XnConvert, Exiftool, ...)
Plus the support among all MP's distributions (Win, Linux,MacOs) will be easier to do, I suppose.

[JohnFredC]

I think to make it as a standalone app

In principle I agree. Also, it would be great to make the batch interface a new kind of image tab.

But, the interface needs lots of tweaks first. The current NConvert interface is more coherent, IMO.

In use, the MP batch dialog doesn't "flow". The user is caught in a limbo between "interactive adjustment" and "scriptbuilding", but without adequate "overview" of the entire sequence of commands.

It needs a script window and much less of the modal-interaction paradigm.

And fewer clicks.

Perhaps a more tool-based, demonstrative interface would work better. The user would select tools from a toolbar and the script engine would follow along, building the script (which could be reviewable/editable at any time).

[xnview]

In use, the MP batch dialog doesn't "flow". The user is caught in a limbo between "interactive adjustment" and "scriptbuilding", but without adequate "overview" of the entire sequence of commands.

If you select last action, you have an overview of entire sequence...

[oops66]

For me the standAlone solution is better especially in case of different output files configurations ( split XnView and XnConvert ) for example : for Jpg quality x%, DCT Method, SubSampling Factor, keep exif data, etc ... then by this way it's possible to have 2 separates default custom config. one for XnView and an other one for XnConvert (and it's less confusing and less "dangerous", and probably easier to do). This was a problem in XnView v1.9X.

[JohnFredC]

If you select last action, you have an overview of entire sequence...

That part is good, excellent, actually. Any step in the sequence shows the up-to-that-point result in the After tab.

Still, having the preview on a separate tab from the original is awkward. See my post:
here.

All those options may seem like "luxury" items to some folks, but without them the before/after comparison process is inefficient and, for me at least, quite cumbersome.

[JohnFredC]

I think the batch processing "dialog" should be more like the XnView main windows: that is, participate in the "theme".

Currently it looks very much an alpha design and un-approachable. Simply giving it the current theme will make it seem finished and trustworthy.

Not an important thing now, but should be fixed before v1.

IMO, only alerts and popups should not have the theme.

Edit:

Well I have tried different sizes of the dialog and find it looks much better at smaller sizes. I had been using it full screen in order to make the preview as large as possible.

[xnview]

Still, having the preview on a separate tab from the original is awkward. See my post:
here.

Yes, i need to add it, i have not the time to finish it...

And this dialog doesn't use the theme??

[JohnFredC]

And this dialog doesn't use the theme??

It uses the Style (Clean looks, etc), but apparently doesn't always use the Theme (colors). Perform a batch, for instance, and observe the log.

By the way, though I have done no benchmarks, the MP 0.25 Batch actions seem very much slower than for XnView 1.9x.

[xnview]

By the way, though I have done no benchmarks, the MP 0.25 Batch actions seem very much slower than for XnView 1.9x.

??? They use the same functions...