changes in latest Athens configuration

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

changes in latest Athens configuration

Nicolai Hess-3-2
ConfigurationOfAthens project version:'3.9.6'

see case
18445 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
Reply | Threaded
Open this post in threaded view
|

Re: changes in latest Athens configuration

Aliaksei Syrel

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" <[hidden email]> wrote:
ConfigurationOfAthens project version:'3.9.6'

see case
18445 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
Reply | Threaded
Open this post in threaded view
|

Re: changes in latest Athens configuration

Nicolai Hess-3-2


2016-06-10 19:13 GMT+02:00 Aliaksei Syrel <[hidden email]>:

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" <[hidden email]> wrote:
ConfigurationOfAthens project version:'3.9.6'

see case
18445 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

Reply | Threaded
Open this post in threaded view
|

Re: changes in latest Athens configuration

Marcus Denker-4

On 10 Jun 2016, at 21:45, Nicolai Hess <[hidden email]> wrote:



2016-06-10 19:13 GMT+02:00 Aliaksei Syrel <[hidden email]>:

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

Reply | Threaded
Open this post in threaded view
|

Re: changes in latest Athens configuration

Nicolai Hess-3-2


2016-06-17 9:04 GMT+02:00 Marcus Denker <[hidden email]>:

On 10 Jun 2016, at 21:45, Nicolai Hess <[hidden email]> wrote:



2016-06-10 19:13 GMT+02:00 Aliaksei Syrel <[hidden email]>:

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
 

We should revert the change. can you add an issue?

Marcus