Closed GoogleCodeExporter closed 9 years ago
> File size is huge for a simple viewer. More than 4 times as big with less
functionality. This doesn't speak for efficient and optimized coding.
Most of the file size is the gigantic icon files. Apple requires really huge
icon files. There is not much that can be done about this, other than not
having icon files.
> Loading and scrolling in a picture isn't smooth on Macbooks with Intel
Graphics on medium and high quality scaling.
This is why there is a low setting.
> Scaled Images are less sharp than they could be (like in v2)
Scaled up or down? Generally, the scaling is much better than v2, but if you
want to see pixels when zooming in, you have to enable that option.
> The noise animation is so terribly annoying. Why not showing a clean
background. Possibly same color as chosen in the theme options.
There might be a different animation in the future, but this really doesn't
seem like an important issue at this point.
> I miss an App Store version. I don't want to leave my personal data spread
around in different payment providers.
You and me will both have to wait for Apple to get around to approving it for
the app store.
Also, please do not post many different issues in one post. This makes it
impossible to track progress.
Original comment by paracel...@gmail.com
on 9 Jun 2013 at 6:01
>> File size is huge for a simple viewer. More than 4 times as big with less
functionality. This doesn't speak for efficient and optimized coding.
> Most of the file size is the gigantic icon files. Apple requires really huge
icon files. There is not much that can be done about this, other than not
having icon files.
Agree, with that. I looked into the package. Maybe one App is enough, no need
to one for each file type. But that's only my personal opinion. Icons,
Theme-Graphics and Perl Framework are the biggest parts.
>> Loading and scrolling in a picture isn't smooth on Macbooks with Intel
Graphics on medium and high quality scaling.
> This is why there is a low setting.
I know, but in Xee 2.2 it runs absolutely smooth even on the high setting. So I
mentioned it.
>> Scaled Images are less sharp than they could be (like in v2)
>Scaled up or down? Generally, the scaling is much better than v2, but if you
want to see pixels when zooming in, you have to enable that option.
Scaled down to monitor/window size. I never use upscaled images in a viewer
app. I only use upscaled views, when editing in a photo editing software. Due
to softening in every scaling algorithm a slight sharpening can improve visual
image quality.
>> The noise animation is so terribly annoying. Why not showing a clean
background. Possibly same color as chosen in the theme options.
> There might be a different animation in the future, but this really doesn't
seem like an important issue at this point.
Yes, it is a suggestion. But others in the support thread don't like it, too.
No animation would be the best for this short amount of loading time. In my
opinion, of course.
>> I miss an App Store version. I don't want to leave my personal data spread
around in different payment providers.
> You and me will both have to wait for Apple to get around to approving it for
the app store.
That is absolutely true. I mentioned it, because I didn't find a hint about a
upcoming App Store version.
Thanks for your support. I appreciate that very much. Xee was and is one of the
best image viewers on the Mac.
Original comment by yaihimgi...@mailinator.com
on 9 Jun 2013 at 8:21
> I know, but in Xee 2.2 it runs absolutely smooth even on the high setting.
The low setting in Xee 3 is actually slightly more advanced than the high
setting in 2.2.
> Scaled down to monitor/window size. I never use upscaled images in a viewer
app. I only use upscaled views, when editing in a photo editing software. Due
to softening in every scaling algorithm a slight sharpening can improve visual
image quality.
Currently it is tuned to maximize sharpness without causing artifacts on some
frequency-response images. It could perhaps be slightly sharper still, but then
other parts would suffer. I think it's a pretty good compromise as it is now.
Original comment by paracel...@gmail.com
on 9 Jun 2013 at 8:32
Original issue reported on code.google.com by
yaihimgi...@mailinator.com
on 9 Jun 2013 at 3:05