September 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] about package naming

by Tudor Girba

Hi, That naming convention is due to the fact that there was a time when Monticello committed the content of packages based on prefix matching. So, if you had: FileSystem-Core FileSystem-Core-Tests committing FileSyste-Core would also commit FileSystem-Core-Tests as a subcategory. Actually, we still have the bug that if you would change something in FileSystem-Core, FileSystem-Core-Tests would be marked as dirty. Still, it would be much better to have naming of a package reflect a categorization. So, FileSystem-Core-Tests would be much more preferable. Cheers, Doru > On Sep 4, 2016, at 10:17 AM, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > Sorry to be that dull and stupid but I do not get why (beside following the seaside convention - and I do not understand it either) why the test package for FileSystem-Core is named FileSystem-Tests-Core > > and not just > > FileSystem-Core-Tests > > like that we could have > > FileSystem-Core-Help > > FileSystem-Core-Examples > > And when we are looking for FileSystem-Core we can see automatically FileSystem-Core-Tests > > Now we cannot. > > Stef > > -- www.tudorgirba.com www.feenk.com "If you can't say why something is relevant, it probably isn't."

Sept. 4, 2016

OCCompilerASTPlugin

by Serge Stinckwich

I have one question about Opal Compiler. I would like do an AST transformation before using the compiler. If I understand correctly, I have to built a subclass of OCCompilerASTPlugin ? Is it correct ? Any documentation more update about Opal than this : https://github.com/SquareBracketAssociates/PharoLimbo/tree/master/Opal Thank you. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Sept. 4, 2016

Re: [Pharo-dev] GTInspector Inspecting a string should provide default interaction shortcut

by Tudor Girba

Hi, We already agreed several times that this is a bug :). I now created an issue to make sure we do not forget it: https://pharo.fogbugz.com/f/cases/19037/String-presentation-in-GTInspector-… Doru > On Sep 4, 2016, at 8:00 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > stepharo wrote >> when I inspect a string, the default shortcuts should be present. > > Yes! No modes!!! It is confusing and does not seem to fit the spirit of our > system. Who can predict where a user will want/need to evaluate? I often > perform doIts in the MC Browser windows, commit log dialogs, etc. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/GTInspector-Inspecting-a-string-should-provide-defaul… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > -- www.tudorgirba.com www.feenk.com "Value is always contextual."

Sept. 4, 2016

Can Sound depend on Jobs?

by Sean P. DeNigris

I wanted to add as an extension method to the Sound package: Job>>#beepAtEnd "Sound must first be enabled via `SoundSystem soundEnabled: true.`" self announcer when: JobEnd do: [ SoundSystem current beep ] I figured I'd get some feedback first since I know we're trying to reduce dependencies... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Can-Sound-depend-on-Jobs-tp4914083.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 4, 2016

Re: [Pharo-dev] Idea: User-Installed Nautilus Package Group

by Sean P. DeNigris

EstebanLM wrote > +1 I will not open an issue because I don't have time to work on it right now and suspect it will languish and be closed (not complaining), so I will add it way down on my personal todo list and I leave opening an issue to anyone actually willing to do the work. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Idea-User-Installed-Nautilus-Package-Group-tp4913942p… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 4, 2016

Re: [Pharo-dev] about package naming

by Yuriy Tymchuk

Hi, I like the FileSystem-Core-Tests more, because then we can also have FileSystem-Core-Rules and FileSystem-Core-Rules-Tests. But I think that the other way to think about this is that if you want to (un)load all the test from filesystem you just work with FileSystem-Tests and not do it individually for each submodule. However this is just my guess. Uko > On 04 Sep 2016, at 10:17, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > Sorry to be that dull and stupid but I do not get why (beside following the seaside convention - and I do not understand it either) why the test package for FileSystem-Core is named FileSystem-Tests-Core > > and not just > > FileSystem-Core-Tests > > like that we could have > > FileSystem-Core-Help > > FileSystem-Core-Examples > > And when we are looking for FileSystem-Core we can see automatically FileSystem-Core-Tests > > Now we cannot. > > Stef > >

Sept. 4, 2016

Re: [Pharo-dev] streamlining creation of gtInspector extensions

by Sean P. DeNigris

Ben Coman wrote > * Show Definition - which opens a browser on the right code > * Create Custom Extension - which opens a dialog to create a new > package "MyGTExtensions" and/or select an existing package, specify an > identifier and choose a template that is created and Browser opened. Great ideas! This brings the behavioral possibilities much closer to the live objects themselves... ----- Cheers, Sean -- View this message in context: http://forum.world.st/streamlining-creation-of-gtInspector-extensions-tp491… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 4, 2016

Re: [Pharo-dev] could we discuss 19006

by Sean P. DeNigris

stepharo wrote > Note that I'm not against. I just want to understand. Me too. I looked over the issue, and it seemed one would already have to understand the issue very well. I wished there was more explanation about the problem and why the solution was a good one. In the end, I shrugged my shoulders and just had to trust the author. ----- Cheers, Sean -- View this message in context: http://forum.world.st/could-we-discuss-19006-tp4913965p4914079.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 4, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] e64121: 60202

by Sean P. DeNigris

GitHub wrote > 19001 Another pass to introduce iconNamed: and avoid Smalltalk ui icons > https://pharo.fogbugz.com/f/cases/19001 This one surprised me. I thought we were trying to avoid extensions to low-level classes when possible. How is icon retrieval a responsibility of ClassDescription?! I'm all about convenience, but not getting this change. Was there a discussion somewhere? What benefits am I missing? ----- Cheers, Sean -- View this message in context: http://forum.world.st/pharo-project-pharo-core-e64121-60202-tp4914016p49140… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 4, 2016

Re: [Pharo-dev] GTInspector Inspecting a string should provide default interaction shortcut

by Sean P. DeNigris

stepharo wrote > when I inspect a string, the default shortcuts should be present. Yes! No modes!!! It is confusing and does not seem to fit the spirit of our system. Who can predict where a user will want/need to evaluate? I often perform doIts in the MC Browser windows, commit log dialogs, etc. ----- Cheers, Sean -- View this message in context: http://forum.world.st/GTInspector-Inspecting-a-string-should-provide-defaul… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 4, 2016