July 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] Baseline test results on pharo core 10392

by Torsten Bergmann

>Solutions I see: >... For the second time: Why not use the #isAbstract trick I proposed on [1]? This makes the unit test an abstract one on non-mac platforms and is the simplest thing that could possibly work ... Bye Torsten [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-June/009640.html -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

July 27, 2009

Re: [Pharo-project] [squeak-dev] [ANN] Win32 Pharo setup 0.0.0.7. (based on Pharo0.1-10388)

by Mariano Martinez Peck

On Mon, Jul 27, 2009 at 9:09 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > see https://gforge.inria.fr/frs/download.php/22699/<https://gforge.inria.fr/frs/download.php/22699/setup_pharo_0.0.0.7.exe> > setup_pharo_0.0.0.7.exe<https://gforge.inria.fr/frs/download.php/22699/setup_pharo_0.0.0.7.exe> > > A new setup for windows from the dev-image 10388 [1] > bundled together with the new Win32 virtual machine [2]. > Excellent news. Now I wonder....this one click Pharo seems to be far the best aproach of installing Pharo on Windows for a newbie...So, what about having a link in http://www.pharo-project.org/pharo-download to this setup_pharo_0.0.0.7.exe? > > Bye > Torsten > > [1] > http://lists.gforge.inria.fr/pipermail/pharo-project/2009-July/011412.html > [2] > http://lists.squeakfoundation.org/pipermail/vm-dev/2009-July/002797.html > -- > Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - > sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser > >

July 27, 2009

Re: [Pharo-project] Baseline test results on pharo core 10392

by Mariano Martinez Peck

As I have said in another mail, we have problems with HostSystemMenusTest. This is mac specific and thus they fail in Linux/Windows. Solutions I see: 1) Put those test in a separated Mac specific Package. The thing is that as they are test I don't know when to download that package 2) Do something so that they are interpreted as "expected failures" if we are in Linux/Windows 3) Put an If in every tests. I don't like this solution at all what do you thing about this ? Thanks, Mariano 2009/7/25 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > As I can't modify the wiki this is the output of the script of Mike > Roberts for Baseline test results on pharo core 10392. > Can someone with write permission update the wiki please, > > Thanks, > Miguel CobÃ¡ > > = 10392 = > 7123 run, 7037 passes, 4 expected failures, 17 failures, 65 errors, 0 > unexpected passes > > == Failures == > {{{ > ClosureCompilerTest>>#testInjectIntoDecompiledDebugs > ClosureCompilerTest>>#testSourceRangeAccessForBlueBookInjectInto > ClosureCompilerTest>>#testSourceRangeAccessForBlueBookLongFormInjectInto > ClosureCompilerTest>>#testSourceRangeAccessForClosureBytecodeInjectInto > > ClosureCompilerTest>>#testSourceRangeAccessForClosureLongFormBytecodeInjectInto > ClosureCompilerTest>>#testSourceRangeAccessForInjectInto > HostWindowTests>>#testOne > > IVsAndClassVarNamesConflictTest>>#testClassWithInvalidClassVariablesShouldNotBeReferencedByItsSuperclass > MethodPragmaTest>>#testReformat > MorphicToolBuilderTests>>#testGetButtonColor > MorphicToolBuilderTests>>#testGetButtonSideEffectFree > MorphicUIBugTest>>#testOpenWorkspaceAns > PNGReadWriterTest>>#test16BitDisplay > ProcessSpecificTest>>#testDynamicVariable > ProcessSpecificTest>>#testLocalVariable > ReleaseTest>>#testObsoleteClasses > ReleaseTest>>#testUndeclared > }}} > > == Errors == > {{{ > BlockContextTest>>#testTrace > ClosureCompilerTest>>#testDebuggerTempAccess > DebuggerUnwindBug>>#testUnwindDebugger > HostSystemMenusTest>>#testAppendWindowMenuMacOnly > HostSystemMenusTest>>#testCharacterChanging > HostSystemMenusTest>>#testCommandIDMacOnly > HostSystemMenusTest>>#testCountsMacOnly > HostSystemMenusTest>>#testEditMenuEncodingMacOnly > HostSystemMenusTest>>#testEditMenuIsMenuItemEnabledMacOnly > HostSystemMenusTest>>#testEditMenuItemCmdMacOnly > HostSystemMenusTest>>#testEditMenuItemIconMacOnly > HostSystemMenusTest>>#testEditMenuItemMarkMacOnly > HostSystemMenusTest>>#testEditMenuItemStyle > HostSystemMenusTest>>#testEditMenuItemsTextMacOnly > HostSystemMenusTest>>#testEditMenuKeyGlyphMacOnly > HostSystemMenusTest>>#testEditMenuModifiersMacOnly > HostSystemMenusTest>>#testEncodingMacOnly > HostSystemMenusTest>>#testFileMenuCommandIDMacOnly > HostSystemMenusTest>>#testFileMenuQuitEnabledMacOnly > HostSystemMenusTest>>#testFileMenuQuitTextMacOnly > HostSystemMenusTest>>#testFontIDMacOnly > HostSystemMenusTest>>#testGetMenuTitleMacOnly > HostSystemMenusTest>>#testKeyGlyphMacOnly > HostSystemMenusTest>>#testMenuHandles > HostSystemMenusTest>>#testMenuHandlesCount > HostSystemMenusTest>>#testMenuHandlesGetMenu1CommandID > HostSystemMenusTest>>#testMenuHandlesGetMenu1Encoding > HostSystemMenusTest>>#testMenuHandlesGetMenu1FontID > HostSystemMenusTest>>#testMenuHandlesGetMenu1KeyGlyph > HostSystemMenusTest>>#testMenuHandlesGetMenu2CommandID > HostSystemMenusTest>>#testMenuHandlesGetMenu2IsMenuItemEnabled > HostSystemMenusTest>>#testMenuHandlesGetMenu2Items > HostSystemMenusTest>>#testMenuHandlesGetMenu3Encoding > HostSystemMenusTest>>#testMenuHandlesGetMenu3IsMenuItemEnabled > HostSystemMenusTest>>#testMenuHandlesGetMenu3ItemCmd > HostSystemMenusTest>>#testMenuHandlesGetMenu3ItemIcon > HostSystemMenusTest>>#testMenuHandlesGetMenu3ItemMark > HostSystemMenusTest>>#testMenuHandlesGetMenu3ItemStyle > HostSystemMenusTest>>#testMenuHandlesGetMenu3Items > HostSystemMenusTest>>#testMenuHandlesGetMenu3KeyGlyph > HostSystemMenusTest>>#testMenuHandlesGetMenu3Modifiers > HostSystemMenusTest>>#testMenuHandlesGetMenuTitle > HostSystemMenusTest>>#testMenuHandlesNewMenu > HostSystemMenusTest>>#testMenuHandlesNewMenuAppend > HostSystemMenusTest>>#testMenuHandlesNewMenuAppend2 > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendCheck > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendCheckSetCmd > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendCheckSetCmd2 > > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendCheckSetItemHierarchicalID > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendCheckSetItemModifiers > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendCheckSetItemText > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendCheckSetItemTextEncoding > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendCheckSetItemTextFondID > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendCheckSetMark > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendCheckSetMenuTitle > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendCheckSetStyle > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendDeleteItem > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendDeleteItem2 > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendInsertItem > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendText > HostSystemMenusTest>>#testMenuHandlesNewMenuAppendWindowMenu > HostSystemMenusTest>>#testMenuHideShowMenu > LocaleTest>>#testIsFontAvailable > MethodContextTest>>#testTempNamed > MethodContextTest>>#testTempNamedPut > }}} > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 27, 2009

Re: [Pharo-project] Baseline test results on pharo core 10392

by Miguel CobÃ¡

2009/7/25 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com>: > As I can't modify the wiki this is the output of the script of Mike > Roberts for Baseline test results on pharo core 10392. > Can someone with write permission update the wiki please, > I have updated the wiki page for baseline results for 10392 pharo core image. Miguel CobÃ¡

July 27, 2009

Re: [Pharo-project] Fix for issue 981 Author class in pharo

by Miguel CobÃ¡

2009/7/25 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com>: > http://code.google.com/p/pharo/issues/detail?id=981 > > Name: SLICE-ChangeAuthorInitialsAndNameToFullName-MiguelCoba.3 > Author: MiguelCoba > Time: 25 July 2009, 3:53:41 am > UUID: 27a1accc-4f41-4d11-94f5-9bdbb4166bd7 > Ancestors: SLICE-ChangeAuthorInitialsAndNameToFullName-MiguelCoba.2 > Dependencies: Monticello-MiguelCoba.372, Morphic-MiguelCoba.347, > ScriptLoader-MiguelCoba.972, System-Changes-MiguelCoba.11, > System-Support-MiguelCoba.62, Tools-MiguelCoba.179 > > Removes all the code from initials and name on Author class. It is > replaced by a new fullName inst var and corresponding methods. The old > code it is deprecated and the image contains no more calls to the old > code. All the new code should call only the fullName methods in Author > > > This is my first intent to rewrite the Author class to unify the > instance variables. > Please, check it on a 10392 core image and post your comments/critics. > > Also, I didn't modify the following methods of Utilities. Tell me what > would you like to do with them, please: > > Utilities fixStamp: > Utilities methodsWithInitials: > Utilities doesMethod:forClass:bearInitials > Also, it should fix also http://code.google.com/p/pharo/issues/detail?id=142 http://code.google.com/p/pharo/issues/detail?id=344 I changed the status of 981 to fixed as directed by the HowToContribute wiki page. Miguel CobÃ¡ > Cheers, > Miguel CobÃ¡ > >

July 27, 2009

Re: [Pharo-project] problem with debugger

by Fabrizio Perin

thanks a lot. You were amazingly helpful :) I will download the next upgrade and next time I will provide you a better feed back. Cheers, Fabrizio 2009/7/27 Marcus Denker <denker(a)acm.org> > > On 27.07.2009, at 10:12, Damien Cassou wrote: > > > Hi Fabrizio, > > > > 2009/7/27 Fabrizio Perin <fabrizio.perin(a)gmail.com>: > >> i'm using the image 10392. When I try to debug something an error > >> occurred > >> every time I hit a button (like debug for instance). The error is > >> "Error: > >> key not found". There is a way to copy the stack? > > > > this is a known bug which has a fix. Please find more information on: > > > > http://code.google.com/p/pharo/issues/detail?id=913 > > > > To load the fix, open the PharoInbox repository using Monticello and > > load Compiler-damiencassou.115. > > > > Sorry about that. > > > > #10393 should fix this and the encoding bug. > > Marcus > > > > > -- > Marcus Denker - http://marcusdenker.de > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2009

Re: [Pharo-project] [update] #10393

by Damien Cassou

Hi Marcus, thank you very much for your quick release. However. I can still reproduce bug #987 that you marked duplicate and then closed. Bye On Mon, Jul 27, 2009 at 4:36 PM, Marcus Denker<denker(a)acm.org> wrote: > 10393 > ----- > Issue 987: Â Â Â 'stack top' variable on debugger crashes it > Issue 986: Â Â Â mac-roman text encoding broken > revert: > Issue 913: Â Â Â Problem with ob-debugger > > Â Â Â Â Marcus > > -- > Marcus Denker - http://marcusdenker.de > New: Twitter account: http://twitter.com/marcusdenker > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 27, 2009

Re: [Pharo-project] problem with debugger

by Marcus Denker

On 27.07.2009, at 10:12, Damien Cassou wrote: > Hi Fabrizio, > > 2009/7/27 Fabrizio Perin <fabrizio.perin(a)gmail.com>: >> i'm using the image 10392. When I try to debug something an error >> occurred >> every time I hit a button (like debug for instance). The error is >> "Error: >> key not found". There is a way to copy the stack? > > this is a known bug which has a fix. Please find more information on: > > http://code.google.com/p/pharo/issues/detail?id=913 > > To load the fix, open the PharoInbox repository using Monticello and > load Compiler-damiencassou.115. > > Sorry about that. > #10393 should fix this and the encoding bug. Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

July 27, 2009

[Pharo-project] [update] #10393

by Marcus Denker

10393 ----- Issue 987: 'stack top' variable on debugger crashes it Issue 986: mac-roman text encoding broken revert: Issue 913: Problem with ob-debugger Marcus -- Marcus Denker - http://marcusdenker.de New: Twitter account: http://twitter.com/marcusdenker

July 27, 2009

Re: [Pharo-project] problem with debugger

by Damien Cassou

Hi Fabrizio, 2009/7/27 Fabrizio Perin <fabrizio.perin(a)gmail.com>: > i'm using the image 10392. When I try to debug something an error occurred > every time I hit a button (like debug for instance). The error is "Error: > key not found". There is a way to copy the stack? this is a known bug which has a fix. Please find more information on: http://code.google.com/p/pharo/issues/detail?id=913 To load the fix, open the PharoInbox repository using Monticello and load Compiler-damiencassou.115. Sorry about that. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 27, 2009