<table><tr><td style="">davidedmundson added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D18005">View Revision</a></tr></table><br /><div><div><p>What previous technical constraint are you referring to?</p>
<p>And we've had the multiple resolutions since 4.x so it dates back a long way.</p>
<p>It's about a few things:</p>
<ul class="remarkup-list">
<li class="remarkup-list-item">CPU usage to load an image is a sizable amount of our loading. Especially for JPEG images.</li>
</ul>
<p>You might see that less in 5.x as it now happens in another thread, and we don't necessarily max out all the cores - but still.</p>
<ul class="remarkup-list">
<li class="remarkup-list-item">Artists wanted some control over /how/ it's cropped. i.e if you have a mountain on the right and lots of sea to the left, you want to always cut off the boring sea part (i.e the spray folder)</li>
</ul>
<ul class="remarkup-list">
<li class="remarkup-list-item">Our run-time resizes will look worse than gimp/inkscape doing it.</li>
</ul></div></div><br /><div><strong>REPOSITORY</strong><div><div>R131 Plasma Wallpapers</div></div></div><br /><div><strong>BRANCH</strong><div><div>keep-only-largest-size (branched from master)</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D18005">https://phabricator.kde.org/D18005</a></div></div><br /><div><strong>To: </strong>ngraham, VDG, Plasma, ndavis<br /><strong>Cc: </strong>davidedmundson, cfeck, ndavis, plasma-devel, kvanton, jraleigh, GB_2, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart<br /></div>