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

Re: [Pharo-project] Issue 3786 in pharo: Debug test .. (d) menu option in OBSystenBrowser gives SystemGuardException in Pharo 1.2

by pharo＠googlecode.com

Comment #1 on issue 3786 by renggli: Debug test .. (d) menu option in OBSystenBrowser gives SystemGuardException in Pharo 1.2 http://code.google.com/p/pharo/issues/detail?id=3786 Hmm, #asContext seems to push nil arguments in cog. Anyway, it can be easily fixed by popping the nil argument and pushing the right one again. Name: OB-SUnitIntegration-lr.40 Author: lr Time: 6 March 2011, 5:33:29 pm UUID: a58de078-0405-41f8-bbf3-1ce9fdb1b5b8 Ancestors: OB-SUnitIntegration-lr.39 - fix 'debug test' for Cog in Pharo 1.2

March 6, 2011

Re: [Pharo-project] Fwd: SIXX in Pharo 1.2

by StÃ©phane Ducasse

thanks On Mar 6, 2011, at 4:16 PM, Serge Stinckwich wrote: > Thanks to Umezawa-san SIXX is working now on Pharo 1.2 & Squeak 4.2. > All 127 tests are green under Pharo 1.2 ! > > To load the last version of SIXX: > > Gofer new squeaksource: 'MetacelloRepository'; package: > 'ConfigurationOfSIXX'; load. > (Smalltalk at:#ConfigurationOfSIXX) load. > > Regards > > ---------- Forwarded message ---------- > From: Masashi UMEZAWA <masashi.umezawa(a)gmail.com> > Date: Sat, Mar 5, 2011 at 7:25 PM > Subject: Re: SIXX in Pharo 1.2 > To: Serge Stinckwich <serge.stinckwich(a)gmail.com> > > > Hi Serge-san, > > Sorry for the delayed reply. I've updated ConfigurationOfSIXX. I > believe the latest SIXX runs on Pharo 1.2 and Squeak 4.2 nicely. > > Best regards, > > 2011/2/22 Masashi UMEZAWA <masashi.umezawa(a)gmail.com>: >> Hi Serge-san, >> >> Updating XMLSupport to version: '1.1.7', I was able to reproduce the >> test failures. >> According to ConfigurationOfSIXX, SIXX assumes XMLSupport 1.0.0. >> So I need to catch up new XMLSupport APIs... >> >> Best regards, >> >> 2011/2/22 Serge Stinckwich <serge.stinckwich(a)gmail.com>: >>> On Mon, Feb 21, 2011 at 8:41 PM, Masashi UMEZAWA >>> <masashi.umezawa(a)gmail.com> wrote: >>>> Hi Serge-san, >>>> >>>> I've updated Pharo 1.2 to the latest version.(#12336). >>>> And loaded SIXX via ConfigurationOfSIXX ( >=0.3.4 [ConfigurationOfSIXX]). >>>> >>>> Luckily all the tests were green. Perhaps there were some temporary problems? >>> >>> Hum ... strange. I try again with a PharoOneClick1.2 version (#12336). >>> I have some problems with deprecated methods : >>> >>> The method XMLNodeWithElements topElement has been deprecated. >>> use #firstElement instead >>> >>> Are you running the SIXXTests ? >>> >>> Regards, >>> -- >>> Serge Stinckwich >>> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >>> Every DSL ends up being Smalltalk >>> http://doesnotunderstand.org/ >>> >> -- >> [:masashi | ^umezawa] >> > > > > -- > [:masashi | ^umezawa] > > > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ >

March 6, 2011

[Pharo-project] Fwd: SIXX in Pharo 1.2

by Serge Stinckwich

Thanks to Umezawa-san SIXX is working now on Pharo 1.2 & Squeak 4.2. All 127 tests are green under Pharo 1.2 ! To load the last version of SIXX: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSIXX'; load. (Smalltalk at:#ConfigurationOfSIXX) load. Regards ---------- Forwarded message ---------- From: Masashi UMEZAWA <masashi.umezawa(a)gmail.com> Date: Sat, Mar 5, 2011 at 7:25 PM Subject: Re: SIXX in Pharo 1.2 To: Serge Stinckwich <serge.stinckwich(a)gmail.com> Hi Serge-san, Sorry for the delayed reply. I've updated ConfigurationOfSIXX. I believe the latest SIXX runs on Pharo 1.2 and Squeak 4.2 nicely. Best regards, 2011/2/22 Masashi UMEZAWA <masashi.umezawa(a)gmail.com>: > Hi Serge-san, > > Updating XMLSupport to version: '1.1.7', I was able to reproduce the > test failures. > According to ConfigurationOfSIXX, SIXX assumes XMLSupport 1.0.0. > So I need to catch up new XMLSupport APIs... > > Best regards, > > 2011/2/22 Serge Stinckwich <serge.stinckwich(a)gmail.com>: >> On Mon, Feb 21, 2011 at 8:41 PM, Masashi UMEZAWA >> <masashi.umezawa(a)gmail.com> wrote: >>> Hi Serge-san, >>> >>> I've updated Pharo 1.2 to the latest version.(#12336). >>> And loaded SIXX via ConfigurationOfSIXX ( >=0.3.4 [ConfigurationOfSIXX]). >>> >>> Luckily all the tests were green. Perhaps there were some temporary problems? >> >> Hum ... strange. I try again with a PharoOneClick1.2 version (#12336). >> I have some problems with deprecated methods : >> >> The method XMLNodeWithElements topElement has been deprecated. >> use #firstElement instead >> >> Are you running the SIXXTests ? >> >> Regards, >> -- >> Serge Stinckwich >> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >> Every DSL ends up being Smalltalk >> http://doesnotunderstand.org/ >> > -- > [:masashi | ^umezawa] > -- [:masashi | ^umezawa] -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

March 6, 2011

[Pharo-project] Fwd: Issue 1064 in pharo: There are still problem with keyboard shortcuts in Windows

by Mariano Martinez Peck

Hi, I fordward this thread to the VM mailing list since it looks more appropiated. David, here "tn" is proposing a fix. I am not qualified to take a look. Hope it helps Mariano ---------- Forwarded message ---------- From: <pharo(a)googlecode.com> Date: Sat, Mar 5, 2011 at 9:23 PM Subject: Re: [Pharo-project] Issue 1064 in pharo: There are still problem with keyboard shortcuts in Windows To: pharo-project(a)lists.gforge.inria.fr Comment #14 on issue 1064 by happy.lo...(a)gmail.com: There are still problem with keyboard shortcuts in Windows http://code.google.com/p/pharo/issues/detail?id=1064 Hi, I'm tn. 'ctrl + m' problem is Cog VM bug. Normally, when character key is pushed, keyboard events occur as follows on Squeak. 1. key press (down) 2. character (character code notification) 3. key release (up) They are produced by a primitive method in IutEventFetcher >> primGetNextEvent. But when ctrl + m is pushed, a character event doesn't occur. Because 'ctrl + m' value is 13. The value is same as ENTER key. Cog VM ignores WM_CHAR message(character event) when ENTER key is pushed. The one of solution for this problem is to add CTRL key state to the if-condition. -- sqWin32Window.c -- int recordKeyboardEvent(MSG *msg) { ... switch(msg->message) { ... case WM_CHAR: case WM_SYSCHAR: /* Note: VK_RETURN is recorded as virtual key ONLY */ if(keyCode == 13 && !ctrl) return 1; // add "&& !ctrl" pressCode = EventKeyChar; break; ... } ... Note: ENTER keyCode is 13. But when ctrl + ENTER is pushed, the keyCode is 10. So if the condition is revised, ctrl + m problem is corrected. but other behavior is not changed. If you want to prevent to generate character event for CTRL + ENTER, you can add following code. By this way, we can produce not only ctrl+m (0x0D)'s character event but also ctrl+j (0x0A)'s one. -- sqWin32Window.c -- // add this function static int isNotKeyDownCtrlReturn(MSG* msgp){ if(msgp->message == WM_KEYDOWN && msgp->wParam == VK_RETURN){ if(GetKeyState(VK_CONTROL) & 0x8000) { return FALSE; } } return TRUE; } ... int ioProcessEvents(void) { static MSG msg; ... if(isNotKeyDownCtrlReturn(&msg)){ // add TranslateMessage(&msg); } // add DispatchMessage(&msg); ... } ... int recordKeyboardEvent(MSG *msg) { ... if(pressCode == EventKeyDown && virtCode != 0 && isNotKeyDownCtrlReturn(lastMessage) ) { // add " && isNotKeyDownCtrlReturn(lastMessage) " /* generate extra character event */ ... } return 1; } An attached file is source, which has been corrected by above way. Note: Below is a comment in the source code. /* note: several keys are not reported as character events; most noticably the mapped virtual keys. For those we generate extra character events here */ Those keys(e.g. arrow) should not be ascii code. ENTER key is not. but an extra character events is created for ENTER. I don't think this behavior is correct. As for ENTER key, an extra character event must not be generated, and WM_CHAR message should be processed. Please see MSDN about TranslateMessage. see also Comment 11. Thanks, Attachments: sqWin32Window.c 99 KB

March 6, 2011

[Pharo-project] Fwd: Https Url in Pharo 1.2

by Stephan Eggermont

Stef wrote: >On Mar 6, 2011, at 8:39 AM, laurent laffont wrote: > Is it planed / possible to have SqueakSSL plugin in official VM shipped with Pharo ? >What is the license? You know the last time we got trapped into the game "oh I did not decided yet" so never again. >What is the status? On squeaksource it is MIT, last update from jan. 12. Stephan

March 6, 2011

Re: [Pharo-project] [squeak-dev] [ANN] ESUG supports once again SqueakDBX

by Mariano Martinez Peck

On Sun, Mar 6, 2011 at 12:40 PM, Levente Uzonyi <leves(a)elte.hu> wrote: > On Fri, 4 Mar 2011, Mariano Martinez Peck wrote: > > We are really happy to announce that ESUG will sponsor us once again >> through >> the ESUG Summer Talk project. This means that we have reached the ESUG >> expectations and that they still think that relational database access is >> an >> important matter in Smalltalk. >> > > snip > > 5) Cog compatibility. >> > > What has to be done? > > Indeed, nothing. We were not sure if FFI was working on it, but it turns out that it was. The idea is to be aware if Eliot releases a threaded VM/FFI so that we do not lock the VM (even if we have our micro-lock strategy when possible) > > >> 6) Use Alien instead of FFI. >> Eliot is working on a threaded CogVM. One of the projects of the GSoC of >> this year was to make something similar to a threaded FFI. What the >> student >> did is a modification in Alien (I think) that can be run in a >> multithreaded >> envirorment. He worked with Eliot. The idea is when Eliot releases the >> threaded CogVM, this FFI would work our of the box, and would avoid >> locking >> the WHOLE vm while a C function is being invoked (as it happens today with >> FFI).....So....when that VM is released, we MUST migrate to that). >> > > How is Alien better than FFI? We do not know. However, we will not spend time in Alien unless it is working out of the box and integrated in all standard VMs. > AFAIK Alien itself is not developed anymore, > parts of it will be merged with FFI. > > Ahh ok, we didn't know. Thnkas. > > Levente > > P.S.: http://www.squeaksource.com/SqueakDBX.html states that code in the > repository has MIT license, but it includes Glorp which has LGPL(S) license. > > Yes, the problem is that SqueakDBX as itself (the database driver), is MIT. Thus, the repository is MIT. Glorp is LGPL. When we started (years after SqueakDBX) with GlorpDBX, we found it easier to commit our changes to SqueakDBX repo instead of the Glorp one (because not everybody may agree with our changes). The good news is that Alan Night was considering making Glorp MIT. I cc'ed him to see if there are news. Cheers Mariano

March 6, 2011

Re: [Pharo-project] what's happened to the blogger group?

by Adrian Lienhard

On Mar 6, 2011, at 12:09 , Geert Claes wrote: > Francois has posted another nice weekly summary on his blog at > http://articles.tulipemoutarde.be For visibility I thought Dmitri and > Farncois were to be given access to the Pharo website so they can post on > the Pharo news/blg area too? Yes. I've created an account on our website for Dmitri. And I'll gladly create one for Farncois too (or anybody else who would like to take responsibility for posting news to the website). Cheers, Adrian

March 6, 2011

[Pharo-project] Issue 3786 in pharo: Debug test .. (d) menu option in OBSystenBrowser gives SystemGuardException in Pharo 1.2

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3786 by jvdsa...(a)gmail.com: Debug test .. (d) menu option in OBSystenBrowser gives SystemGuardException in Pharo 1.2 http://code.google.com/p/pharo/issues/detail?id=3786 Pharo image: Pharo Pharo core version: Pharo1.2rc2 update #12340 (Build #169) Virtual machine used: CogVM on OSX Class browser used: OBSystemDebugger Steps to reproduce: 1. Select any test method in the browser 2. Choose " Debug test ..." from the methods context menu Attachments: PharoDebug.log 28.1 KB

March 6, 2011

Re: [Pharo-project] what's happened to the blogger group?

by Geert Claes

Francois has posted another nice weekly summary on his blog at http://articles.tulipemoutarde.be For visibility I thought Dmitri and Farncois were to be given access to the Pharo website so they can post on the Pharo news/blg area too? -- View this message in context: http://forum.world.st/what-s-happened-to-the-blogger-group-tp3337416p333749… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 6, 2011

Re: [Pharo-project] defaultBorderColor and defaultBorderStyle

by StÃ©phane Ducasse

Hi doug Many things should be fixed it you want to see something happening faster, join :) provide a change. Stef On Mar 6, 2011, at 10:33 AM, DougEdmunds wrote: > Styles ( such as #inset, #raised, etc) should be separated out from > non-intuitive "defaultBorderColor" methods and consistently replaced with > defaultBorderStyle. > > For example, > Slider>>defaultBorderColor is #inset. > > Slider>>defaultBorderStyle would be much clearer. > > > > > -- > View this message in context: http://forum.world.st/defaultBorderColor-and-defaultBorderStyle-tp3337429p3… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

March 6, 2011