changes in latest Athens configuration
ConfigurationOfAthens project version:'3.9.6' see case 18445 <https://pharo.fogbugz.com/f/cases/18445/ConfigurationOfAthens-is-not-in-sync...> ConfigurationOfAthens is not in sync with current Pharo packages Why do we merge compositing modes with "paint options"? I would consider a compositing mode as a "mode" for current drawing operations and the antialiasing setting is only a "hint" for the backend, it may be completly ignored. Or am I confused with the font rendering antialiasing hint? Can we paint by set compositing mode do paint set different compositing set antialiasing mode do paint set different antialiasing mode do paint does it work that way (and would it make sense)? nicolai
Sorry, I don't get what you mean with this: "Why do we merge compositing modes with "paint options"?" I just renamed paintMode -> paintOptions and moved setAA: (paint antialias) from canvas to paintOptions. Changing antialias mode of drawing operation is as common as changing composition operator. Because there are two different antialiases (paint and font) it makes sense to have a concrete distinction between them, therefore moved paint antialias from canvas to paintOptions. Does it now make sense for you? If not, it can be reverted, anyway I don't need it anymore. Cheers Alec On Jun 10, 2016 2:27 PM, "Nicolai Hess" <nicolaihess@gmail.com> wrote:
ConfigurationOfAthens project version:'3.9.6'
see case 18445 <https://pharo.fogbugz.com/f/cases/18445/ConfigurationOfAthens-is-not-in-sync...> ConfigurationOfAthens is not in sync with current Pharo packages
Why do we merge compositing modes with "paint options"?
I would consider a compositing mode as a "mode" for current drawing operations and the antialiasing setting is only a "hint" for the backend, it may be completly ignored.
Or am I confused with the font rendering antialiasing hint?
Can we paint by
set compositing mode do paint set different compositing set antialiasing mode do paint set different antialiasing mode do paint
does it work that way (and would it make sense)?
nicolai
2016-06-10 19:13 GMT+02:00 Aliaksei Syrel <alex.syrel@gmail.com>:
Sorry, I don't get what you mean with this: "Why do we merge compositing modes with "paint options"?"
I just renamed paintMode -> paintOptions and moved setAA: (paint antialias) from canvas to paintOptions.
Changing antialias mode of drawing operation is as common as changing composition operator.
Ok, I wasn't sure if the aa-option is just an option for the whole rending and composition mode only for the current drawing operation.
Because there are two different antialiases (paint and font) it makes sense to have a concrete distinction between them, therefore moved paint antialias from canvas to paintOptions.
Does it now make sense for you? If not, it can be reverted, anyway I don't need it anymore.
? If you don't need it anymore, why is it now in the new ConfigurationOfAthens for pharo 6.0
Cheers Alec On Jun 10, 2016 2:27 PM, "Nicolai Hess" <nicolaihess@gmail.com> wrote:
ConfigurationOfAthens project version:'3.9.6'
see case 18445 <https://pharo.fogbugz.com/f/cases/18445/ConfigurationOfAthens-is-not-in-sync...> ConfigurationOfAthens is not in sync with current Pharo packages
Why do we merge compositing modes with "paint options"?
I would consider a compositing mode as a "mode" for current drawing operations and the antialiasing setting is only a "hint" for the backend, it may be completly ignored.
Or am I confused with the font rendering antialiasing hint?
Can we paint by
set compositing mode do paint set different compositing set antialiasing mode do paint set different antialiasing mode do paint
does it work that way (and would it make sense)?
nicolai
On 10 Jun 2016, at 21:45, Nicolai Hess <nicolaihess@gmail.com> wrote:
2016-06-10 19:13 GMT+02:00 Aliaksei Syrel <alex.syrel@gmail.com <mailto:alex.syrel@gmail.com>>: Sorry, I don't get what you mean with this: "Why do we merge compositing modes with "paint options"?"
I just renamed paintMode -> paintOptions and moved setAA: (paint antialias) from canvas to paintOptions.
Changing antialias mode of drawing operation is as common as changing composition operator.
Ok, I wasn't sure if the aa-option is just an option for the whole rending and composition mode only for the current drawing operation.
Because there are two different antialiases (paint and font) it makes sense to have a concrete distinction between them, therefore moved paint antialias from canvas to paintOptions.
Does it now make sense for you? If not, it can be reverted, anyway I don't need it anymore.
? If you don't need it anymore, why is it now in the new ConfigurationOfAthens for pharo 6.0
Because these âexternal packages without maintainersâ do not work. (the commit was in the repo and was taken into account for the new config). We should revert the change. can you add an issue? Marcus
2016-06-17 9:04 GMT+02:00 Marcus Denker <marcus.denker@inria.fr>:
On 10 Jun 2016, at 21:45, Nicolai Hess <nicolaihess@gmail.com> wrote:
2016-06-10 19:13 GMT+02:00 Aliaksei Syrel <alex.syrel@gmail.com>:
Sorry, I don't get what you mean with this: "Why do we merge compositing modes with "paint options"?"
I just renamed paintMode -> paintOptions and moved setAA: (paint antialias) from canvas to paintOptions.
Changing antialias mode of drawing operation is as common as changing composition operator.
Ok, I wasn't sure if the aa-option is just an option for the whole rending and composition mode only for the current drawing operation.
Because there are two different antialiases (paint and font) it makes sense to have a concrete distinction between them, therefore moved paint antialias from canvas to paintOptions.
Does it now make sense for you? If not, it can be reverted, anyway I don't need it anymore.
? If you don't need it anymore, why is it now in the new ConfigurationOfAthens for pharo 6.0
Because these âexternal packages without maintainersâ do not work. (the commit was in the repo and was taken into account for the new config).
The latest configuration is not yet integrated (issue validation error for 18445 ConfigurationOfAthens is not in sync with current Pharo packages) <https://pharo.fogbugz.com/f/cases/18445/ConfigurationOfAthens-is-not-in-sync...>
We should revert the change. can you add an issue?
Marcus
participants (3)
-
Aliaksei Syrel -
Marcus Denker -
Nicolai Hess