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" <[email protected]> >>> To: "Pharo Development" <[email protected]> >>> 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 >>>> [email protected] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [email protected] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
