- Pharo-dev - lists.pharo.org

[Pharo-project] New packages to include in PharoDev 1.1
by Torsten Bergmann May 13, 2010

May 13, 2010

If you load "ScriptManager-Help-tbn.1.mcz" from http://www.squeaksource.com/ScriptManager afterwards and reopen the HelpBrowser you will also get a short introduction to ScriptManager. It's not yet in the ConfigurationOfHelpSystem. Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

1 0

[Pharo-project] New packages to include in PharoDev 1.1
by Mariano Martinez Peck May 12, 2010

May 12, 2010

Hi folks. We need to think if we want new packages for PharoDev 1.1. For the moment, we think in adding: - Packages from http://www.squeaksource.com/PharoNonCorePackages - ScriptManager - WorkingSet or Algernon - I don't agree, but people wanted also FFI - ProfStefBrowser In PharoDev 1.0 we assure all tests were green. Now we want the same. Some of the above packages not even have tests or have failing/error. Some of them, not even load in Pharo 1.1 because of the underscore assignment. Ok, this can be easily fixed. The same with the TheWorldMenu and Preferences, etc... I will be clear: I am asking you your opinion, but we need someone to do it. If everybody want, but nobody do, those packages won't be included. is there something else you think it should be added ? Cheers Mariano

2 1

[Pharo-project] Newbie: How to load and use HTTP parser
by Andrei Stebakov May 12, 2010

May 12, 2010

Hi Sent this message to the Pharo-users group, but no response for a couple of days, so trying it here ;) I have a simple task of parsing some html content in Pharo (loading an html page using HTTPSocket and retrieving useful info from it). Having browsed for an html parser in my current one-click Pharo 1.0 image, I couldn't find one. How do I find/download a (the) HTML parser? What's the general routine of discovering and installing packages in Pharo? I believe in Squeak there was a menu to explore and download packages, I couldn't find it in Pharo though. Thank you, Andrei

6 8

[Pharo-project] I would like to kill some tests
by StÃ©phane Ducasse May 12, 2010

May 12, 2010

Hi I would like to kill some tests that do not really make the system better. testMetaclassSuperclass "self run: #testMetaclassSuperclass" self assert: Dictionary class superclass == Set class. self assert: OrderedCollection class superclass == SequenceableCollection class. testSuperclass "self run: #testSuperclass" | s | self assert: Dictionary superclass == Set. self assert: OrderedCollection superclass == SequenceableCollection. s := OrderedCollection new. s add: SequenceableCollection. s add: Collection. s add: Object. s add: ProtoObject. self assert: OrderedCollection allSuperclasses = s. let me know what you think. Stef

4 6

[Pharo-project] new gettext package
by Hilaire Fernandes May 12, 2010

May 12, 2010

I have uploaded a new version of the gettext package. I have removed a few classes used for the itnernal translator. So now, only gettext based catalog messages is used. Philipp, I have added a String>>translateTo: aLocale you can used from Seaside application. If we agree on that protocole, we can have in Pharo-Cire two String messages defined as follow: String>>translated "answer the receiver translated to the default language" ^ NaturalLanguageTranslator translate: self String>>translatedTo: localeID "answer the receiver translated to the given locale id" ^ NaturalLanguageTranslator translate: self toLocale: localeID Then a dummy class NaturalLanguageTranslator withn two class messages: NaturalLanguageTranslator class>>translate: aString ^ aString NaturalLanguageTranslator class>>translate: aString toLocale: localeID ^ aString NaturalLanguageTranslator class is redefined in the Gettext package. It should be possible to simplify the whole protocole after removing the LanguageEditor. This one is totaly unused, and it does not make sense to me to use Smalltalk to translated string, there are better third party tool to do that. Can I remove the LanguageEditor? Hilaire

3 3

[Pharo-project] rename a symbol
by Sean Allen May 12, 2010

May 12, 2010

is there a way to do a refactoring that takes all instances of a symbol and renames them? So if I had a symbol #Foo in a method, rename it and all other uses of #Foo to #Bar.

2 1

[Pharo-project] Issue 2420 and fix in inbox (alain can you check?)
by Mariano Martinez Peck May 12, 2010

May 12, 2010

Alain: we should check if these problem is not present in another place. Fix in Inbox: Name: Morphic-MarianoMartinezPeck.584 Author: MarianoMartinezPeck Time: 12 May 2010, 7:42:50 pm UUID: 33b351fa-fc71-4ae1-8e7b-019570597208 Ancestors: Morphic-StephaneDucasse.583 Fix to issue Issue 2420 WorldState >> mostUsedToolsOn: is hardcoded to use StandardToolSet. When using another ToolSet, like the case of the Dev image, the most used tools still uses StandardToolSet instead of DEVToolSet. It need to be changed to use "ToolSet default" instead.

1 0

Re: [Pharo-project] DEVImageCreator >> setDefaultPreferences (alain?)
by Mariano Martinez Peck May 12, 2010

May 12, 2010

On Tue, May 11, 2010 at 1:55 PM, Alain Plantec <alain.plantec(a)free.fr>wrote: > Hi Mariano, all > Le 11/05/2010 11:43, Mariano Martinez Peck a Ã©crit : > > Hi Alain. DEVImageCreator has to be updated to use the new preferences. I >> can do it but it will require much more than for me than for you ;) >> >> For preferences it is DEVImageCreator >> setDefaultPreferences >> it is using Preferences class for the moment. It should be updated to use >> Settings, isn't it ? >> > I don't think so. There is no need for such a initialization anymore since > package are defining their own preferences. > If a default value is desired then it should be set by an initialization > method or lazily by the getter. > I find the lazy initialization better because then, the SettingBrowser can > reset the preference to the default by setting it to nil. > > But maybe the default value in the "PharoCore" is not the same as PharoDev? I mean, suppose these are the default prefrences we used in the pharo dev images: setDefaultPreferences. Preferences disable: #annotationPanes; disable: #allwaysShowVScrollBar; enable: #alternativeButtonsInScrollBars; disable: #fadedBackgroundWindows; enable: #fastDragWindowForMorphic; disable: #fullScreenLeavesDeskMargins; enable: #generalizedYellowButtonMenu; enable: #mouseClickForKeyboardFocus; enable: #noWindowAnimationForClosing; disable: #scrollBarsNarrow; disable: #scrollBarsWithoutMenuButton; disable: #showSplitterHandles; disable: #syntaxHighlightingAsYouTypeAnsiAssignment; enable: #showTextEditingState; disable: #windowAnimation; setPreference: #GlyphContrast toValue: 55; disable: #roundedWindowCorners; disable: #roundedMenuCorners; enable: #infiniteUndo; enable: #useUndo; enable: #mercuryPanel; disable: #showUpdateOptionInWorldMenu. If we used to do this, I guess it was becuase most of the default preferences of the core image was different. Otherwise, this method doesn't have sense. If I now do what you say, I am changing the default value of the pharo core image also. Is this correct ? or this should be only one flavor (PharoDev) ? Anyway, suppose I want to do the same as above, I should do something like: Preferences infiniteUndoSetting: true; etc.... Similar happens with external packages. Suppose OB developers (Lukas?) doesn't want to have mercury bar enable by default, but us (in PharoDev) we DO want it. Then I need to set such preference. Maybe the name default looks bad for you. It should be "preferences for PharoDev image" > BTW, Preferences is still present in Pharo 1.1 and thus, >> setDefaultPreferences is still working but I guess it should be updated. >> > why ? there is no need for setDefaultPreferences anymore. > > >> Do you know when Preferences class will be completely removed? Pharo 1.2? >> > I don't know. Maybe we can let it in the 1.1 in order > to let maintainers the possibility to port their packages and > definitively remove it in 1.2. > I agree, 1.2. > The same for TheWorldMenu I guess. > ok Cheers Mariano > Cheers > Alain > > >> Thanks! >> >> Mariano >> > >

3 8

[Pharo-project] Issue 2418 and fix in inbox
by Mariano Martinez Peck May 12, 2010

May 12, 2010

http://code.google.com/p/pharo/issues/detail?id=2418 Fix is in inbox: Name: System-Tools-MarianoMartinezPeck.30 Author: MarianoMartinezPeck Time: 12 May 2010, 12:22:36 pm UUID: 4785af6c-1ebe-487d-af22-2640e763e9f5 Ancestors: System-Tools-StephaneDucasse.29 Fix to issue 2418 <http://code.google.com/p/pharo/issues/detail?id=2418>: Now MethodContext can be taken into account in SpaceTally as MethodContext allInstancesDo: is working again.

1 0

[Pharo-project] Issue 2124
by Luc Fabresse May 12, 2010

May 12, 2010

SLICE-BadCharactersInPackagenames-fix2124-LucFabresse.1 fix 2124 : add a TestCase ensuring that existing package name do not contain \ / : * ? " < > | Another fix should prevent the creation of package names with bad characters Luc

1 0