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

Re: [Pharo-project] Pharo 1.1/1.2 and class names in Chinese

by Alexandre Bergel

> I'd even suggest the system to reject names and selectors not in ASCII. I agree for what has to be put in PharoCore and Pharo. However, a user lambda must be able to create a class called MaClassePrÃ©fÃ©rÃ©e if he/she wishes. Every beginner do this... Cheers, Alexandre > > Cheers, > Juan Vuletich > > Alexandre Bergel wrote: >> I have no idea how to help you. But trying to have classes with chinese (or any other alphabet with accents) names is important. >> Even though I personally write all my code in English, many like to write code in their favorite natural language. This is what I see with students for example. >> >> Cheers, >> Alexandre >> >> >> On 28 Jul 2010, at 21:33, empty wrote: >> >> >>> In 1.1 and 1.2, without setting a language environment for Chinese, I am able >>> to use Chinese by setting fonts. It seems to work except for accepting a >>> class named in Chinese will end in a ClassBuilder error of 'Class names must >>> be capitalized'. Well is it a feature(requires language environment being >>> set correctly) or bug? >>> >>> The code located being: >>> >>> validateClassName: aString >>> "Validate the new class name" >>> >>> aString isSymbol >>> ifFalse: [ ^ false ]. >>> aString first canBeGlobalVarInitial ifFalse:[ >>> self error: 'Class names must be capitalized'. >>> ^false]. >>> environ at: aString ifPresent:[:old| >>> (old isKindOf: Behavior) ifFalse:[ >>> self notify: aString asText allBold, ' already exists!\Proceed will store over it.' withCRs]]. >>> ^ true >>> >>> and following the code the problemic method is #canBeGlobalVarInitial: which >>> is found in two classes: >>> in EncodedCharSet class side: >>> canBeGlobalVarInitial: char >>> >>> | leadingChar | >>> leadingChar := char leadingChar. >>> >>> leadingChar = 0 ifTrue: [^ self isUppercase: char]. >>> ^ self isLetter: char. >>> >>> and in LanguageEnvironment >>> >>> canBeGlobalVarInitial: char >>> >>> ^ Unicode canBeGlobalVarInitial: char. >>> >>> I didn't set a Chinese environment and the exception is occured in in >>> EncodedCharSet class since leadingChar is 0 and a Chinese char seems thought >>> to be lowercased. >>> >>> >>> >>> >>> ----- >>> åç¡ä½ åç¡æ³ åç¡å§ >>> -- >>> View this message in context: http://forum.world.st/Pharo-1-1-1-2-and-class-names-in-Chinese-tp2305496p23… >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> ------------------------------------------------------------------------ >> >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com Version: 9.0.851 / Virus Database: 271.1.1/3030 - Release Date: 07/26/10 15:34:00 >> >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 28, 2010

Re: [Pharo-project] Pharo 1.1/1.2 and class names in Chinese

by Juan Vuletich

Hi Folks, I think that is a mistake. Having Spanish as my mother tongue, I used to code with Spanish names before knowing Smalltalk. So when started using Smalltalk I kept doing it. Later I realized it is a bad idea. In Smalltalk there is no clear distinction between the "vendor libraries" and our own code. Our application specific classes will many times implement methods akin to existing ones in the system. Writing their names in English makes the whole system more consistent. Following this a little bit, it is better if all the code we write is in English too. OTOH, I believe it is ok to write comments in languages other than English (if the code will not be open sourced). I'd even suggest the system to reject names and selectors not in ASCII. Cheers, Juan Vuletich Alexandre Bergel wrote: > I have no idea how to help you. But trying to have classes with chinese (or any other alphabet with accents) names is important. > Even though I personally write all my code in English, many like to write code in their favorite natural language. This is what I see with students for example. > > Cheers, > Alexandre > > > On 28 Jul 2010, at 21:33, empty wrote: > > >> In 1.1 and 1.2, without setting a language environment for Chinese, I am able >> to use Chinese by setting fonts. It seems to work except for accepting a >> class named in Chinese will end in a ClassBuilder error of 'Class names must >> be capitalized'. Well is it a feature(requires language environment being >> set correctly) or bug? >> >> The code located being: >> >> validateClassName: aString >> "Validate the new class name" >> >> aString isSymbol >> ifFalse: [ ^ false ]. >> aString first canBeGlobalVarInitial ifFalse:[ >> self error: 'Class names must be capitalized'. >> ^false]. >> environ at: aString ifPresent:[:old| >> (old isKindOf: Behavior) ifFalse:[ >> self notify: aString asText allBold, >> ' already exists!\Proceed will store over it.' withCRs]]. >> ^ true >> >> and following the code the problemic method is #canBeGlobalVarInitial: which >> is found in two classes: >> in EncodedCharSet class side: >> canBeGlobalVarInitial: char >> >> | leadingChar | >> leadingChar := char leadingChar. >> >> leadingChar = 0 ifTrue: [^ self isUppercase: char]. >> ^ self isLetter: char. >> >> and in LanguageEnvironment >> >> canBeGlobalVarInitial: char >> >> ^ Unicode canBeGlobalVarInitial: char. >> >> I didn't set a Chinese environment and the exception is occured in in >> EncodedCharSet class since leadingChar is 0 and a Chinese char seems thought >> to be lowercased. >> >> >> >> >> ----- >> åç¡ä½ åç¡æ³ åç¡å§ >> -- >> View this message in context: http://forum.world.st/Pharo-1-1-1-2-and-class-names-in-Chinese-tp2305496p23… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.851 / Virus Database: 271.1.1/3030 - Release Date: 07/26/10 15:34:00 > >

July 28, 2010

Re: [Pharo-project] Pharo 1.1/1.2 and class names in Chinese

by Alexandre Bergel

I have no idea how to help you. But trying to have classes with chinese (or any other alphabet with accents) names is important. Even though I personally write all my code in English, many like to write code in their favorite natural language. This is what I see with students for example. Cheers, Alexandre On 28 Jul 2010, at 21:33, empty wrote: > > In 1.1 and 1.2, without setting a language environment for Chinese, I am able > to use Chinese by setting fonts. It seems to work except for accepting a > class named in Chinese will end in a ClassBuilder error of 'Class names must > be capitalized'. Well is it a feature(requires language environment being > set correctly) or bug? > > The code located being: > > validateClassName: aString > "Validate the new class name" > > aString isSymbol > ifFalse: [ ^ false ]. > aString first canBeGlobalVarInitial ifFalse:[ > self error: 'Class names must be capitalized'. > ^false]. > environ at: aString ifPresent:[:old| > (old isKindOf: Behavior) ifFalse:[ > self notify: aString asText allBold, > ' already exists!\Proceed will store over it.' withCRs]]. > ^ true > > and following the code the problemic method is #canBeGlobalVarInitial: which > is found in two classes: > in EncodedCharSet class side: > canBeGlobalVarInitial: char > > | leadingChar | > leadingChar := char leadingChar. > > leadingChar = 0 ifTrue: [^ self isUppercase: char]. > ^ self isLetter: char. > > and in LanguageEnvironment > > canBeGlobalVarInitial: char > > ^ Unicode canBeGlobalVarInitial: char. > > I didn't set a Chinese environment and the exception is occured in in > EncodedCharSet class since leadingChar is 0 and a Chinese char seems thought > to be lowercased. > > > > > ----- > åç¡ä½ åç¡æ³ åç¡å§ > -- > View this message in context: http://forum.world.st/Pharo-1-1-1-2-and-class-names-in-Chinese-tp2305496p23… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 28, 2010

[Pharo-project] Pharo 1.1/1.2 and class names in Chinese

by empty

In 1.1 and 1.2, without setting a language environment for Chinese, I am able to use Chinese by setting fonts. It seems to work except for accepting a class named in Chinese will end in a ClassBuilder error of 'Class names must be capitalized'. Well is it a feature(requires language environment being set correctly) or bug? The code located being: validateClassName: aString "Validate the new class name" aString isSymbol ifFalse: [ ^ false ]. aString first canBeGlobalVarInitial ifFalse:[ self error: 'Class names must be capitalized'. ^false]. environ at: aString ifPresent:[:old| (old isKindOf: Behavior) ifFalse:[ self notify: aString asText allBold, ' already exists!\Proceed will store over it.' withCRs]]. ^ true and following the code the problemic method is #canBeGlobalVarInitial: which is found in two classes: in EncodedCharSet class side: canBeGlobalVarInitial: char | leadingChar | leadingChar := char leadingChar. leadingChar = 0 ifTrue: [^ self isUppercase: char]. ^ self isLetter: char. and in LanguageEnvironment canBeGlobalVarInitial: char ^ Unicode canBeGlobalVarInitial: char. I didn't set a Chinese environment and the exception is occured in in EncodedCharSet class since leadingChar is 0 and a Chinese char seems thought to be lowercased. ----- åç¡ä½ åç¡æ³ åç¡å§ -- View this message in context: http://forum.world.st/Pharo-1-1-1-2-and-class-names-in-Chinese-tp2305496p23… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 28, 2010

Re: [Pharo-project] help with Glamour

by Alexandre Bergel

Hi Felipe, No idea, but this is good to see you here! Alexandre On 28 Jul 2010, at 18:47, Felipe Ignacio Valverde Campos wrote: > Hi, i'm beginner on this tools, so i need your help please :) > i have some doubts about Glamour, specificaly with GLMTabulator. > > how can i set the window size ? > and how can i close it without pressing the X ? > > thanks > -- > http://www.dcc.uchile.cl/~fvalverd/public_key.asc > Estudiante de IngenierÃa Civil en ComputaciÃ³n. > Facultad de Ciencias FÃsicas y MatemÃ¡ticas. > Universidad de Chile. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 28, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo by Example on Amazon.com

by Marcus Denker

On Jul 28, 2010, at 6:56 PM, laurent laffont wrote: > On Wed, Jul 28, 2010 at 4:16 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Pharo by Example can now finally be ordered at Amazon.com: > > http://www.amazon.com/Pharo-Example-Oscar-Nierstrasz/dp/3952334146/ > > (the availability at Amazon should mean that it is orderable at any bookstore *and* orderable > for libraries world-wide). > > IMHO there should be more informations about the book on Amazon page, pictures, table of contents, bio of authors .... actually it's not very attractive.I buy most of the books on Amazon and I'm often guided by quantity and quality of informations and reviews of the books. So I think it's important. > > Is this generated automatically from Lulu or is it possible to update the page ? sadly it's automatically generated. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 28, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo by Example on Amazon.com

by laurent laffont

On Wed, Jul 28, 2010 at 4:16 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > Hi, > > Pharo by Example can now finally be ordered at Amazon.com: > > http://www.amazon.com/Pharo-Example-Oscar-Nierstrasz/dp/3952334146/ > > (the availability at Amazon should mean that it is orderable at any > bookstore *and* orderable > for libraries world-wide). > IMHO there should be more informations about the book on Amazon page, pictures, table of contents, bio of authors .... actually it's not very attractive.I buy most of the books on Amazon and I'm often guided by quantity and quality of informations and reviews of the books. So I think it's important. Is this generated automatically from Lulu or is it possible to update the page ? Anyway, the availability on Amazon is a good step forward. Cheers, Laurent > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

July 28, 2010

[Pharo-project] help with Glamour

by Felipe Ignacio Valverde Campos

Hi, i'm beginner on this tools, so i need your help please :) i have some doubts about Glamour, specificaly with GLMTabulator. how can i set the window size ? and how can i close it without pressing the X ? thanks -- http://www.dcc.uchile.cl/~fvalverd/public_key.asc Estudiante de IngenierÃa Civil en ComputaciÃ³n. Facultad de Ciencias FÃsicas y MatemÃ¡ticas. Universidad de Chile.

July 28, 2010

[Pharo-project] [ANN] Pharo by Example on Amazon.com

by Marcus Denker

Hi, Pharo by Example can now finally be ordered at Amazon.com: http://www.amazon.com/Pharo-Example-Oscar-Nierstrasz/dp/3952334146/ (the availability at Amazon should mean that it is orderable at any bookstore *and* orderable for libraries world-wide). Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 28, 2010

Re: [Pharo-project] ProcessWrapper BUGs

by Levente Uzonyi

On Wed, 28 Jul 2010, Denis Kudriashov wrote: > Hello > > I found bugs in ProcessWrapper > > try > > externalKiosk := ProcessWrapper new. > externalKiosk startWithCommand: 'notepad'. > > Do "externalKiosk terminate" twice. And image crashed without any logs Terminate is the hard way to kill a process. You don't have to use it, if your process can terminate in another way. There's a workaround for this issue in ProcessWrapperTests >> #tearDown : process isRunning ifTrue: [ process terminate ]. > > Do "externalKiosk finalize" twice.And image crashed without any logs but not > immediately. #finalize is not something that you're intended to send. It's a private method, part of the finalization logic. > > Besides I found that multiple starting and terminating ProcessWrapper and > then saving image can corrupt it. And restarting image crashed by some > failure of finalization process in ProcessWrapper plugin. (I see it in crash > log). > > I test it in Pharo 1.1 with stardart and cog VM > It works fine in Squeak trunk (at least for me). I don't know if it works in Pharo, since WeakRegistry works differently than in Squeak. Btw removing the finalization logic is a bad idea because it's totally ok to not send #terminate at all. Without proper finalization you're leaking resources (memory, semaphores, etc) in this case. Levente

July 28, 2010

Re: [Pharo-project] How to interactively add items to a tree widget?

by Rob Rothwell

Benjamin, Thanks for the encouragement! > This is probably a pretty newbie question, but can anyone point me towards > > creating some code to right click on a tree item and add a pop-up menu so > I > > can prompt for some input and create a new child of that node? > > > > > I figured out how to change the contents of the tree in UITheme > > exampleBasicControls by creating a Dictionary with some child > Dictionaries > > containing some objects, but now I seem to have a few challenges: > > > > 1. The items are not being highlighted when I click on them (they aren't > > in > > the example either). > > > > I have the same problem, so if you find how to make it works i'm listening > ^^ > I think we can learn a lot from FileList, which uses the superclass of TreeListMorph (SimpleHierarchicalListMorph). It properly highlights, and SimpleHierarchicalListMorph has a context menu as well. It's all there, I am just not that good at reading Smalltalk code in general and morphic code specifically! Also, SimpleHierarchicalListMorph submorphs example displays the same behavior we have noted, but you can see WHY since a proper selection method is not given during initialization. I'm going to try to expand the submorphs example to have the functionality that the FileList drive volume pane does, and go from there... > > > 2. I need a nudge in the right direction to capture the right click. > > > > > Maybe you should rewrite the mouseDown: method and add a test like > > event yellowButtonPressed (or the button you want) > ifTrue: [ "popup a menu" ] > We don't even need this for a popup menu...the functionality is built in, I think! > > > > > 3. If I do that and successfully add a new child to a node, I don't know > > how to tell the tree to refresh itself... > > > > > Send the message updateList to your MorphTreeMorph. If you have correctly > build your tree it works great ( but the highlighting doesn't work :s ) > I was using TreeListMorph, one of the Polymorph controls, for which you seem to specifiy a #changeSelected: method... > > > Good luck > > Benjamin > Thanks! Rob

July 28, 2010

[Pharo-project] ProcessWrapper BUGs

by Denis Kudriashov

Hello I found bugs in ProcessWrapper try externalKiosk := ProcessWrapper new. externalKiosk startWithCommand: 'notepad'. Do "externalKiosk terminate" twice. And image crashed without any logs Do "externalKiosk finalize" twice.And image crashed without any logs but not immediately. Besides I found that multiple starting and terminating ProcessWrapper and then saving image can corrupt it. And restarting image crashed by some failure of finalization process in ProcessWrapper plugin. (I see it in crash log). I test it in Pharo 1.1 with stardart and cog VM

July 28, 2010

Re: [Pharo-project] How do I enter Cyrillic letters in Pharo 1.1 / Seaside3.0rc images

by Andrey Larionov

In Pharo1.1 by default installed Bitmap fonts, which dosen't contains unicode glyphs. In preference browser you can select TrueType fonts as you like, which will correctly diaplays cyrillic glyphs. On Wed, Jul 28, 2010 at 00:17, Stanislav Paskalev <kshorg(a)gmail.com> wrote: > Hello, > Using the PBE 1.0 image, entering and displaying cyrillic characters > works fine. However in Pharo 1.1 or the seaside image, all I get are > question marks. I copied over the DejaVu fonts folder, selected > "Install bitmap DejaVu fonts", but I'm still getting ???. Â What should > I do so I can have them working ? > > Best regards, > Stanislav Paskalev > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 28, 2010

[Pharo-project] SpellChecker problem [WAS] [ANN 1.1] One-Click 1.1 release

by Mariano Martinez Peck

On Tue, Jul 27, 2010 at 5:09 AM, Serge Stinckwich < serge.stinckwich(a)gmail.com> wrote: > I added the following methods: > > RBMacSpellChecker>>primitiveSetLanguage: data > <primitive: 'primitiveSetLanguage' module: 'SpellingPlugin'> > self primitiveFailed > > RBMacSpellChecker>>primitiveGetLanguage > <primitive:'primitiveGetLanguage' module: 'SpellingPlugin'> > > self primitiveFailed > > I do not understand why : > > checker := RBMacSpellChecker new. > checker primitiveSetLanguage: 'fr'. > result := checker check: 'How are you ?'. > checker primitiveSetLanguage: 'en'. > result > > returns an OrderedCollection() > > and : > > checker := RBMacSpellChecker new. > checker primitiveSetLanguage: 'fr'. > checker primitiveGetLanguage. > result := checker check: 'How are you ?'. > checker primitiveSetLanguage: 'en'. > result > > returns the correct answer: an OrderedCollection('How' 'you') > > Any ideas ? Something wrong with the SpellingPlugin ? > > > On Mon, Jul 26, 2010 at 3:46 PM, Serge Stinckwich > <serge.stinckwich(a)gmail.com> wrote: > > On Mon, Jul 26, 2010 at 2:05 PM, Serge Stinckwich > > <serge.stinckwich(a)gmail.com> wrote: > >> 2010/7/25 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >>> > >>> > >>> On Sun, Jul 25, 2010 at 4:02 PM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: > >>>> > >>>> Hm, the link doesn't work for me. I just get an empty response... > >>>> > >>> > >>> https://gforge.inria.fr/frs/download.php/27303/Pharo-1.1-OneClick.zip > >>> > >>> works ok here > >> > >> Works ok for me also. > >> > >> 9764 tests, 9693 passes, 53 expected failures, 17 failures, 1 error > >> on Mac OS X 10.6.4. Most of the failures reported are inside > RBSpellingRuleTest. > >> Tests like: > >> > >> testPerfectSentence > >> | result | > >> result := self checker > >> check: 'This is an english sentence without problems.'. > >> self assert: result isCollection. > >> self assert: result isEmpty > >> > >> could not work on my machine, because by default i'm using the french > >> speller ... > >> I made some modifications to switch the speller to english and came > >> back to the original language after the tests. I put my modifications > >> here: http://code.google.com/p/pharo/issues/detail?id=2714 > >> > >> After that all RBSpellingRuleTest are green. > > > > Hum in fact no ... there is still some problems. > > > > -- > > Serge Stinckwich > > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > > Every DSL ends up being Smalltalk > > http://doesnotunderstand.org/ > > > > > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] Nested Configurations

by Mariano Martinez Peck

Yes, the tutorial include Project references. It is the second class. In addition, you may want to see the draft I attach of the Metacello chapter we wrote for PBE2 Feedback is welcome! mariano On Tue, Jul 27, 2010 at 10:42 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > > Good point... I've created it a critical tutorial task for it.... > > Else I forgot to say that your tutorial is very well done and quite useful. > Very good job. I should do one for Mondrian... > > Alexandre > > > > > > Dale > > > > Alexandre Bergel wrote: > >> Hi Dale, > >> I tried your tutorial some times ago. This was not featured. Maybe this > is something useful to have... > >> Cheers, > >> Alexandre > >> On 27 Jul 2010, at 21:44, Dale Henrichs wrote: > >>> Denis Kudriashov wrote: > >>>> Hello > >>>> Can I use configurations inner my configurations to set dependencies > between packages. > >>>> For example, my application depends on XmlParser. In > ConfigurationOfMyApp I need set "requires: 'XmlParser'". > >>>> But I load XmlParser to my image by ConfigurationOfXmlParser. And I > dont want inspect ConfigurationOfXmlParser to see what packages I need load > for XmlParser. > >>>> Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp? > >>> Denis, > >>> > >>> You can refer to the XML config with the following statement in your > baseline method define the project reference and the dependencies: > >>> > >>> ... > >>> spec > >>> project: 'XML Parser' with: [ > >>> spec > >>> className: 'ConfigurationOfXMLSupport'; > >>> loads: #('Core'); > >>> repository: 'http://www.squeaksource.com/MetacelloRepository' ]. > >>> ... > >>> spec package: 'myPackage' with: [ > >>> spec requires: #('XML Parser'). > >>> ... > >>> > >>> Then in your version method specify the particular version of the XML > Parser that you want to use: > >>> > >>> ... > >>> spec project: 'XML Parser' with: '1.0'. > >>> .... > >>> > >>> Dale > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] Object>>doesNotUnderstand:

by Denis Kudriashov

> > In either case control should not return to the point of error. If you > want to log errors and then continue you need to continue from some > well-defined point, not merely return control to the point of error. So if > your approach is to catch and log errors, after logging you need to transfer > control back to some starting point, e.g. by throwing some ResumeExecution > exception. > Thanks, It really work

July 27, 2010

Re: [Pharo-project] Object>>doesNotUnderstand:

by Eliot Miranda

2010/7/27 Eliot Miranda <eliot.miranda(a)gmail.com> > > > 2010/7/27 Denis Kudriashov <dionisiydk(a)gmail.com> > >> This is intentional. Martin's reply is one half of the issue, that you >>> want to be able to proceed after defining a method in the debugger. The >>> otehr half is that you want to be able to catch doesNotUnderstand: in an >>> exception handler and proceed with a result, e.g. >>> >> >> [nil zork] >> on: MessageNotUnderstood >> do: [:ex| >> ex message selector == #zork ifTrue: >> [ex resume: #ok]. >> ex pass] >> >> evaluates to #ok. >> >> >> This all work correct with ProtoObject implementation >> >> ProtoObject>>doesNotUnderstand: aMessage >> >> ^ MessageNotUnderstood new >> message: aMessage; >> receiver: self; >> signal >> > > Right, but you can't redefine and continue. The Object implementation does > both. It used to only allow redefinition, not catching. > I mean the Object implementation used to not allow catching and proceeding, only catching and aborting. cheers Eliot > >> >> 28 Ð¸ÑÐ»Ñ 2010 Ð³. 0:48:18 UTC+4 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ dionisiydk < >> dionisiydk(a)gmail.com> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: >> >> I think that the bug is that you haven't modified the system to quit on >>>> an UnhandledException. i.e. in a headless context control should never get >>>> back to the doesNotUnderstand: method if the MessageNotUnderstood exception >>>> is not caught. How should one continue after an unhandled error? >>>> >>> >>> With my approach I have "null object message eating" behavior. And when >>> any unhandled errors raised in system user will see nothing. Only log file >>> will contain it. >>> >>> 2010/7/28 Eliot Miranda <eliot.miranda(a)gmail.com> >>> >>>> >>>> >>>> 2010/7/27 Denis Kudriashov <dionisiydk(a)gmail.com> >>>> >>>> Hello, >>>>> >>>>> I found method doesNotUnderstand have very strange implementation >>>>> >>>>> Object>>doesNotUnderstand: aMessage >>>>> | exception resumeValue | >>>>> (exception := MessageNotUnderstood new) >>>>> message: aMessage; >>>>> receiver: self. >>>>> resumeValue := exception signal. >>>>> ^exception reachedDefaultHandler >>>>> ifTrue: [aMessage sentTo: self] >>>>> ifFalse: [resumeValue] >>>>> >>>>> When Error has no handlers #defaultAction is executed. For >>>>> MessageNotUnderstood #defaultAction is UnhandledError signal. And for >>>>> UnhandledError #defaultAction is opening debugger. >>>>> If you change it to do nothing (^self) you get infinite loop on any >>>>> MessageNotUnderstood signal. >>>>> It is because "ifTrue" branch executed in doesNotUnderstood method and >>>>> message resend to receiver. >>>>> >>>>> Why method implemented such way? Why it is differ from ProtoObject >>>>> implementation. I think It's bug implementation. >>>>> >>>> >>>> This is intentional. Martin's reply is one half of the issue, that you >>>> want to be able to proceed after defining a method in the debugger. The >>>> otehr half is that you want to be able to catch doesNotUnderstand: in an >>>> exception handler and proceed with a result, e.g. >>>> >>>> [nil zork] >>>> on: MessageNotUnderstood >>>> do: [:ex| >>>> ex message selector == #zork ifTrue: >>>> [ex resume: #ok]. >>>> ex pass] >>>> >>>> evaluates to #ok. >>>> >>>> >>>>> >>>>> I found this problem when I try implement stuff to turn off openning >>>>> debugger on unhandled error (and write it to log) >>>>> >>>>> UnhandledError>>defaultAction >>>>> "The current computation is terminated. The cause of the error >>>>> should be logged or reported to the user. If the program is operating in an >>>>> interactive debugging environment the computation should be suspended and >>>>> the debugger activated." >>>>> ^ToolSet debugError: exception. >>>>> >>>>> ToolSet class>>debugError: anError >>>>> "Handle an otherwise unhandled error" >>>>> self default ifNil:[ | ctx | >>>>> Smalltalk >>>>> logError: anError description >>>>> inContext: (ctx := anError signalerContext) >>>>> to: 'PharoDebug.log'. >>>>> self inform: (anError description, String cr, ctx shortStack). >>>>> ^anError return]. >>>>> ^self default debugError: anError >>>>> >>>>> I just implement subclass of StandartToolSet with empty method >>>>> #debugError:. Then I do "ToolSet default: MyToolSet". And now unhandled >>>>> errors raise infinit loop and never return. >>>>> >>>>> I fix that by: >>>>> >>>>> MyToolSet>>debugError: anError >>>>> anError class = MessageNotUnderstand ifTrue: [anError >>>>> reachedDefaultHandler: true]. >>>>> >>>>> I think this is hack. But it is work. No errors show to user.And all >>>>> work good. >>>>> >>>>> What do you think? >>>>> >>>> >>>> I think that the bug is that you haven't modified the system to quit on >>>> an UnhandledException. i.e. in a headless context control should never get >>>> back to the doesNotUnderstand: method if the MessageNotUnderstood exception >>>> is not caught. How should one continue after an unhandled error? >>>> >>>> HTH >>>> Eliot >>>> >>>> >>>>> Best regards, >>>>> Denis >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >

July 27, 2010

Re: [Pharo-project] Object>>doesNotUnderstand:

by Eliot Miranda

2010/7/27 Denis Kudriashov <dionisiydk(a)gmail.com> > This is intentional. Martin's reply is one half of the issue, that you >> want to be able to proceed after defining a method in the debugger. The >> otehr half is that you want to be able to catch doesNotUnderstand: in an >> exception handler and proceed with a result, e.g. >> > > [nil zork] > on: MessageNotUnderstood > do: [:ex| > ex message selector == #zork ifTrue: > [ex resume: #ok]. > ex pass] > > evaluates to #ok. > > > This all work correct with ProtoObject implementation > > ProtoObject>>doesNotUnderstand: aMessage > > ^ MessageNotUnderstood new > message: aMessage; > receiver: self; > signal > Right, but you can't redefine and continue. The Object implementation does both. It used to only allow redefinition, not catching. > > 28 Ð¸ÑÐ»Ñ 2010 Ð³. 0:48:18 UTC+4 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ dionisiydk < > dionisiydk(a)gmail.com> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: > > I think that the bug is that you haven't modified the system to quit on an >>> UnhandledException. i.e. in a headless context control should never get >>> back to the doesNotUnderstand: method if the MessageNotUnderstood exception >>> is not caught. How should one continue after an unhandled error? >>> >> >> With my approach I have "null object message eating" behavior. And when >> any unhandled errors raised in system user will see nothing. Only log file >> will contain it. >> >> 2010/7/28 Eliot Miranda <eliot.miranda(a)gmail.com> >> >>> >>> >>> 2010/7/27 Denis Kudriashov <dionisiydk(a)gmail.com> >>> >>> Hello, >>>> >>>> I found method doesNotUnderstand have very strange implementation >>>> >>>> Object>>doesNotUnderstand: aMessage >>>> | exception resumeValue | >>>> (exception := MessageNotUnderstood new) >>>> message: aMessage; >>>> receiver: self. >>>> resumeValue := exception signal. >>>> ^exception reachedDefaultHandler >>>> ifTrue: [aMessage sentTo: self] >>>> ifFalse: [resumeValue] >>>> >>>> When Error has no handlers #defaultAction is executed. For >>>> MessageNotUnderstood #defaultAction is UnhandledError signal. And for >>>> UnhandledError #defaultAction is opening debugger. >>>> If you change it to do nothing (^self) you get infinite loop on any >>>> MessageNotUnderstood signal. >>>> It is because "ifTrue" branch executed in doesNotUnderstood method and >>>> message resend to receiver. >>>> >>>> Why method implemented such way? Why it is differ from ProtoObject >>>> implementation. I think It's bug implementation. >>>> >>> >>> This is intentional. Martin's reply is one half of the issue, that you >>> want to be able to proceed after defining a method in the debugger. The >>> otehr half is that you want to be able to catch doesNotUnderstand: in an >>> exception handler and proceed with a result, e.g. >>> >>> [nil zork] >>> on: MessageNotUnderstood >>> do: [:ex| >>> ex message selector == #zork ifTrue: >>> [ex resume: #ok]. >>> ex pass] >>> >>> evaluates to #ok. >>> >>> >>>> >>>> I found this problem when I try implement stuff to turn off openning >>>> debugger on unhandled error (and write it to log) >>>> >>>> UnhandledError>>defaultAction >>>> "The current computation is terminated. The cause of the error >>>> should be logged or reported to the user. If the program is operating in an >>>> interactive debugging environment the computation should be suspended and >>>> the debugger activated." >>>> ^ToolSet debugError: exception. >>>> >>>> ToolSet class>>debugError: anError >>>> "Handle an otherwise unhandled error" >>>> self default ifNil:[ | ctx | >>>> Smalltalk >>>> logError: anError description >>>> inContext: (ctx := anError signalerContext) >>>> to: 'PharoDebug.log'. >>>> self inform: (anError description, String cr, ctx shortStack). >>>> ^anError return]. >>>> ^self default debugError: anError >>>> >>>> I just implement subclass of StandartToolSet with empty method >>>> #debugError:. Then I do "ToolSet default: MyToolSet". And now unhandled >>>> errors raise infinit loop and never return. >>>> >>>> I fix that by: >>>> >>>> MyToolSet>>debugError: anError >>>> anError class = MessageNotUnderstand ifTrue: [anError >>>> reachedDefaultHandler: true]. >>>> >>>> I think this is hack. But it is work. No errors show to user.And all >>>> work good. >>>> >>>> What do you think? >>>> >>> >>> I think that the bug is that you haven't modified the system to quit on >>> an UnhandledException. i.e. in a headless context control should never get >>> back to the doesNotUnderstand: method if the MessageNotUnderstood exception >>> is not caught. How should one continue after an unhandled error? >>> >>> HTH >>> Eliot >>> >>> >>>> Best regards, >>>> Denis >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] Object>>doesNotUnderstand:

by Denis Kudriashov

> > This is intentional. Martin's reply is one half of the issue, that you > want to be able to proceed after defining a method in the debugger. The > otehr half is that you want to be able to catch doesNotUnderstand: in an > exception handler and proceed with a result, e.g. > [nil zork] on: MessageNotUnderstood do: [:ex| ex message selector == #zork ifTrue: [ex resume: #ok]. ex pass] evaluates to #ok. This all work correct with ProtoObject implementation ProtoObject>>doesNotUnderstand: aMessage ^ MessageNotUnderstood new message: aMessage; receiver: self; signal 28 Ð¸ÑÐ»Ñ 2010 Ð³. 0:48:18 UTC+4 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ dionisiydk <dionisiydk(a)gmail.com>Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: > I think that the bug is that you haven't modified the system to quit on an >> UnhandledException. i.e. in a headless context control should never get >> back to the doesNotUnderstand: method if the MessageNotUnderstood exception >> is not caught. How should one continue after an unhandled error? >> > > With my approach I have "null object message eating" behavior. And when any > unhandled errors raised in system user will see nothing. Only log file will > contain it. > > 2010/7/28 Eliot Miranda <eliot.miranda(a)gmail.com> > >> >> >> 2010/7/27 Denis Kudriashov <dionisiydk(a)gmail.com> >> >> Hello, >>> >>> I found method doesNotUnderstand have very strange implementation >>> >>> Object>>doesNotUnderstand: aMessage >>> | exception resumeValue | >>> (exception := MessageNotUnderstood new) >>> message: aMessage; >>> receiver: self. >>> resumeValue := exception signal. >>> ^exception reachedDefaultHandler >>> ifTrue: [aMessage sentTo: self] >>> ifFalse: [resumeValue] >>> >>> When Error has no handlers #defaultAction is executed. For >>> MessageNotUnderstood #defaultAction is UnhandledError signal. And for >>> UnhandledError #defaultAction is opening debugger. >>> If you change it to do nothing (^self) you get infinite loop on any >>> MessageNotUnderstood signal. >>> It is because "ifTrue" branch executed in doesNotUnderstood method and >>> message resend to receiver. >>> >>> Why method implemented such way? Why it is differ from ProtoObject >>> implementation. I think It's bug implementation. >>> >> >> This is intentional. Martin's reply is one half of the issue, that you >> want to be able to proceed after defining a method in the debugger. The >> otehr half is that you want to be able to catch doesNotUnderstand: in an >> exception handler and proceed with a result, e.g. >> >> [nil zork] >> on: MessageNotUnderstood >> do: [:ex| >> ex message selector == #zork ifTrue: >> [ex resume: #ok]. >> ex pass] >> >> evaluates to #ok. >> >> >>> >>> I found this problem when I try implement stuff to turn off openning >>> debugger on unhandled error (and write it to log) >>> >>> UnhandledError>>defaultAction >>> "The current computation is terminated. The cause of the error should >>> be logged or reported to the user. If the program is operating in an >>> interactive debugging environment the computation should be suspended and >>> the debugger activated." >>> ^ToolSet debugError: exception. >>> >>> ToolSet class>>debugError: anError >>> "Handle an otherwise unhandled error" >>> self default ifNil:[ | ctx | >>> Smalltalk >>> logError: anError description >>> inContext: (ctx := anError signalerContext) >>> to: 'PharoDebug.log'. >>> self inform: (anError description, String cr, ctx shortStack). >>> ^anError return]. >>> ^self default debugError: anError >>> >>> I just implement subclass of StandartToolSet with empty method >>> #debugError:. Then I do "ToolSet default: MyToolSet". And now unhandled >>> errors raise infinit loop and never return. >>> >>> I fix that by: >>> >>> MyToolSet>>debugError: anError >>> anError class = MessageNotUnderstand ifTrue: [anError >>> reachedDefaultHandler: true]. >>> >>> I think this is hack. But it is work. No errors show to user.And all work >>> good. >>> >>> What do you think? >>> >> >> I think that the bug is that you haven't modified the system to quit on an >> UnhandledException. i.e. in a headless context control should never get >> back to the doesNotUnderstand: method if the MessageNotUnderstood exception >> is not caught. How should one continue after an unhandled error? >> >> HTH >> Eliot >> >> >>> Best regards, >>> Denis >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >

July 27, 2010

Re: [Pharo-project] Object>>doesNotUnderstand:

by Eliot Miranda

2010/7/27 Denis Kudriashov <dionisiydk(a)gmail.com> > I think that the bug is that you haven't modified the system to quit on an >> UnhandledException. i.e. in a headless context control should never get >> back to the doesNotUnderstand: method if the MessageNotUnderstood exception >> is not caught. How should one continue after an unhandled error? >> > > With my approach I have "null object message eating" behavior. And when any > unhandled errors raised in system user will see nothing. Only log file will > contain it. > In either case control should not return to the point of error. If you want to log errors and then continue you need to continue from some well-defined point, not merely return control to the point of error. So if your approach is to catch and log errors, after logging you need to transfer control back to some starting point, e.g. by throwing some ResumeExecution exception. HTH Eliot > 2010/7/28 Eliot Miranda <eliot.miranda(a)gmail.com> > > >> >> 2010/7/27 Denis Kudriashov <dionisiydk(a)gmail.com> >> >> Hello, >>> >>> I found method doesNotUnderstand have very strange implementation >>> >>> Object>>doesNotUnderstand: aMessage >>> | exception resumeValue | >>> (exception := MessageNotUnderstood new) >>> message: aMessage; >>> receiver: self. >>> resumeValue := exception signal. >>> ^exception reachedDefaultHandler >>> ifTrue: [aMessage sentTo: self] >>> ifFalse: [resumeValue] >>> >>> When Error has no handlers #defaultAction is executed. For >>> MessageNotUnderstood #defaultAction is UnhandledError signal. And for >>> UnhandledError #defaultAction is opening debugger. >>> If you change it to do nothing (^self) you get infinite loop on any >>> MessageNotUnderstood signal. >>> It is because "ifTrue" branch executed in doesNotUnderstood method and >>> message resend to receiver. >>> >>> Why method implemented such way? Why it is differ from ProtoObject >>> implementation. I think It's bug implementation. >>> >> >> This is intentional. Martin's reply is one half of the issue, that you >> want to be able to proceed after defining a method in the debugger. The >> otehr half is that you want to be able to catch doesNotUnderstand: in an >> exception handler and proceed with a result, e.g. >> >> [nil zork] >> on: MessageNotUnderstood >> do: [:ex| >> ex message selector == #zork ifTrue: >> [ex resume: #ok]. >> ex pass] >> >> evaluates to #ok. >> >> >>> >>> I found this problem when I try implement stuff to turn off openning >>> debugger on unhandled error (and write it to log) >>> >>> UnhandledError>>defaultAction >>> "The current computation is terminated. The cause of the error should >>> be logged or reported to the user. If the program is operating in an >>> interactive debugging environment the computation should be suspended and >>> the debugger activated." >>> ^ToolSet debugError: exception. >>> >>> ToolSet class>>debugError: anError >>> "Handle an otherwise unhandled error" >>> self default ifNil:[ | ctx | >>> Smalltalk >>> logError: anError description >>> inContext: (ctx := anError signalerContext) >>> to: 'PharoDebug.log'. >>> self inform: (anError description, String cr, ctx shortStack). >>> ^anError return]. >>> ^self default debugError: anError >>> >>> I just implement subclass of StandartToolSet with empty method >>> #debugError:. Then I do "ToolSet default: MyToolSet". And now unhandled >>> errors raise infinit loop and never return. >>> >>> I fix that by: >>> >>> MyToolSet>>debugError: anError >>> anError class = MessageNotUnderstand ifTrue: [anError >>> reachedDefaultHandler: true]. >>> >>> I think this is hack. But it is work. No errors show to user.And all work >>> good. >>> >>> What do you think? >>> >> >> I think that the bug is that you haven't modified the system to quit on an >> UnhandledException. i.e. in a headless context control should never get >> back to the doesNotUnderstand: method if the MessageNotUnderstood exception >> is not caught. How should one continue after an unhandled error? >> >> HTH >> Eliot >> >> >>> Best regards, >>> Denis >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] Object>>doesNotUnderstand:

by Denis Kudriashov

> > I think that the bug is that you haven't modified the system to quit on an > UnhandledException. i.e. in a headless context control should never get > back to the doesNotUnderstand: method if the MessageNotUnderstood exception > is not caught. How should one continue after an unhandled error? > With my approach I have "null object message eating" behavior. And when any unhandled errors raised in system user will see nothing. Only log file will contain it. 2010/7/28 Eliot Miranda <eliot.miranda(a)gmail.com> > > > 2010/7/27 Denis Kudriashov <dionisiydk(a)gmail.com> > > Hello, >> >> I found method doesNotUnderstand have very strange implementation >> >> Object>>doesNotUnderstand: aMessage >> | exception resumeValue | >> (exception := MessageNotUnderstood new) >> message: aMessage; >> receiver: self. >> resumeValue := exception signal. >> ^exception reachedDefaultHandler >> ifTrue: [aMessage sentTo: self] >> ifFalse: [resumeValue] >> >> When Error has no handlers #defaultAction is executed. For >> MessageNotUnderstood #defaultAction is UnhandledError signal. And for >> UnhandledError #defaultAction is opening debugger. >> If you change it to do nothing (^self) you get infinite loop on any >> MessageNotUnderstood signal. >> It is because "ifTrue" branch executed in doesNotUnderstood method and >> message resend to receiver. >> >> Why method implemented such way? Why it is differ from ProtoObject >> implementation. I think It's bug implementation. >> > > This is intentional. Martin's reply is one half of the issue, that you > want to be able to proceed after defining a method in the debugger. The > otehr half is that you want to be able to catch doesNotUnderstand: in an > exception handler and proceed with a result, e.g. > > [nil zork] > on: MessageNotUnderstood > do: [:ex| > ex message selector == #zork ifTrue: > [ex resume: #ok]. > ex pass] > > evaluates to #ok. > > >> >> I found this problem when I try implement stuff to turn off openning >> debugger on unhandled error (and write it to log) >> >> UnhandledError>>defaultAction >> "The current computation is terminated. The cause of the error should >> be logged or reported to the user. If the program is operating in an >> interactive debugging environment the computation should be suspended and >> the debugger activated." >> ^ToolSet debugError: exception. >> >> ToolSet class>>debugError: anError >> "Handle an otherwise unhandled error" >> self default ifNil:[ | ctx | >> Smalltalk >> logError: anError description >> inContext: (ctx := anError signalerContext) >> to: 'PharoDebug.log'. >> self inform: (anError description, String cr, ctx shortStack). >> ^anError return]. >> ^self default debugError: anError >> >> I just implement subclass of StandartToolSet with empty method >> #debugError:. Then I do "ToolSet default: MyToolSet". And now unhandled >> errors raise infinit loop and never return. >> >> I fix that by: >> >> MyToolSet>>debugError: anError >> anError class = MessageNotUnderstand ifTrue: [anError >> reachedDefaultHandler: true]. >> >> I think this is hack. But it is work. No errors show to user.And all work >> good. >> >> What do you think? >> > > I think that the bug is that you haven't modified the system to quit on an > UnhandledException. i.e. in a headless context control should never get > back to the doesNotUnderstand: method if the MessageNotUnderstood exception > is not caught. How should one continue after an unhandled error? > > HTH > Eliot > > >> Best regards, >> Denis >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] Nested Configurations

by Alexandre Bergel

> Good point... I've created it a critical tutorial task for it.... Else I forgot to say that your tutorial is very well done and quite useful. Very good job. I should do one for Mondrian... Alexandre > > Dale > > Alexandre Bergel wrote: >> Hi Dale, >> I tried your tutorial some times ago. This was not featured. Maybe this is something useful to have... >> Cheers, >> Alexandre >> On 27 Jul 2010, at 21:44, Dale Henrichs wrote: >>> Denis Kudriashov wrote: >>>> Hello >>>> Can I use configurations inner my configurations to set dependencies between packages. >>>> For example, my application depends on XmlParser. In ConfigurationOfMyApp I need set "requires: 'XmlParser'". >>>> But I load XmlParser to my image by ConfigurationOfXmlParser. And I dont want inspect ConfigurationOfXmlParser to see what packages I need load for XmlParser. >>>> Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp? >>> Denis, >>> >>> You can refer to the XML config with the following statement in your baseline method define the project reference and the dependencies: >>> >>> ... >>> spec >>> project: 'XML Parser' with: [ >>> spec >>> className: 'ConfigurationOfXMLSupport'; >>> loads: #('Core'); >>> repository: 'http://www.squeaksource.com/MetacelloRepository' ]. >>> ... >>> spec package: 'myPackage' with: [ >>> spec requires: #('XML Parser'). >>> ... >>> >>> Then in your version method specify the particular version of the XML Parser that you want to use: >>> >>> ... >>> spec project: 'XML Parser' with: '1.0'. >>> .... >>> >>> Dale >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 27, 2010

Re: [Pharo-project] Nested Configurations

by Dale Henrichs

Good point... I've created it a critical tutorial task for it.... Dale Alexandre Bergel wrote: > Hi Dale, > > I tried your tutorial some times ago. This was not featured. Maybe this is something useful to have... > > Cheers, > Alexandre > > > On 27 Jul 2010, at 21:44, Dale Henrichs wrote: > >> Denis Kudriashov wrote: >>> Hello >>> Can I use configurations inner my configurations to set dependencies between packages. >>> For example, my application depends on XmlParser. In ConfigurationOfMyApp I need set "requires: 'XmlParser'". >>> But I load XmlParser to my image by ConfigurationOfXmlParser. And I dont want inspect ConfigurationOfXmlParser to see what packages I need load for XmlParser. >>> Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp? >> Denis, >> >> You can refer to the XML config with the following statement in your baseline method define the project reference and the dependencies: >> >> ... >> spec >> project: 'XML Parser' with: [ >> spec >> className: 'ConfigurationOfXMLSupport'; >> loads: #('Core'); >> repository: 'http://www.squeaksource.com/MetacelloRepository' ]. >> ... >> spec package: 'myPackage' with: [ >> spec requires: #('XML Parser'). >> ... >> >> Then in your version method specify the particular version of the XML Parser that you want to use: >> >> ... >> spec project: 'XML Parser' with: '1.0'. >> .... >> >> Dale >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

[Pharo-project] How do I enter Cyrillic letters in Pharo 1.1 / Seaside3.0rc images

by Stanislav Paskalev

Hello, Using the PBE 1.0 image, entering and displaying cyrillic characters works fine. However in Pharo 1.1 or the seaside image, all I get are question marks. I copied over the DejaVu fonts folder, selected "Install bitmap DejaVu fonts", but I'm still getting ???. What should I do so I can have them working ? Best regards, Stanislav Paskalev

July 27, 2010

Re: [Pharo-project] Object>>doesNotUnderstand:

by Eliot Miranda

2010/7/27 Denis Kudriashov <dionisiydk(a)gmail.com> > Hello, > > I found method doesNotUnderstand have very strange implementation > > Object>>doesNotUnderstand: aMessage > | exception resumeValue | > (exception := MessageNotUnderstood new) > message: aMessage; > receiver: self. > resumeValue := exception signal. > ^exception reachedDefaultHandler > ifTrue: [aMessage sentTo: self] > ifFalse: [resumeValue] > > When Error has no handlers #defaultAction is executed. For > MessageNotUnderstood #defaultAction is UnhandledError signal. And for > UnhandledError #defaultAction is opening debugger. > If you change it to do nothing (^self) you get infinite loop on any > MessageNotUnderstood signal. > It is because "ifTrue" branch executed in doesNotUnderstood method and > message resend to receiver. > > Why method implemented such way? Why it is differ from ProtoObject > implementation. I think It's bug implementation. > This is intentional. Martin's reply is one half of the issue, that you want to be able to proceed after defining a method in the debugger. The otehr half is that you want to be able to catch doesNotUnderstand: in an exception handler and proceed with a result, e.g. [nil zork] on: MessageNotUnderstood do: [:ex| ex message selector == #zork ifTrue: [ex resume: #ok]. ex pass] evaluates to #ok. > > I found this problem when I try implement stuff to turn off openning > debugger on unhandled error (and write it to log) > > UnhandledError>>defaultAction > "The current computation is terminated. The cause of the error should > be logged or reported to the user. If the program is operating in an > interactive debugging environment the computation should be suspended and > the debugger activated." > ^ToolSet debugError: exception. > > ToolSet class>>debugError: anError > "Handle an otherwise unhandled error" > self default ifNil:[ | ctx | > Smalltalk > logError: anError description > inContext: (ctx := anError signalerContext) > to: 'PharoDebug.log'. > self inform: (anError description, String cr, ctx shortStack). > ^anError return]. > ^self default debugError: anError > > I just implement subclass of StandartToolSet with empty method > #debugError:. Then I do "ToolSet default: MyToolSet". And now unhandled > errors raise infinit loop and never return. > > I fix that by: > > MyToolSet>>debugError: anError > anError class = MessageNotUnderstand ifTrue: [anError > reachedDefaultHandler: true]. > > I think this is hack. But it is work. No errors show to user.And all work > good. > > What do you think? > I think that the bug is that you haven't modified the system to quit on an UnhandledException. i.e. in a headless context control should never get back to the doesNotUnderstand: method if the MessageNotUnderstood exception is not caught. How should one continue after an unhandled error? HTH Eliot > Best regards, > Denis > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] Nested Configurations

by Alexandre Bergel

Hi Dale, I tried your tutorial some times ago. This was not featured. Maybe this is something useful to have... Cheers, Alexandre On 27 Jul 2010, at 21:44, Dale Henrichs wrote: > Denis Kudriashov wrote: >> Hello >> Can I use configurations inner my configurations to set dependencies between packages. >> For example, my application depends on XmlParser. In ConfigurationOfMyApp I need set "requires: 'XmlParser'". >> But I load XmlParser to my image by ConfigurationOfXmlParser. And I dont want inspect ConfigurationOfXmlParser to see what packages I need load for XmlParser. >> Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp? > Denis, > > You can refer to the XML config with the following statement in your baseline method define the project reference and the dependencies: > > ... > spec > project: 'XML Parser' with: [ > spec > className: 'ConfigurationOfXMLSupport'; > loads: #('Core'); > repository: 'http://www.squeaksource.com/MetacelloRepository' ]. > ... > spec package: 'myPackage' with: [ > spec requires: #('XML Parser'). > ... > > Then in your version method specify the particular version of the XML Parser that you want to use: > > ... > spec project: 'XML Parser' with: '1.0'. > .... > > Dale > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 27, 2010

Re: [Pharo-project] Object>>doesNotUnderstand:

by Martin McClure

On 07/27/2010 12:21 PM, Denis Kudriashov wrote: > Hello, > > I found method doesNotUnderstand have very strange implementation > [...] > > When Error has no handlers #defaultAction is executed. For > MessageNotUnderstood #defaultAction is UnhandledError signal. And for > UnhandledError #defaultAction is opening debugger. > If you change it to do nothing (^self) you get infinite loop on any > MessageNotUnderstood signal. > It is because "ifTrue" branch executed in doesNotUnderstood method and > message resend to receiver. > > Why method implemented such way? Why it is differ from ProtoObject > implementation. I think It's bug implementation. It's this way so that in development when you hit a MNU the debugger opens, you can define the missing method, hit proceed in the debugger, and it retries the send. It's not the best implementation for allowing the debugger to be turned off in production like you're doing. Regards, -Martin

July 27, 2010

Re: [Pharo-project] Nested Configurations

by Denis Kudriashov

Thank you very much :)) 2010/7/27 Dale Henrichs <dhenrich(a)vmware.com> > Denis Kudriashov wrote: > >> Hello >> >> Can I use configurations inner my configurations to set dependencies >> between packages. >> >> For example, my application depends on XmlParser. In ConfigurationOfMyApp >> I need set "requires: 'XmlParser'". >> But I load XmlParser to my image by ConfigurationOfXmlParser. And I dont >> want inspect ConfigurationOfXmlParser to see what packages I need load for >> XmlParser. >> Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp? >> >> >> >> Denis, > > You can refer to the XML config with the following statement in your > baseline method define the project reference and the dependencies: > > ... > spec > project: 'XML Parser' with: [ > spec > className: 'ConfigurationOfXMLSupport'; > loads: #('Core'); > repository: 'http://www.squeaksource.com/MetacelloRepository' ]. > ... > spec package: 'myPackage' with: [ > spec requires: #('XML Parser'). > ... > > Then in your version method specify the particular version of the XML > Parser that you want to use: > > ... > spec project: 'XML Parser' with: '1.0'. > .... > > Dale > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] Nested Configurations

by Dale Henrichs

Denis Kudriashov wrote: > Hello > > Can I use configurations inner my configurations to set dependencies between packages. > > For example, my application depends on XmlParser. In ConfigurationOfMyApp I need set "requires: 'XmlParser'". > But I load XmlParser to my image by ConfigurationOfXmlParser. And I dont want inspect ConfigurationOfXmlParser to see what packages I need load for XmlParser. > Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp? > > > Denis, You can refer to the XML config with the following statement in your baseline method define the project reference and the dependencies: ... spec project: 'XML Parser' with: [ spec className: 'ConfigurationOfXMLSupport'; loads: #('Core'); repository: 'http://www.squeaksource.com/MetacelloRepository' ]. ... spec package: 'myPackage' with: [ spec requires: #('XML Parser'). ... Then in your version method specify the particular version of the XML Parser that you want to use: ... spec project: 'XML Parser' with: '1.0'. .... Dale

July 27, 2010

[Pharo-project] Nested Configurations

by Denis Kudriashov

Hello Can I use configurations inner my configurations to set dependencies between packages. For example, my application depends on XmlParser. In ConfigurationOfMyApp I need set "requires: 'XmlParser'". But I load XmlParser to my image by ConfigurationOfXmlParser. And I dont want inspect ConfigurationOfXmlParser to see what packages I need load for XmlParser. Can I refer to ConfigurationOfXmlParser in ConfigurationOfMyApp?

July 27, 2010

[Pharo-project] Object>>doesNotUnderstand:

by Denis Kudriashov

Hello, I found method doesNotUnderstand have very strange implementation Object>>doesNotUnderstand: aMessage | exception resumeValue | (exception := MessageNotUnderstood new) message: aMessage; receiver: self. resumeValue := exception signal. ^exception reachedDefaultHandler ifTrue: [aMessage sentTo: self] ifFalse: [resumeValue] When Error has no handlers #defaultAction is executed. For MessageNotUnderstood #defaultAction is UnhandledError signal. And for UnhandledError #defaultAction is opening debugger. If you change it to do nothing (^self) you get infinite loop on any MessageNotUnderstood signal. It is because "ifTrue" branch executed in doesNotUnderstood method and message resend to receiver. Why method implemented such way? Why it is differ from ProtoObject implementation. I think It's bug implementation. I found this problem when I try implement stuff to turn off openning debugger on unhandled error (and write it to log) UnhandledError>>defaultAction "The current computation is terminated. The cause of the error should be logged or reported to the user. If the program is operating in an interactive debugging environment the computation should be suspended and the debugger activated." ^ToolSet debugError: exception. ToolSet class>>debugError: anError "Handle an otherwise unhandled error" self default ifNil:[ | ctx | Smalltalk logError: anError description inContext: (ctx := anError signalerContext) to: 'PharoDebug.log'. self inform: (anError description, String cr, ctx shortStack). ^anError return]. ^self default debugError: anError I just implement subclass of StandartToolSet with empty method #debugError:. Then I do "ToolSet default: MyToolSet". And now unhandled errors raise infinit loop and never return. I fix that by: MyToolSet>>debugError: anError anError class = MessageNotUnderstand ifTrue: [anError reachedDefaultHandler: true]. I think this is hack. But it is work. No errors show to user.And all work good. What do you think? Best regards, Denis

July 27, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.1 released

by Johan Fabry

Congrats and thanks to all involved! On 26 Jul 2010, at 16:22, Adrian Lienhard wrote: > Hi all, > > I'm excited to announce our second release of Pharo! > > Please check out the updated website at www.pharo-project.org. > > This release contains many bug fixes, improvements, performance optimizations, and new features that didn't get into version 1.0. Specific information about what is new in this release can be found on > www.pharo-project.org/pharo-download/release-1-1. > > Thanks everyone who has contributed and helped to bring Pharo one step further! > > Please help to spread the word... > > Cheers, > Adrian > > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

July 27, 2010

Re: [Pharo-project] Pool dictionaries

by Schwab,Wilhelm K

Gary, Now THAT helped :) One caveat is that the resulting monolithic #initialize overwhelms the compiler. At least the compiler complains about it rather than silently failing. I simply broke up the source into #initialize1 and 2, and all appears to have worked. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Gary Chambers [gazzaguru2(a)btinternet.com] Sent: Tuesday, July 27, 2010 5:26 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Pool dictionaries Hi Bill, not sure of the limit, if there is one. See BalloonEngineConstants for an example (that has lots too!). Regards, Gary ----- Original Message ----- From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, July 27, 2010 2:56 AM Subject: Re: [Pharo-project] Pool dictionaries > Gary, > > I found SharedPool, but it was not clear to me how it was supposed to > work. By initializers, do you mean a class-side #initialize that sets the > values of the class variables? How many class variables can a class have? > There are quite a few constants in/for the offending gizmo =:0 I could > create multiple pools, which might make things more readable, but the real > goal is to just make it work. > > Thanks, > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr > [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Gary Chambers > [gazzaguru2(a)btinternet.com] > Sent: Monday, July 26, 2010 2:20 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Pool dictionaries > > See SharedPool and subclasses... > > No longer dictionaries as such, explained in the class comment. > > Subclass SharedPool with the name you want and add class vars and > initialisers. > > Regards, Gary > > ----- Original Message ----- > From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Monday, July 26, 2010 6:51 PM > Subject: [Pharo-project] Pool dictionaries > > >> What is the current status of pool dictionaries? I have some code that >> uses one, and for pretty good reason. What do I need to do? >> >> Bill >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 27, 2010

Re: [Pharo-project] Pool dictionaries

by Schwab,Wilhelm K

---- Wilhelm K. Schwab, Ph.D. bschwab AT anest DOT ufl DOT edu ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Gary Chambers [gazzaguru2(a)btinternet.com] Sent: Tuesday, July 27, 2010 5:26 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Pool dictionaries Hi Bill, not sure of the limit, if there is one. See BalloonEngineConstants for an example (that has lots too!). Regards, Gary ----- Original Message ----- From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, July 27, 2010 2:56 AM Subject: Re: [Pharo-project] Pool dictionaries > Gary, > > I found SharedPool, but it was not clear to me how it was supposed to > work. By initializers, do you mean a class-side #initialize that sets the > values of the class variables? How many class variables can a class have? > There are quite a few constants in/for the offending gizmo =:0 I could > create multiple pools, which might make things more readable, but the real > goal is to just make it work. > > Thanks, > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr > [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Gary Chambers > [gazzaguru2(a)btinternet.com] > Sent: Monday, July 26, 2010 2:20 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Pool dictionaries > > See SharedPool and subclasses... > > No longer dictionaries as such, explained in the class comment. > > Subclass SharedPool with the name you want and add class vars and > initialisers. > > Regards, Gary > > ----- Original Message ----- > From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Monday, July 26, 2010 6:51 PM > Subject: [Pharo-project] Pool dictionaries > > >> What is the current status of pool dictionaries? I have some code that >> uses one, and for pretty good reason. What do I need to do? >> >> Bill >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 27, 2010

[Pharo-project] Unicode characters

by Alberto Bacchelli

Hi, Are Unicode characters supported in Pharo? If so, how can I verify whether an input is an unicode character? Thank you, Alberto

July 27, 2010

[Pharo-project] [update 1.2] #12068

by Marcus Denker

12068 ----- Issue 2719: CachedBlockClosure >> value should uncache block Issue 2695: Tasklist on Mac -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 27, 2010

Re: [Pharo-project] Pool dictionaries

by Nicolas Cellier

There is no limit in the number of class variables nor the number of pool variables, not the number of globals in a namspace, they all behave like a Dictionary... The limit is on the number of literals you can embed in a method, and each shared variable (Gloabls, class varaibles and pool variables) consumes one slot. Practically you'll just need to split your initialization into several chunks MyPool>>initialize self initializeThis; initializeThat; initializeTheRest. Nicolas 2010/7/27 Gary Chambers <gazzaguru2(a)btinternet.com>: > Hi Bill, > > not sure of the limit, if there is one. > See BalloonEngineConstants for an example (that has lots too!). > > Regards, Gary > > ----- Original Message ----- From: "Schwab,Wilhelm K" > <bschwab(a)anest.ufl.edu> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, July 27, 2010 2:56 AM > Subject: Re: [Pharo-project] Pool dictionaries > > >> Gary, >> >> I found SharedPool, but it was not clear to me how it was supposed to >> work. Â By initializers, do you mean a class-side #initialize that sets the >> values of the class variables? Â How many class variables can a class have? >> There are quite a few constants in/for the offending gizmo Â =:0 Â I could >> create multiple pools, which might make things more readable, but the real >> goal is to just make it work. >> >> Thanks, >> >> Bill >> >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Gary Chambers >> [gazzaguru2(a)btinternet.com] >> Sent: Monday, July 26, 2010 2:20 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Pool dictionaries >> >> See SharedPool and subclasses... >> >> No longer dictionaries as such, explained in the class comment. >> >> Subclass SharedPool with the name you want and add class vars and >> initialisers. >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Monday, July 26, 2010 6:51 PM >> Subject: [Pharo-project] Pool dictionaries >> >> >>> What is the current status of pool dictionaries? Â I have some code that >>> uses one, and for pretty good reason. Â What do I need to do? >>> >>> Bill >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.1 released

by Richard Durr

Cool, it's so fast! :) On Tue, Jul 27, 2010 at 9:56 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Thanks for this release! > > Cheers, > Doru > > > On 27 Jul 2010, at 00:04, GermÃ¡n Arduino wrote: > >> Excellent news! >> >> Thanks by the effort to all the people involved. >> >> GermÃ¡n. >> >> 2010/7/26 Adrian Lienhard <adi(a)netstyle.ch>: >>> >>> Hi all, >>> >>> I'm excited to announce our second release of Pharo! >>> >>> Please check out the updated website at www.pharo-project.org. >>> >>> This release contains many bug fixes, improvements, performance >>> optimizations, and new features that didn't get into version 1.0. Specific >>> information about what is new in this release can be found on >>> www.pharo-project.org/pharo-download/release-1-1. >>> >>> Thanks everyone who has contributed and helped to bring Pharo one step >>> further! >>> >>> Please help to spread the word... >>> >>> Cheers, >>> Adrian >>> >>> ___________________ >>> http://www.adrian-lienhard.ch/ >>> >>> >>> _______________________________________________ >>> Pharo-users mailing list >>> Pharo-users(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >>> >> >> >> >> -- >> ================================================= >> GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino >> Arduino Software & Web Hosting http://www.arduinosoftware.com >> PasswordsPro http://www.passwordspro.com >> ================================================= >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] Pharo-project Digest, Vol 27, Issue 184

by Benjamin Van Ryseghem

Date: Mon, 26 Jul 2010 22:03:26 -0400 > From: Rob Rothwell <r.j.rothwell(a)gmail.com> > Subject: [Pharo-project] How to interactively add items to a tree > widget? > To: "Pharo-project(a)lists.gforge.inria.fr" > <pharo-project(a)lists.gforge.inria.fr> > Message-ID: > <AANLkTimBNqkvGnUMFHSqRJOJ8WqJdPwynbxCDym4AJk+(a)mail.gmail.com<AANLkTimBNqkvGnUMFHSqRJOJ8WqJdPwynbxCDym4AJk%2B(a)mail.gmail.com> > > > Content-Type: text/plain; charset="iso-8859-1" > > This is probably a pretty newbie question, but can anyone point me towards > creating some code to right click on a tree item and add a pop-up menu so I > can prompt for some input and create a new child of that node? > > I figured out how to change the contents of the tree in UITheme > exampleBasicControls by creating a Dictionary with some child Dictionaries > containing some objects, but now I seem to have a few challenges: > > 1. The items are not being highlighted when I click on them (they aren't > in > the example either). > I have the same problem, so if you find how to make it works i'm listening ^^ > 2. I need a nudge in the right direction to capture the right click. > Maybe you should rewrite the mouseDown: method and add a test like event yellowButtonPressed (or the button you want) ifTrue: [ "popup a menu" ] > 3. If I do that and successfully add a new child to a node, I don't know > how to tell the tree to refresh itself... > > Send the message updateList to your MorphTreeMorph. If you have correctly build your tree it works great ( but the highlighting doesn't work :s ) Good luck Benjamin

July 27, 2010

Re: [Pharo-project] why "maximize" does not fills all the window in1.1?

by Richard Durr

Maybe using more graphics from the Aristo-Theme could be a solution for the window-button problem? http://cappuccinotutorials.files.wordpress.com/2009/12/bildschirmfoto-2009-… On Tue, Jul 27, 2010 at 9:31 AM, Geert Claes <geert.wl.claes(a)gmail.com> wrote: > > Thanks Gary, that's great! > -- > View this message in context: http://forum.world.st/why-maximize-does-not-fills-all-the-window-in-1-1-tp2… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] [update 1.2] #12066

by Henrik Johansen

On Jul 26, 2010, at 12:46 26PM, Marcus Denker wrote: > 12066 > ----- > > Issue 2712: Once Just noticed a small inconsistency with the VW implementation, CachedBlockClosure value should revert the an uncached block, then evaluate value, rather than also return the cached value. (Issue 2719) Also, there are currently some limitations to which kinds of blocks will be cached, as per the first two comments in: http://forum.world.st/The-Trunk-Kernel-eem-474-mcz-td2299352.html#a2299352 Cheers, Henry

July 27, 2010

Re: [Pharo-project] Pool dictionaries

by Gary Chambers

Hi Bill, not sure of the limit, if there is one. See BalloonEngineConstants for an example (that has lots too!). Regards, Gary ----- Original Message ----- From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, July 27, 2010 2:56 AM Subject: Re: [Pharo-project] Pool dictionaries > Gary, > > I found SharedPool, but it was not clear to me how it was supposed to > work. By initializers, do you mean a class-side #initialize that sets the > values of the class variables? How many class variables can a class have? > There are quite a few constants in/for the offending gizmo =:0 I could > create multiple pools, which might make things more readable, but the real > goal is to just make it work. > > Thanks, > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr > [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Gary Chambers > [gazzaguru2(a)btinternet.com] > Sent: Monday, July 26, 2010 2:20 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Pool dictionaries > > See SharedPool and subclasses... > > No longer dictionaries as such, explained in the class comment. > > Subclass SharedPool with the name you want and add class vars and > initialisers. > > Regards, Gary > > ----- Original Message ----- > From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Monday, July 26, 2010 6:51 PM > Subject: [Pharo-project] Pool dictionaries > > >> What is the current status of pool dictionaries? I have some code that >> uses one, and for pretty good reason. What do I need to do? >> >> Bill >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 27, 2010

Re: [Pharo-project] [Pharo 1.1 OneClick] Errors launching the one click distrib on Linux

by Nicolas Petton

You're right, using the unzip command line works fine here too, sorry guys. Cheers, Nicolas

July 27, 2010

Re: [Pharo-project] [Pharo 1.1 OneClick] Errors launching the one click distrib on Linux

by Norbert Hartl

I can confirm that it works under linux. Tried from the commandline as well by double-clicking the shell script in the file manager. Norbert On 27.07.2010, at 10:31, Marcus Denker wrote: > > On Jul 27, 2010, at 1:08 AM, Nicolas Petton wrote: > >> Hi guys, >> >> I just tried the one click distribution on Linux. Some files seem to >> miss execution rights: >> >> pharo.sh cannot be executed >> >> $ chmod +x ./pharo.sh >> $ ./pharo.sh >> exec: 12: ./Contents/Linux/squeakvm: Permission denied >> >> easily fixed too: >> $ chmod +x ./Contents/Linux/squeakvm >> >> I don't know if this problem only happens on my system though. >> > strange... on MacOS it unpacks this zip correctly: > > Marcus-MacBook-Pro:Linux denker$ ./squeakvm -bash: ./squeakvm: cannot execute binary file > > Maybe your machine is configured to never set the x when extracting zips? > > We should check if others have the same problem. > > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 27, 2010

Re: [Pharo-project] [Pharo 1.1 OneClick] Errors launching the one click distrib on Linux

by laurent laffont

2010/7/27 Nicolas Petton <petton.nicolas(a)gmail.com> > Hi guys, > > I just tried the one click distribution on Linux. Some files seem to > miss execution rights: > > pharo.sh cannot be executed > > $ chmod +x ./pharo.sh > $ ./pharo.sh > exec: 12: ./Contents/Linux/squeakvm: Permission denied > > easily fixed too: > $ chmod +x ./Contents/Linux/squeakvm > > I don't know if this problem only happens on my system though. > It works on my Linux box. But pharo.sh is 754, so if the owner of the file is different from the account used to run pharo.sh, it doesn't work. Laurent > > Cheers, > Nico > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] [Pharo 1.1 OneClick] Errors launching the one click distrib on Linux

by Marcus Denker

On Jul 27, 2010, at 1:08 AM, Nicolas Petton wrote: > Hi guys, > > I just tried the one click distribution on Linux. Some files seem to > miss execution rights: > > pharo.sh cannot be executed > > $ chmod +x ./pharo.sh > $ ./pharo.sh > exec: 12: ./Contents/Linux/squeakvm: Permission denied > > easily fixed too: > $ chmod +x ./Contents/Linux/squeakvm > > I don't know if this problem only happens on my system though. > strange... on MacOS it unpacks this zip correctly: Marcus-MacBook-Pro:Linux denker$ ./squeakvm -bash: ./squeakvm: cannot execute binary file Maybe your machine is configured to never set the x when extracting zips? We should check if others have the same problem. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 27, 2010

Re: [Pharo-project] [ANN 1.1] One-Click 1.1 release

by Mariano Martinez Peck

https://gforge.inria.fr/frs/download.php/27303/Pharo-1.1-OneClick.zip > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 27, 2010

Re: [Pharo-project] Autotest, proof-of-concept [was: About TDD and Pharo]

by Alexandre Bergel

> Indeed I also want to log for each test: > - min / max / mean execution time > - time to first failure > - % of errors/failures/success > - run count That would be cool > so with these datas we know long tests. I think about wrapping run test methods with an object which then can collect these datas. Would you go this way ? > (Another way is to modify TestResult / TestCase, but it's more intrusive). Over the last few month I intensively used method wrapper (a.k.a object as compiled method). Time to time, the image just freezes or crashes. Maybe due to the garbage collector. Modifying SUnit should not be that complex. It would be nice to turn SUnit into something more extensible. One shoot two targets. > I also think that execution time is not the only criteria. For example, Autotest can have a "feedback deadline" of 2 seconds. That means it can run: > - 2 tests of 1 second > - 20 tests of 100 ms > So knowing execution times, Autotest can run as many tests as it can, starting from fastest to lowest. It seems that JUnitMax do this way. Method consumption as well. A test that is fast to execute but require a lot of memory becomes slow. Alexandre > > > Laurent Laffont > > http://pharocasts.blogspot.com/ > http://magaloma.blogspot.com/ > > > > Cheers, > Alexandre > > > On 26 Jul 2010, at 07:44, laurent laffont wrote: > > > > > On Sat, Jul 24, 2010 at 10:16 AM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > I have been using Autotest for a while already. I greatly reduce the window switching. This is cool. > > However, I have to disable Autotest when the tests take time to execute. > > > > > > An idea is to be able to tag tests with pragmas to put them in categories. So we can have a LongRunning category which is not run by default. Like NUnit (http://www.nunit.org/index.php?p=category&r=2.2) > > > > Then SUnit could be enhanced to show these categories. Useful to quickly select all tests related to a project for example; or run only performance tests. > > > > > > How would you name the tag ? Where the implementation should go ? (TestCase ?) > > > > > > Laurent. > > > > > > Alexandre > > > > > > On 15 Jun 2010, at 21:41, laurent laffont wrote: > > > > > Hi Alexandre, > > > > > > I've reorganized Autotest to write tests. The tests now run in a thread with lower priority. Thanks for feedback. > > > > > > Cheers, > > > > > > Laurent Laffont > > > > > > http://pharocasts.blogspot.com/ > > > http://magaloma.blogspot.com/ > > > > > > > > > On Mon, Jun 14, 2010 at 4:52 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > > Hi Laurent, > > > > > > I tried to program while having AutoTest running. > > > More importantly than the interface, I experienced some problem with long executing tests. Basically, these tests should not be executed while I am programming. Or at least in a thread of a lesser priority. Am I the only one to experience this? > > > > > > Cheers, > > > Alexandre > > > > > > > > > On 11 Jun 2010, at 09:02, laurent laffont wrote: > > > > > > > On Fri, Jun 11, 2010 at 2:29 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > > > Hi Laurent, > > > > > > > > I like Autotest. It is true that I always execute the test after modifying it. > > > > There are three horizontal panes. Why so? Is it just to open a debugger when necessary? > > > > > > > > I want to be able to open a debugger from autotest. I agree the GUI is crap now. > > > > > > > > > > > > We could imagine one standalone button instead with a green color to say the test I just edited is green, and yellow or red when it fails. In that case, clicking on the button open a debugger. > > > > > > > > I just feel the window of autotest takes a lot of space in the screen, without having a real benefit. > > > > > > > > Yes it's true. I'm still thinking on a good GUI. But I'm learning how to make GUI now :) > > > > > > > > If you look at Autotest package, AutotestView is just the GUI, so we can implement several GUI and see the best solution. I need to take the time to do it, repository is read / write so feel free to commit :) > > > > > > > > What I want to have is a dashboard docked on one side of the screen which acts like you're driving a car. It's always visible, you have to be able to look quickly at it as when you check the speed of your car, adjust your drive, .... > > > > > > > > Also another problem with the current version if that if a test fails, change it and fails again, you don't see it has run (nothing moves in the GUI). > > > > > > > > Finally, another problem is that you see that a test has failed, but you don't know why (SUnit TestRunner has the same problem). I want to display the exception message too. > > > > > > > > Thanks a lot for feedback. > > > > > > > > Laurent Laffont > > > > > > > > http://pharocasts.blogspot.com/ > > > > http://magaloma.blogspot.com/ > > > > > > > > > > > > > > > > Cheers, > > > > Alexandre > > > > > > > > > > > > On 3 Jun 2010, at 17:11, laurent laffont wrote: > > > > > > > > > Hi, > > > > > > > > > > I've written a proof-of-concept for Autotest. Draft/crappy code and no tests (exploration mode :) but it loads on PharoCore-1.1-11383-beta image. > > > > > > > > > > Load it: > > > > > Gofer new > > > > > squeaksource: 'Autotest'; > > > > > package: 'Autotest'; > > > > > load > > > > > > > > > > Open it: > > > > > AutotestView open > > > > > (there's en entry in WorldMenu > Tools) > > > > > > > > > > And change a tested method to see the results. > > > > > > > > > > There's a bug I need to find, maybe someone knows: > > > > > - Change Bag>>occurrencesOf: > > > > > - Autotest gives: > > > > > > > > > > 284 run, 281 passes, 0 expected failures, 1 failures, 2 errors, 0 unexpected passes > > > > > Failures: > > > > > CollectionRootTest>>#test0FixtureIterateTest > > > > > > > > > > Errors: > > > > > CollectionRootTest>>#testBasicCollect > > > > > CollectionRootTest>>#testDoWithout > > > > > > > > > > but in SUnit CollectionRootTest gives > > > > > 0 run, 0 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes ?? > > > > > > > > > > > > > > > Cheers, > > > > > > > > > > Laurent Laffont > > > > > > > > > > http://pharocasts.blogspot.com/ > > > > > http://magaloma.blogspot.com/ > > > > > > > > > > > > > > > On Thu, Jun 3, 2010 at 6:09 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > > > > The idea is excellent. > > > > > > > > > > Cheers, > > > > > Alexandre > > > > > > > > > > > > > > > On 3 Jun 2010, at 10:22, laurent laffont wrote: > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jun 3, 2010 at 3:42 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > > > > > > You may have a lot of noise. > > > > > > > > > > > > > > I guess that Ruby uses files as a unit of development/deployment. The closest Smalltalk/Pharo has is the class and the package. > > > > > > > > > > > > > > I would suggest that TestCase which would use this feature use some pragma/method to identify/declare which classes/packages this test depends upon. Then the "autotest" framework would register such tests and listen for changes in the given classes/packages, launching required tests whenever a change happen. > > > > > > > > > > > > > > Additionally, one could declare such a pragma on a single test method, when this test should be run for a specific class. > > > > > > > > > > > > > > Of course, you also to take care of long running tests, which you probably want to exclude from auto-testing. > > > > > > > > > > > > I see autotest in Pharo in a slighly different way: When I press save in the Monticello browser, I have a popup menu which asks me whether (i) I want to run all the tests or (ii) only the tests that cover that I changed from the last version. > > > > > > > > > > > > Does this make sense? > > > > > > > > > > > > Please no popup :) What I like in ruby autotest is that I can quickly look at test results if I want (or not) without stop writing. Often you want to see your tests failing, as you type / save code. I don't have to stop writing, click a button, wait test results, go again.... testing is done in background and I just see notifications whether it's OK or not. > > > > > > > > > > > > So test log in a Transcript is OK for me. > > > > > > > > > > > > > > > > > > For autotest unit of work is file: it runs the test file which has the same name as the code file, but you can customize this behavior. For autotest-rails: > > > > > > "A simplified version of Autotest heuristics in this mode would be: > > > > > > When changing a test file, only this file is run (e.g. test/unit/foo_test.rb âtest/unit/foo_test.rb). > > > > > > When changing a model file, only associated unit test file is run (e.g.app/models/foo.rb â test/unit/foo_test.rb). > > > > > > When changing a controller file, associated functional test file is run (e.g.app/controllers/foo_controller.rb âtest/functional/foo_controller_test.rb). > > > > > > When changing a fixture file, associated unit test and functional test are run (e.g.app/fixtures/foos.yml â test/unit/foo_test.rb +test/functional/foo_controller_test.rb). > > > > > > When changing a helper file, associated functional test file is run (e.g.app/helpers/foo_helper.rb âtest/functional/foo_controller_test.rb). > > > > > > When changing application_helper.rb file all functional test files are run (e.g.application_helper.rb â test/functional/*_test.rb). > > > > > > When changing a file under the config directory, all tests are run." > > > > > > > > > > > > Laurent > > > > > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > Alexandre > > > > > > -- > > > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > > > Alexandre Bergel http://www.bergel.eu > > > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Pharo-project mailing list > > > > > > Pharo-project(a)lists.gforge.inria.fr > > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > > > > > _______________________________________________ > > > > > > Pharo-project mailing list > > > > > > Pharo-project(a)lists.gforge.inria.fr > > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > > > -- > > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > > Alexandre Bergel http://www.bergel.eu > > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Pharo-project mailing list > > > > > Pharo-project(a)lists.gforge.inria.fr > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > > > _______________________________________________ > > > > > Pharo-project mailing list > > > > > Pharo-project(a)lists.gforge.inria.fr > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > -- > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > Alexandre Bergel http://www.bergel.eu > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Pharo-project mailing list > > > > Pharo-project(a)lists.gforge.inria.fr > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > _______________________________________________ > > > > Pharo-project mailing list > > > > Pharo-project(a)lists.gforge.inria.fr > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > Alexandre Bergel http://www.bergel.eu > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 27, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.1 released

by Tudor Girba

Thanks for this release! Cheers, Doru On 27 Jul 2010, at 00:04, GermÃ¡n Arduino wrote: > Excellent news! > > Thanks by the effort to all the people involved. > > GermÃ¡n. > > 2010/7/26 Adrian Lienhard <adi(a)netstyle.ch>: >> Hi all, >> >> I'm excited to announce our second release of Pharo! >> >> Please check out the updated website at www.pharo-project.org. >> >> This release contains many bug fixes, improvements, performance >> optimizations, and new features that didn't get into version 1.0. >> Specific information about what is new in this release can be found >> on >> www.pharo-project.org/pharo-download/release-1-1. >> >> Thanks everyone who has contributed and helped to bring Pharo one >> step further! >> >> Please help to spread the word... >> >> Cheers, >> Adrian >> >> ___________________ >> http://www.adrian-lienhard.ch/ >> >> >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> > > > > -- > ================================================= > GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino > Arduino Software & Web Hosting http://www.arduinosoftware.com > PasswordsPro http://www.passwordspro.com > ================================================= > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

July 27, 2010

[Pharo-project] [update 1.2] #12067

by Marcus Denker

12067 ----- Issue 670: should clean Morph menu Issue 2716: New graphics for mouse over on window controls -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 27, 2010