Hi Igor,

ok. Everyone has other programming habits....

Greetings
Sabine

On Mon, Jun 10, 2013 at 10:56 AM, Igor Stasenko [via Smalltalk]
<[email protected]> wrote:
> On 10 June 2013 10:52, Sabine Knöfel <[hidden email]> wrote:
>> Hi Igor,
>>
>> thanks!
>>
>> Don't you agree with me that in this point, Pharo should have the same
>> behaviour as the other smalltalk dialects (VisualAge/IBM Smalltalk,
>> VisualWorks, Gemstone)?
>>
> i don't have strong opinion on that.
> for me, this is not a big deal.
>
>> Greetings
>> Sabine
>>
>> On Sun, Jun 9, 2013 at 6:37 PM, Igor Stasenko [via Smalltalk]
>> <[hidden email]> wrote:
>>
>>> On 9 June 2013 08:03, Sabine Knöfel <[hidden email]> wrote:
>>>
>>>> I should give an example why this is not useful for me.
>>>>
>>>> While developing, I use >>inspect to see, what is in any object AND I
>>>> want
>>>> the app to proceed.
>>>> E.g. while creating a report, I want to see the table columns in an
>>>> inspector.
>>>> I don't want to halt and debug, I only want to see an inspector.
>>>>
>>>> self currentPage        add:
>>>>                 (PDFDataTableWithColumnsCaptionElement new
>>>>                         captions: self costReportDaysTableColumns
>>>> inspect;
>>>>                         data: ...;
>>>>
>>>> Now, I have to write it like that
>>>>
>>>> self costReportDaysTableColumns inspect.
>>>> self currentPage add:
>>>>                 (PDFDataTableWithColumnsCaptionElement new
>>>>                         captions: self costReportDaysTableColumns ;
>>>>                         data: ...;
>>>>
>>>> Yes, this is possible but it is not so easigoing as simply put an
>>>> inspect
>>>> somewhere.
>>>>
>>> you still can use it:
>>>
>>>  self currentPage        add:
>>>                  (PDFDataTableWithColumnsCaptionElement new
>>>                          captions: (self costReportDaysTableColumns
>>> inspect; yourself);
>>>                          data: ...;
>>>
>>>> Remarks:
>>>> 1) I develop a seaside app. I am not interested in the System Window;-)
>>>> 2) I cant find a selector >>onWindowClosed:
>>>> 3) >>inspect is a selector which exists in every smalltalk dialect. In
>>>> every
>>>> smalltalk dialect I worked with, inspect returned the receiver.  It is
>>>> kind
>>>> of standard IMHO.
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>>
>>>>
>>>> http://forum.world.st/inspect-returns-iOf-SystemWindow-and-not-receiver-tp4692399p4692430.html
>>>
>>>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>>>>
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Igor Stasenko.
>>>
>>>
>>>
>>> ________________________________
>>> If you reply to this email, your message will be added to the discussion
>>> below:
>>>
>>>
>>> http://forum.world.st/inspect-returns-iOf-SystemWindow-and-not-receiver-tp4692399p4692470.html
>>
>>> To unsubscribe from inspect returns iOf SystemWindow and not receiver,
>>> click
>>> here.
>>> NAML
>>
>> ________________________________
>> View this message in context: Re: inspect returns iOf SystemWindow and not
>> receiver
>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>
>
>
> --
> Best regards,
> Igor Stasenko.
>
>
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://forum.world.st/inspect-returns-iOf-SystemWindow-and-not-receiver-tp4692399p4692589.html
> To unsubscribe from inspect returns iOf SystemWindow and not receiver, click
> here.
> NAML




--
View this message in context: 
http://forum.world.st/inspect-returns-iOf-SystemWindow-and-not-receiver-tp4692399p4692591.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Reply via email to