September 2014 - Pharo-users

Re: [Pharo-users] not a smalltalk!

by Norbert Hartl

> Am 15.09.2014 um 23:54 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > >> On 15 Sep 2014, at 23:47, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> Uko2 wrote >>> about pharo not being a smalltalk... is it true? >> >> Oh goodie... it's been a few weeks and I've been craving one of these >> threads ;) > > Actually, we were not talking about this at all when you were gone, it always starts when you are around ;-) Where's the like button? :)

Sept. 16, 2014

Re: [Pharo-users] [ANN] Easy I18N for Pharo

by Tudor Girba

Nice job! And nice doc! Thank you. Doru On Mon, Sep 15, 2014 at 11:18 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > I just refer to my original announcement: "Need an EASY translation > framework for your Pharo application with NO EXTERNAL dependency?" > > That's it. Nothing fancy. Nothing more. Only a simple project. You can - > but must > not use it and I did not announce it as a GetText replacement. ;) > > With "I18N" there is no need to externally set up other tools, by default > no playing > with files. One can manage and version the translation with the code. It > is open to > the format and I do not have to reinstall external tools when I switch > between > computers. Start up Pharo and off I go. But this is specific to me and > maybe > different for others. > > If it gets complicated one can always switch to GetText or other > solutions. Look at the > webframeworks - we have Teapot, Aida, Seaside, ... so let the users decide > what > he wants to use. > > And GetText is not the only format. Look at Java - there you have messages > and > message property files or *.resx from .NET world. In I18N I can use them > as source as well > if I like and they are also not uncommon in translation (offices) and have > nice > tool support too. > > Hilaire wrote: > >For DrGeo this is a show stopper. > > As I said it depends on the needs and you may be right for Dr. Geo (or > other > Pharo based applications). > > From the discussion I think we can agree that it would be good to also > have good > Pharo support for GetText. And then lets talk about the IMHO currently > horrible > state of GetText and how to fix it: > > 1. Why is "GetText" not easily loadable from the config browser? If we > want people to find and use it we should make it accessible. > > 2. When you google for "Pharo" and "GetText" you will find > https://code.google.com/p/seaside/wiki/Gettext as the first match. > > The page is outdated, points to the old repository on SqueakSource > http://www.squeaksource.com/PharoNonCorePackages/ and even that > page does not include a hint that meanwhile the package moved to STHub. > > 3. Also the new hosting on the STHub page > http://smalltalkhub.com/#!/~PharoExtras/Gettext > seems broken, it includes the following comment: > > "Migrated from PharoNonCorePackages. Should be adapted to Pharo2.0" > > Outdated comment or not usable in Pharo 3.0/4.0? > > 4. The last version there is Gettext-HilaireFernandes.33, that is the one > that is > also included in Dr. Geo. The code should be updated as > > a) it includes a reference to missing class "MethodReference" in > #appendVocabulary:domains: > b) the NaturalLanguageTranslator>>cleanUp method references a class > variable that is not there > > Any takers? > > 5. Writing a simple docu for I18N on STHub took me only a few minutes > using markdown and > https://stackedit.io. (Pillar and PillarHub provide the same, but > STHub does not support it). > > So why not write a similar docu for GetText including code snippets > and all the knowledge that > seems to be there already from using it... > > Bye > T. > > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 16, 2014

Re: [Pharo-users] Zoomable & Infinitely scrollable PasteupMorph

by Alexandre Bergel

Hi! Can you describe a bit more what you need? In Roassal, you do not have submorph, but do you really need them? Alexandre > Le 15-09-2014 Ã 20:18, "Sean P. DeNigris" <sean(a)clipperadams.com> a Ã©crit : > > Sean P. DeNigris wrote >> I see the GT playground seems to have something like this for the Roassal >> previews... > > Although digging a bit, I see that the sub-objects are not true Morphs, so > it seems that particular approach is not applicable... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Zoomable-Infinitely-scrollable-PasteupMorph-tp4778229… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Sept. 16, 2014

Re: [Pharo-users] Zoomable & Infinitely scrollable PasteupMorph

by Sean P. DeNigris

Sean P. DeNigris wrote > I see the GT playground seems to have something like this for the Roassal > previews... Although digging a bit, I see that the sub-objects are not true Morphs, so it seems that particular approach is not applicable... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Zoomable-Infinitely-scrollable-PasteupMorph-tp4778229… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 16, 2014

Zoomable & Infinitely scrollable PasteupMorph

by Sean P. DeNigris

I need to create such a beast. What is my best bet to build on top of? I see the GT playground seems to have something like this for the Roassal previews... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Zoomable-Infinitely-scrollable-PasteupMorph-tp4778229… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 16, 2014

Recursive #printOn: renders the image unusable

by Esteban A. Maringolo

Today I made the mistake (twice) of developing in the debugger a #printOn: method depending on a not yet defined #name method in the same class. The result is an image completely blocked out, with an infinite recursion trying to print receiver The culprit is Object>>#name, which by default... is the receiver printString (bypassing the #printStringLimitedTo:... version)! So if you implement #printOn: depending on #name, but you didn't implement #name differently to how Object does, you created yourself an infinite recursion. Now I found why it is happening, so I will explicitly define #name prior to any #printOn: implementation. Particularly if I'm inside the debugger which will try to print the offending class or any variable affected by this bug. However I have a few questions about this: a) Shouldn't a recursion too deep be detected? b) Why can't I interrupt a process running in the UI thread like this one? Regards. Esteban A. Maringolo The call stack: DTColumnParameter(Object)>>printOn: DTColumnParameter>>printOn: DTColumnParameter(Object)>>printStringLimitedTo: in Block: [ :s | self printOn: s ] String class(SequenceableCollection class)>>streamContents:limitedTo: DTColumnParameter(Object)>>printStringLimitedTo: DTColumnParameter(Object)>>printString DTColumnParameter(Object)>>name <<---- Here we go... DTColumnParameter>>printOn: DTColumnParameter(Object)>>printStringLimitedTo: in Block: [ :s | self printOn: s ] String class(SequenceableCollection class)>>streamContents:limitedTo: DTColumnParameter(Object)>>printStringLimitedTo: DTColumnParameter(Object)>>printString DTColumnParameter(Object)>>name

Sept. 15, 2014

Re: [Pharo-users] not a smalltalk!

by kilon alios

nuke it from orbit only way to be sure , this and "smalltalk is dead" On Tue, Sep 16, 2014 at 12:54 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 15 Sep 2014, at 23:47, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > Uko2 wrote > >> about pharo not being a smalltalk... is it true? > > > > Oh goodie... it's been a few weeks and I've been craving one of these > > threads ;) > > Actually, we were not talking about this at all when you were gone, it > always starts when you are around ;-) >

Sept. 15, 2014

Re: [Pharo-users] not a smalltalk!

by Sven Van Caekenberghe

On 15 Sep 2014, at 23:47, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Uko2 wrote >> about pharo not being a smalltalk... is it true? > > Oh goodie... it's been a few weeks and I've been craving one of these > threads ;) Actually, we were not talking about this at all when you were gone, it always starts when you are around ;-)

Sept. 15, 2014

Re: [Pharo-users] not a smalltalk!

by Sean P. DeNigris

Uko2 wrote > about pharo not being a smalltalk... is it true? Oh goodie... it's been a few weeks and I've been craving one of these threads ;) ----- Cheers, Sean -- View this message in context: http://forum.world.st/not-a-smalltalk-tp4776586p4778202.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 15, 2014

[ANN] Easy I18N for Pharo

by Torsten Bergmann

I just refer to my original announcement: "Need an EASY translation framework for your Pharo application with NO EXTERNAL dependency?" That's it. Nothing fancy. Nothing more. Only a simple project. You can - but must not use it and I did not announce it as a GetText replacement. ;) With "I18N" there is no need to externally set up other tools, by default no playing with files. One can manage and version the translation with the code. It is open to the format and I do not have to reinstall external tools when I switch between computers. Start up Pharo and off I go. But this is specific to me and maybe different for others. If it gets complicated one can always switch to GetText or other solutions. Look at the webframeworks - we have Teapot, Aida, Seaside, ... so let the users decide what he wants to use. And GetText is not the only format. Look at Java - there you have messages and message property files or *.resx from .NET world. In I18N I can use them as source as well if I like and they are also not uncommon in translation (offices) and have nice tool support too. Hilaire wrote: >For DrGeo this is a show stopper. As I said it depends on the needs and you may be right for Dr. Geo (or other Pharo based applications). >From the discussion I think we can agree that it would be good to also have good Pharo support for GetText. And then lets talk about the IMHO currently horrible state of GetText and how to fix it: 1. Why is "GetText" not easily loadable from the config browser? If we want people to find and use it we should make it accessible. 2. When you google for "Pharo" and "GetText" you will find https://code.google.com/p/seaside/wiki/Gettext as the first match. The page is outdated, points to the old repository on SqueakSource http://www.squeaksource.com/PharoNonCorePackages/ and even that page does not include a hint that meanwhile the package moved to STHub. 3. Also the new hosting on the STHub page http://smalltalkhub.com/#!/~PharoExtras/Gettext seems broken, it includes the following comment: "Migrated from PharoNonCorePackages. Should be adapted to Pharo2.0" Outdated comment or not usable in Pharo 3.0/4.0? 4. The last version there is Gettext-HilaireFernandes.33, that is the one that is also included in Dr. Geo. The code should be updated as a) it includes a reference to missing class "MethodReference" in #appendVocabulary:domains: b) the NaturalLanguageTranslator>>cleanUp method references a class variable that is not there Any takers? 5. Writing a simple docu for I18N on STHub took me only a few minutes using markdown and https://stackedit.io. (Pillar and PillarHub provide the same, but STHub does not support it). So why not write a similar docu for GetText including code snippets and all the knowledge that seems to be there already from using it... Bye T.

Sept. 15, 2014