April 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Gettext in Pharo2.0

by Marcus Denker

On Apr 2, 2013, at 6:34 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Johan Brichau-2 wrote >> Hi, >> >> Loading Gettext into Pharo2.0 crashes badly (system locks up, eventually >> an emergency debugger appears). >> The reason is the class initialization of NaturalLanguageTranslator: >> >> Smalltalk addToStartUpList: NaturalLanguageTranslator after: >> FileDirectory. >> >> Because the class FileDirectory is no longer in that list, it crashes. >> So, my questions: >> >> - should it not produce a nicer debugger window? >> - I can fix the load problem itself and also take a look to port this >> package to Pharo2.0 if it requires more than adapting the above. But I >> have no write access to the PharoNonCorePackages repository. Is there a >> new location? Or is there already a version for Pharo2.0 somewhere? Or >> should we move it out of that repository and give it it's own special >> place? >> >> cheers >> Johan > > I think Gettext should be in its own place, and I don't think there is one > for it yet. I think Gettext that worked in 1.3 also doesn't work in Pharo > 1.4, which I could look at fixing. Or if it does work in 1.4 let me know > how to load it. > I wonder if it should not be part of the releaseâ¦ having the system in multiple languages seems to be not that of a seldomly used feature. Marcus

April 2, 2013

Re: [Pharo-project] Gettext in Pharo2.0

by Paul DeBruicker

Johan Brichau-2 wrote > Hi, > > Loading Gettext into Pharo2.0 crashes badly (system locks up, eventually > an emergency debugger appears). > The reason is the class initialization of NaturalLanguageTranslator: > > Smalltalk addToStartUpList: NaturalLanguageTranslator after: > FileDirectory. > > Because the class FileDirectory is no longer in that list, it crashes. > So, my questions: > > - should it not produce a nicer debugger window? > - I can fix the load problem itself and also take a look to port this > package to Pharo2.0 if it requires more than adapting the above. But I > have no write access to the PharoNonCorePackages repository. Is there a > new location? Or is there already a version for Pharo2.0 somewhere? Or > should we move it out of that repository and give it it's own special > place? > > cheers > Johan I think Gettext should be in its own place, and I don't think there is one for it yet. I think Gettext that worked in 1.3 also doesn't work in Pharo 1.4, which I could look at fixing. Or if it does work in 1.4 let me know how to load it. I made some slime rules for Seaside that run in Pharo 1.3 that automatically find strings and adds the conversion stuff if those strings aren't in methods that end in 'Id' or 'Css' or 'Class' (etc). I'd publish them to a Gettext repository if there was one. -- View this message in context: http://forum.world.st/Gettext-in-Pharo2-0-tp4679315p4679321.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 2, 2013

[Pharo-project] Gettext in Pharo2.0

by Johan Brichau

Hi, Loading Gettext into Pharo2.0 crashes badly (system locks up, eventually an emergency debugger appears). The reason is the class initialization of NaturalLanguageTranslator: Smalltalk addToStartUpList: NaturalLanguageTranslator after: FileDirectory. Because the class FileDirectory is no longer in that list, it crashes. So, my questions: - should it not produce a nicer debugger window? - I can fix the load problem itself and also take a look to port this package to Pharo2.0 if it requires more than adapting the above. But I have no write access to the PharoNonCorePackages repository. Is there a new location? Or is there already a version for Pharo2.0 somewhere? Or should we move it out of that repository and give it it's own special place? cheers Johan

April 2, 2013

Re: [Pharo-project] [Pharo-users] SLOC in Smalltalk

by Marcus Denker

On Apr 2, 2013, at 4:54 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Hi Janko. Thanks for your useful package. > > Apparently there is some issue with #linesOfCode. The dummy expression below return 5 instead of 4 in Pharo 1.4 and 2 because is counting the autogenerated 'DoIt' selector. > > (UndefinedObject evaluatorClass new > compileNoPattern: '| oc | > oc := OrderedCollection new: 20. > oc add: 1. > oc size' > in: UndefinedObject > context: nil > notifying: nil > ifFail: []) generate linesOfCode Hello, I do not think that this is wrong. The doit *does* contain a selector. if #linesOfCode would contain a special case for doits, it would be inconsistent. E.g. print this: thisContext method sourceCode --> 'DoIt ^ thisContext method sourceCode' There is a Doit. There is even a return in the that is generatedâ¦ and the doit is actually pretty-printed: thisContext method linesOfCode --> 2 So in short: dots are special, there is no need to change #linesOfCode, as there is no thinkable change that would make any sense. In general, LOC as a metric is not that good. It is better than nothing, but it makes more sense to count e.g. message sends or use more advanced metrics on the AST (not every statement adds the same to complexity, e.g. conditionals versus simple statements). Marcus

April 2, 2013

Re: [Pharo-project] new Pharo 2.0 version

by Esteban Lorenzano

it is semantics. is the release, but is 2.0.596... why? because mark the version as 2.0.1 would be horrible pain (yep, it is a hand made process)... so, for now, we are ok like that :) Esteban On Apr 2, 2013, at 3:10 PM, Ben Coman <btc(a)openInWorld.com> wrote: > Esteban Lorenzano wrote: >> Hi, >> >> I made some changes in the Pharo 2.0 release (can be called 2.0.1, but well... it is 2.0.596. in fact :) >> 1) Nautilus keybindings settings are now the old ones by default (asked by Stef) >> 2) Backported the fix that prevents that load FFI crashes image (thanks to Guille) >> 3) Backported the platform versions (thanks to... well, myself :) >> >> Now, there is a problem with the page because the big "Download" button still points to the portable version, but well... nothing is perfect in life :) >> >> enjoy, >> Esteban >> >> >> >> > cool. > For me 2.0.1 would be the "release" while 20596 would be the "build number". Its useful to have these as distinct concepts. > > cheers -ben >

April 2, 2013

Re: [Pharo-project] new Pharo 2.0 version

by Ben Coman

Esteban Lorenzano wrote: > Hi, > > I made some changes in the Pharo 2.0 release (can be called 2.0.1, but well... it is 2.0.596. in fact :) > > 1) Nautilus keybindings settings are now the old ones by default (asked by Stef) > 2) Backported the fix that prevents that load FFI crashes image (thanks to Guille) > 3) Backported the platform versions (thanks to... well, myself :) > > Now, there is a problem with the page because the big "Download" button still points to the portable version, but well... nothing is perfect in life :) > > enjoy, > Esteban > > > > cool. For me 2.0.1 would be the "release" while 20596 would be the "build number". Its useful to have these as distinct concepts. cheers -ben

April 2, 2013

Re: [Pharo-project] How to define a ConfigurationOf with a #development version that depends on a baseline?

by Tobias Pape

Am 02.04.2013 um 13:15 schrieb Damien Cassou <damien.cassou(a)gmail.com>: > http://stackoverflow.com/questions/15762706/how-to-define-a-configurationof… http://stackoverflow.com/a/15763244/1197440

April 2, 2013

[Pharo-project] new Pharo 2.0 version

by Esteban Lorenzano

Hi, I made some changes in the Pharo 2.0 release (can be called 2.0.1, but well... it is 2.0.596. in fact :) 1) Nautilus keybindings settings are now the old ones by default (asked by Stef) 2) Backported the fix that prevents that load FFI crashes image (thanks to Guille) 3) Backported the platform versions (thanks to... well, myself :) Now, there is a problem with the page because the big "Download" button still points to the portable version, but well... nothing is perfect in life :) enjoy, Esteban

April 2, 2013

[Pharo-project] How to define a ConfigurationOf with a #development version that depends on a baseline?

by Damien Cassou

http://stackoverflow.com/questions/15762706/how-to-define-a-configurationof… -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 2, 2013

[Pharo-project] [update 2.0] #20596

by Esteban Lorenzano

20596 ----- Prepared for updated release (yep, Stef asked for some special changes... and since he is the boss... :) Esteban

April 2, 2013