June 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Spec: custom layouts for sub-models

by Benjamin

Sorry for the delay, I was on holidays :) Can you tell me more please ? Ben Ben On May 28, 2013, at 9:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I have a UI, let's call it ParentUI, which includes ChildUI - another > ComposableModel. In the default layout, ChildUI includes a toolbar. > > When embedded in the ParentUI, I want the toolbars to be merged. It is easy > to include the ChildUI tools in the ParentUI bar by adding > ParentUI>>childTools, which I can then #add: to the layout. But the ChildUI > tools also still show up in ChildUI (so they appear twice). > > I ended up defining ChildUI>>#noToolbarSpec, which I can pass to the layout > like "add: #(#currentScenario. #noToolbarSpec)", and which delegates to > ChildUI class>>#noToolbarSpec. I want to have the default ChildUI spec > simply extend noToolbarSpec, but I didn't look into that yet. > > Anyway my question is: is this the best way to do what I'm trying to do? > > Thanks! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Spec-custom-layouts-for-sub-models-tp4690508.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

June 9, 2013

Re: [Pharo-users] inspect returns iOf SystemWindow and not receiver

by Igor Stasenko

On 9 June 2013 08:03, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> 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-tp4… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > -- Best regards, Igor Stasenko.

June 9, 2013

Re: [Pharo-users] DateAndTime>>asTime

by StÃ©phane Ducasse

you are welcome :) On Jun 9, 2013, at 12:53 PM, JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com> wrote: > Done. > > Sorry for my ignorance, :). > > Thanks > > 2013/6/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > thanks :) > This is less work for us and the process can automatically check the code and run the tests automatically. > Stef > >

June 9, 2013

Re: [Pharo-users] inspect returns iOf SystemWindow and not receiver

by StÃ©phane Ducasse

but halt is really a simple method you can introduce myHalt Object>>myHalt Halt signal. and you are done. Stef On Jun 9, 2013, at 9:58 AM, phil(a)highoctane.be wrote: > +1 to what Sabine says. Very useful behavior. > > Phil > > > On Sun, Jun 9, 2013 at 8:03 AM, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> 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. > > 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-tp4… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > >

June 9, 2013

Re: [Pharo-users] DateAndTime>>asTime

by JosÃ© ComesaÃ±a

Done. Sorry for my ignorance, :). Thanks 2013/6/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > thanks :) > This is less work for us and the process can automatically check the code > and run the tests automatically. > Stef > >

June 9, 2013

Re: [Pharo-users] inspect returns iOf SystemWindow and not receiver

by Marcus Denker

On Jun 8, 2013, at 8:30 PM, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Hi, > > while developing my app with seaside, I sometimes use inspect within any > statement. > I am used from Pharo 1.4 and from other smalltalk dialects, that >>inspect > returns the receiver itself. > But in Pharo 2.0 it returns an instance of SystemWindow. > I dont see any sense in that. It that with intent? > A bug report is here: https://pharo.fogbugz.com/f/cases/6989/Inspect-should-be-silent Marcus

June 9, 2013

Re: [Pharo-users] inspect returns iOf SystemWindow and not receiver

by phil＠highoctane.be

+1 to what Sabine says. Very useful behavior. Phil On Sun, Jun 9, 2013 at 8:03 AM, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com>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. > > 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-tp4… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > >

June 9, 2013

Re: [Pharo-users] inspect returns iOf SystemWindow and not receiver

by Sabine KnÃ¶fel

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. 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-tp4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 9, 2013

Re: [Pharo-users] inspect returns iOf SystemWindow and not receiver

by ClÃ©ment Bera

I think the reason was the need of registering onWindowClose: event or closing the window by the code easily. Now you can do : | w | w := Object inspect. w onWindowClosed: [ ... ]. ... w close. 2013/6/9 Igor Stasenko <siguctua(a)gmail.com> > On 8 June 2013 20:29, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > > Hi, > > > > while developing my app with seaside, I sometimes use inspect within any > > statement. > > I am used from Pharo 1.4 and from other smalltalk dialects, that > >>inspect > > returns the receiver itself. > > But in Pharo 2.0 it returns an instance of SystemWindow. > > I dont see any sense in that. It that with intent? > > > > I was not behind the change, but i think answering window is more > useful than just receiver. > Since you sending 'inspect' message to object you already having access to > it, > and getting same object back is less useful, than inspector window, > which you can > give extra instructions (like placement etc). > > > > Sabine > > > > > > > > -- > > View this message in context: > http://forum.world.st/inspect-returns-iOf-SystemWindow-and-not-receiver-tp4… > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > > -- > Best regards, > Igor Stasenko. > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

June 9, 2013

Re: [Pharo-users] inspect returns iOf SystemWindow and not receiver

by Igor Stasenko

On 8 June 2013 20:29, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Hi, > > while developing my app with seaside, I sometimes use inspect within any > statement. > I am used from Pharo 1.4 and from other smalltalk dialects, that >>inspect > returns the receiver itself. > But in Pharo 2.0 it returns an instance of SystemWindow. > I dont see any sense in that. It that with intent? > I was not behind the change, but i think answering window is more useful than just receiver. Since you sending 'inspect' message to object you already having access to it, and getting same object back is less useful, than inspector window, which you can give extra instructions (like placement etc). > Sabine > > > > -- > View this message in context: http://forum.world.st/inspect-returns-iOf-SystemWindow-and-not-receiver-tp4… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > -- Best regards, Igor Stasenko.

June 9, 2013