- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Baseline test results on pharo core 10392

by Adrian Lienhard

On Jul 28, 2009, at 14:51 , Mariano Martinez Peck wrote: > On Tue, Jul 28, 2009 at 5:42 AM, Damien Cassou <damien.cassou(a)gmail.com > >wrote: > >> 2009/7/27 Mariano Martinez Peck <marianopeck(a)gmail.com>: >>> HostSystemMenusTest class>>expectedFailures >>> >>> SmalltalkImage current platformName = 'Mac OS' ifFalse:[ >>> ^#(#testXXX #testYYY)]. >>> ]. >>> ^#() >> >> Expected failures are indications of bugs that are not yet corrected. >> Does not seem to apply here. > > > ahhh okok. So...shall we go for torsten solution ? Yes. Adrian > > >> >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Lambdas are relegated to relative obscurity until Java makes them >> popular by not having them." James Iry >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 28, 2009

Re: [Pharo-project] Baseline test results on pharo core 10392

by Mariano Martinez Peck

On Tue, Jul 28, 2009 at 5:42 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > 2009/7/27 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > HostSystemMenusTest class>>expectedFailures > > > > SmalltalkImage current platformName = 'Mac OS' ifFalse:[ > > ^#(#testXXX #testYYY)]. > > ]. > > ^#() > > Expected failures are indications of bugs that are not yet corrected. > Does not seem to apply here. ahhh okok. So...shall we go for torsten solution ? > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 28, 2009

Re: [Pharo-project] Polymorph depends on Sound

by Igor Stasenko

2009/7/28 Adrian Lienhard <adi(a)netstyle.ch>: > Hi Todd, > > I don't think it is a true core capability, considering that many if > not the majority of applications built with Pharo are web-based. I > don't think that Sound will rot now _if_ projects exist that are using > it. If nobody is using and caring about it, then, yes, it may indeed > rott. If really a lot of projects use Sound we could consider > including it in the Pharo image. In any case, I strongly believe that > making the image more modular and removing non-system/core behavior > from the core image is the way to go. Also, keeping code in the image > does not guarantee it does not rott (see e.g., EToys). > +1 if one package can live without strict dependency on some other package, then it should. > Cheers, > Adrian > > > > On Jul 28, 2009, at 10:52 , Eagle Offshore wrote: > >> I understand wanting to limit dependencies and clean stuff up - but is >> there a particular reason why we don't think the basic ability to play >> sounds belongs in a base application development environment? >> >> Seems like a core capability and I worry about sound rotting if it >> doesn't live in the base image. >> >> -Todd Blanchard >> >> On Jul 28, 2009, at 12:34 AM, Adrian Lienhard wrote: >> >>> Hi Gary, >>> >>> In the Pharo project, there is a new version of Polymorph with these >>> changes. >>> >>> Cheers, >>> Adrian >>> >>> On Jul 27, 2009, at 11:54 , Gary Chambers wrote: >>> >>>> No problem. >>>> >>>> Regards, Gary >>>> >>>> ----- Original Message ----- >>>> From: "Adrian Lienhard" <adi(a)netstyle.ch> >>>> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> >>>> Sent: Saturday, July 25, 2009 10:21 AM >>>> Subject: [Pharo-project] Polymorph depends on Sound >>>> >>>> >>>>> Hi Gary, >>>>> >>>>> I'm working on removing the Sound package. Polymorph's SoundTheme >>>>> class has some methods that reference RestSound. >>>>> >>>>> For instance: >>>>> >>>>> windowRestoreDownSound >>>>> ^self sounds at: #windowRestoreDown ifAbsent: [RestSound dur: 0] >>>>> >>>>> >>>>> Could we change these methods, for example like this: >>>>> >>>>> windowRestoreDownSound >>>>> ^self sounds at: #windowRestoreDown ifAbsent: [self >>>>> defaultDefaultSound] >>>>> >>>>> and then >>>>> >>>>> defaultDefaultSound >>>>> ^ Beeper default >>>>> >>>>> Projects that use sound can then load the Sound package and define >>>>> their own SoundTheme. If this is OK with you I'll do these changes >>>>> in >>>>> Pharo and you can pick them up and merge them later. >>>>> >>>>> Cheers, >>>>> Adrian >>>>> ___________________ >>>>> http://www.adrian-lienhard.ch/ >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

July 28, 2009

Re: [Pharo-project] Polymorph depends on Sound

by Adrian Lienhard

Hi Todd, I don't think it is a true core capability, considering that many if not the majority of applications built with Pharo are web-based. I don't think that Sound will rot now _if_ projects exist that are using it. If nobody is using and caring about it, then, yes, it may indeed rott. If really a lot of projects use Sound we could consider including it in the Pharo image. In any case, I strongly believe that making the image more modular and removing non-system/core behavior from the core image is the way to go. Also, keeping code in the image does not guarantee it does not rott (see e.g., EToys). Cheers, Adrian On Jul 28, 2009, at 10:52 , Eagle Offshore wrote: > I understand wanting to limit dependencies and clean stuff up - but is > there a particular reason why we don't think the basic ability to play > sounds belongs in a base application development environment? > > Seems like a core capability and I worry about sound rotting if it > doesn't live in the base image. > > -Todd Blanchard > > On Jul 28, 2009, at 12:34 AM, Adrian Lienhard wrote: > >> Hi Gary, >> >> In the Pharo project, there is a new version of Polymorph with these >> changes. >> >> Cheers, >> Adrian >> >> On Jul 27, 2009, at 11:54 , Gary Chambers wrote: >> >>> No problem. >>> >>> Regards, Gary >>> >>> ----- Original Message ----- >>> From: "Adrian Lienhard" <adi(a)netstyle.ch> >>> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> >>> Sent: Saturday, July 25, 2009 10:21 AM >>> Subject: [Pharo-project] Polymorph depends on Sound >>> >>> >>>> Hi Gary, >>>> >>>> I'm working on removing the Sound package. Polymorph's SoundTheme >>>> class has some methods that reference RestSound. >>>> >>>> For instance: >>>> >>>> windowRestoreDownSound >>>> ^self sounds at: #windowRestoreDown ifAbsent: [RestSound dur: 0] >>>> >>>> >>>> Could we change these methods, for example like this: >>>> >>>> windowRestoreDownSound >>>> ^self sounds at: #windowRestoreDown ifAbsent: [self >>>> defaultDefaultSound] >>>> >>>> and then >>>> >>>> defaultDefaultSound >>>> ^ Beeper default >>>> >>>> Projects that use sound can then load the Sound package and define >>>> their own SoundTheme. If this is OK with you I'll do these changes >>>> in >>>> Pharo and you can pick them up and merge them later. >>>> >>>> Cheers, >>>> Adrian >>>> ___________________ >>>> http://www.adrian-lienhard.ch/ >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 28, 2009

Re: [Pharo-project] Polymorph depends on Sound

by Eagle Offshore

I understand wanting to limit dependencies and clean stuff up - but is there a particular reason why we don't think the basic ability to play sounds belongs in a base application development environment? Seems like a core capability and I worry about sound rotting if it doesn't live in the base image. -Todd Blanchard On Jul 28, 2009, at 12:34 AM, Adrian Lienhard wrote: > Hi Gary, > > In the Pharo project, there is a new version of Polymorph with these > changes. > > Cheers, > Adrian > > On Jul 27, 2009, at 11:54 , Gary Chambers wrote: > >> No problem. >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "Adrian Lienhard" <adi(a)netstyle.ch> >> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> >> Sent: Saturday, July 25, 2009 10:21 AM >> Subject: [Pharo-project] Polymorph depends on Sound >> >> >>> Hi Gary, >>> >>> I'm working on removing the Sound package. Polymorph's SoundTheme >>> class has some methods that reference RestSound. >>> >>> For instance: >>> >>> windowRestoreDownSound >>> ^self sounds at: #windowRestoreDown ifAbsent: [RestSound dur: 0] >>> >>> >>> Could we change these methods, for example like this: >>> >>> windowRestoreDownSound >>> ^self sounds at: #windowRestoreDown ifAbsent: [self >>> defaultDefaultSound] >>> >>> and then >>> >>> defaultDefaultSound >>> ^ Beeper default >>> >>> Projects that use sound can then load the Sound package and define >>> their own SoundTheme. If this is OK with you I'll do these changes >>> in >>> Pharo and you can pick them up and merge them later. >>> >>> Cheers, >>> Adrian >>> ___________________ >>> http://www.adrian-lienhard.ch/ >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 28, 2009

Re: [Pharo-project] Polymorph depends on Sound

by Adrian Lienhard

Hi Gary, In the Pharo project, there is a new version of Polymorph with these changes. Cheers, Adrian On Jul 27, 2009, at 11:54 , Gary Chambers wrote: > No problem. > > Regards, Gary > > ----- Original Message ----- > From: "Adrian Lienhard" <adi(a)netstyle.ch> > To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> > Sent: Saturday, July 25, 2009 10:21 AM > Subject: [Pharo-project] Polymorph depends on Sound > > >> Hi Gary, >> >> I'm working on removing the Sound package. Polymorph's SoundTheme >> class has some methods that reference RestSound. >> >> For instance: >> >> windowRestoreDownSound >> ^self sounds at: #windowRestoreDown ifAbsent: [RestSound dur: 0] >> >> >> Could we change these methods, for example like this: >> >> windowRestoreDownSound >> ^self sounds at: #windowRestoreDown ifAbsent: [self >> defaultDefaultSound] >> >> and then >> >> defaultDefaultSound >> ^ Beeper default >> >> Projects that use sound can then load the Sound package and define >> their own SoundTheme. If this is OK with you I'll do these changes in >> Pharo and you can pick them up and merge them later. >> >> Cheers, >> Adrian >> ___________________ >> http://www.adrian-lienhard.ch/ >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 28, 2009

Re: [Pharo-project] Baseline test results on pharo core 10392

by Damien Cassou

2009/7/27 Mariano Martinez Peck <marianopeck(a)gmail.com>: > HostSystemMenusTest class>>expectedFailures > > SmalltalkImage current platformName = 'Mac OS' ifFalse:[ > Â Â Â Â ^#(#testXXX #testYYY)]. > ]. > ^#() Expected failures are indications of bugs that are not yet corrected. Does not seem to apply here. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 28, 2009

Re: [Pharo-project] Making GLMorphic plugin work in Pharo

by Javier PimÃ¡s

Mariano, you can update and test it again now. I moved all the code to GLMorphic package and everything you need should be there. On Mon, Jul 27, 2009 at 6:45 PM, Javier PimÃ¡s <elpochodelagente(a)gmail.com>wrote: > >- you can't access the squeak window handle directly, there is no > primitive. > > Yes, I also found that problem, but there must be a way to find it in some > place (or there should be) without writing a plugin. > > >Please, put this into GLMorphic package. Make a separate class & copy > >the code you need. > >FFI-Examples is bad place for this. > > Ok I'll change that, and also I'll try to fix the glitches (at least making > the fonts respect the ascend so that the characters are placed in the > baseline. > > On Mon, Jul 27, 2009 at 4:34 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> 2009/7/27 Javier PimÃ¡s <elpochodelagente(a)gmail.com>: >> >> [snip] >> >> > If you want to try it, you should do >> > >> > ScriptLoader loadFFI. >> > >> > and then download the GLMorphic-JEP version of GLMorphic package from >> > squeaksource (after GLMorphic-sig? ). I also made some modifications to >> > FFI-Examples, so you may also have to dowonload FF-Examples-JEP from >> > squeakfoundation.org. I'm new to monticello so it wouldn't be strange >> if >> > nothing got uploaded correctly. >> > >> >> >> Btw, i'm currently in the middle of writing plugin for binding the >> OpenVG (http://www.khronos.org/openvg/) >> And your new additions could be useful, because for tests i wanna use >> the ShivaVG implementation, which >> expects a pre-initialized OpenGL rendering context... >> >> [snip] >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > -- Javier PimÃ¡s Ciudad de Buenos Aires

July 28, 2009

[Pharo-project] Communication medium - Why not use/anticipate wave tools ?

by CÃ©drick BÃ©ler

Hi, Just got a wavesanbox[1] account and I can't help thinking this would be a good (global?) comunication medium (enriched emails, mailing-lists, tutorials, technical discussions and also bug tracker...). What do other think ? Could we create a Smalltalk related waves/groups as a start ? And what about having bindings and a protocol implementation in Smalltalk ? Cheers, -- CÃ©drick (cdrick(a)wavesandbox.com) [1] wave is a new tool from google aiming at redefining emails and instant messages (based on waveprotocol)... The application proposed is epecially interesting (to me) in its collaborative creation/edition of "waves". Video: http://www.youtube.com/watch?v=v_UyVmITiYQ

July 28, 2009

[Pharo-project] wikiserver 1.4.3 ships

by John M McIntosh

Apple told me today that WikiServer for the iPhone version 1.4.3 is now in the store. This version is not yet based on Pier 1.2 I am working on that, anyone who wants to beta-test WikiServer 1.5 should email me. However we have add a macintosh, windows, and linux client so you can import/export wiki content to/from desktop machines and iphone devices. See http://www.mobilewikiserver.com/1.4.html for links to the desktop clients. -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

July 27, 2009