- Pharo-dev - lists.pharo.org

[Pharo-project] [COTDC] 84 - FreeTypeCacheLinkedList
by laurent laffont Sept. 10, 2011

Sept. 10, 2011

Today: FreeTypeCacheLinkedList Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

1 0

[Pharo-project] [COTDC] 83 - MCVersionInspector
by laurent laffont Sept. 10, 2011

Sept. 10, 2011

Today: MCVersionInspector Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

2 2

[Pharo-project] Immutability and Pharo
by Torsten Bergmann Sept. 10, 2011

Sept. 10, 2011

... comments? -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

3 3

[Pharo-project] Polymorph changes
by Gary Chambers Sept. 9, 2011

Sept. 9, 2011

Before I forget... A few changes to Polymorph and fixes for a few other packages attached. AlphaImageMorph supports #scaledAspect layout option (scales the image to fit whilst retaining aspect ratio) also class side accessor to set DefaultImage (I use the Pharo logo, appears in #exampleOtherControls) DialogItemsChooserUI centering rounded to avoid layout anomalies EditorFindReplaceDialogWindow initialized to position within usable area of display so not obscured by docks etc. GeneralScrollPane minWidth/minHeight when shrinkWrapping to target LazyListMorph mouse down row indication fixed PluggableListMorph fix for startDragExtended: mouse focus and wrapItem (when wrapSelector takes 0 args) ScrollPane will ignore mouse wheel iv not vertically scrollable (allows owners to handle) SystemWindow basicActivate no longer passivates old top window if no longer in world UITheme expander color no longer set to white by default nil labels for label groups now allow the associated control to fill whole width Also I've noticed that in latest updates, corner rounding no longer functions (affects scrollbars etc. in Watery 2 theme). Regards, Gary

4 11

[Pharo-project] Windows with nested menu
by Torsten Bergmann Sept. 9, 2011

Sept. 9, 2011

Do we have examples for building windows with a top menu somewhere? Is there support for icons, checked menu items, accelerator keys, ...? Tx. Torsten -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone

1 0

Re: [Pharo-project] [Vm-beginners] Fwd: Oops - I put a halt in a startup method
by Mariano Martinez Peck Sept. 9, 2011

Sept. 9, 2011

Sean: it may be difficult/impossible. But....you may want to try invoking the function say printOop() from the XCode console. If you read my post: http://marianopeck.wordpress.com/2011/04/23/how-to-debug-the-vm/ Then instead of doing "(gdb) call printAllStacks()" you can try something like "(gdb) call printOop(526237628)" and that will print something like "an XXX class". Of course, you need to replace 526237628 with the real OOP of your receiver object. Good luck! On Fri, Sep 9, 2011 at 5:35 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > From > http://forum.world.st/Oops-I-put-a-halt-in-a-startup-method-td3800163.html: > My image appears for an instant and then crashes. Is there any way to > recover from this? > > I made some progress, but I'm not sure I'm on the right track... > I built a debug VM and found primitivePerform, which is apparently called > by the following: > FeaturesDB perform: #startUp: with: resuming > > How will I know which call to skip/break on? Maybe there is there a way, > from the VM side, to get the receiver class name as a string? If I knew > that > the receiver was FeaturesDB, that would be the one... > > And then once I have the right call, can I just skip over it? > > Sean > > > -- > View this message in context: > http://forum.world.st/Fwd-Oops-I-put-a-halt-in-a-startup-method-tp3800729p3… > Sent from the Smalltalk VM - Beginners mailing list archive at Nabble.com. > _______________________________________________ > VM-beginners mailing list > VM-beginners(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/vm-beginners > -- Mariano http://marianopeck.wordpress.com

2 1

Re: [Pharo-project] [Seaside] Announcements/Seaside continuations collision in newer cog vm's
by Tudor Girba Sept. 9, 2011

Sept. 9, 2011

Henrik provided a better answer than mine: On 9 Sep 2011, at 14:44, Henrik Sperre Johansen wrote: > Which is why it was changed, after discussion with Lukas. > It only forks UnhandledErrors now, before delivering the remaining. > As long as there is no abnormal termination, it will work just as before. > If any subscribers would abnormally terminate though, the ifCurtailed: kicks in, and (was supposed to) ensure delivers to remaining subscribers. > > If something in Seaside relies on such behaviour (like terminating current process in order for subsequent subscribers to not receive the announcement) that will be broken. > I don't think messing with announcement delivery should be considered a good control flow mechanism though. > > What Esteban encountered as an error on some VM's was a pure bug I made in the ifCurtailed: block (by using after: instead of copyAfter:), and had nothing to do with forking. > Why some VM's considered the delivery abnormally terminated, while others didn't, I have no idea though... > (The error he got only happens when the ifCurtailed block is invoked). > > Cheers, > Henry Cheers, Doru On 9 Sep 2011, at 15:20, Sebastian Sastre wrote: > Isn't the plain events mechanism forkless and essential to the core of the system already? > > if you introduce that fork you break not only seaside but all artifacts of all the people that will rightly assume the current process between event and reaction is the same > > > > On Sep 9, 2011, at 7:13 AM, Tudor Girba wrote: > >> Igor and Stef can provide more details. >> >> The reason for forking is that even if one announcement breaks, the others should still be announced. Announcements are used for the functioning of the core of the system and this means that even if you register new objects, the core mechanisms (such as package management) should continue to work. >> >> It would be great if Seaside would work with these, and now depend on another framework. >> >> Cheers, >> Doru >> >> >> On 9 Sep 2011, at 06:38, Philippe Marschall wrote: >> >>> 2011/9/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>> Hi, >>>> (yep, I'm copying tree lists because I think is a vm problem, but can be a seaside problem, or a pharo problem) >>>> (yes, it can be MY problem too... but I don't think so... ;) >>>> >>>> I'm having this really, really strange problem (because it was working before, and I do not change anything... so, maybe a change in latest changes on pharo 1.3, the version I'm using, is the cause)... >>> >>> The announcements in the latest Pharo 1.3 don't work with Seaside >>> anymore. For some reason they fork them instead of running them in an >>> exception handler. >>> >>> Cheers >>> Philippe >>> _______________________________________________ >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> -- >> www.tudorgirba.com >> >> "Yesterday is a fact. >> Tomorrow is a possibility. >> Today is a challenge." >> >> >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > sebastian > > o/ > > > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -- www.tudorgirba.com "Be rather willing to give than demanding to get."

2 1

Re: [Pharo-project] [Seaside] Announcements/Seaside continuations collision in newer cog vm's
by Tudor Girba Sept. 9, 2011

Sept. 9, 2011

Igor and Stef can provide more details. The reason for forking is that even if one announcement breaks, the others should still be announced. Announcements are used for the functioning of the core of the system and this means that even if you register new objects, the core mechanisms (such as package management) should continue to work. It would be great if Seaside would work with these, and now depend on another framework. Cheers, Doru On 9 Sep 2011, at 06:38, Philippe Marschall wrote: > 2011/9/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >> Hi, >> (yep, I'm copying tree lists because I think is a vm problem, but can be a seaside problem, or a pharo problem) >> (yes, it can be MY problem too... but I don't think so... ;) >> >> I'm having this really, really strange problem (because it was working before, and I do not change anything... so, maybe a change in latest changes on pharo 1.3, the version I'm using, is the cause)... > > The announcements in the latest Pharo 1.3 don't work with Seaside > anymore. For some reason they fork them instead of running them in an > exception handler. > > Cheers > Philippe > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

1 0

[Pharo-project] [update 1.3] #13304
by Marcus Denker Sept. 9, 2011

Sept. 9, 2011

13304 ----- Issue 4778: Merge Browser is broken http://code.google.com/p/pharo/issues/detail?id=4778 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Help
by Lorenzo Schiavina Sept. 9, 2011

Sept. 9, 2011

Hi, I am trying to insert into a JQTab a JQCheckBox to obtain the same format as the one you can see in JQCheckBox, but I am not able to set CSS in JQTab to get the same format. Can anybody help me? Grazie Lorenzo

2 2