- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fwd: [Moose-dev] [seed] New project around the kernel

by Yanni Chiu

StÃ©phane Ducasse wrote: > > > Begin forwarded message: > >> *From: *Nicolas Paez <nicopaez(a)gmail.com >> >> Hi, I am working in the RMoD team (INRIA) in a project called /Seed/. >> One of the tasks of the project is to identify those mandatory classes >> that should be part of Pharo kernel. Would it be worthwhile to look at the class/methods in a Spoon image? http://netjam.org/projects/spoon/ The "minimal" Spoon image which is meant to have just enough to connect to another image to provide more code, IMHO, is too small to be Pharo Kernel.

Aug. 31, 2010

[Pharo-project] ThemeSettings>>#menuSelectionColor: should return self

by Sven Van Caekenberghe

I was playing with the new Pro theme, and this bit me hard (crashed my image several times before I found out why): ThemeSettings>>#menuSelectionColor: should return self not a Color, just like all other setters, otherwise the cascades in UITheme class>>#newDefaultSettings won't work, although a final #yourself would be good style there too. Sven

Aug. 31, 2010

[Pharo-project] Fwd: [Moose-dev] [seed] New project around the kernel

by StÃ©phane Ducasse

Begin forwarded message: > From: Nicolas Paez <nicopaez(a)gmail.com> > Date: August 31, 2010 5:02:04 PM GMT+02:00 > To: moose-dev(a)iam.unibe.ch, pharo-project-request(a)lists.gforge.inria.fr > Subject: [Moose-dev] [seed] New project around the kernel > Reply-To: Moose-related development <moose-dev(a)iam.unibe.ch> > > Hi, I am working in the RMoD team (INRIA) in a project called Seed. One of the tasks of the project is to identify those mandatory classes that should be part of Pharo kernel. Currently, Pharo kernel has some "unhappy dependecies". We are using Moose + Glamour to create a tool (a browser) that help up with this task. The idea is to start by loading in our browser the classes used in the SpecialObjectsArray and then iterate to add dependencies incrementally. This way we will be able to detect smells and "blacklist" methods we don't want to be part of our kernel. > > During this days we will have a working version of our browser to start the analysis. > If you want to take a look, search for Seed on SqueackSource. > We will be sharing our findings in the Pharo mailing list. > > > > > Regards, > NicoPaez. > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Aug. 31, 2010

Re: [Pharo-project] Inter-image communication

by Sean P. DeNigris

Noury Bouraqadi-2 wrote: > > I added you as a developer to the rST project as well as UbiquiTalk. > Thanks, I'll copy the files over. Sean -- View this message in context: http://forum.world.st/Inter-image-communication-tp2320723p2401752.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 31, 2010

Re: [Pharo-project] DNU MIMEType>>#forURIReturnSingleMimeTypeOrDefault:

by Sven Van Caekenberghe

On 31 Aug 2010, at 16:02, StÃ©phane Ducasse wrote: > On Aug 31, 2010, at 3:49 PM, Sven Van Caekenberghe wrote: > >> Well, the issue says 'tagged FIXED an hour ago by StephaneDucasse'. > > I put fixed because I thought that the file should be integrated. But now I see that marcus already integrated it. > sorry for the confusion. > Is it correct? I thought that it was a test to be included? > Else what is it? Its Philippe's issue, but I reported a bug and it seems that he already reported it as an issue. He seems to have added an extended NetworkTests package that should expose the bug that I mentioned. Yes, his changes seem to have been integrated by Marcus. I understand that is why you marked it as fixed. But the underlying issue is not fixed, and I don't see a test that exposes the issue, so maybe Philippe made a mistake in the test package that he submitted. >> This is a really unfriendly place: one does not have the time to report problems, let alone fix them! > you confuse me on this one. I'm lost. This was a joke ;-) >> Where can I see the fix, my 1.2 is up to date and it fails there too, I see no slice named after the issue and no new version of Networking-MIME ? Where should I be looking ? > > Ok my mistake I thought that philippe since there is a >> >> Sven >> >> On 31 Aug 2010, at 15:33, Sven Van Caekenberghe wrote: >> >>> Philippe, >>> >>> Is it that obvioius ;-) ? >>> >>> Seriously though, I think this is quite easily fixable, but it is hard to get a grip on the implications outside Pharo(Core). >>> Should I propose a patch ? >>> >>> I will first have a look at the 'contributing to pharo' webcast. >>> >>> Sven >>> >>> On 31 Aug 2010, at 14:42, Philippe Marschall wrote: >>> >>>> On 08/31/2010 01:58 PM, Sven Van Caekenberghe wrote: >>>>> Hi, >>>>> >>>>> In Pharo-1.1-11411 these >>>>> >>>>> MIMEDocument guessTypeFromName: 'pharo.png'. >>>>> MIMEDocument guessTypeFromExtension: 'png'. >>>>> >>>>> give a DNU for >>>>> >>>>> MIMEType>>#forURIReturnSingleMimeTypeOrDefault: >>>> >>>> See also: >>>> >>>> http://code.google.com/p/pharo/issues/detail?id=2797 >>>> >>>> I know what you're working on ;-) >>>> >>>> Cheers >>>> Philippe

Aug. 31, 2010

Re: [Pharo-project] problems with 12119 and 12120

by StÃ©phane Ducasse

Hi guys I'm sorry to have to revert changes like that but the changes I pushed where destroying packages saved on the server. So now I cannot realy check the changes because of the university cache. But please restart from 12016. Once everything is working I will publish a new image. Stef On Aug 31, 2010, at 3:53 PM, StÃ©phane Ducasse wrote: > I'm cleaning the scriptloader and update list because there were intertwined fixes. > I will redo them in order. > We need a scriptable source. > > Stef > > On Aug 31, 2010, at 10:18 AM, StÃ©phane Ducasse wrote: > >> HI guys >> >> to lower my stress I removed from the update stream the items related to my MethodReference changes. >> so please update from 12016 >> Benjamin I will try to find what is the problem. >> >> >> Stef >> >> >> On Aug 31, 2010, at 9:50 AM, StÃ©phane Ducasse wrote: >> >>> I was trying to clean a bit MethodReference and now I broke the merge in Monticello. >>> Now I get all the method with revision changed >>> >>> So what do we do? >>> >>> The changes were to help the integration of the new recentMessages changes >>> >>> 1- rollback because I do not have the time to dive into this part of the system. >>> We need a better and cleaner infrastructure with a real declarative code model and not a hack like methodReference and tweak it to get >>> comments and class definition on it. I hate that we have so lousy and brittle foundation >>> >>> 2- let it and try to understand why it breaks. But I have no time (now this stuff will stay in my mind until I check -grgrg). >>> >>> Stef >>> _______________________________________________ >>> 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

Aug. 31, 2010

Re: [Pharo-project] About the icons

by StÃ©phane Ducasse

> > icon := IconMorph named: 'apply' size: 16 familyNamed: 'gaucho'. > > I think that it wouldn't be hard to integrate this into Pharo1.2, to have a standardized manner of requesting icons, managing the forms, and easily importing external icon-families. I would be willing to work on this during the sprint. yes would be great!

Aug. 31, 2010

Re: [Pharo-project] UbiquiTalk running in Pharo 1.1

by Noury Bouraqadi

cool. Noury On 30 aoÃ»t 2010, at 23:50, Sean P. DeNigris wrote: > > I haven't done much with it, and there are some deprecation warnings, but > it's running. In the attached screenshot, the "host 2" entry in the > "Detected Hosts" window is the Squeak 4.1 image running on the right. > http://forum.world.st/file/n2400767/Screen_shot_2010-08-30_at_August_30%2C_… > Screen_shot_2010-08-30_at_August_30%2C_2010_5.47.42_PM.png > > Load it with: > Gofer new > squeaksource: 'KomHttpServer'; > package: 'DynamicBindings'; > load. > > Gofer new > squeaksource: 'KomHttpServer'; > package: 'KomServices'; > load. > > Gofer new > squeaksource: 'SPDProjectUpdates'; > package: 'rST'; > load. > > Gofer new > squeaksource: 'OSProcess'; > package: 'OSProcess'; > load. > > Gofer new > squeaksource: 'SPDProjectUpdates'; > package: 'UbiquiTalk-Platform.pharo'; > load. > > Gofer new > squeaksource: 'SPDProjectUpdates'; > package: 'UbiquiTalk-Cache'; > load. > > Gofer new > squeaksource: 'SPDProjectUpdates'; > package: 'UbiquiTalk-GUI'; > load. > > Gofer new > squeaksource: 'SPDProjectUpdates'; > package: 'UbiquiTalk-Utilities'; > load. > > "requires Utilities" > Gofer new > squeaksource: 'SPDProjectUpdates'; > package: 'UbiquiTalk-Kernel'; > load. > > "requires Kernel" > Gofer new > squeaksource: 'SPDProjectUpdates'; > package: 'UbiquiTalk-Plugins'; > load. > > Gofer new > squeaksource: 'SPDProjectUpdates'; > package: 'UbiquiTalk-PDA'; > load. > > Gofer new > squeaksource: 'SPDProjectUpdates'; > package: 'UbiquiTalk-Property Editors'; > load. > > Gofer new > squeaksource: 'SPDProjectUpdates'; > package: 'UbiquiTalk-Tests'; > load. > > "requires platform" > Gofer new > squeaksource: 'UbiquiTalk'; > package: 'UTAllServices'; > load. > > Sean > -- > View this message in context: http://forum.world.st/UbiquiTalk-running-in-Pharo-1-1-tp2400767p2400767.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project Noury

Aug. 31, 2010

Re: [Pharo-project] Inter-image communication

by Noury Bouraqadi

Sean, I added you as a developer to the rST project as well as UbiquiTalk. Noury On 30 aoÃ»t 2010, at 21:29, Sean P. DeNigris wrote: > > While some of the suggestions (AMQP, STOMP) were over my head, I'm in the > process of getting UbiquiTalk to work and already have rST going. > > But, for my use case i.e. sending remote commands between (only) two images > on the same machine, why not just send the commands as strings over a > socket, and evaluate them with the compiler? Obviously there's no security, > but since it's in-house only... A proof-of-concept is below: > > Server image: > server := Socket newTCP. > server listenOn: 8081. > server waitForConnectionFor: 600. > server sendData: 'Workspace open' > > Client image: > client := Socket newTCP. > client connectTo: (NetNameResolver localHostAddress) port: 8081. > Compiler evaluate: client receiveData. > > Add a loop and we're all set. > > Sean > -- > View this message in context: http://forum.world.st/Inter-image-communication-tp2320723p2400616.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project Noury

Aug. 31, 2010

Re: [Pharo-project] DNU MIMEType>>#forURIReturnSingleMimeTypeOrDefault:

by StÃ©phane Ducasse

On Aug 31, 2010, at 3:49 PM, Sven Van Caekenberghe wrote: > Well, the issue says 'tagged FIXED an hour ago by StephaneDucasse'. I put fixed because I thought that the file should be integrated. But now I see that marcus already integrated it. sorry for the confusion. Is it correct? I thought that it was a test to be included? Else what is it? > This is a really unfriendly place: one does not have the time to report problems, let alone fix them! you confuse me on this one. I'm lost. > Where can I see the fix, my 1.2 is up to date and it fails there too, I see no slice named after the issue and no new version of Networking-MIME ? Where should I be looking ? Ok my mistake I thought that philippe since there is a > > Sven > > On 31 Aug 2010, at 15:33, Sven Van Caekenberghe wrote: > >> Philippe, >> >> Is it that obvioius ;-) ? >> >> Seriously though, I think this is quite easily fixable, but it is hard to get a grip on the implications outside Pharo(Core). >> Should I propose a patch ? >> >> I will first have a look at the 'contributing to pharo' webcast. >> >> Sven >> >> On 31 Aug 2010, at 14:42, Philippe Marschall wrote: >> >>> On 08/31/2010 01:58 PM, Sven Van Caekenberghe wrote: >>>> Hi, >>>> >>>> In Pharo-1.1-11411 these >>>> >>>> MIMEDocument guessTypeFromName: 'pharo.png'. >>>> MIMEDocument guessTypeFromExtension: 'png'. >>>> >>>> give a DNU for >>>> >>>> MIMEType>>#forURIReturnSingleMimeTypeOrDefault: >>> >>> See also: >>> >>> http://code.google.com/p/pharo/issues/detail?id=2797 >>> >>> I know what you're working on ;-) >>> >>> Cheers >>> Philippe >>> >>> >>> _______________________________________________ >>> 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

Aug. 31, 2010