March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] migration to FogBugz

by Camillo Bruni

that implies that we have to migrate the PharoInbox :) otherwise we will have a mess of higher order matching slices numbers and issue numbers on fogbugz. On 2013-03-10, at 18:13, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > The problem is that you can not specify a id for issue while migrating. > > To prevent collision, the issues reported to fogbugz should start at id: 10000. > > Ben > > On Mar 10, 2013, at 4:34 PM, Ben Coman <btc(a)openInWorld.com> wrote: > >> I just noticed (for example) that https://code.google.com/p/pharo/issues/detail?id=6763 >> has been migrated as https://pharo.fogbugz.com/f/cases/6700. >> >> Is that change of issue number a concern to break the convention of slice names matching issue numbers >> as well as historical issue cross referencing? >> >> hope I'm missing something.. >> >> regards -ben >> >> >> >

March 10, 2013

Re: [Pharo-project] migration to FogBugz

by Benjamin

The problem is that you can not specify a id for issue while migrating. To prevent collision, the issues reported to fogbugz should start at id: 10000. Ben On Mar 10, 2013, at 4:34 PM, Ben Coman <btc(a)openInWorld.com> wrote: > I just noticed (for example) that https://code.google.com/p/pharo/issues/detail?id=6763 > has been migrated as https://pharo.fogbugz.com/f/cases/6700. > > Is that change of issue number a concern to break the convention of slice names matching issue numbers > as well as historical issue cross referencing? > > hope I'm missing something.. > > regards -ben > > >

March 10, 2013

Re: [Pharo-project] what do we do with SoundService?

by phil＠highoctane.be

e.g. of sound being useful: With the help of Craig Latta, I've been trying out Spoon. There is a remote browser for browsing classes remotely. Well, sound cues while things are transferred over the network are very useful when debugging. That's why sound matters in the core of Pharo. And Beeper may be interesting too. Phil 2013/3/10 stephane ducasse <stephane.ducasse(a)free.fr>: > Sounds ok for me. We should do that for 3.0alpha :) > Now I do not care about Beeper removal. > > I will split sound in different packages because there are sound and score and these are different domains. > > Stef > > On Mar 10, 2013, at 11:38 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > >> Hi, >> >> removal of this class is proposed in >> https://code.google.com/p/pharo/issues/detail?id=6996 >> >> -- Pavel >> >> >> On Sun, Mar 10, 2013 at 11:31 AM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> Hi guy >>> >>> Sound has an AbstractSoundSystem and a Base and Dummy. Then in addition there is SounService. >>> >>> SoundService is not doing much >>> >>> soundEnabled >>> ^ self defaultSoundEnabled >>> >>> defaultSoundEnabled >>> ^DefaultSoundEnabled ifNil: [false] >>> >>> toggleSoundEnabling >>> self soundEnabled: self soundEnabled not >>> >>> >>> >>> So we could just keep AbstractSoundSystem and deprecate SoundService. >>> >>> Stef >> > >

March 10, 2013

Re: [Pharo-project] FMSound bass1 play

by phil＠highoctane.be

SoundService and all that looks like in need of some refactoring at the moment. Here is what I do and it appears to work: in my app initialize BaseSoundSystem soundEnabled: true. BaseSoundSystem initialize. soundbank := Dictionary new. soundbank add: #rightAnswer -> FMSound flute1. soundbank add: #wrongAnswer -> FMSound bassoon1. soundbank add: #clearAnswer -> FMSound marimba. and to play: (soundbank at: aSoundSymbol) play. Works fine. Phil 2013/3/10 stephane ducasse <stephane.ducasse(a)free.fr>: > In fact I get really unpredictable behavior. > > Sometimes I can produce a sound sometimes not. > > SoundService default soundEnabled: true > > I'm puzzled > Stef > > On Mar 9, 2013, at 10:21 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> Hi guys >> >> I'm migrating the package Sound and MorphicSound to Pharo2.0 and SmalltalkHub. >> But I cannot make >> >> FMSound bass1 play >> produce a sound. >> >> Phil if i remember correctly you worked on that a couple of months ago. >> Can you summarize your findings? >> >> Stef > >

March 10, 2013

Re: [Pharo-project] MorphicEventHandler behavior.

by Guillermo Polito

Steph, I was looking and in the end of #buildKeyboard you have: self submorphsDo: [:m | m on: #mouseMove send: #mouseMovePitch:event:noteMorph: to: self; on: #mouseUp send: #mouseUpPitch:event:noteMorph: to: self; on: #mouseEnterDragging send: #mouseDownPitch:event:noteMorph: to: self; on: #mouseLeaveDragging send: #mouseUpPitch:event:noteMorph: to: self]. Which create subscriptions without any value. And that's why you get the nil and the DNU. It probably was working in 1.4 because the EventHandler code did only manage one subscription at a time and probably didn't notice these last subscriptions. Now int 2.0 all subscriptions to events are handled, and that's the reason of the DNU. I tested the code without that statement and get it work.. Guille On Sun, Mar 10, 2013 at 11:01 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > Hi fernando > > May be you know more than me on MorphicEventHandler. > > Gofer new > squeaksource: 'PharoNonCorePackages'; > package: 'Sound'; > package: 'SoundMorphicUserInterface'; > load. > > > > While trying to make > PianoKeyboardMorph new openInWorld > (which works in 1.4 and does not in 20). > > It breaks here: > > ------------- > mouseUpPitch: pitch event: event noteMorph: noteMorph > > noteMorph color: ((#(0 1 3 5 6 8 10) includes: pitch \\12) > ifTrue: [whiteKeyColor] > ifFalse: [blackKeyColor]). > soundPlaying ifNotNil: [soundPlaying stopGracefully]. > > pitch is nil because notify:from: uses valueParameter which is nil. > ------------- > > mouseUpPitch is invoked by notify: anEvent from: sourceMorph which is > invoked by notifyMorphsOfEvent: anEvent ofType: eventType from: sourceMorph > > notify: anEvent from: sourceMorph > | arity | > recipient ifNil: [^ self]. > arity := selector numArgs. > arity = 0 ifTrue: > [^ recipient perform: selector]. > arity = 1 ifTrue: > [^ recipient perform: selector with: anEvent]. > arity = 2 ifTrue: > [^ recipient perform: selector with: anEvent with: > sourceMorph]. > arity = 3 ifTrue: > [^ recipient perform: selector with: valueParameter with: > anEvent with: sourceMorph]. > > ^^^^^^^^^^^^^^^^^^^^^^^ > self error: 'Event handling selectors must be Symbols and take 0-3 > arguments' > > notifyMorphsOfEvent: anEvent ofType: eventType from: sourceMorph > | result | > result := false. > ((subscriptions includesKey: eventType) not or: [ (subscriptions > at: eventType) isEmpty ]) > ifTrue: [ ^false ]. > (subscriptions at: eventType) do: [ :s | result := result | ((s > notify: anEvent from: sourceMorph) == true) ]. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > ^result > > > The idea is that morphs get notified when a certain event occurs so when > we look at the morph creation and event registry we get: > > > The buildKeyboard create morph and define event with a given value that > will be used > on: #mouseDown send: #mouseDownPitch:event:noteMorph: to: self > withValue: i-1*12 + (#(2 4 7 9 11) at: j) > below: > > > buildKeyboard > | wtWid bkWid keyRect octavePt nWhite nBlack | > self removeAllMorphs. > wtWid := 8. bkWid := 5. > self extent: 10@10. > 1 to: nOctaves+1 do: > [:i | i <= nOctaves ifTrue: [nWhite := 7. nBlack := 5] > ifFalse: [nWhite := 1. > nBlack := 0 "High C"]. > octavePt := self innerBounds topLeft + ((7*wtWid*(i-1)-1) > @ -1). > 1 to: nWhite do: > [:j | keyRect := octavePt + (j-1*wtWid@0) extent: > (wtWid+1)@36. > self addMorph: ((RectangleMorph newBounds: keyRect > color: whiteKeyColor) > > borderWidth: 1; > on: #mouseDown send: > #mouseDownPitch:event:noteMorph: to: self > withValue: > i-1*12 + (#(1 3 5 6 8 10 12) at: j))]. > 1 to: nBlack do: > [:j | keyRect := octavePt + ((#(6 15 29 38 47) at: > j)@1) extent: bkWid@21. > self addMorph: ((Morph newBounds: keyRect color: > blackKeyColor) > on: #mouseDown send: > #mouseDownPitch:event:noteMorph: to: self > withValue: > i-1*12 + (#(2 4 7 9 11) at: j))]]. > self submorphsDo: > [:m | m on: #mouseMove send: > #mouseMovePitch:event:noteMorph: to: self; > on: #mouseUp send: > #mouseUpPitch:event:noteMorph: to: self; > on: #mouseEnterDragging send: > #mouseDownPitch:event:noteMorph: to: self; > on: #mouseLeaveDragging send: > #mouseUpPitch:event:noteMorph: to: self]. > self extent: (self fullBounds extent + borderWidth - 1) > > > > Now I can understand that > #mouseDownPitch:event:noteMorph: get notified with a value because > this is what is written. > But I do not get why this would be the case with > #mouseUpPitch:event:noteMorph: > since we simply get > on: #mouseUp send: #mouseUpPitch:event:noteMorph: to: self; > > > And I do not get why this was working in 1.4 > > > > > > > > >

March 10, 2013

[Pharo-project] migration to FogBugz

by Ben Coman

I just noticed (for example) that https://code.google.com/p/pharo/issues/detail?id=6763 has been migrated as https://pharo.fogbugz.com/f/cases/6700. Is that change of issue number a concern to break the convention of slice names matching issue numbers as well as historical issue cross referencing? hope I'm missing something.. regards -ben

March 10, 2013

[Pharo-project] Dr. Geo in your native language

by Hilaire Fernandes

Hello, I am looking for proposing Dr. Geo in more native languages. It is now more or less completely translated in about 12 languages. If you want to translate, you can give a try at http://translate.drgeo.eu. Thanks Hilaire -- Dr. Geo http://drgeo.eu

March 10, 2013

Re: [Pharo-project] GSoC13: Google Summer of Code started, your ideas please!

by Serge Stinckwich

Dear all, I would like to propose something related to SciSmalltalk: https://github.com/SergeStinckwich/SciSmalltalk This is really important if we want Smalltalk to be accepted in the scientific community. I want to submit a project that will only focus on ODE (Ordinary Differential Equation) solving. Some preliminary works has already be done in this direction. I would like to know if a GSOC student could be hosted in a lab ? Regards, On Sat, Mar 9, 2013 at 1:03 PM, Janko MivÅ¡ek <janko.mivsek(a)eranova.si> wrote: > Dear Smalltalkers, > > Time for your cool project ideas on this year Smalltalk GSoC! > > For now just express any idea you have here on the mailing list. Later > we will together develop it to be in complete format together with two > mentors needed. Deadline is end of Mart, so we have three weeks of time. > To see how fully developed ideas look like please look at 2012 ones at: > http://gsoc2012.esug.org/ideas. > > Note also that students yourselves can propose a GSoC project. So if you > like to be a student on this year GSoC and have a nice idea, don't be > shy and propose it here! The community will listen you and guide to the > really nicely proposed project. Last year 6 student proposed projects > were accepted and finished successfully! > > For the community, start looking around for students. Think about how to > approach the universities near by you, do you know who to contact > there, etc. > > We are namely preparing an application to this year Smalltalk Google > Summer of Code under ESUG umbrella, as last year. If accepted, Google > will pay few stipendiums to students on our Smalltalk projects. > > More on our special Smalltalk GSoC 2013 website: > > http://gsoc2013.esug.org > > I'm specially inviting mentors of all past GSoCs to rejoin the mentors > mailing list, where we discuss all details about this year GSoC: > > http://groups.google.com/group/smalltalk-gsoc-mentors > > While students interested on GSoC please join a special Smalltalk GSoC > mailing list for you: > > http://groups.google.com/group/smalltalk-gsoc-students > > Best regards > Janko > > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://doesnotunderstand.org/

March 10, 2013

Re: [Pharo-project] [Pharo-users] GSoC13: Google Summer of Code started, your ideas please!

by stephane ducasse

Ok I will send other descriptions a plain text. I still continue to believe that we can create a real eco system where people can make money. Stef > Hi Stef, > > Dne 09. 03. 2013 21:47, piÅ¡e StÃ©phane Ducasse: > >> I sent some topics now I think that it would be better to edit directly the web site because else somebody will have to do it again. >> So if you need I can edit directly a form. > > Direct editing will certainly be a better solution, just that for now > only the whole ideas page will be editable and not through a form for > each idea separately (I don't have a time right now for adding that). > > To edit a whole page publicly I need to recheck the locking mechanism > first, then OpenID authentication currently don't work because of a > expired Google's cert, so ... let me put ideas by me for now, later > I'll try to open editing more broadly. > > Best regards > Janko > > >> >> Stef >> >> >>> Hi Stef, >>> >>> Post on the mailing list for each project idea by following this template: >>> >>> Level: (beginner, intermediate, advanced) >>> >>> Possible mentor: >>> >>> Possible second mentor: >>> >>> Description >>> >>> Technical Details >>> >>> Benefits to the Student >>> >>> Benefits to the Community >>> >>> Best regards >>> Janko >>> >>> Dne 09. 03. 2013 13:46, piÅ¡e stephane ducasse: >>>> Hi janko >>>> >>>> How do you want to proceed for the topics? >>>> I have a list of topics now where do we write them. >>>> >>>> - tool support rewrite rules >>>> - new generation debugger >>>> - new change model and session manager (with martin dias) >>>> - improving roassal (with alexandre bergel et vanessa pena) >>>> - improving eyesee (with alexandre bergel et vanessa pena) >>>> - support touch event >>>> - UIPainter (with esteban lorenzano) >>>> - New widgets >>>> >>>> >>>> Stef >>>> >>>> >>>>> Dear Smalltalkers, >>>>> >>>>> Time for your cool project ideas on this year Smalltalk GSoC! >>>>> >>>>> For now just express any idea you have here on the mailing list. Later >>>>> we will together develop it to be in complete format together with two >>>>> mentors needed. Deadline is end of Mart, so we have three weeks of time. >>>>> To see how fully developed ideas look like please look at 2012 ones at: >>>>> http://gsoc2012.esug.org/ideas. >>>>> >>>>> Note also that students yourselves can propose a GSoC project. So if you >>>>> like to be a student on this year GSoC and have a nice idea, don't be >>>>> shy and propose it here! The community will listen you and guide to the >>>>> really nicely proposed project. Last year 6 student proposed projects >>>>> were accepted and finished successfully! >>>>> >>>>> For the community, start looking around for students. Think about how to >>>>> approach the universities near by you, do you know who to contact >>>>> there, etc. >>>>> >>>>> We are namely preparing an application to this year Smalltalk Google >>>>> Summer of Code under ESUG umbrella, as last year. If accepted, Google >>>>> will pay few stipendiums to students on our Smalltalk projects. >>>>> >>>>> More on our special Smalltalk GSoC 2013 website: >>>>> >>>>> http://gsoc2013.esug.org >>>>> >>>>> I'm specially inviting mentors of all past GSoCs to rejoin the mentors >>>>> mailing list, where we discuss all details about this year GSoC: >>>>> >>>>> http://groups.google.com/group/smalltalk-gsoc-mentors >>>>> >>>>> While students interested on GSoC please join a special Smalltalk GSoC >>>>> mailing list for you: >>>>> >>>>> http://groups.google.com/group/smalltalk-gsoc-students >>>>> >>>>> Best regards >>>>> Janko >>>>> >>>>> >>>>> -- >>>>> Janko MivÅ¡ek >>>>> Aida/Web >>>>> Smalltalk Web Application Server >>>>> http://www.aidaweb.si >>>>> >>>> >>>> >>>> >>> >>> -- >>> Janko MivÅ¡ek >>> Aida/Web >>> Smalltalk Web Application Server >>> http://www.aidaweb.si >>> >> >> >> > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si >

March 10, 2013

Re: [Pharo-project] [Pharo-users] GSoC13: Google Summer of Code started, your ideas please!

by Janko MivÅ¡ek

Hi Stef, Dne 09. 03. 2013 21:47, piÅ¡e StÃ©phane Ducasse: > I sent some topics now I think that it would be better to edit directly the web site because else somebody will have to do it again. > So if you need I can edit directly a form. Direct editing will certainly be a better solution, just that for now only the whole ideas page will be editable and not through a form for each idea separately (I don't have a time right now for adding that). To edit a whole page publicly I need to recheck the locking mechanism first, then OpenID authentication currently don't work because of a expired Google's cert, so ... let me put ideas by me for now, later I'll try to open editing more broadly. Best regards Janko > > Stef > > >> Hi Stef, >> >> Post on the mailing list for each project idea by following this template: >> >> Level: (beginner, intermediate, advanced) >> >> Possible mentor: >> >> Possible second mentor: >> >> Description >> >> Technical Details >> >> Benefits to the Student >> >> Benefits to the Community >> >> Best regards >> Janko >> >> Dne 09. 03. 2013 13:46, piÅ¡e stephane ducasse: >>> Hi janko >>> >>> How do you want to proceed for the topics? >>> I have a list of topics now where do we write them. >>> >>> - tool support rewrite rules >>> - new generation debugger >>> - new change model and session manager (with martin dias) >>> - improving roassal (with alexandre bergel et vanessa pena) >>> - improving eyesee (with alexandre bergel et vanessa pena) >>> - support touch event >>> - UIPainter (with esteban lorenzano) >>> - New widgets >>> >>> >>> Stef >>> >>> >>>> Dear Smalltalkers, >>>> >>>> Time for your cool project ideas on this year Smalltalk GSoC! >>>> >>>> For now just express any idea you have here on the mailing list. Later >>>> we will together develop it to be in complete format together with two >>>> mentors needed. Deadline is end of Mart, so we have three weeks of time. >>>> To see how fully developed ideas look like please look at 2012 ones at: >>>> http://gsoc2012.esug.org/ideas. >>>> >>>> Note also that students yourselves can propose a GSoC project. So if you >>>> like to be a student on this year GSoC and have a nice idea, don't be >>>> shy and propose it here! The community will listen you and guide to the >>>> really nicely proposed project. Last year 6 student proposed projects >>>> were accepted and finished successfully! >>>> >>>> For the community, start looking around for students. Think about how to >>>> approach the universities near by you, do you know who to contact >>>> there, etc. >>>> >>>> We are namely preparing an application to this year Smalltalk Google >>>> Summer of Code under ESUG umbrella, as last year. If accepted, Google >>>> will pay few stipendiums to students on our Smalltalk projects. >>>> >>>> More on our special Smalltalk GSoC 2013 website: >>>> >>>> http://gsoc2013.esug.org >>>> >>>> I'm specially inviting mentors of all past GSoCs to rejoin the mentors >>>> mailing list, where we discuss all details about this year GSoC: >>>> >>>> http://groups.google.com/group/smalltalk-gsoc-mentors >>>> >>>> While students interested on GSoC please join a special Smalltalk GSoC >>>> mailing list for you: >>>> >>>> http://groups.google.com/group/smalltalk-gsoc-students >>>> >>>> Best regards >>>> Janko >>>> >>>> >>>> -- >>>> Janko MivÅ¡ek >>>> Aida/Web >>>> Smalltalk Web Application Server >>>> http://www.aidaweb.si >>>> >>> >>> >>> >> >> -- >> Janko MivÅ¡ek >> Aida/Web >> Smalltalk Web Application Server >> http://www.aidaweb.si >> > > > -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

March 10, 2013