July 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Polymorph depends on Sound

by Gary Chambers

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

July 27, 2009

Re: [Pharo-project] Usage of fast drag

by Stuart Herring

On Mon, Jul 27, 2009 at 7:37 PM, Damien Cassou<damien.cassou(a)gmail.com> wrote: >> (4) [...] FWIW, I still think you should reconsider fast drag - enabling it makes a HUGE difference when moving and resizing windows. > > what do people think about 'fast drag' preference? > I use it all the time - but I do most my development on an EeePC, so it makes a big difference there. Interestingly, that - and switching to the Soft Squeak theme (which is actually more because I like the colour coded windows than the performance improvement) is the only performance change I make. I infinitely prefer the package browser, and I even think the delays associated with dynamic protocols are worthwhile. Regards, Stuart

July 27, 2009

[Pharo-project] Usage of fast drag

by Damien Cassou

> (4) [...] FWIW, I still think you should reconsider fast drag - enabling it makes a HUGE difference when moving and resizing windows. what do people think about 'fast drag' preference? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 27, 2009

Re: [Pharo-project] New Pharo based on core 10388

by Damien Cassou

Hi Bill, On Fri, Jul 24, 2009 at 9:59 PM, Schwab,Wilhelm K<bschwab(a)anest.ufl.edu> wrote: > (1) in the w2k theme, the pressed state of the browser buttons is "backwards." could you please report an issue on the tracker and assign it to gazzaguru? > (2) When I open the Seaside image for the first time, it complains about a service already running on port 8080 - this is similar (not exactly the same though) as my working image started doing, but I have not loaded any of my code yet. Â Something must have changed. I think this is a problem with Seaside and I saw something related on the mailing list already. Could you please report that on the Seaside mailing list. > (3) I'm not sure about the new inspector. Â I have more or less adapted to the explorer and inspector; this looks like it's trying to do both jobs, and I will have to use it for a while to give a fair opinion. Â So far, I _think_ I'll be happier with the current tools. Â The last time an inspector really got my attention was a "diving inspector" that was ported to Dolphin a while back. Â The idea is that a double click/enter on an instance variable would alter the contents of the inspector, not open a new one, and there was a way to back up to any previous levels, one at a time. Could you please play with it for some time and report later what's your opinion about it? You can also send feature requests to FrÃ©dÃ©ric Pluquet who implemented all features ever requested yet. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 27, 2009

Re: [Pharo-project] New Pharo based on core 10388

by Damien Cassou

2009/7/24 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Damien are you talking about Frederic Pluquet work? I put something in a > workspace like Smalltalk, right button, "inspect it" but it opens the > default inspector. > wasn't new inspector something like those Mac's app (finder?) ? Yes, I'm talking about FrÃ©dÃ©ric Pluquet's inspector. I confirm it works for me on pharo-0.1-10388dev09.07.04. Could you please check that you are using latest image and did not change anything? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 27, 2009

Re: [Pharo-project] Access to pharo wiki

by Damien Cassou

Hi Miguel, 2009/7/25 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com>: > > Who can give me permission to modify the pharo wiki? > > How can I change the status of a issue in the issue tracker? you have now access to everything. Bye -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 27, 2009

Re: [Pharo-project] about status "fixed" on the bugtracker

by Damien Cassou

On Sat, Jul 25, 2009 at 1:36 AM, Marcus Denker<denker(a)acm.org> wrote: > When looking at the bugtracker to get fixed closed, the nicest thing > are those entries that have status "fixed". > In my naive way, I think that these entries are kind of ready for > inclusion. That means, it has a changset > ready to be filed in or a slice published. *Not* some preliminary > changesets that need Â to be "slightly edited". > Not a verbal description of what to do. And for sure not a quiz > formulated to show the cleverness of the submitter... > > Somtimes this is really annoying... Sorry Marcus, most of them are from me I guess. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 27, 2009

Re: [Pharo-project] mac-roman encoding borken?

by Nicolas Cellier

See http://code.google.com/p/pharo/issues/list?updated=986 2009/7/26 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > Fortunately, an analysis of code clearly shows that > ByteTextConverter class>>#initializeTables > is broken (stamped 2/5/2009) > > It maps characters with an offset of 128... > > Nicolas > > 2009/7/26 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >> I don't know about the changes, but I know I cannot debug it in a core >> image because debugger does not work at all... :( >> >> Nicolas >> >> 2009/7/26 Philippe Marschall <kustos(a)gmx.net>: >>> Hi >>> >>> We have some failing tests in Seaside in the latest versions of Pharo >>> that work in older versions. A short analysis seems to indicate that the >>> there are some issues with mac-roman support in current versions Pharo. >>> To be concrete the following code used to work in older versions but >>> fails for newer ones. >>> >>> (('Ã¤Ã¶Ã¼' convertToEncoding: 'mac-roman') convertFromEncoding: >>> 'mac-roman') = 'Ã¤Ã¶Ã¼' >>> >>> Is anybody aware of any changes? Should I open a bug? >>> >>> Cheers >>> Philippe >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

July 26, 2009

Re: [Pharo-project] mac-roman encoding borken?

by Nicolas Cellier

Fortunately, an analysis of code clearly shows that ByteTextConverter class>>#initializeTables is broken (stamped 2/5/2009) It maps characters with an offset of 128... Nicolas 2009/7/26 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > I don't know about the changes, but I know I cannot debug it in a core > image because debugger does not work at all... :( > > Nicolas > > 2009/7/26 Philippe Marschall <kustos(a)gmx.net>: >> Hi >> >> We have some failing tests in Seaside in the latest versions of Pharo >> that work in older versions. A short analysis seems to indicate that the >> there are some issues with mac-roman support in current versions Pharo. >> To be concrete the following code used to work in older versions but >> fails for newer ones. >> >> (('Ã¤Ã¶Ã¼' convertToEncoding: 'mac-roman') convertFromEncoding: >> 'mac-roman') = 'Ã¤Ã¶Ã¼' >> >> Is anybody aware of any changes? Should I open a bug? >> >> Cheers >> Philippe >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 26, 2009

Re: [Pharo-project] mac-roman encoding borken?

by Nicolas Cellier

I don't know about the changes, but I know I cannot debug it in a core image because debugger does not work at all... :( Nicolas 2009/7/26 Philippe Marschall <kustos(a)gmx.net>: > Hi > > We have some failing tests in Seaside in the latest versions of Pharo > that work in older versions. A short analysis seems to indicate that the > there are some issues with mac-roman support in current versions Pharo. > To be concrete the following code used to work in older versions but > fails for newer ones. > > (('Ã¤Ã¶Ã¼' convertToEncoding: 'mac-roman') convertFromEncoding: > 'mac-roman') = 'Ã¤Ã¶Ã¼' > > Is anybody aware of any changes? Should I open a bug? > > Cheers > Philippe > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 26, 2009