The class side methods seem easy enough to move to the instance side of DisplayScreen so that the global Display can execute them.� Just some hunting down of the senders of those methods to do.� All that remains on the instance side is:

ScreenController>>objectForDataStream: refStrm
��� "I am about to be written on an object file. Write a path to me in the
��� other system instead."
��� "| dp |
��� dp := DiskProxy
��� ��� ��� ��� global: #ScheduledControllers
��� ��� ��� ��� selector: #screenController
��� ��� ��� ��� args: #().
��� refStrm replace: self with: dp.
��� ^ dp"
��� ^ nil

Can this just go away if the class goes away?� I think I can do this for you...

Rob


On Mon, Feb 23, 2009 at 10:17 PM, Rob Rothwell <r.j.rothwell@gmail.com> wrote:
Michael,

Do you mean:

fullScreen:
fullScreenOff
fullScreenOn
isFullScreen
lastScreenModeSelected
toggleFullScreen

???

I mean, that actually looks like something I can handle if you think of me like a first year apprentice who needs very specific instructions!� Where do you want them to go?� It's the whole change set thing that always takes me a while to figure out...!

Rob


On Mon, Feb 23, 2009 at 10:06 PM, Michael Rueger <m.rueger@acm.org> wrote:
Hi all,

while further battling full unicode support I ended up refactoring
ParagraphEditor to the extend that there a no references to the inst var
sensor left. There are still a few references to the global Sensor though.

With moving the model inst var down we could now basically get rid of
class Controller :-)

Class KeyboardBuffer is gone already.

All that needs to be done is moving the utility methods in
ScreenController to e.g. Display so we can remove that subclass of
Controller as well.

Volunteers?

Michael

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project