eventually, yes.
at least we care about it from very beginning:

Object subclass: #OSWindowAttributes
������ instanceVariableNames: 'bounds title fullscreen screenId preferableDriver'
������ classVariableNames: 'DefaultBounds DefaultFullscreen DefaultTitle'
������ poolDictionaries: ''
������ category: 'OSWindow'

this object is used to describe a window attributes. sure thing not all of them
listed there and much more will be added later, but as you can see,

screenId is already there, so potentially you can control which screen your window must use.

it is not clear now, how we will facilitate the screen selection and what values/api to use to identify them, but at this early stage we lying a foundations to make this option come into play one day.

��