- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Trie in Pharo

by Stephan Eggermont

Ok, thanks, that makes thing clear. Stephan

July 25, 2014

[Tip] Image init scripts when working with PharoLauncher

by Torsten Bergmann

PharoLauncher [1] allows you to work with many Pharo images. You can download fresh images, clone existing ones and with its access to the Pharo CI it allows you to easily reproduce errors in specific Pharo image versions. I REALLY like this tool when working with Pharo. There is a customizable hardware key on my laptop that I can just press to open PharoLauncher, manage and launch the images and dive into the world of Pharo. To optimize my Pharo "easy access workflows" further I wanted all the images that I started with PharoLauncher: - to share a common metacello repository cache (where all the mcz are stored independent from image location) for faster loading - to have the possibility to preset the Squeaksource, SS3 and STHub password already - to set my authors name All this is already explained in Marianos blog posts [2] and [3] and the PharoEnterprise book [4]. Nonetheless I would like to share the script that I personally use. Maybe (in an adopted version) it is usefull for other PharoLauncher users as well: ===================================================================== COMMON SETTINGS FOR ALL PHARO IMAGES WHEN STARTED USING PHAROLAUNCHER ===================================================================== Open any Pharo 3.0/4.0 image and execute StartupPreferencesLoader preferencesGeneralFolder fullName in a workspace to find out the common preferences folder on your local machine. You can put a Smalltalk script into this folder, for instance "initAllImages.st" that is evaluated each time an image runs. I've found the following script very useful: ----------------------------------------------------------------- | sharedPackageCacheDirectory | "Never apply to PharoLauncher itself" (SmalltalkImage current imageName includesSubstring: 'Launcher') ifTrue: [ ^self ]. "ask if script should be applied" (UIManager default confirm: 'Apply init script from ', StartupPreferencesLoader preferencesGeneralFolder fullName,' to image') ifFalse: [^self ]. "Use a shared package cache to store Monticello MCS files for all images" sharedPackageCacheDirectory := 'C:\Pharo\commonpackage-cache' asFileReference ensureCreateDirectory; yourself. MCCacheRepository default directory: sharedPackageCacheDirectory. "Set password for Squeaksource" (MCRepositoryGroup default repositories select: [:each | (each isKindOf: MCHttpRepository) and: [((each locationWithTrailingSlash includesSubstring: 'www.squeaksource.com') or: [each locationWithTrailingSlash includesSubstring: 'http://ss3.gemstone.com/ss/'])] ]) do: [:each | each user: 'squeaksourceuser'; password: 'secretsqueaksourcepassword']. "Set password for SmalltalkHub (hub and HTTP repos)" (MCRepositoryGroup default repositories select: [:each | (each isKindOf: MCSmalltalkhubRepository) and: [each locationWithTrailingSlash includesSubstring: 'smalltalkhub.com'] ]) do: [:each | each user: 'PharoUser'; password: 'sthubpassword']. (MCRepositoryGroup default repositories select: [:each | (each isKindOf: MCHttpRepository) and: [each locationWithTrailingSlash includesSubstring: 'smalltalkhub.com'] ]) do: [:each | each user: 'PharoUser'; password: 'sthubpassword']. "Set author name" Author fullName: 'PharoUser'. UIManager default inform: 'Script applied'. ----------------------------------------------------------------- Hope it is usefull for others too. Bye T. [1] http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher [2] http://marianopeck.wordpress.com/2012/05/19/pharo-tips-and-tricks/ [3] http://marianopeck.wordpress.com/2012/05/12/startuploader-running-startup-s… [4] https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Startup…

July 25, 2014

Re: [Pharo-dev] Trie in Pharo

by Marcus Denker

On 25 Jul 2014, at 13:03, Ben Coman <btc(a)openInWorld.com> wrote: > Marcus Denker wrote: >> >> On 25 Jul 2014, at 12:39, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >>> I have mentioned this before, but EyeCollectionInspector is actually written against SequenceableCollection since it expects ordered external integer indexing. That is why currently every Collection subclass without this protocol and/or without a custom inspector fails. >>> >>> The alternative would be to move Collection class>>#inspectorClass to SequenceableCollection>>#inspectorClass. Then Collection subclasses that are not SequenceableCollection and that do not have a custom inspector will fail. >>> >>> Note that fail means a fall back to EyeBasicInspector. >>> >>> >> >> I did that change in 4.0 (with the mistake of putting #inspectorClass on the instance side of SequenceableCollection, I will fix that soon) >> >> Marcus >> >> > > So EyeCollectionInspector should be called EyeSequenceableCollectionInspector ? yesâ¦ if it only works for those it needs to make it clear. Marcus

July 25, 2014

Re: [Pharo-dev] Trie in Pharo

by Ben Coman

July 25, 2014

Re: [Pharo-dev] Trie in Pharo

by Sven Van Caekenberghe

On 25 Jul 2014, at 12:55, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 25 Jul 2014, at 12:39, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> I have mentioned this before, but EyeCollectionInspector is actually written against SequenceableCollection since it expects ordered external integer indexing. That is why currently every Collection subclass without this protocol and/or without a custom inspector fails. >> >> The alternative would be to move Collection class>>#inspectorClass to SequenceableCollection>>#inspectorClass. Then Collection subclasses that are not SequenceableCollection and that do not have a custom inspector will fail. >> >> Note that fail means a fall back to EyeBasicInspector. >> > > I did that change in 4.0 (with the mistake of putting #inspectorClass on the instance side of SequenceableCollection, I will fix that soon) > > Marcus Ah, OK. Yes it is class side (I made a typo too). Don't forget to remove the selector from Collection.

July 25, 2014

Re: [Pharo-dev] Trie in Pharo

by Marcus Denker

On 25 Jul 2014, at 12:39, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I have mentioned this before, but EyeCollectionInspector is actually written against SequenceableCollection since it expects ordered external integer indexing. That is why currently every Collection subclass without this protocol and/or without a custom inspector fails. > > The alternative would be to move Collection class>>#inspectorClass to SequenceableCollection>>#inspectorClass. Then Collection subclasses that are not SequenceableCollection and that do not have a custom inspector will fail. > > Note that fail means a fall back to EyeBasicInspector. > I did that change in 4.0 (with the mistake of putting #inspectorClass on the instance side of SequenceableCollection, I will fix that soon) Marcus

July 25, 2014

Re: [Pharo-dev] Trie in Pharo

by Sven Van Caekenberghe

I have mentioned this before, but EyeCollectionInspector is actually written against SequenceableCollection since it expects ordered external integer indexing. That is why currently every Collection subclass without this protocol and/or without a custom inspector fails. The alternative would be to move Collection class>>#inspectorClass to SequenceableCollection>>#inspectorClass. Then Collection subclasses that are not SequenceableCollection and that do not have a custom inspector will fail. Note that fail means a fall back to EyeBasicInspector. On 25 Jul 2014, at 12:32, Stephan Eggermont <stephan(a)stack.nl> wrote: > I took a look at what would be needed to port the Cuis Trie to Pharo. > Trie is a subclass of Collection, and expects at: aKey, not at: anIndex. > That breaks the EyeInspector view. What interface expects the > explorer a Collection subclass to have? > > Stephan >

July 25, 2014

Re: [Pharo-dev] File Outs: Can We Have Unix Line Endings?

by Nicolas Cellier

At the origin, Smalltalk was all CR Then some conversions were introduced at input/output from/to external world. Then we made some of our tools line-Ending-Zoo-Agnostic (for example, text rendering now supports CR, LF, or CR-LF). This was questionnable, because we injected a bit more complexity in the image, rather than segregating the complexity at the interfaces. But I think it was a good change, because we had more and more interfaces, and more and more patches/workarounds to handle. And finally, being line-Ending-Zoo-Agnostic costs a bit, but not that much. The most questionnable feature is the presence of mixed convention in image and the impact on simple String comparison... Some conversion is still required. In any case, what we must avoid is massively replace cr with lf in our source code. What I recommand is using (aStream nextLine) rather than (aStream upTo: Character cr). And we should probably replace most of the (aStream cr) with (aStream newLine) in our tools. ( except in rare places where with really want to control cr/lf because it is protocol specific ) This way, cr/lf will be an implementation detail that we can rapidly switch with a Preference/Setting, some OS-Aware environment variable (some class variable set at image startup to avoid asking os colour at each newLine), or just hardcode. Even if that does not completely eliminate the need for converting some input/output... 2014-07-25 12:03 GMT+02:00 Stephan Eggermont <stephan(a)stack.nl>: > Sean wrote: > >git was mentioned (which is my use-case too). Since the community is > using it more and more, it might make sense to have a default, no? > > Not AFAIK. You are supposed to tell git and github what to use. > > > http://stackoverflow.com/questions/170961/whats-the-best-crlf-handling-stra… > > Stephan >

July 25, 2014

Trie in Pharo

by Stephan Eggermont

I took a look at what would be needed to port the Cuis Trie to Pharo. Trie is a subclass of Collection, and expects at: aKey, not at: anIndex. That breaks the EyeInspector view. What interface expects the explorer a Collection subclass to have? Stephan

July 25, 2014

smalltakhub down

by Esteban Lorenzano

Hi, We disabled smalltalkhub for one or two hours. The reason is that we need to fix some integrity problems. Esteban

July 25, 2014