I've opened a JIRA for this and set the fix version for 1.1.
http://issues.fluidproject.org/browse/FLUID-2398
Michelle
On 24-Mar-09, at 6:54 PM, Gary Thompson wrote:
Michelle,
I think that is a great solution. It may be worth adding a balloon
help text to the Minimum Text Size label that states the behavior,
something like: "Any text smaller than this size will be increased
to the size you specify. All larger text sizes will remain
unaffected."
-Gary
Michelle D'Souza wrote:
One of the reasons that we changed from having a text size setting
to having a minimum text size setting was because it's important
for people to be able to specify the smallest they can see. If we
only set a base size, things that are scaled down from there may
not be readable for the user. The current experience is not
correct however, it does do more then just set a base size - it
also removes FSS classes that scale down the text size.
I have a suggestion for a possible implementation change. We have
decided that it is important for integrators to specify their
defaults in order for UIOptions to behave correctly. We could add a
setting in the defaultSiteSettings called 'baseTextSize'. Then
setting the minimum text size could check if the size is larger
then the integrator specified base text size. If it is, we would
set the base font for the user to the size they had specified and
remove the scaled down text sizes. If not we would only remove the
scaled down text sizes that are scaled to smaller then the base
text size and leave everything else the same.
Michelle
On 23-Mar-09, at 2:42 PM, [email protected] wrote:
I have a question about the meaning of "Minimum text size" in the
UI Options dialog.
My understanding of the purpose of "Minimum text size" is to
enlarge things that are smaller than the desired minimum, but to
leave alone anything that is already larger than the minimum. The
current implementation does not do this.
I've filed a JIRA about this that describes how to view the
scenario:
http://issues.fluidproject.org/browse/FLUID-2394
I've discussed the implementation with Michelle and Jacob. It
seems that it isn't really technically possible to implement what
I expect "minimum text size" to do, as described above.
My question is: If we can't do this, should we be offering to do it?
Maybe given what we *can* technically do, the control should be
labelled "Base text size"
Thoughts?
--
Anastasia Cheetham [email protected]
Software Designer, Fluid Project
Adaptive Technology Resource Centre / University of Toronto
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
------------------------------------------------------
Michelle D'Souza
Software Developer, Fluid Project
Adaptive Technology Resource Centre
University of Toronto
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
------------------------------------------------------
Michelle D'Souza
Software Developer, Fluid Project
Adaptive Technology Resource Centre
University of Toronto
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
