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

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

by Esteban A. Maringolo

2014-07-25 3:57 GMT-03:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > There is no need to choose a default because before the file out is > executed, one could check the which OS the system is running. > And then switch to the proper line ending. > Is just a one-liner Okay, OS line ending by default, but what I want is a way to override current setting and use the one I like. If you work both in Linux and Windows, normally you choose only one (usually linux). If you install git on Windows, it will ask you if you want to use OS default or convert everything to a particular line ending when pushing changes. Regards, Esteban A. Maringolo

July 25, 2014

Re: [Pharo-dev] Trie in Pharo

by stepharo

In StephaneDucasse/PetitsBazars package Box and BoxTests contains an alternate implementation you could add the one of cuis so that we can compare. BXTrie is a work under progress. Stef > 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] Does anyone use menuMorph in dockingbar?

by stepharo

If one day we need to menubar we will design a specific menuMorph that avoids to be crippled of is....whatever. In old code the power of dispatch was largely underestimated. Stef On 25/7/14 12:12, Nicolas Cellier wrote: > I don't know if Squeak has exclusivity or patents on DockingBar ;), > but it is used in Squeak 4.x for sure. > My productivity had a great boost since we attached one top of the World. > > > 2014-07-25 7:48 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com > <mailto:i.uhnak@gmail.com>>: > > Isn't DockingBar a Squeak thing? The little tabs things that would > live around the edges of the screen and you could grab morphs onto > a canvas. > > > On Fri, Jul 25, 2014 at 2:06 AM, Alexandre Bergel > <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: > > No idea what this could be. > go go go! > > Alexandre > > > On Jul 24, 2014, at 4:39 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > > Hi guys > > > > the code of MenuMorph is crippled of isInDockingBar and the > logic is much more complex. > > I have the impression that it is decades since we got a menu > in a docking bar. I do not even remember > > what it mean. I would like to clean this part because we > should really be a bit more radical else we will die under > > the mass of complex, old.... code. > > > > Stef > > > > looks like a dockingbar is this > > > > DockingBarMorph new > > addMorph: (SimpleButtonMorph new > > label: 'Say hello'; > > target: [UIManager inform: 'Hello']; > > actionSelector: #value); > > addMorph: (SimpleButtonMorph new > > label: 'Say bonjour'; > > target: [UIManager inform: 'Bonjour']; > > actionSelector: #value); > > addMorph: (SimpleButtonMorph new > > label: 'Close'; > > target: [DockingBarMorph allInstances last delete]; > > actionSelector: #value); > > adhereToBottom; > > openInWorld. > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

July 25, 2014

Re: [Pharo-dev] Trie in Pharo

by stepharo

There are several implementation of trie. Benoit St jean did another one and he told me that it was simpler and faster. I have it around and I can send it to you if you need. I was slowly going to add them to a project where I collect on collections implementation Stef On 25/7/14 12:32, Stephan Eggermont 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

[ANN] Voronyj Diagram

by Natalia Tymchuk

Hello. I implemented Voronyj diagrams for Roassal. You can read about it here: http://natalia.tymchuk.me/RTVoronyjDiagram/ . I will be on vacation from Monday till Thursday, but it will be really cool if you can write me your opinion about this project and all your remarks. Best regards, Natalia

July 25, 2014

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