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

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

Re: [Pharo-dev] Does anyone use menuMorph in dockingbar?

by Nicolas Cellier

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>: > 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 > > wrote: > >> No idea what this could be. >> go go go! >> >> Alexandre >> >> >> On Jul 24, 2014, at 4:39 PM, stepharo <stepharo(a)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] File Outs: Can We Have Unix Line Endings?

by Stephan Eggermont

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

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

by HernÃ¡n Morales Durand

I see. I don't know the Git use-case. I was suggesting OS detection for the file-out from image to local disk. But I use Windows now, if you set Unix line ending that would mean I (or anyone using Windows) have to unix2dos for every pull or fetch from any Git repository commited from Pharo? HernÃ¡n 2014-07-25 4:42 GMT-03:00 Sean P. DeNigris <sean(a)clipperadams.com>: > HernÃ¡n Morales Durand wrote > > There is no need to choose a default... > > 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? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/File-Outs-Can-We-Have-Unix-Line-Endings-tp4769721p477… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

July 25, 2014

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

by Sean P. DeNigris

HernÃ¡n Morales Durand wrote > There is no need to choose a default... 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? ----- Cheers, Sean -- View this message in context: http://forum.world.st/File-Outs-Can-We-Have-Unix-Line-Endings-tp4769721p477… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 25, 2014

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

by HernÃ¡n Morales Durand

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 Smalltalk os isUnix 2014-07-24 11:12 GMT-03:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > 2014-07-24 2:17 GMT-03:00 Sean P. DeNigris <sean(a)clipperadams.com>: > > Any reason not to? Tedious to continually do "%s/\r/\r/g"s on Mac to fix: > > TextStream subclass:^M#UCTextStream^MinstanceVariableNames: > > ''^MclassVariableNames: ''^MpoolDictionaries: ''^Mcategory: > 'UFFA-Core'!^M! > > Yes please. > > And have an option to switch to any other ending for those who want it > that way for any uncomprehensible reason :P. > But Unix by default. > > > Esteban A. Maringolo > >

July 25, 2014