Open GoogleCodeExporter opened 9 years ago
Not opposed in general, but don't like this specific implementation as it makes
individual items too tall, and information density is already low.
Note also that items listed in Pending Updates are _already_ downloaded, and so
it really is irrelevant information here. It may have a value in the the "Other
Updates" section.
Original comment by gregnea...@mac.com
on 17 Mar 2014 at 1:36
I agree with not displaying updates in the pending update pane.
I don't think adding size distracts from the view though and the extra detail
is worth the screen real estate. Compared to the App Store it has release date
as extra detail, although I notice it does not display update size either.
Anyway, I've had a look at hiding the size from the pending updates pane. See
https://code.google.com/r/bartreardon-munki/source/detail?name=Munki2&r=97eed150
5a8146b8ce0804428316b4cef97fce3c
Having this means adding an "other update" makes the update size disappear
after adding it to the pending updates although I think this behaviour is
acceptable.
Original comment by bart.rea...@gmail.com
on 17 Mar 2014 at 11:29
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
I'd like to re-visit this request.
I have made a change as per Revision: fdb1f1d9bdf1 which puts the size next to
the version number. This is how update size currently appear in iOS but not in
the MAS however it does limit the display to one line.
This also only displays for updates that are not yet downloaded. Updates
already downloaded but not yet applied don't show the size.
Original comment by bart.rea...@gmail.com
on 18 Jun 2014 at 1:38
would help if I linked to the revision
https://code.google.com/r/bartreardon-munki/source/detail?r=fdb1f1d9bdf1db777636
0d839b07fd9d92a128b2&name=Munki2
Original comment by bart.rea...@gmail.com
on 18 Jun 2014 at 1:39
Got a screen shot of what it looks like?
Original comment by gregnea...@mac.com
on 18 Jun 2014 at 3:26
Both versions attached.
Original comment by bart.rea...@gmail.com
on 18 Jun 2014 at 3:59
Attachments:
Original issue reported on code.google.com by
bart.rea...@gmail.com
on 17 Mar 2014 at 10:59