- Pharo-dev - lists.pharo.org

[Pharo-project] Sound tutorials
by Wilker Feb. 6, 2012

Feb. 6, 2012

Hi guys, My first post on this maillist, and brand new on Smalltalk too :) Today I'm here to ask a few things to you guys. I'm planning to do some experimental projects (just to learn more Pharo) and I'm getting stuck on some stuff... I'm trying to do some work with Sounds (playing, recording, analysis...), and I saw that Pharo cames with some sound libraries, but I can't find any tutorial or book talking about it... You have any recommendations about that? Where I can learn more about dealing with sound on Pharo? Thanks a lot. --- Wilker LÃºcio http://about.me/wilkerlucio/bio Kajabi Consultant +55 81 82556600

6 12

[Pharo-project] Open Advice Essays
by Ben Coman Feb. 6, 2012

Feb. 6, 2012

I hesitated to share this since I actually found most of it a bit bland and Pharo is already doing many of the suggestions quite well - but I had picked out the few interesting parts as a went along, so here they are. Many of the essays would apply more to the Pharo ecosystem of surrounding projects rather than Pharo itself - particularly those that end up abandoned. This 40 short essays [1] on "What we wish we had known when we started Free Software" [1] http://open-advice.org/Open-Advice.pdf <http://open-advice.org/> pdf p23-29 - Out of the Lab, into the Wild - Growing Open Source Communities around Academic Projects... pdf p43 - "when you lose interest in a program, your last duty is to hand it off to a competent successor" (or document well the transition to the replacement) pdf p44 - "As a new contributor to a project, you are an invaluable asset not for your knowledge, but for your ignorance" pdf p52 - "Potential contributors often think they are not allowed to contribute. The reasons for this [...] are all misconceptions" pdf p135 - "If you are a developer, it is particularly difficult for you to sit in the user's chair" pdf p186 - Planning pdf p270 - "it is far more important to have documentation of the things that will not work, so they can be avoided or worked around, than it is to know that some future version will behave much better. [...] Today's documented bug is, ironically, often preferable to tomorrow's fix with unforeseeable side effects." pdf p301-302 "the tension in Free Software did not lie in the introduction of increased commercial activity, in the increased participation of company employees in projects, or in change itself. The real problem lay in the gap between a dis- placed previous elite and their newer, occasionally very different, fellow stakeholders." regards, Ben

1 0

Re: [Pharo-project] startDrag: error
by Fernando Olivero Feb. 5, 2012

Feb. 5, 2012

ouch...this kind of method is why i chose to start from scratchâ¦. what is the err you get? Fernando On Sun, Feb 5, 2012 at 6:13 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > In 1.4 I get from time to time a problem with > > PluggableListMorph>>startDrag: evt > Â Â Â Â |row ddm draggedItem draggedItemMorph | > > Â Â Â Â dragItemSelector ifNotNil: [ ^self startDragExtended: evt ]. > Â Â Â Â evt hand hasSubmorphs ifTrue: [^ self]. > Â Â Â Â (self dragEnabled and: [model okToChange]) ifFalse: [^ self]. > > Â Â Â Â (row := self mouseDownRow) > Â Â Â Â Â Â Â Â ifNil: [ draggedItem := self getListItem: lastNonZeroIndex. "self selection" ] > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â where lastNonZeroIndex is nil > > > Â Â Â Â Â Â Â Â ifNotNil: [ draggedItem := self getListItem: row ]. > > Â Â Â Â "Here I ensureat least one element is selected " > Â Â Â Â draggedItem ifNil: [ ^ self ]. > > Â Â Â Â self isMultipleSelection > Â Â Â Â Â Â Â Â ifTrue: [ | passengers | > Â Â Â Â Â Â Â Â Â Â Â Â passengers := self model dragPassengersFor: draggedItem inMorph: self. > Â Â Â Â Â Â Â Â Â Â Â Â passengers ifNil: [ ^ self ]. > Â Â Â Â Â Â Â Â Â Â Â Â draggedItemMorph := StringMorph contents: (passengers joinUsing: ' ') asStringOrText. > Â Â Â Â Â Â Â Â Â Â Â Â ddm := TransferMorph withPassenger: passengers from: self ] > Â Â Â Â Â Â Â Â ifFalse: [ | passenger | > Â Â Â Â Â Â Â Â Â Â Â Â passenger := self model dragPassengerFor: draggedItem inMorph: self. > Â Â Â Â Â Â Â Â Â Â Â Â passenger ifNil: [ ^ self ]. > Â Â Â Â Â Â Â Â Â Â Â Â draggedItemMorph := StringMorph contents: passenger asStringOrText. > Â Â Â Â Â Â Â Â Â Â Â Â ddm := TransferMorph withPassenger: passenger from: self ]. > > > Â Â Â Â self mouseDownRow: nil. > > Â Â Â Â ddm dragTransferType: (self model dragTransferTypeForMorph: self). > > Â Â Â Â [evt hand grabMorph: ddm ] ensure: [ > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Cursor normal show. > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â evt hand releaseMouseFocus: self] > > > > listSelectionAt: index > > Â Â Â Â index isZero ifFalse:[ lastNonZeroIndex := index ]. > Â Â Â Â getSelectionListSelector ifNil:[^false]. > Â Â Â Â ^model perform: getSelectionListSelector with: index > > > So it looks like there are path where lastNonZeroIndex can be nil. > >

1 0

[Pharo-project] Seaside going better
by Schwab,Wilhelm K Feb. 5, 2012

Feb. 5, 2012

A clean 1.3 image is starting to work. I would still like to see Jenkins create Seaside-enabled images, because the download times can be significant, and I have experienced intermittent failures that might be due to down servers, etc. My most recent attempt choked at one point, but I *think* that's because my attempt to load Magritte might be flawed. I might tweak Migrate (my own answer to building images) to save after critical steps in the hope of avoiding lots of lost time when things don't go well. Bill

2 2

[Pharo-project] startDrag: error
by StÃ©phane Ducasse Feb. 5, 2012

Feb. 5, 2012

Hi guys In 1.4 I get from time to time a problem with PluggableListMorph>>startDrag: evt |row ddm draggedItem draggedItemMorph | dragItemSelector ifNotNil: [ ^self startDragExtended: evt ]. evt hand hasSubmorphs ifTrue: [^ self]. (self dragEnabled and: [model okToChange]) ifFalse: [^ self]. (row := self mouseDownRow) ifNil: [ draggedItem := self getListItem: lastNonZeroIndex. "self selection" ] where lastNonZeroIndex is nil ifNotNil: [ draggedItem := self getListItem: row ]. "Here I ensureat least one element is selected " draggedItem ifNil: [ ^ self ]. self isMultipleSelection ifTrue: [ | passengers | passengers := self model dragPassengersFor: draggedItem inMorph: self. passengers ifNil: [ ^ self ]. draggedItemMorph := StringMorph contents: (passengers joinUsing: ' ') asStringOrText. ddm := TransferMorph withPassenger: passengers from: self ] ifFalse: [ | passenger | passenger := self model dragPassengerFor: draggedItem inMorph: self. passenger ifNil: [ ^ self ]. draggedItemMorph := StringMorph contents: passenger asStringOrText. ddm := TransferMorph withPassenger: passenger from: self ]. self mouseDownRow: nil. ddm dragTransferType: (self model dragTransferTypeForMorph: self). [evt hand grabMorph: ddm ] ensure: [ Cursor normal show. evt hand releaseMouseFocus: self] listSelectionAt: index index isZero ifFalse:[ lastNonZeroIndex := index ]. getSelectionListSelector ifNil:[^false]. ^model perform: getSelectionListSelector with: index So it looks like there are path where lastNonZeroIndex can be nil.

1 0

[Pharo-project] FS: How do I get the equivalent to slash
by StÃ©phane Ducasse Feb. 5, 2012

Feb. 5, 2012

Hi is there a way to know the character that encode a folder separator using FS? FileDirectory slash Stef

1 0

Re: [Pharo-project] [squeak-dev] Re: Trying to undeerstand Morphic subclasses and step/stepAt:
by Dave Mason Feb. 5, 2012

Feb. 5, 2012

Hi Marcel, On 2012-Feb-5, at 2:04 , Marcel Taeumel wrote: > You need to call #startStepping if you want #step to get called frequently > according to #stepTime. Actually you don't with Squeak 4.2 and Pharo 1.3 (don't know about earlier versions), because Morph>>initialize does that. But just for completeness, I did that, and it made no difference. My class is just: MorphExp>>initialize super initialize. self startStepping. self color: Color red lighter MorphExp>>step self halt MorphExp>>stepAt: t self halt and it doesn't halt if it is a subclass of SystemWindow, but does if it's any higher up the hierarchy. > Nevertheless, you may want to take a closer look at this project: > https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki… Thanks, but I don't want the issue about unloading, and I'm not worried about it being super-smooth animation. Also thanks for the link, because it looks like interesting things are happening at HPI! ../Dave

2 1

Re: [Pharo-project] [squeak-dev] Re: Trying to undeerstand Morphic subclasses and step/stepAt:
by Dave Mason Feb. 5, 2012

Feb. 5, 2012

On 2012-Feb-5, at 7:40 , Bob Arning wrote: > Look at the methods #wantsSteps. Bingo! I assumed it was something stupid I was missing. On 2012-Feb-4, at 14:23 , Sean P. DeNigris wrote: > I don't know if it's any better, but when I create my own morph-in-a-window, > I usually don't subclass SystemWindow, but add my morph to a window using > openInWindowLabelled: or addMorph:fullFrame:. I feel like I have a little > more flexibility if I later want to use it not-in-a-window. After defining wantsSteos, I see that color: seems to work a bit strangely too in SystemWindow, so I'm going to try this. Thanks, Bob and Sean.

1 0

[Pharo-project] Pharo Morphic View Application Framework
by S Krish Feb. 5, 2012

Feb. 5, 2012

http://skrishnamachari.wordpress.com/2012/01/31/pharo-application-framework… Obliged for feedback ... For details and links.. Sharing this little framework that should go some way to ease creating large applications ( currently morphic oriented). AbstractMorphicView subclass: #MyNewView â¦ #createMorphsSpecs ^{ âpanel1â² -> #SomeOtherView. âlabel1â² -> #LabelMorph. âtext1â² -> #PluggableTextMorph. âbutton1â² -> #PluggableButtonMorph. } layoutSpecsArray ^{ âwidgetNameInMorphsDictionaryâ -> { #fractions -> (0 @ 0 corner: 1 @ 0.5). â fractional value 0 to 1 range â #offsets -> (10 @ 10 corner: 0 @ 0). â offsets relative to the fractional position â }. ââ¦ add other widgetspecsâ¦â } Thats it.. you should have a prototype UI neatly laid out.. and then specify: #morphsPrimaryPropertiesSpecs and #morphsSecondaryPropertiesSpecs for full functionality that composes views inside views and scales well. AbstractSimpleMorphicView can make it simpler for TableLayout stuff without requiring #layoutSpecsArray. ..... the main post has other details and links to package...

6 18

[Pharo-project] ConfigurationOfCitezen - any bugs?
by Schwab,Wilhelm K Feb. 5, 2012

Feb. 5, 2012

Hello all, I am making progress toward building a 1.3 image, but I am getting a hung system when loading (#loadNoWeb) Citezen. Is this a known problem? Bill

4 17