Fwd: API Change Proposal - Re: MSAA and Scene anti aliasing

[Scott Palmer]

copying the list...

---------- Forwarded message ----------
From: Scott Palmer <swpalmer at gmail.com>
Date: Tue, Jul 23, 2013 at 9:33 PM
Subject: Re: API Change Proposal - Re: MSAA and Scene anti aliasing
To: Chien Yang <chien.yang at oracle.com>


Is DEFAULT intended to defer to the settings in the system graphics drivers
(e.g. nVidia control panel) such that the precise settings used are defined
outside the scope of JavaFX and could vary between otherwise identical
systems based on the settings the user has selected somewhere else?

If so perhaps something like SYSTEM, USER, or UNSPECIFIED ,make sense.


On Tue, Jul 23, 2013 at 9:14 PM, Chien Yang <chien.yang at oracle.com> wrote:

> Well, I personally think that might be over stretching. :-)  FAST and
> NICEST will behave no difference on a platform that can't support AA. For
> such platform we will have to cover in the API specification.
>
> - Chien
>
>
> On 7/23/2013 2:37 PM, Richard Bair wrote:
>
>> Actually that is exactly what I was hoping DEFAULT would mean -- some
>> kind of typical option for the particular platform (maybe even disabled on
>> some!).
>>
>> Richard
>>
>> On Jul 23, 2013, at 1:41 PM, Felix Bembrick <felix.bembrick at gmail.com>
>> wrote:
>>
>>  I am not sure I like the name of the value DEFAULT.  To me "default"
>>> implies some kind of "typical" option for the particular platform which
>>> could conceivably be very different on each platform.  For example, on my
>>> Windows super-computer with ultra fast GPU the "default" would logically
>>> be
>>> something like 16x whereas on my iPhone I would expect the default to be
>>> using only 2x.  The comment for DEFAULT implies that it's really more of
>>> a
>>> BALANCED or MODERATE setting that would have the same characteristics on
>>> each platform.
>>>
>>>
>>> On 24 July 2013 06:29, Chien Yang <chien.yang at oracle.com> wrote:
>>>
>>>  Hi all,
>>>>
>>>>     We appreciate all the feedback you have contributed to this topic.
>>>> After listening to the feedback and an internal discussion, we would
>>>> like
>>>> to propose a minor change to the API for supporting scene
>>>> anti-aliasing. We
>>>> intentionally choose not to expose the number of samples and techniques
>>>> used in this release, but this doesn't preclude future addition when the
>>>> time is right for more options. This change will be tracked by RT-31878
>>>> (
>>>> https://javafx-jira.kenai.****com/browse/RT-31878<https://**
>>>> javafx-jira.kenai.com/browse/**RT-31878<https://javafx-jira.kenai.com/browse/RT-31878>
>>>> >
>>>> ):
>>>>
>>>> Anti-aliasing API Change Proposal:
>>>>
>>>> Constructors remove:
>>>> public Scene(Parent root, double width, double height, boolean
>>>> depthBuffer, boolean antiAliasing)
>>>> public SubScene(Parent root, double width, double height, boolean
>>>> depthBuffer, boolean antiAliasing)
>>>>
>>>> Constructor add:
>>>> public Scene(Parent root, double width, double height, boolean
>>>> depthBuffer, SceneAntiAliasing antiAliasing)
>>>> public SubScene(Parent root, double width, double height, boolean
>>>> depthBuffer, SceneAntiAliasing antiAliasing)
>>>>
>>>> Note:The antiAliasing argument will be used if the underlying graphics
>>>> driver has anti-aliasing support.
>>>>
>>>> Where SceneAntiAliasing is an enum with the following entries at the
>>>> moment:
>>>>
>>>> public enum SceneAntiAliasing {
>>>>     DISABLED, // disables anti-aliasing
>>>>     DEFAULT, // enables anti-aliasing using a default system setting
>>>> available that balances speed and quality
>>>>     FASTEST, // enables anti-aliasing using minimum system setting
>>>> available that results in better frame rate
>>>>     NICEST // enables anti-aliasing using maximum system setting
>>>> available
>>>> that results in best visual quality
>>>> }
>>>>
>>>> Thanks,
>>>> - Chien
>>>>
>>>>
>