[Pharo 1.1] Object>>initialExtent

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

[Pharo 1.1] Object>>initialExtent

Alexandre Bergel
Hi!

I do not have a solution, but Object>>initialExtent was recently  
deprecated and this causes great usability problem. This deprecation  
is very valuable for a clean UI separation. However, I have a warning  
deprecation each time a window is open. The reason stems from the  
method:

SystemWindow>>initialExtent
        ^ model initialExtent

For now, in my image, I suppressed this deprecation.
Again, I do not have a clean solution.

Cheers,
Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo 1.1] Object>>initialExtent

Alexandre Bergel
Sorry guys, wrong mailing list. It has to happen once in a while else  
there is no fun.

Alexandre


On 4 Mar 2010, at 14:33, Alexandre Bergel wrote:

> Hi!
>
> I do not have a solution, but Object>>initialExtent was recently  
> deprecated and this causes great usability problem. This deprecation  
> is very valuable for a clean UI separation. However, I have a  
> warning deprecation each time a window is open. The reason stems  
> from the method:
>
> SystemWindow>>initialExtent
> ^ model initialExtent
>
> For now, in my image, I suppressed this deprecation.
> Again, I do not have a clean solution.
>
> Cheers,
> Alexandre
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo 1.1] Object>>initialExtent

Simon Denier-3
In reply to this post by Alexandre Bergel

Where does the deprecation come from? I guess there was an issue in the Pharo bugs? Did you find it?


On 4 mars 2010, at 18:33, Alexandre Bergel wrote:

> Hi!
>
> I do not have a solution, but Object>>initialExtent was recently deprecated and this causes great usability problem. This deprecation is very valuable for a clean UI separation. However, I have a warning deprecation each time a window is open. The reason stems from the method:
>
> SystemWindow>>initialExtent
> ^ model initialExtent
>
> For now, in my image, I suppressed this deprecation.
> Again, I do not have a clean solution.
>
> Cheers,
> Alexandre
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
 Simon




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo 1.1] Object>>initialExtent

Alexandre Bergel
> Where does the deprecation come from? I guess there was an issue in  
> the Pharo bugs? Did you find it?

I haven't deeply check, but it is easy to understand why. You should  
not '10 initialExtent', even if 10 is the model of a system window.
Maybe SystemWindow>>initialExtent is wrongly defined, but I do not  
have enough Morphic knowledge to understand the implication.

Cheers,
Alexandre


>
>
> On 4 mars 2010, at 18:33, Alexandre Bergel wrote:
>
>> Hi!
>>
>> I do not have a solution, but Object>>initialExtent was recently  
>> deprecated and this causes great usability problem. This  
>> deprecation is very valuable for a clean UI separation. However, I  
>> have a warning deprecation each time a window is open. The reason  
>> stems from the method:
>>
>> SystemWindow>>initialExtent
>> ^ model initialExtent
>>
>> For now, in my image, I suppressed this deprecation.
>> Again, I do not have a clean solution.
>>
>> Cheers,
>> Alexandre
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> Simon
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev