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

OSSubProcess?

by Alexandre Bergel

Hi! I tried to use OSSubProcess, but I got an error. I have installed it in the latest Pharo 5, latest VM, I am running in OSX. I have installed OSSubProcess from the catalog. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 5, 2016

PharoV50.sources

by Alexandre Bergel

Hi! It would be fantastic to have that file downloadable from the pharo.org :-) This is all good work! Keep doing! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 5, 2016

Mac OS Cocoa MIDI Plugin

by Eliot Miranda

Hi All, recently the Cog VM on Mac OS X moved to Cocoa, the Objective-C API for the platform, leaving behind the old Carbon C API. There is some backward compatibility support but it is gradually being deprecated by Apple. One victim is the MIDIPlugin which was written against a ComponentManager API that, while Apple docs say is only deprecated, has actually disappeared. Consequently the MIDIPlugin support (see http://www.squeakvm.org/svn/squeak/branches/Cog/platforms/iOS/plugins/MIDIP…) needs completely rewriting to use Cocoa APIs. I've recently changed the build so that the MIDIPlgin is built externally, which will make it easier to work on; one doesn't need to build the entire VM, only the plugin. I'm looking for volunteers who a) love music/know MIDI b) are happy programming at the Objective-C level using command-line builds and perhaps Xcode, but more immediately lldb for debugging. If interested, reply to vm-dev and we can continue discussions there; there are folks that can help with Mac OS support, but no one I know of that has time to write this rather important plugin for multi-media. It would be a great shame to lose MIDI on Mac. ______,,,^..^,,,______ AdvThanksance, Eliot

May 5, 2016

Re: [Pharo-dev] [HELP WANTED] Getting ready for Pharo 5.0 release (CentOS, oldLibC, Nix, ArchLinux, and others)

by Bernardo Ezequiel Contreras

Ben, This thread mail subject is Pharo 5.0 release (there is no beta), and even if you are right please take a look at http://files.pharo.org/sources/, there's a PharoV50.sources. And also if you try to open a Pharo5.0.image , it will ask for the file PharoV50.sources. thanks On Thu, May 5, 2016 at 6:04 AM, Ben Coman <btc(a)openinworld.com> wrote: > On Thu, May 5, 2016 at 7:12 AM, Bernardo Ezequiel Contreras > <vonbecmann(a)gmail.com> wrote: > > Hi Esteban, > > I tried again and it doesn't work. :( > > But now i found another issue, if you take a look to pharo5.0/shared > > folder you will see the file PharoV40.sources (wrong version for this > > release) > > This is the correct sources for Pharo5-*beta*. It doesn't become > PharoV50.sources until the changes file is compacted for actual > *release*. However I understand the confusion. I think this naming > is based off the Squeak workflow, where IIUC they just work in, for > example 4.5, and don't call it 4.6 until just weeks before release. > But we've called it Pharo 5 (beta) for 12 months. > > I have thought a few times myself that maybe for Pharo 6 we could have > PharoV60dev.sources and later PharoV60.sources. > > cheers -ben > > > > > > thanks > > > > On Sun, May 1, 2016 at 7:13 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > > wrote: > >> > >> > >> > On 01 May 2016, at 10:59, Stephan Eggermont <stephan(a)stack.nl> wrote: > >> > > >> > On 30/04/16 23:13, Bernardo Ezequiel Contreras wrote: > >> >> Hi Esteban, > >> >> i found a problem with one of the packages, see below > >> >> > >> >> ** TODO This interpreter (vers. 6505) cannot read image file (vers. > >> >> 6521) > >> > > >> > So you have a non-spur vm there. You need a spur one > >> > >> yes, but Pharo5.0-linux-oldLibC.zip should download a spur vmâ¦ I need to > >> review that :) > >> > >> Esteban > >> > >> > > >> > Stephan > >> > > >> > > >> > >> > > > > > > > > -- > > Bernardo E.C. > > > > Sent from a cheap desktop computer in South America. > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

May 5, 2016

Re: [Pharo-dev] call for cleaning ideas around Spec

by Thierry Goubier

Le 04/05/2016 19:18, Stephan Eggermont a Ã©crit : > > > On 04/05/16 18:18, stepharo wrote: >> Can you open bug entries with such points? > > 18164 Put drag-and-drop behaviour in one object > > 18165 ComposableModel: aboutText seems to be in the wrong place > > 18166 Where should focus change keystrokes be handled? For this one there was an debate about the following point: why Spec needs to reimplement the focus change keystroke implemented by Morphic? Thierry > Stephan > > >

May 5, 2016

Re: [Pharo-dev] call for cleaning ideas around Spec

by Stephan Eggermont

On 05/05/16 00:15, Stephan Eggermont wrote: > On 04/05/16 08:19, stepharo wrote: >> if you have ideas let us know too. > > Why does every NewValueHolder have its own announcer? > And is initializing all those unused valueHolders in initialize > of Spec presentation classes not slow? Talking to Latsabben on Slack, first step: Name: SLICE-Issue-18167-NewValueHolder-classvalue-should-use-rawValue-StephanEggermont.1 Author: StephanEggermont Time: 5 May 2016, 11:55:36.083109 am UUID: d89767d0-5d9d-40b8-ad67-5887b22a338f Ancestors: Dependencies: NewValueHolder-StephanEggermont.34 Do not send announcements when you know there can't be any subscriptions

May 5, 2016

Re: [Pharo-dev] Another look at the [First Impression Count] in Pharo 5

by Stephan Eggermont

On 05/05/16 10:38, Eliot Miranda wrote: > Hilaire, please, never shut up. +1 Noticing all theses things and not having enough time and energy to be able to fix them all can be tiring. We value what you are able to do. Stephan

May 5, 2016

Re: [Pharo-dev] [HELP WANTED] Getting ready for Pharo 5.0 release (CentOS, oldLibC, Nix, ArchLinux, and others)

by Ben Coman

On Thu, May 5, 2016 at 7:12 AM, Bernardo Ezequiel Contreras <vonbecmann(a)gmail.com> wrote: > Hi Esteban, > I tried again and it doesn't work. :( > But now i found another issue, if you take a look to pharo5.0/shared > folder you will see the file PharoV40.sources (wrong version for this > release) This is the correct sources for Pharo5-*beta*. It doesn't become PharoV50.sources until the changes file is compacted for actual *release*. However I understand the confusion. I think this naming is based off the Squeak workflow, where IIUC they just work in, for example 4.5, and don't call it 4.6 until just weeks before release. But we've called it Pharo 5 (beta) for 12 months. I have thought a few times myself that maybe for Pharo 6 we could have PharoV60dev.sources and later PharoV60.sources. cheers -ben > > thanks > > On Sun, May 1, 2016 at 7:13 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: >> >> >> > On 01 May 2016, at 10:59, Stephan Eggermont <stephan(a)stack.nl> wrote: >> > >> > On 30/04/16 23:13, Bernardo Ezequiel Contreras wrote: >> >> Hi Esteban, >> >> i found a problem with one of the packages, see below >> >> >> >> ** TODO This interpreter (vers. 6505) cannot read image file (vers. >> >> 6521) >> > >> > So you have a non-spur vm there. You need a spur one >> >> yes, but Pharo5.0-linux-oldLibC.zip should download a spur vmâ¦ I need to >> review that :) >> >> Esteban >> >> > >> > Stephan >> > >> > >> >> > > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America.

May 5, 2016

Re: [Pharo-dev] Another look at the [First Impression Count] in Pharo 5

by Eliot Miranda

> On May 5, 2016, at 12:32 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > > AMHO, there are some needed feedbacks on some tools. There are the most > visible I can see, where newbies will be contemplating without > understanding. > > I try to propose a tip, please *correct* it when wrong or incomplete. > > NAUTILUS > - 'Scoped'-> not sure what is the extent of the Scoped, but a proposed > tip: 'Browse in the context of the selected package/class: all nautilus > tools -- including refactoring -- will proceed only within the selected > package/class.' > - 'Format as you read' -> based on Peter suggestion: 'Autoformat code > without editing. Useful when reading some old/unformatted code.' > - 'NW/W' -> I don't know > - '+L' -> 'Toggle line number for code" > > SETTINGS BROWSERS > - There are about 100 Spotter entries without unhelpful descriptions as: > 'Trait>>#spotterReferenceFor: > spotterReferenceFor: aStep > <spotterOrder: 30> > aStep listProcessor > title: 'References'; > allCandidates: [ (SystemNavigation default allReferencesTo: self > binding) collect: #compiledMethod ]; > itemName: [ :method | method gtDisplayString ]; > filter: GTFilterSubstring' > > is it a bug or on purpose? However definitely not newbie friendly. > > If these settings are not relevant, may be hiding it. > > - GRAPHIC THEME > It lacks contrast, (and no there is objective measure, otherwise what is > design for) but I guess nothing much can be done. > Tooltips lost again the blue contrasting background for a grey > unconstrasting one. In the past I already fixed the Water theme from > random refactoring, it is sad to see few care on the UI: this is the > first thing newbies will notice even before reaching the deep beauty of > Pharo, they will be gone because the first impression went wrong. > > > Hilaire > > PS: > Please, don't assume because I post this review I take responsibility on > fixing it, I may or not. I really get this irritating feedback from my > feedbacks, and I don't think pressure is helpful. We are doing our best > according to our personnel life constraints. If not ok, I will shut up > for ever. Hilaire, please, never shut up. > -- > Dr. Geo > http://drgeo.eu

May 5, 2016

Another look at the [First Impression Count] in Pharo 5

by Hilaire

AMHO, there are some needed feedbacks on some tools. There are the most visible I can see, where newbies will be contemplating without understanding. I try to propose a tip, please *correct* it when wrong or incomplete. NAUTILUS - 'Scoped'-> not sure what is the extent of the Scoped, but a proposed tip: 'Browse in the context of the selected package/class: all nautilus tools -- including refactoring -- will proceed only within the selected package/class.' - 'Format as you read' -> based on Peter suggestion: 'Autoformat code without editing. Useful when reading some old/unformatted code.' - 'NW/W' -> I don't know - '+L' -> 'Toggle line number for code" SETTINGS BROWSERS - There are about 100 Spotter entries without unhelpful descriptions as: 'Trait>>#spotterReferenceFor: spotterReferenceFor: aStep <spotterOrder: 30> aStep listProcessor title: 'References'; allCandidates: [ (SystemNavigation default allReferencesTo: self binding) collect: #compiledMethod ]; itemName: [ :method | method gtDisplayString ]; filter: GTFilterSubstring' is it a bug or on purpose? However definitely not newbie friendly. If these settings are not relevant, may be hiding it. - GRAPHIC THEME It lacks contrast, (and no there is objective measure, otherwise what is design for) but I guess nothing much can be done. Tooltips lost again the blue contrasting background for a grey unconstrasting one. In the past I already fixed the Water theme from random refactoring, it is sad to see few care on the UI: this is the first thing newbies will notice even before reaching the deep beauty of Pharo, they will be gone because the first impression went wrong. Hilaire PS: Please, don't assume because I post this review I take responsibility on fixing it, I may or not. I really get this irritating feedback from my feedbacks, and I don't think pressure is helpful. We are doing our best according to our personnel life constraints. If not ok, I will shut up for ever. -- Dr. Geo http://drgeo.eu

May 5, 2016