[Pharo-project] Issue 3623 in pharo: Pharo 1.2 OCompletion in browser not good
Status: Accepted Owner: laurent@gmail.com New issue 3623 by laurent@gmail.com: Pharo 1.2 OCompletion in browser not good http://code.google.com/p/pharo/issues/detail?id=3623 In Pharo 1.2 there's inconsistency in auto-completion between Workspace and Browser. In Workspace, if I type |builder| builder := UITheme builder. builder newText then press the tab key, I have the method newTextEntryFor:getText:setText:help: in the list (which is what I want). In the browser, I get only the method defined in UITheme (and builder is an instance of ComposableMorph). It's very disturbing (for me). May be there's a way to tell completion to look for all implementors ?
Re: [Pharo-project] Introducing smallUML: a little project to help us document :)
How's MinimalConnectors coming? I thought I saw an announcement somewhere, but I couldn't find it searching the list. Also, I tried loading it in Pharo 1.1.1 (both each package individually and via the ConfigurationOf) and got an error that it depended on CategoryDiagramsHolder. When I made a dummy class for that, it loaded okay, but I wasn't sure how to use it. I want to connect text boxes together and keep them that way as I move them around. Thanks. Sean -- View this message in context: http://forum.world.st/Introducing-smallUML-a-little-project-to-help-us-document-tp2331341p3247000.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Re: [Pharo-project] Easy access on pharo-project.org
On Jan 26, 2011, at 3:45 PM, Adrian Lienhard wrote: > Implemented as redirects this is possible. Making the build server available > under, say, ci.pharo-project.org should also be possible (without a redirect) > since we have access to the server (I assume). It's a server managed by INRIA IT, though... so we need to check. > With Google project this is obviously not possible. > > The question is where to implement the redirects. Marcus, can Hetzner, who > hosts the DNS, do this? > they just provide DNS... is this possible just with DNS? > Adrian > > On Jan 26, 2011, at 13:44 , Sven Van Caekenberghe wrote: > >> +1 >> >> On a related note, I just discovered that pharo.st actually does the right >> thing, cool! >> I don't know how things are organized, but at least the pharo.st domain >> seems to be owned by Marcus. >> Anyway, in some respects it seems like a better name. >> >> Sven >> >> On 26 Jan 2011, at 11:14, Torsten Bergmann wrote: >> >>> We have the shortcut to the collaborative book: >>> >>> http://book.pharo-project.org >>> >>> >>> Would it be possible: >>> >>> 1. to access the build server >>> https://pharo-ic.lille.inria.fr/hudson/ >>> >>> under a simple name like: >>> >>> http://hudson.pharo.org or >>> http://ci.pharo.org (ci = continuos integration) >>> >>> 2. to access the issue tracker >>> http://code.google.com/p/pharo/issues >>> under >>> >>> http://issues.pharo-project.org or >>> http://bugs.pharo-project.org >>> >>> 3. to access the wiki >>> http://code.google.com/p/pharo/w/list >>> under >>> http://wiki.pharo-project.org >>> >>> 4. And the book page >>> http://pharo-project.org/documentation/tutorials-books >>> has no reference to the collaborative book >>> http://book.pharo-project.org >>> >>> Thx >>> T. >>> -- >>> GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit >>> gratis Handy-Flat! http://portal.gmx.net/de/go/dsl >>> >> >> > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Re: [Pharo-project] Issue 2586 in pharo: line breaks lost on Linux when copying from one pharo image to another
Updates: Status: Closed Comment #10 on issue 2586 by marcus.d...@gmail.com: line breaks lost on Linux when copying from one pharo image to another http://code.google.com/p/pharo/issues/detail?id=2586 in 13030
[Pharo-project] [update 1.3] #13030
13030 - Issue 2586: line breaks lost on Linux when copying from one pharo image to another -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
[Pharo-project] [ANN] Alien on Pharo 1.2
Hi all,
I just committed new versions of Alien on squeaksource to make it run on 1.2
I also modified the ConfigurationOfAlien to easily load it:
(ConfigurationOfAlien project version: 'Pharo 1.1') load
(ConfigurationOfAlien project version: 'Pharo 1.2') load
(ConfigurationOfAlien project version: 'Pharo 1.1') load: {'All'. 'MacOSX'}
(ConfigurationOfAlien project version: 'Pharo 1.2') load: {'All'. 'MacOSX'}
#Luc
[Pharo-project] react on low space
Hi guys Is there an easy way to react on low space? Something like: SmalltalkImage isSpaceLow ifTrue: [ ] The reason I'm asking is that I have a background process running that causes a low space condition but I never get around to opening the debugger and the image crashes on me. So for debugging purposes I'd like to periodically check the space that is left or alternatively be notified if low space is signalled. Any ideas? Thanks, Max
[Pharo-project] Where is the new mechanism for save preferences on Pharo 1.2??
Hi I´m using my deployer tool on Pharo 1.2 Core RC, but get a error when I try save my preferences. In last version of Pharo I could for example call Preferences>>savePersonalPreferences method. There´s equivalent on new Pharo? Many thanks for the help Regards. -- View this message in context: http://forum.world.st/Where-is-the-new-mechanism-for-save-preferences-on-Pharo-1-2-tp3247079p3247079.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Re: [Pharo-project] [ANN] Alien on Pharo 1.2
That sounds really nice.
Just a question: Is Alien only working on Mac?
Cheers,
Doru
On 30 Jan 2011, at 13:05, Luc Fabresse wrote:
> Hi all,
>
> I just committed new versions of Alien on squeaksource to make it run on 1.2
> I also modified the ConfigurationOfAlien to easily load it:
>
> (ConfigurationOfAlien project version: 'Pharo 1.1') load
>
> (ConfigurationOfAlien project version: 'Pharo 1.2') load
>
> (ConfigurationOfAlien project version: 'Pharo 1.1') load: {'All'. 'MacOSX'}
>
> (ConfigurationOfAlien project version: 'Pharo 1.2') load: {'All'. 'MacOSX'}
>
> #Luc
--
www.tudorgirba.com
"Speaking louder won't make the point worthier."
Re: [Pharo-project] Where is the new mechanism for save preferences on Pharo 1.2??
I do not know the answer but look for Settings Stef On Jan 30, 2011, at 1:17 PM, nullPointer wrote: > > Hi > > I´m using my deployer tool on Pharo 1.2 Core RC, but get a error when I try > save my preferences. In last version of Pharo I could for example call > Preferences>>savePersonalPreferences method. There´s equivalent on new > Pharo? Many thanks for the help > > Regards. > -- > View this message in context: > http://forum.world.st/Where-is-the-new-mechanism-for-save-preferences-on-Pharo-1-2-tp3247079p3247079.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >
Re: [Pharo-project] [ANN] Alien on Pharo 1.2
2011/1/30 Tudor Girba
> That sounds really nice.
>
> Just a question: Is Alien only working on Mac?
>
It just requires the I32ABI VM plugin which is included in the Cog VM as
Eliot told me.
So it should work on linux+cog but I didn't test it recently.
Not sure this plugin is included in the regular unix VM.
#Luc
>
> Cheers,
> Doru
>
>
> On 30 Jan 2011, at 13:05, Luc Fabresse wrote:
>
> > Hi all,
> >
> > I just committed new versions of Alien on squeaksource to make it run on
> 1.2
> > I also modified the ConfigurationOfAlien to easily load it:
> >
> > (ConfigurationOfAlien project version: 'Pharo 1.1') load
> >
> > (ConfigurationOfAlien project version: 'Pharo 1.2') load
> >
> > (ConfigurationOfAlien project version: 'Pharo 1.1') load: {'All'.
> 'MacOSX'}
> >
> > (ConfigurationOfAlien project version: 'Pharo 1.2') load: {'All'.
> 'MacOSX'}
> >
> > #Luc
>
> --
> www.tudorgirba.com
>
> "Speaking louder won't make the point worthier."
>
>
>
Re: [Pharo-project] Vision
I DO like this Vision. I remember myself about 8 years ago trying to give my first steps in Smalltalk on my own. Despite I had solid OOP knowledge it took a while to understand that there was no "main" function. All my experience was with Java and C++ and I couldn't understand where was the entry point of my application if there were no main. Of course, today things are totally different, there are many resources on the web but I think that we still can improve that, implementing improvements in the environment and generating more and better training resources. Saludos! Nico. blog: nicopaez.wordpress.com > Hi guys > > Some days ago we were chatting with igor and he made an interesting remark > about a kind of hidden philosophy > behind pharo: the idea that we systematically want to make the system > better. > In fact I realized that what we are doing is to make a system nice, robust > and powerful so that everybody can use > to realize their goals. But we want to have a system where not only smart > guys can manage to do something with it but also > less talented people like me (I know that some of you will say but stef you > are good, I'm a newbie in a lot of domains but > I learn fast if I can get a chance to avoid to bump on the walls). I want a > system that let me learn from itself. > I think that lot of things fall naturally in place from this vision > (documentation, oo practices - not having car inheriting from wheel, tests > comments, adequate abstractions, modularity). I want a system that > everybody can nicely build his own software. > So in short I want pharo to be like a nice garden with greenhouses for > building new garden with tools versus a jungle where > only skilled adventurers can make it through. > > Stef > > >
Re: [Pharo-project] Vision
I think the main point that we are not making software for some virtual users. We are making it for ourselves. For example - i was needed some level of guarantees from image when running in headless mode, so i can easily detect any problems and address them quickly. This lead me to implementing non-interactive ui manager stuff. So, now when image runs on Hudson server, any unexpected errors/behavior could be observed and fixed afterwards. -- Best regards, Igor Stasenko AKA sig.
Re: [Pharo-project] Issue 3613 in pharo: Hudson 1.2 dev : testOBAutocategorizeCommandOverride
Updates: Status: Duplicate Mergedinto: 3471 Comment #1 on issue 3613 by marcus.d...@gmail.com: Hudson 1.2 dev : testOBAutocategorizeCommandOverride http://code.google.com/p/pharo/issues/detail?id=3613 (No comment was entered for this change.)
Re: [Pharo-project] Issue 3471 in pharo: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride
Updates: Cc: marianopeck Comment #7 on issue 3471 by marcus.d...@gmail.com: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride http://code.google.com/p/pharo/issues/detail?id=3471 Issue 3613 has been merged into this issue.
Re: [Pharo-project] Issue 3471 in pharo: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride
Comment #8 on issue 3471 by marcus.d...@gmail.com: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride http://code.google.com/p/pharo/issues/detail?id=3471 Issue 3613 has an (alternative?) fix
Re: [Pharo-project] Issue 3619 in pharo: Hudson Pharo 1.2dev OBBrowser keybinding
Updates: Status: Duplicate Mergedinto: 3470 Comment #1 on issue 3619 by marcus.d...@gmail.com: Hudson Pharo 1.2dev OBBrowser keybinding http://code.google.com/p/pharo/issues/detail?id=3619 (No comment was entered for this change.)
[Pharo-project] TODO 1.2
Hi, So for a release, we need to fix the following bugs: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage Now as these are all problems of packages, not of the Core, I can not just commit to core. So we need to actually fix the package in the place where the package is loaded from. (potentially by discussion this with the maintainer) This is something anyone can do. We do not need to wait for Mariano to ne back from holiday (which will be in 3 weeks), nor will I do this. I am a bit sick of 1.2... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Re: [Pharo-project] Issue 3470 in pharo: [Failing Tests] OBKeyBindingsTest
Comment #5 on issue 3470 by marcus.d...@gmail.com: [Failing Tests] OBKeyBindingsTest http://code.google.com/p/pharo/issues/detail?id=3470 Issue 3619 has been merged into this issue.
Re: [Pharo-project] Issue 3470 in pharo: [Failing Tests] OBKeyBindingsTest
Comment #6 on issue 3470 by marcus.d...@gmail.com: [Failing Tests] OBKeyBindingsTest http://code.google.com/p/pharo/issues/detail?id=3470 Issue 3619 proposed a fix (I merged it into this report)
Re: [Pharo-project] Issue 3469 in pharo: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy
Updates: Status: FixProposed Comment #6 on issue 3469 by marcus.d...@gmail.com: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy http://code.google.com/p/pharo/issues/detail?id=3469 (No comment was entered for this change.)
Re: [Pharo-project] TODO 1.2
Marcus Can I suggest that we really remove the non show stopper? and I'm sorry but we cannot maintain packages we do not know. Lukas could you integrate the fix I did for OB? Stef > Hi, > > So for a release, we need to fix the following bugs: > > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage > > Now as these are all problems of packages, not of the Core, I can not just > commit > to core. > > So we need to actually fix the package in the place where the package is > loaded > from. (potentially by discussion this with the maintainer) > > This is something anyone can do. We do not need to wait for Mariano to ne > back > from holiday (which will be in 3 weeks), nor will I do this. I am a bit sick > of 1.2... > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >
Re: [Pharo-project] Issue 3470 in pharo: [Failing Tests] OBKeyBindingsTest
Updates: Status: FixProposed Comment #7 on issue 3470 by marcus.d...@gmail.com: [Failing Tests] OBKeyBindingsTest http://code.google.com/p/pharo/issues/detail?id=3470 (No comment was entered for this change.)
Re: [Pharo-project] Issue 3599 in pharo: Serial Port
On Fri, Jan 28, 2011 at 09:33:50AM +0700, Serge Stinckwich wrote: > On Fri, Jan 28, 2011 at 9:12 AM, David T. Lewis wrote: > > On Wed, Jan 26, 2011 at 03:09:14PM +, ph...@googlecode.com wrote: > >> Status: Accepted > >> Owner: stephane...@gmail.com > >> Labels: Milestone-1.3 > >> > >> New issue 3599 by stephane...@gmail.com: Serial Port > >> http://code.google.com/p/pharo/issues/detail?id=3599 > >> > >> Hello > >> We are developing software to interact with small robots for educational > >> purposes. To do this we need to use the serial port. SerialPort class that > >> includes Pharo does not work on mac or linux, because it?s not ?able to > >> open ports by name. > > > > FYI, the primitives for named serial ports are now in the standard VM > > (maybe not yet in Cog, but it is a small change). If someone would like > > to test on a Linux platform, try using any recent build of the standard > > VM or use the latest 4.4.7.2357 unix VM from http://squeakvm.org/unix/. > > > > The image changes to SerialPort are simple. You can either copy changes > > from Squeak or get the orginal change sets from the Mantis report at > > http://bugs.squeak.org/view.php?id=7266. > > > > The named serial port work was contributed by Severin Lemaignan > > and I helped with some of the integration. > > Anything that I did is MIT licensed. > > Hi David, > > there is a issue in the Pharo bug tracker since several months for the > integration of this changes into Pharo here: > http://code.google.com/p/pharo/issues/detail?id=1057 > > Could we integrate these changes in 1.2 as there is no licence problems at > all. > David and S?verin could you sign the licence agreement, just to be > sure everything is ok. Just to be clear, the status of named serial port support is: - VM support for named serial ports is present in the standard VM. - VM support for named serial ports is not yet included in Cog. - Pharo developers should IMO include S?verin's SerialPort changes, but I am not involved in this and there are no changes to SerialPort with my author initials either in Squeak or in the change sets on Mantis 7266. HTH, Dave > > The quality of the code is not really good, there is a lot of isString > everywhere in order to test if the port is a number or a string > regarding the OS platform used: > > SerialPort>>close > "Close the serial port. Do nothing if the port is not open." > port > ifNotNil: [port isString ifTrue:[self primClosePortByName: port] > ifFalse:[self primClosePort:port]]. > port := nil > > I think we need to polish it in order maybe to use only strings. Why > not used string like 'COM1' for a windows platform and '/dev/ttyS*' > for Linux ? Any comments about that ? > > Regards, > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/
Re: [Pharo-project] Issue 3471 in pharo: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride
Updates: Status: FixProposed Comment #9 on issue 3471 by marcus.d...@gmail.com: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride http://code.google.com/p/pharo/issues/detail?id=3471 (No comment was entered for this change.)
Re: [Pharo-project] Issue 3589 in pharo: ClassComment in OB
Updates: Status: FixProposed Comment #3 on issue 3589 by marcus.d...@gmail.com: ClassComment in OB http://code.google.com/p/pharo/issues/detail?id=3589 (No comment was entered for this change.)
Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes
Comment #17 on issue 3583 by marcus.d...@gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 And what about 1.2?
Re: [Pharo-project] Issue 3623 in pharo: Pharo 1.2 OCompletion in browser not good
Updates: Labels: Milestone-1.3-DevImage Comment #1 on issue 3623 by marcus.d...@gmail.com: Pharo 1.2 OCompletion in browser not good http://code.google.com/p/pharo/issues/detail?id=3623 (No comment was entered for this change.)
Re: [Pharo-project] Issue 3623 in pharo: Pharo 1.2 OCompletion in browser not good
Updates: Labels: -Milestone-1.3-DevImage Milestone-1.2-DevImage Comment #2 on issue 3623 by marcus.d...@gmail.com: Pharo 1.2 OCompletion in browser not good http://code.google.com/p/pharo/issues/detail?id=3623 (No comment was entered for this change.)
Re: [Pharo-project] How to take advantage of SimpleMorphic
Stéphane Ducasse wrote: I started to look inside SimpleMorphic to find a path to make progress and this is not clear to me. For example if I want to remove PopUpMenu and the rest I would have to rely on UITheme or something like that and the problem is that UITheme so far does not work for SimpleMorphic. So I could - do not think to remove PopUp right now or - start building a SimpleMorphic Theme which returns SM objects. Returning SM objects sounds reasonable to me. Now the migration path is still not clear to me. Stef Neither to me. It requires a deep knowledge of the changes done in Pharo, and the reasons behind them. I lack all this. Cheers, Juan Vuletich
[Pharo-project] SoundSettings reference in Sound?
Hi guy when I take 1.2 latest version I see that there are reference to SoundSetting in SoundPlayer. Now I cannot find any definition of this setting. Henrik I saw that you work on setting in sounds. Does it ring a bell for you? Stef resumePlaying: aSound quickStart: quickStart "Start playing the given sound without resetting it; it will resume playing from where it last stopped. If quickStart is true, then try to start playing the given sound immediately." | doQuickStart | SoundSettings soundsEnabled ifFalse: [^ self]. doQuickStart := quickStart. SoundSettings soundQuickStart ifFalse: [doQuickStart := false]. PlayerProcess == nil ifTrue: [ self canStartPlayer ifFalse: [^ self]. ^self startUpWithSound: aSound]. PlayerSemaphore critical: [ (ActiveSounds includes: aSound) ifTrue: [doQuickStart := false] ifFalse: [ doQuickStart ifFalse: [ActiveSounds add: aSound]]]. "quick-start the given sound, unless the sound player has just started" doQuickStart ifTrue: [self startPlayingImmediately: aSound].
Re: [Pharo-project] Issue 3620 in pharo: Settings: OCompletion settings appear twice
Updates: Status: FixProposed Labels: Milestone-1.2-DevImage Comment #2 on issue 3620 by marcus.d...@gmail.com: Settings: OCompletion settings appear twice http://code.google.com/p/pharo/issues/detail?id=3620 (No comment was entered for this change.)
Re: [Pharo-project] Issue 3465 in pharo: Hundson OneClick: Does not show Mac menues
Updates: Labels: -Milestone-1.3 -Milestone-1.3 Milestone-1.2-DevImage Comment #4 on issue 3465 by marcus.d...@gmail.com: Hundson OneClick: Does not show Mac menues http://code.google.com/p/pharo/issues/detail?id=3465 But the one-click of Hudson does not (yet) use cog.
Re: [Pharo-project] Issue 3469 in pharo: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy
Updates: Cc: renggli Comment #7 on issue 3469 by stephane...@gmail.com: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy http://code.google.com/p/pharo/issues/detail?id=3469 What should we do here? Should we commit to shout? OB?
[Pharo-project] [update 1.2] #12326
12326 - - RecentMessage list should be reset on ReleaseClean (backport from 1.3) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Re: [Pharo-project] Issue 3470 in pharo: [Failing Tests] OBKeyBindingsTest
Comment #8 on issue 3470 by stephane...@gmail.com: [Failing Tests] OBKeyBindingsTest http://code.google.com/p/pharo/issues/detail?id=3470 Can we publish in OB repository? What is the solution? Should we clone the repository?
Re: [Pharo-project] Issue 3471 in pharo: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride
Comment #10 on issue 3471 by stephane...@gmail.com: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride http://code.google.com/p/pharo/issues/detail?id=3471 Same question as with previous entry: can we commit to OB and else do we fork it?
Re: [Pharo-project] Issue 3482 in pharo: InterimSoundMorph references to SketchMorph
Comment #4 on issue 3482 by stephane...@gmail.com: InterimSoundMorph references to SketchMorph http://code.google.com/p/pharo/issues/detail?id=3482 I'm working on it InterimSoundMorph>>addGraphic graphic := self speakerGraphic asMorph. graphic position: bounds center - (graphic extent // 2). self addMorph: graphic. solves a part of the problem. I'm checking for the rest
Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes
Comment #18 on issue 3583 by stephane...@gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 not a showstopper so for 1.3. Stef
Re: [Pharo-project] Issue 3465 in pharo: Hundson OneClick: Does not show Mac menues
Updates: Labels: -Milestone-1.2-DevImage Type-ReportDefect Comment #5 on issue 3465 by siguc...@gmail.com: Hundson OneClick: Does not show Mac menues http://code.google.com/p/pharo/issues/detail?id=3465 Note, this bug related to Cog VM only. AFAIK, an official Squeak VM works fine with menus (Squeak 4.2.4b1) This issue is not show stopper for releasing Pharo 1.2 , because its not related to Pharo itself, but to VM. And let me remind you that Cog currently are not officially supported VM, and there are no obligations from Pharo to make sure it works correctly under Cog VM. - removed from 1.2 milestone
[Pharo-project] about Sound and setting :(
Hi guys loadSoundEnabled self loadSetting: #soundEnabled withBlock: [SoundService soundEnabled: nil]. since mariano is away and I do not know what was done in Sound, I'm trying but this is not simple when you do not know what was the intention. The method is: resumePlaying: aSound quickStart: quickStart "Start playing the given sound without resetting it; it will resume playing from where it last stopped. If quickStart is true, then try to start playing the given sound immediately." | doQuickStart | SoundSettings soundsEnabled ifFalse: [^ self]. doQuickStart := quickStart. SoundSettings soundQuickStart ifFalse: [doQuickStart := false]. PlayerProcess == nil ifTrue: [ self canStartPlayer ifFalse: [^ self]. ^self startUpWithSound: aSound]. PlayerSemaphore critical: [ (ActiveSounds includes: aSound) ifTrue: [doQuickStart := false] ifFalse: [ doQuickStart ifFalse: [ActiveSounds add: aSound]]]. "quick-start the given sound, unless the sound player has just started" doQuickStart ifTrue: [self startPlayingImmediately: aSound]. it refers to SoundSettings and there is no such a thing. There is no implementors of soundsEnabled So I tried to understand the changes made in Slice-3566 Now the question is do we want SoundService to play the role of a setting provider? Originally I thought to put it in BaseSoundSystem. But the code of henrik seems to use SoundService. Now BaseSoundSystem register itself as the default sound service. So I'm confused! Help is welcome. Stef
Re: [Pharo-project] Easy access on pharo-project.org
On Jan 30, 2011, at 12:09 , Marcus Denker wrote: > > On Jan 26, 2011, at 3:45 PM, Adrian Lienhard wrote: > >> Implemented as redirects this is possible. Making the build server available >> under, say, ci.pharo-project.org should also be possible (without a >> redirect) since we have access to the server (I assume). > > It's a server managed by INRIA IT, though... so we need to check. > >> With Google project this is obviously not possible. >> >> The question is where to implement the redirects. Marcus, can Hetzner, who >> hosts the DNS, do this? >> > > they just provide DNS... is this possible just with DNS? Not with DNS, but some DNS hosting services offer redirects AFAIK. We can also do redirects with Cmsbox. You would just need to point the third-level domains to us. Let's take that offline... Adrian
Re: [Pharo-project] about Sound and setting :(
So here is a part of the answer Sound should be self contained so BaseSoundSystem could have AbstractSoundSystem subclass: #BaseSoundSystem instanceVariableNames: '' classVariableNames: 'SoundEnabled SoundQuickStart UseThemeSounds' poolDictionaries: '' category: 'Sound-Synthesis' and class level accessor Then we can defined adequate method extension in Sound-Settings that describe the default value Then SoundService should not have state but delegate to the current install class player the SoundService supplier. I hope it makes sense. I will code that. Stef
Re: [Pharo-project] Issue 3382 in pharo: BUG: Class variable creation behavior Inconsistent/incorrect
Updates: Status: FixProposed Comment #3 on issue 3382 by marcus.d...@gmail.com: BUG: Class variable creation behavior Inconsistent/incorrect http://code.google.com/p/pharo/issues/detail?id=3382 (No comment was entered for this change.)
Re: [Pharo-project] Issue 3562 in pharo: Deferred UI messages executed slowly
Updates: Status: FixProposed Comment #2 on issue 3562 by marcus.d...@gmail.com: Deferred UI messages executed slowly http://code.google.com/p/pharo/issues/detail?id=3562 (No comment was entered for this change.)
Re: [Pharo-project] about Sound and setting :(
If somebody wants to have a look here is my solution: - in SoundService I added the possibility to delegate to the registered soundsystem for preferences see package: System-Applications in inbox - I fixed all the references to SoundSettings in Sounds to refer to BaseSoundSystem and BaseSoundSystem is not the hold of the preferences. see Slice-3482 in the inbox Stef On Jan 30, 2011, at 6:59 PM, Stéphane Ducasse wrote: > So here is a part of the answer > > Sound should be self contained so BaseSoundSystem could have > > AbstractSoundSystem subclass: #BaseSoundSystem > instanceVariableNames: '' > classVariableNames: 'SoundEnabled SoundQuickStart UseThemeSounds' > poolDictionaries: '' > category: 'Sound-Synthesis' > > and class level accessor > > Then we can defined adequate method extension in > > Sound-Settings that describe the default value > > Then SoundService should not have state but delegate to the current install > class player the SoundService supplier. > > I hope it makes sense. I will code that. > > Stef > >
Re: [Pharo-project] Issue 3482 in pharo: InterimSoundMorph references to SketchMorph
Comment #5 on issue 3482 by stephane...@gmail.com: InterimSoundMorph references to SketchMorph http://code.google.com/p/pharo/issues/detail?id=3482 Marcus we can integrate System-Applications that I published in the inbox. It makes the logic of SoundService delegating to the BaseSoundSystem. I published a slice for Sound in the inbox too.3482 - in SoundService I added the possibility to delegate to the registered soundsystem for preferences see package: System-Applications in inbox - I fixed all the references to SoundSettings in Sounds to refer to BaseSoundSystem and BaseSoundSystem is not the hold of the preferences.
Re: [Pharo-project] Issue 3623 in pharo: Pharo 1.2 OCompletion in browser not good
It's fixed in http://www.squeaksource.com/OCompletion/OCForOB-ul.5.mcz . Levente On Sun, 30 Jan 2011, ph...@googlecode.com wrote: Status: Accepted Owner: laurent@gmail.com New issue 3623 by laurent@gmail.com: Pharo 1.2 OCompletion in browser not good http://code.google.com/p/pharo/issues/detail?id=3623 In Pharo 1.2 there's inconsistency in auto-completion between Workspace and Browser. In Workspace, if I type |builder| builder := UITheme builder. builder newText then press the tab key, I have the method newTextEntryFor:getText:setText:help: in the list (which is what I want). In the browser, I get only the method defined in UITheme (and builder is an instance of ComposableMorph). It's very disturbing (for me). May be there's a way to tell completion to look for all implementors ?
Re: [Pharo-project] Issue 3623 in pharo: Pharo 1.2 OCompletion in browser not good
Comment #3 on issue 3623 by torsten@astares.de: Pharo 1.2 OCompletion in browser not good http://code.google.com/p/pharo/issues/detail?id=3623 According to Levente this is fixed in http://www.squeaksource.com/OCompletion/OCForOB-ul.5.mcz See http://lists.gforge.inria.fr/pipermail/pharo-project/2011-January/040946.html
Re: [Pharo-project] Issue 3623 in pharo: Pharo 1.2 OCompletion in browser not good
Updates: Status: Fixed Comment #4 on issue 3623 by laurent@gmail.com: Pharo 1.2 OCompletion in browser not good http://code.google.com/p/pharo/issues/detail?id=3623 I've updated ConfigurationOfOmniBrowser
Re: [Pharo-project] does anybody knows who is using StandardToolSet?
Hi, I am not sure what is the current status in this area. Could anyone provide an idea of what is the desired solution? Cheers, Doru On 28 Jan 2011, at 19:35, Igor Stasenko wrote: > On 28 January 2011 19:20, Mariano Martinez Peck wrote: >> yes, check the archives. I opened tickes for that. and I sent several mails. >> Seems no-one has time to do it. >> > we discussed that today. > probably i will take care about it for 1.3.. not sure how soon it will > be but i will :) > >> http://code.google.com/p/pharo/issues/detail?id=1915 >> >> On Fri, Jan 28, 2011 at 10:44 AM, Stéphane Ducasse >> wrote: >>> >>> Because it would be good that it uses a registration mechanism. >>> Hardcoding the classes of the tools is not optimal for example for the new >>> Finder. >>> >>> Stef >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."
Re: [Pharo-project] Issue 3482 in pharo: InterimSoundMorph references to SketchMorph
Comment #6 on issue 3482 by stephane...@gmail.com: InterimSoundMorph references to SketchMorph http://code.google.com/p/pharo/issues/detail?id=3482 So apparently I should move the behavior from BaseSoundSystem to AsbtractSoundSystem. Then there is a problem since the registeredClasses contain instances So I will fix that too.
[Pharo-project] Beware, self environment is a SystemDictionary, not a SmalltalkImage
Untill recent past, Smalltalk was a SystemDictionary representing both the namespace and the System. It was bloated with many messages, and sending messages like: self environment garbageCollect. was correct. Now, self environment is supposed to answer the namespace object (a SystemDictionary) not the system object (a SmalltalkImage). So, some usages are not correct anymore. See for example #removeUninstantiatedSubclassesSilently. Fortunately, this message is unsent (quite dangerous isn't it ?). But IMHO, all senders of #environment should be reviewed. Nicolas
Re: [Pharo-project] Issue 3482 in pharo: InterimSoundMorph references to SketchMorph
Comment #7 on issue 3482 by stephane...@gmail.com: InterimSoundMorph references to SketchMorph http://code.google.com/p/pharo/issues/detail?id=3482 I published a new Slice named 3482-FixSoundService It is probably necessary to do a SoundService reset (newly introduced method) and DummySoundSystem initialize. as postload action Then I published another slice
Re: [Pharo-project] Beware, self environment is a SystemDictionary, not a SmalltalkImage
Hi nicolas did you check in pharo because if I remember correctly I spent a lot of time doing such a kind of review and fixes? Stef On Jan 30, 2011, at 9:43 PM, Nicolas Cellier wrote: > Untill recent past, Smalltalk was a SystemDictionary representing both > the namespace and the System. > It was bloated with many messages, and sending messages like: > self environment garbageCollect. > was correct. > > Now, self environment is supposed to answer the namespace object (a > SystemDictionary) not the system object (a SmalltalkImage). > So, some usages are not correct anymore. > > See for example #removeUninstantiatedSubclassesSilently. > Fortunately, this message is unsent (quite dangerous isn't it ?). > But IMHO, all senders of #environment should be reviewed. > > Nicolas >
[Pharo-project] [update 1.2] #12327
12327 - - Issue 3482: InterimSoundMorph references to SketchMorph. Fixing the SoundService registration + making sure that it delegates to the registered sound system when available. After the Sound packages can be updated. Marcus I published the other sounds fixes in the sound packages. Now I do not know how the dev image is specified. May be the script should be changed to load the new packages versions I published. Do you know where is this script? Stef
[Pharo-project] Issue 3624 in pharo: LeftOver of Smalltalk and SystemDictionary
Status: Accepted Owner: stephane...@gmail.com Labels: Milestone-1.3 New issue 3624 by stephane...@gmail.com: LeftOver of Smalltalk and SystemDictionary http://code.google.com/p/pharo/issues/detail?id=3624 there are wrong messages sent to self environment here garbageCollect. removeUninstantiatedSubclassesSilently "Remove the classes of any subclasses that have neither instances nor subclasses. Answer the number of bytes reclaimed" "Player removeUninstantiatedSubclassesSilently" | candidatesForRemoval oldFree | oldFree := self environment garbageCollect. candidatesForRemoval := self subclasses select: [:c | (c instanceCount = 0) and: [c subclasses size = 0]]. candidatesForRemoval do: [:c | c removeFromSystem]. ^ self environment garbageCollect - oldFree
Re: [Pharo-project] Beware, self environment is a SystemDictionary, not a SmalltalkImage
No, I was just browsing Kernel differences with MC from Squeak and found this usage in Pharo/#removeUninstantiatedSubclassesSilently. Nicolas 2011/1/30 Stéphane Ducasse : > Hi nicolas > > did you check in pharo because if I remember correctly I spent a lot of time > doing such a kind of review > and fixes? > > Stef > > On Jan 30, 2011, at 9:43 PM, Nicolas Cellier wrote: > >> Untill recent past, Smalltalk was a SystemDictionary representing both >> the namespace and the System. >> It was bloated with many messages, and sending messages like: >> self environment garbageCollect. >> was correct. >> >> Now, self environment is supposed to answer the namespace object (a >> SystemDictionary) not the system object (a SmalltalkImage). >> So, some usages are not correct anymore. >> >> See for example #removeUninstantiatedSubclassesSilently. >> Fortunately, this message is unsent (quite dangerous isn't it ?). >> But IMHO, all senders of #environment should be reviewed. >> >> Nicolas >> > > >
Re: [Pharo-project] Issue 3482 in pharo: InterimSoundMorph references to SketchMorph
Updates: Status: FixedProposed Labels: Milestone-1.3 Comment #8 on issue 3482 by stephane...@gmail.com: InterimSoundMorph references to SketchMorph http://code.google.com/p/pharo/issues/detail?id=3482 I integrate the core part in 12327
Re: [Pharo-project] Beware, self environment is a SystemDictionary, not a SmalltalkImage
Ok thanks. I verified them all and published a fix for that one. Stef On Jan 30, 2011, at 10:07 PM, Nicolas Cellier wrote: > No, I was just browsing Kernel differences with MC from Squeak and > found this usage in Pharo/#removeUninstantiatedSubclassesSilently. > > Nicolas > > 2011/1/30 Stéphane Ducasse : >> Hi nicolas >> >> did you check in pharo because if I remember correctly I spent a lot of time >> doing such a kind of review >> and fixes? >> >> Stef >> >> On Jan 30, 2011, at 9:43 PM, Nicolas Cellier wrote: >> >>> Untill recent past, Smalltalk was a SystemDictionary representing both >>> the namespace and the System. >>> It was bloated with many messages, and sending messages like: >>> self environment garbageCollect. >>> was correct. >>> >>> Now, self environment is supposed to answer the namespace object (a >>> SystemDictionary) not the system object (a SmalltalkImage). >>> So, some usages are not correct anymore. >>> >>> See for example #removeUninstantiatedSubclassesSilently. >>> Fortunately, this message is unsent (quite dangerous isn't it ?). >>> But IMHO, all senders of #environment should be reviewed. >>> >>> Nicolas >>> >> >> >> >
Re: [Pharo-project] Issue 3624 in pharo: LeftOver of Smalltalk and SystemDictionary
Updates: Status: Fixed Comment #1 on issue 3624 by stephane...@gmail.com: LeftOver of Smalltalk and SystemDictionary http://code.google.com/p/pharo/issues/detail?id=3624 Here is the fix. So far only one method getting wrong Attachments: environment.1.cs 644 bytes
Re: [Pharo-project] [update 1.2] #12327
I rollbacked the changes since I got a dependency on archiveViewer (no idea why but I'm checking). On Jan 30, 2011, at 9:58 PM, Stéphane Ducasse wrote: > 12327 > - > > - Issue 3482: InterimSoundMorph references to SketchMorph. Fixing the > SoundService registration + making sure that it delegates to the registered > sound system when available. After the Sound packages can be updated. > > Marcus I published the other sounds fixes in the sound packages. > Now I do not know how the dev image is specified. May be the script should be > changed to load the new packages versions I published. > Do you know where is this script? > > Stef
Re: [Pharo-project] [update 1.2] #12327
republished. Now waiting for hudson to see. >> Marcus I published the other sounds fixes in the sound packages. >> Now I do not know how the dev image is specified. May be the script should >> be changed to load the new packages versions I published. >> Do you know where is this script? Stef
Re: [Pharo-project] does anybody knows who is using StandardToolSet?
On 30 January 2011 20:30, Tudor Girba wrote: > Hi, > > I am not sure what is the current status in this area. Could anyone provide > an idea of what is the desired solution? > The idea is to get rid of ToolSet references and replace all patterns like ToolSet default foo with Smalltalk tools foo or even more extreme, leave only a message send and get rid of using globals, because it is early binding: self toolset foo where #toolset implemented in Object with ^ Smalltalt tools. The answer of 'Smalltalk tools' should be a tool registry instance. The tool registry is a system-wide object where packages can register their tools. I don't remember all of the details, but the idea, when i implemented it was following: - you registering your tool(s) by sending: Smalltalk tools addTool: myTool verb: #myTool and then you can send messages to registry directly using #myTool selector: Smalltalk tools myTool So, there will be no hardcoded set of tools in a system and therefore no need for having a class, like ToolSet, which implements a protocol for 'standard' toolset. I imagine in stripped down images, some tools can be non-existing, but some still could be there. Making tools pluggable will improve modularity. > Cheers, > Doru > > > On 28 Jan 2011, at 19:35, Igor Stasenko wrote: > >> On 28 January 2011 19:20, Mariano Martinez Peck >> wrote: >>> yes, check the archives. I opened tickes for that. and I sent several mails. >>> Seems no-one has time to do it. >>> >> we discussed that today. >> probably i will take care about it for 1.3.. not sure how soon it will >> be but i will :) >> >>> http://code.google.com/p/pharo/issues/detail?id=1915 >>> >>> On Fri, Jan 28, 2011 at 10:44 AM, Stéphane Ducasse >>> wrote: Because it would be good that it uses a registration mechanism. Hardcoding the classes of the tools is not optimal for example for the new Finder. Stef >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > -- Best regards, Igor Stasenko AKA sig.
Re: [Pharo-project] does anybody knows who is using StandardToolSet?
Thanks for the explanations, Igor. I like the direction. Cheers, Doru On 31 Jan 2011, at 03:01, Igor Stasenko wrote: > On 30 January 2011 20:30, Tudor Girba wrote: >> Hi, >> >> I am not sure what is the current status in this area. Could anyone provide >> an idea of what is the desired solution? >> > > The idea is to get rid of ToolSet references and replace all patterns like > > ToolSet default foo > > with > > Smalltalk tools foo > > or even more extreme, leave only a message send and get rid of using > globals, because it is early binding: > > self toolset foo > > where #toolset implemented in Object with > ^ Smalltalt tools. > > The answer of 'Smalltalk tools' should be a tool registry instance. > > The tool registry is a system-wide object where packages can register > their tools. > I don't remember all of the details, but the idea, when i implemented > it was following: > > - you registering your tool(s) by sending: > > Smalltalk tools addTool: myTool verb: #myTool > > and then you can send messages to registry directly using #myTool selector: > > Smalltalk tools myTool > > So, there will be no hardcoded set of tools in a system and therefore > no need for having a class, like ToolSet, > which implements a protocol for 'standard' toolset. > I imagine in stripped down images, some tools can be non-existing, but > some still could be there. > Making tools pluggable will improve modularity. > > >> Cheers, >> Doru >> >> >> On 28 Jan 2011, at 19:35, Igor Stasenko wrote: >> >>> On 28 January 2011 19:20, Mariano Martinez Peck >>> wrote: yes, check the archives. I opened tickes for that. and I sent several mails. Seems no-one has time to do it. >>> we discussed that today. >>> probably i will take care about it for 1.3.. not sure how soon it will >>> be but i will :) >>> http://code.google.com/p/pharo/issues/detail?id=1915 On Fri, Jan 28, 2011 at 10:44 AM, Stéphane Ducasse wrote: > > Because it would be good that it uses a registration mechanism. > Hardcoding the classes of the tools is not optimal for example for the new > Finder. > > Stef >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> -- >> www.tudorgirba.com >> >> "In a world where everything is moving ever faster, >> one might have better chances to win by moving slower." >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > -- www.tudorgirba.com "What we can governs what we wish."
[Pharo-project] See me @ Smalltalk Solutions 2011 ...
Hi All, If you happen to come along to Smalltalk Solutions 2011 in Vegas, please try to say Hello to me. I'll be presenting on Redline Smalltalk and I'd really like to meet people from this list. Rgs, James.
Re: [Pharo-project] does anybody knows who is using StandardToolSet?
> > The answer of 'Smalltalk tools' should be a tool registry instance. > > The tool registry is a system-wide object where packages can register > their tools. > I don't remember all of the details, but the idea, when i implemented > it was following: > > - you registering your tool(s) by sending: > > Smalltalk tools addTool: myTool verb: #myTool would be good to have addTool: myTool named: #myTool kind: #codebrowser so that we can avoid to have one subclass per kind. Stef
Re: [Pharo-project] [update 1.2] #12327
On Jan 30, 2011, at 10:47 PM, Stéphane Ducasse wrote: > republished. > Now waiting for hudson to see. > I like automatic builds and tests! I think it brings an improvement equal (or even larger) then using bug-tracking vs. not using it. And if now somebody says: "Everyone uses a bug tracker": No, Squeak did not for many, many years. And when it did, not many people looked at it... amazing now in retrospect. We will say the same about continuous integration soon, especially when it encompasses everything: VM build from source, *that* vm used to run tests, the resulting image and vm used to build the artefact people download automatically, every time a commit happens. And that for all supported plattforms, of course. >>> Marcus I published the other sounds fixes in the sound packages. >>> Now I do not know how the dev image is specified. May be the script should >>> be changed to load the new packages versions I published. >>> Do you know where is this script? It uses the ConfigurationOfPharo Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
