June 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Cuis 3.3

by Guillermo Polito

On Sun, Jun 5, 2011 at 4:53 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > > > > Maybe we can list the interesting things to add and open tickets? That > we we'll not forget ;) > > Yes here is the list > > > > > On Sat, Jun 4, 2011 at 6:09 PM, stephane ducasse < > stephane.ducasse(a)free.fr> wrote: > > Hi guys > > > > Some items would be good to have in pharo like the event cleaning... to > bad that we cannot collaborate more > > but this is like that. > > > > May be have a look > > > * New hierarchy of Morphic Windows for tools, builds and handles UI > > and menus; handles keystrokes > > - View / Model separation is now complete > > - Models are now GUI agnostic: they have 25% less methods and no > references to Morphs > > http://code.google.com/p/pharo/issues/detail?id=4359 > we are rewriting all StringHolder with the same purpose so comparing is > interesting at the design level. > > certainly: > > > * Object level events cleanup > > - Gone is Model and the DependentsFields classVar in Object > > - Only object event system mechanism is #when:send:to: > It's already here: http://code.google.com/p/pharo/issues/detail?id=4352&colspec=ID%20Type%20St… > > > > * Deep Models cleanup > http://code.google.com/p/pharo/issues/detail?id=4360 > > > > * Big cleanup of copy and friends. > > - #deepCopy eliminated > > - #veryDeepCopy, DeepCopier, #veryDeepInner:, > > #veryDeepFixupWith: eliminated. > > http://code.google.com/p/pharo/issues/detail?id=4361&q=owner%3Ame&colspec=I… > > > * Editor tweaks and enhancements. Code simplification, removed > > several ivars > > > > http://code.google.com/p/pharo/issues/detail?id=4362 > > > * FileList refactor > > http://code.google.com/p/pharo/issues/detail?id=4363

June 5, 2011

[Pharo-project] help to remove toolbuilder

by StÃ©phane Ducasse

Hi gary I could nearly remove toolBuilder if I could know what to do with [ToolBuilder default runModal: aSystemWindow openAsIs] in openModal: aSystemWindow "Open the given window locking the receiver until it is dismissed. Answer the system window. Restore the original keyboard focus when closed." |area mySysWin keyboardFocus| keyboardFocus := self activeHand keyboardFocus. mySysWin := self isSystemWindow ifTrue: [self] ifFalse: [self ownerThatIsA: SystemWindow]. mySysWin ifNil: [mySysWin := self]. mySysWin modalLockTo: aSystemWindow. area := RealEstateAgent maximumUsableArea. aSystemWindow extent: aSystemWindow initialExtent. aSystemWindow position = (0@0) ifTrue: [aSystemWindow position: self activeHand position - (aSystemWindow extent // 2)]. aSystemWindow bounds: (aSystemWindow bounds translatedToBeWithin: area). [ToolBuilder default runModal: aSystemWindow openAsIs] ensure: [mySysWin modalUnlockFrom: aSystemWindow. self activeHand newKeyboardFocus: keyboardFocus]. ^aSystemWindow Stef

June 5, 2011

Re: [Pharo-project] testing ui errors in headless mode

by Tudor Girba

Hi, I would need a bit of help with this one :). I tried: testStartup self shouldnt: [[1 inspect] on: ErrorNonInteractive do: [:x | ]] raise: Error This still fails. Is there a way around it? You can try using the attached st file. Cheers, Doru Begin forwarded message: > From: Tudor Girba <tudor(a)tudorgirba.com> > Date: 31 May 2011 23:08:03 CEST > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] testing ui errors in headless mode > > Hi, > > On 31 May 2011, at 22:32, Igor Stasenko wrote: > >> On 31 May 2011 23:15, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> Hi Igor, >>> >>> Sorry for the late reply. >>> >>> >>> >>> On 26 May 2011, at 17:48, Igor Stasenko wrote: >>> >>>> On 26 May 2011 17:03, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>> Hi, >>>>> >>>>> I tried several ways to get my head around this problem, but I do not know how to proceed. Can anyone help? >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> On 25 May 2011, at 21:21, Tudor Girba wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> We have some smoke tests in Moose that basically spawn a UI and check for Error. >>>>>> >>>>>> This used to work when running headless in Pharo 1.2 but now they fail in Pharo 1.3. I believe this has to do with the new changes in the UI Manager, but I do not know what to do. >>>>>> >>>>>> To reproduce the problem, you can simply call a Pharo-1.3.image in headless mode and file in the attached st file that: >>>>>> >>>>>> - installs a simple test: >>>>>> HeadlessTest>>testStartup >>>>>> self shouldnt: [1 inspect] raise: Error >>>> >>>> Tudor, your test is wrong. >>>> During image startup and in headless mode calling inspector will and >>>> should raise an error. >>>> Because inspecting object requires a presence of UI. >>>> But there's no UI in headless mode and prohibited from use during >>>> image startup phase, because >>>> you cannot start asking questions from user before properly >>>> initializing everything related to startup. >>>> Startup is called startup on purpose: is should not be interrupted nor >>>> require user's interaction. >>>> >>>> Assume that you don't have Morphic loaded in your image, then what you >>>> expect to happen if you do >>>> 1 inspect >>>> ? >>> >>> I understand now that the test is wrong. I just wanted to offer an example of spawning a ui, but I think I found the problem like this :). >>> >>> Now, the thing is that my test tests that triggering the entries from a menu does not result in an error. And inspect or browse happen to be among the menu entries. Is there a way to still have this test working on the server? >>> >>> Should I put a guard condition in the method triggering the inspector? That sounds bad. Any other ideas? >>> >> >> Yes, you could swallow all ErrorNonInteractive. >> So if you will know that something will lead to UI interaction, you >> can catch ErrorNonInteractive. >> Since there is no UI you won't proceed further, but still will know >> that during running the test some UI is involved. >> >> So, actually a following should pass: >> >> UIManager default isInteractive ifFalse: [ >> self should: [1 inspect] raise: ErrorNonInteractive >> ] >> >> The problem is that there is some missing protocol in >> NonInteractiveUIManager (because at the time i was adding it , i >> covered all methods, >> but then some more stuff were added to morphic ui manager without >> parallel extension to other ui managers, >> so the test above can fail because you will get DNU error instead of >> ErrorNonInteractive ) > > I tried it: > > testStartup > self shouldnt: [[1 inspect] on: ErrorNonInteractive do: [:x | ]] raise: Error > > But this still fails. You can try using the attached st file. > > Cheers, > Doru > > >>> Cheers, >>> Doru >>> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > -- > www.tudorgirba.com > > "The coherence of a trip is given by the clearness of the goal." > > > > -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

June 5, 2011

Re: [Pharo-project] Oops.... unloading toolbuilder-Morphic leads to image crash....

by StÃ©phane Ducasse

it seems that toolbuilder contained MorphicUIManager... Stef On Jun 5, 2011, at 7:57 PM, StÃ©phane Ducasse wrote: > when using unload on toolbuilder-morphic > we get a VM crash without a log :( > > stef >

June 5, 2011

[Pharo-project] Oops.... unloading toolbuilder-Morphic leads to image crash....

by StÃ©phane Ducasse

when using unload on toolbuilder-morphic we get a VM crash without a log :( stef

June 5, 2011

Re: [Pharo-project] About Morph and name?

by StÃ©phane Ducasse

On Jun 5, 2011, at 6:08 PM, Fernando Olivero wrote: > I agree 100%. > > #externalName also is a strangely named method. > > I never felt the need to refer to a morph by its name. Yes Ok so I will start removing the setNameTo: > > another issue is wether we want to keep the halos? Making them > unavailable in current Pharo (at least directly ) was on purpose? yes so that they do not get in our way all the time. > > Fernando. > > On Sun, Jun 5, 2011 at 3:28 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> I was looking at Cuis and juan removed externalName and friends and replace them by printLimited.... >> What do you think we should do? >> Name for morph are mainly used in halosmorph and to debug (so we could do the same than cuis). >> >> Stef >> >

June 5, 2011

Re: [Pharo-project] About Morph and name?

by Fernando Olivero

I agree 100%. #externalName also is a strangely named method. I never felt the need to refer to a morph by its name. another issue is wether we want to keep the halos? Making them unavailable in current Pharo (at least directly ) was on purpose? Fernando. On Sun, Jun 5, 2011 at 3:28 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I was looking at Cuis and juan removed externalName and friends and replace them by printLimited.... > What do you think we should do? > Name for morph are mainly used in halosmorph and to debug (so we could do the same than cuis). > > Stef >

June 5, 2011

Re: [Pharo-project] [SqueakDBX] MS SQL access on a MAC

by Mariano Martinez Peck

On Sun, Jun 5, 2011 at 4:56 PM, Michael Atkisson <michaelatkisson1(a)me.com>wrote: > Can you use Squeakdbx to access a MS SQL database > on a MAC. Yes. > I don't understand the designation > X( not us yet) in the supported backends doc. > > What "not us yet" means is that WE (SqueakDBX developers) didn't test it ourselfs. Instead, someone else, a SqueakDBX user did it. So, we couldn't document the website as we usually do in: http://www.squeakdbx.org/Different%20backends%20under%20Mac The following links may help: http://www.squeakdbx.org/Compiling%20and%20installing%20OpenDBX I think it may not be too much differnt of how to make it work in Linux: http://www.squeakdbx.org/SQL%20Server Maybe there is someone else that could help. Please ask if you have more questions/problems. Best regards, Mariano Thanks! > _______________________________________________ > SqueakDBX mailing list > SqueakDBX(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx > -- Mariano http://marianopeck.wordpress.com

June 5, 2011

[Pharo-project] About Morph and name?

by StÃ©phane Ducasse

Hi guys I was looking at Cuis and juan removed externalName and friends and replace them by printLimited.... What do you think we should do? Name for morph are mainly used in halosmorph and to debug (so we could do the same than cuis). Stef

June 5, 2011

Re: [Pharo-project] squeaksource is down

by Fabrizio Perin

is up now 2011/6/5 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Jun 5, 2011, at 1:46 PM, Norbert Hartl wrote: > > > > > Am 05.06.2011 um 13:23 schrieb StÃ©phane Ducasse: > > > >> The problem is that I do not know the password to restart it and marcus > and fabrizio do not seem to be connected. > >> > > I think I see Marcus in a short timeframe. If I think it is a good idea > to ruin his afternoon I will tell him :) > lol :) > you re evil :) > Stef > > > > Norbert > > > > > > >

June 5, 2011