[Kstars-devel] Memory management UI

[Jason Harris]

I think it would be counter-productive to expose obscure
implementation-specific numbers like nCache and number of stars per
block in the UI.  I like the "memory usage" slider, but maybe we need
a label that says something about what the setting means.  Like a
number showing a typical RAM footprint for stars for the given
memUsage setting.

ASCII mockup:

--|--------   about 40 MB of RAM needed for the stars

-----|-----   about 80 MB of RAM needed for the stars

---------|-   about 120 MB of RAM needed for the stars


Jason

On Sun, Jun 29, 2008 at 3:57 PM, Akarsh Simha <akarshsimha at gmail.com> wrote:
> Hi,
>
> Any suggestions on the memory management UI? I don't know which
> parameters I must keep internal and which I must expose to the
> user.
>
> Right now, we have a slider called 'Memory Usage' that actually
> adjusts the Star Density formula, and the zoomed out faint magnitude
> limit, which also affects the star density, but is not entirely
> specifiable in terms of memory usage (i.e. they are independent
> variables).
>
> Should I expose internals like number of stars per block or nCache?
>
> Regards
> Akarsh
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFIaBN1kAo+aFFLL8MRAg3lAJ9mLWpUbFF1oBMaorMkIt2WpdZEEACfZc9h
> DPmriZEyGrCxxX1T7gmBqwE=
> =ezv/
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Kstars-devel mailing list
> Kstars-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kstars-devel
>
>