On May 31, 2011, at 8:19 AM, Andreas Wacknitz wrote:
> Hi all,
>
> I have convinced a friend to take a closer look at Pharo 1.2.1 and Dolphin
> Smalltalk. He is an experienced Java developer.
> After some time he started to complain about Pharo. I was discussing with him
> and now think that he has some valid points.
>
> His biggest complaint is: "Why does Pharo always show windows at sizes and
> positions I don't want?"
> I answered him: You could set the standard window size in the class
> RealEstateAgent and furthermore you can create or change >>initialExtent
> methods in every class that is involved.
> But his answer was: Why should I do that? It's the responsibility of an IDE.
> I don't want to program elementary things of my IDE. Why is there no
> mechanism that let a user set the sizes and positions of windows? Netbeans
> and Eclipse are doing that nicely. Why isn't it possible in Pharo?
> After that discussion I now question my own way of using Pharo and Squeak. I
> have created some changesets that I used to file in when using
> a fresh image. But that seems stupid now...
>
The RealEstateAgent assumes a machine in the spirit of one with a screenseize
of 800*600 (old imac).
It should be re-implemented taking into account we are now 15 years later.
Marcus
--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
