- Pharo-dev - lists.pharo.org

Re: [Pharo-project] New pharo-dev based on 10196

by Bill Schwab

Stef, You are certainly welcome to beat me to it, though it could be a simple matter of my not having installed all of it. My goal was/is to install the cryptography team's work, including SSL sockets. One possible explanation is as follows: (1) the main package wants to be installed from a universe; (2) SSL is separate. That's just a guess. I will take another crack at it. Thanks! Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 12/20/08 2:59 AM >>> Bill report any problem to load packages and we willcheck what we can do? Do you have something that we can repeat. And indeed we prefer MC as package format. Stef On Dec 20, 2008, at 1:04 AM, Bill Schwab wrote: > Damien, > > Thanks for making the new image. Is there a way to tell the image to > display walkbacks instead of going straight into the debugger? > > The new image seemed a nice excuse to play catch-up, which means > getting a few things loaded. > > Seaside - I recalled discussion of it, and quckly stumbled onto a > closed bug report about > > ScriptLoader new universalInstaller universe install: 'Seaside'. > > That appears to work. The cryptography team's work will be important. > This gets weird fast. I have a 3.9 image where it is installed > correctly and works; I have very little idea how that happened. My > subsequent installation attempts appear not to be complete. > > SqueakMap appears to be going away in Pharo. Replacing it appear to > be > Installer, ScriptLoader, and maybe some of your tools to build the > developer images. Is there a clear correct way to install packages > now? > Put another way, if I make an attempt to sort out installing the > cryptography and SSL classes in Pharo, how would recommend attacking > it? > > Pharo is not even in beta yet, so no complaints, but I am missing > something on how to go from a new core image to something that is > ready > for use. > > Bill > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > > > _______________________________________________ > 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

Dec. 20, 2008

Re: [Pharo-project] Fwd: could you sign the pharo license?

by Adrian Lienhard

Hi Keith, Its nothing against your license (I think its cool). Its just that we initially decided that whoever contributes needs to sign the agreement. Like this, we will not have to discuss licenses over and over again. Now imagine, that every second Pharo contributor comes with his own license. Even if it is more liberal, it just adds complexity to the process and makes us discuss this topic, like we do now. I would prefer to fix a bug instead... Hence, if you could sign the "official" agreement, that would be great. Cheers, Adrian On Dec 20, 2008, at 13:09 , Keith Hodges wrote: > StÃ©phane Ducasse wrote: >> now the questions are >> - is it really that difficult to agree for a project on a given >> simple license such as MIT? >> - I also hate licenses since they polute our lives but I just don't >> care and signed MIT >> - should we accept this kind of license (of course it is compatible >> with MIT) >> but this looks a door open to the mess. >> >> I'm not sure squeakers realized that after all the effort of yohsiki >> to get SqueakEtoys clean >> 3.11 could be WTFPL because keith commit on it. >> > Thats a complete load of rubbish. > No. 1 I dont see any need for profanity. > > No. 2 my licence is not like GNU, please dont say it is because you > will > just confuse people. > > Its freer than MIT because I don't care if you take my code and sell > it > as your own. You can even say you wrote it if you like. The > responsibility for what you do with it is yours not mine. > > Keith >> I'm quite convinced that they will boycott such a code. >> >> Stef >> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 20, 2008

Re: [Pharo-project] Fwd: could you sign the pharo license?

by Keith Hodges

StÃ©phane Ducasse wrote: > now the questions are > - is it really that difficult to agree for a project on a given > simple license such as MIT? > - I also hate licenses since they polute our lives but I just don't > care and signed MIT > - should we accept this kind of license (of course it is compatible > with MIT) > but this looks a door open to the mess. > > I'm not sure squeakers realized that after all the effort of yohsiki > to get SqueakEtoys clean > 3.11 could be WTFPL because keith commit on it. > Thats a complete load of rubbish. No. 1 I dont see any need for profanity. No. 2 my licence is not like GNU, please dont say it is because you will just confuse people. Its freer than MIT because I don't care if you take my code and sell it as your own. You can even say you wrote it if you like. The responsibility for what you do with it is yours not mine. Keith > I'm quite convinced that they will boycott such a code. > > Stef > >

Dec. 20, 2008

Re: [Pharo-project] New pharo-dev based on 10196

by StÃ©phane Ducasse

Sounds a good plan to my ears :) Stef On Dec 20, 2008, at 11:16 AM, Adrian Lienhard wrote: > In a recent discussion with Marcus and Lukas we came to the conclusion > that a package universe for Pharo 1.0 would be the best solution. > Somebody would be responsible to manage this universe and only add > packages that are tested and known to work. I think this is really > important that we have higher standards regarding external packages. > In my experience with SqueakMap, the chance that a package actually > works is less than the chance it is not working. This is a show > stopper for newcomers. > Our plan was to remove SqueakMap from Pharo-core, but I assume it > could be put into the universe so it can be loaded again. > > Cheers, > Adrian > > On Dec 20, 2008, at 01:04 , Bill Schwab wrote: > >> Damien, >> >> Thanks for making the new image. Is there a way to tell the image to >> display walkbacks instead of going straight into the debugger? >> >> The new image seemed a nice excuse to play catch-up, which means >> getting a few things loaded. >> >> Seaside - I recalled discussion of it, and quckly stumbled onto a >> closed bug report about >> >> ScriptLoader new universalInstaller universe install: 'Seaside'. >> >> That appears to work. The cryptography team's work will be >> important. >> This gets weird fast. I have a 3.9 image where it is installed >> correctly and works; I have very little idea how that happened. My >> subsequent installation attempts appear not to be complete. >> >> SqueakMap appears to be going away in Pharo. Replacing it appear to >> be >> Installer, ScriptLoader, and maybe some of your tools to build the >> developer images. Is there a clear correct way to install packages >> now? >> Put another way, if I make an attempt to sort out installing the >> cryptography and SSL classes in Pharo, how would recommend attacking >> it? >> >> Pharo is not even in beta yet, so no complaints, but I am missing >> something on how to go from a new core image to something that is >> ready >> for use. >> >> Bill >> >> >> >> Wilhelm K. Schwab, Ph.D. >> University of Florida >> Department of Anesthesiology >> PO Box 100254 >> Gainesville, FL 32610-0254 >> >> Email: bschwab(a)anest.ufl.edu >> Tel: (352) 273-6785 >> FAX: (352) 392-7029 >> >> >> _______________________________________________ >> 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 >

Dec. 20, 2008

Re: [Pharo-project] focus and moving windows

by Adrian Lienhard

Hi Alex, I find the existing behavior also strange. Setting the threshold in HandMorph>>waitForClicksOrDrag:event: to 0 seems to fix this. Does this solve your problem? Adrian On Dec 20, 2008, at 00:18 , Alexandre Bergel wrote: > This was the case few years ago in Squeak > > Alexandre > > > On 19 Dec 2008, at 16:25, Bill Schwab wrote: > >> FWIW, I frequently have had troubles like that with graphical systems >> that were mixing current cursor position with positions from the >> events. >> >> Bill >> >> >> >> Wilhelm K. Schwab, Ph.D. >> University of Florida >> Department of Anesthesiology >> PO Box 100254 >> Gainesville, FL 32610-0254 >> >> Email: bschwab(a)anest.ufl.edu >> Tel: (352) 273-6785 >> FAX: (352) 392-7029 >> >> >>>>> Alexandre.Bergel(a)inria.fr 12/19/2008 12:42 PM >>> >> Dear List, >> >> The cursor position when I grab a window and move it around is not >> the >> >> same than the position where I clicked first. I do not know whether >> this is clear or not. >> Sadly, I do not have enough expertise on this to effectively >> produce a >> >> fix. >> >> Issue #420 >> >> Cheers, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> 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 >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 20, 2008

Re: [Pharo-project] New pharo-dev based on 10196

by Adrian Lienhard

In a recent discussion with Marcus and Lukas we came to the conclusion that a package universe for Pharo 1.0 would be the best solution. Somebody would be responsible to manage this universe and only add packages that are tested and known to work. I think this is really important that we have higher standards regarding external packages. In my experience with SqueakMap, the chance that a package actually works is less than the chance it is not working. This is a show stopper for newcomers. Our plan was to remove SqueakMap from Pharo-core, but I assume it could be put into the universe so it can be loaded again. Cheers, Adrian On Dec 20, 2008, at 01:04 , Bill Schwab wrote: > Damien, > > Thanks for making the new image. Is there a way to tell the image to > display walkbacks instead of going straight into the debugger? > > The new image seemed a nice excuse to play catch-up, which means > getting a few things loaded. > > Seaside - I recalled discussion of it, and quckly stumbled onto a > closed bug report about > > ScriptLoader new universalInstaller universe install: 'Seaside'. > > That appears to work. The cryptography team's work will be important. > This gets weird fast. I have a 3.9 image where it is installed > correctly and works; I have very little idea how that happened. My > subsequent installation attempts appear not to be complete. > > SqueakMap appears to be going away in Pharo. Replacing it appear to > be > Installer, ScriptLoader, and maybe some of your tools to build the > developer images. Is there a clear correct way to install packages > now? > Put another way, if I make an attempt to sort out installing the > cryptography and SSL classes in Pharo, how would recommend attacking > it? > > Pharo is not even in beta yet, so no complaints, but I am missing > something on how to go from a new core image to something that is > ready > for use. > > Bill > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 20, 2008

[Pharo-project] Fwd: [squeak-dev] Re: [ANN] ConflictFinder (help needed!)

by StÃ©phane Ducasse

Begin forwarded message: > From: Andreas Raab <andreas.raab(a)gmx.de> > Date: December 20, 2008 7:52:01 AM CEST > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > Subject: [squeak-dev] Re: [ANN] ConflictFinder (help needed!) > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > > Some progress: >> [x] Find a good name for the integration testing project. > > Done. The project is now on http://squeaksource.com/InT.html (as you > can see I got really creative ;-) BTW, the project is world-writable > - if you have an improvement just go right at it and post it into > the repository. > >> [x] Following dependencies. > > Done. ConflictFinder now also has a utility method that you can use > to run the entire process: > > ConflictFinder findConflictsInUniverse: > UUniverse systemUniverse updatePackagesViaWWW > >> [x] Providing the "right" answers automatically > > Done. ConflictFinder now provides answers for everything (and as you > can guess they are not particularly intelligent answers ;-) When > input is required, ConflictFinder logs both question and answer so > that if something goes wrong we can find out why. For confirmations > it flips a coin so be aware that a question like "would you like to > send 1 million dollars to Tim now?" might get the wrong answer. > > Also, logging has been improved to report warnings (like MC warnings > about unresolved dependencies) as well as errors if anything should > go wrong during load. > > Finally, I removed the LFP/Installer dependencies since I didn't > want to modify the base 3.10.2 system (loading LFP / Installer could > affect other parts of the system). > > Which means that in theory you should now be able to: > * Load the Integration package into 3.10.2 > * Fire up the above expression > * Have it run until Squeak runs out of memory > * Post the report about your run here. > > Since the weekend is up ahead maybe one or two of you have a bit of > time to give this a try. I'm currently running the test in the > background; below is my output so far (it looks like OBTraits is > missing a dependency in 3.10). > > Cheers, > - Andreas > > > --------------------------------------------------------------------- > > Analysing base system ... done. > > OSProcess > --------- > Loading ... > Finding conflicts... > > FFI > --- > Loading ... > Finding conflicts... > > Algernon > -------- > Loading ... > Question: Would you like to open an instance of Algernon on the > current project? > Answer: false > Finding conflicts... > > Video and Image Processing > -------------------------- > Loading ... > Finding conflicts... > > SmaCC runtime > ------------- > Loading ... > Finding conflicts... > > DynamicBindings > --------------- > Loading ... > Finding conflicts... > > SimpleLog > --------- > Loading ... > Finding conflicts... > > KomServices > ----------- > Loading ... > Finding conflicts... > > KomHttpServer > ------------- > Loading ... > Finding conflicts... > > SeasideAdaptersCompatibility > ---------------------------- > Loading ... > Finding conflicts... > > PostgreSQL Client > ----------------- > Loading ... > Finding conflicts... > > Lisp > ---- > Loading ... > Finding conflicts... > > Seaside > ------- > Loading ... > Question: Please choose a username for > the application 'config' > Answer: 2 - yeah, sure whatever > Finding conflicts... > > NetStrings > ---------- > Loading ... > Finding conflicts... > > Telnet > ------ > Loading ... > Question: The default fixed-width font is abominable. > Do you want me to create a better fixed-width font for you? > Answer: true > Finding conflicts... > > AST > --- > Loading ... > Finding conflicts... > > HTTPClient > ---------- > Loading ... > Finding conflicts... > Object>>displayString (conflicts with Seaside) > String>>trimBlanks (conflicts with Seaside) > > Refactoring Engine > ------------------ > Loading ... > Finding conflicts... > > Polymorph Widgets > ----------------- > Loading ... > Finding conflicts... > > Speech > ------ > Loading ... > Finding conflicts... > > TraitsOmniBrowser > ----------------- > Loading ... > WARNING: This package depends on the following classes: > OBMethodNode > OBClassAwareNode > OBSystemBrowser > OBClassCategoryNode > OBMethodCategoryNode > OBMethodDefinition > OBClassNode > You must resolve these dependencies before you will be able to load > these definitions: > OBAliasMethodNode > OBAliasMethodNode classSide>>on: > OBAliasMethodNode>>alias > OBAliasMethodNode>>alias: > OBAliasMethodNode>>fullName > OBAliasMethodNode>>name > OBAliasMethodNode>>source > OBClassAwareNode>>addCommentComponentsTo: > OBClassAwareNode>>addComponentsTo: > OBClassAwareNode>>browse > OBClassAwareNode>>defineClass:notifying: > OBClassAwareNode>>indent > OBClassAwareNode>>indentedNameIndicatingAbstractness > OBClassAwareNode>>signalSelectionOf: > OBClassAwareNode>>superior: > OBClassCategoryNode>>classAndTraitCommentsHierarchically > OBClassCategoryNode>>classesAndComponentTraits > OBClassCategoryNode>>classesAndTraitsHierarchically > OBClassCategoryNode>>classesShowingAbstractness > OBClassCategoryNode>>commentsShowingAbstractness > OBClassCategoryNode>>metaclassesAndClassTraitsHierarchically > OBClassCategoryNode>>metaclassesShowingAbstractness > OBClassCategoryNode>>registerAsShowingAbstractness: > OBClassNode>>categories > OBClassNode>>categoryNodeNamed: > OBClassNode>>dropSelector > OBClassNode>>localCategory > OBClassNode>>rename > OBClassNode>>traits > OBClassNode>>virtualCategories > OBClassTraitNode > OBClassTraitNode>>nonMetaName > OBClassTraitNode>>setClass: > OBClassTraitNode>>stringName > OBLocalMethodCategoryNode > OBLocalMethodCategoryNode classSide>>localCategory > OBLocalMethodCategoryNode classSide>>on: > OBLocalMethodCategoryNode>>category > OBLocalMethodCategoryNode>>methodReferences > OBLocalMethodCategoryNode>>methods > OBMethodCategoryNode classSide>>on:inTrait: > OBMethodCategoryNode>>methodReferences > OBMethodCategoryNode>>signifier > OBMethodCategoryNode>>signifyingName > OBMethodDefinition>>category > OBMethodDefinition>>text > OBMethodNode>>browseInheritance > OBMethodNode>>browseVersions > OBMethodNode>>dropOnTraitTransformation: > OBMethodNode>>isDescendantOfMethodCat: > OBMethodNode>>isRequired > OBMethodNode>>name > OBMethodNode>>signifyingName > OBMethodNode>>textcolor > OBMethodNode>>virtualMethodCategoryPrimeAttribute > OBNoCommentNode > OBNoCommentNode classSide>>on: > OBNoCommentNode>>color > OBNoCommentNode>>indent > OBNoCommentNode>>name > OBNoCommentNode>>setClass: > OBNoCommentNode>>stringName > OBNoCommentNode>>text > OBNonLocalMethodNode > OBNonLocalMethodNode>>actions > OBNonLocalMethodNode>>exclude > OBNonLocalMethodNode>>isAlias > OBNonLocalMethodNode>>isConflict > OBNonLocalMethodNode>>removeAlias > OBNonLocalMethodNode>>species > OBNonLocalMethodNode>>textcolor > OBRequiredBrowser > OBRequiredBrowser classSide>>defaultMetagraph > OBRequiredBrowser classSide>>title > OBRequiredSelectorNode > OBRequiredSelectorNode>>proposedHeader > OBRequiredSelectorNode>>remove > OBRequiredSelectorNode>>source > OBRequiredSelectorNode>>species > OBSystemBrowser classSide>>onTrait: > OBSystemBrowser classSide>>onTrait:category: > OBSystemBrowser classSide>>onTrait:selector: > OBSystemBrowser classSide>>openOnTrait: > OBSystemBrowser classSide>>openOnTrait:category: > OBSystemBrowser classSide>>openOnTrait:selector: > OBTraitCommentNode > OBTraitCommentNode classSide>>on: > OBTraitCommentNode>>setClass: > OBTraitCommentNode>>stringName > OBTraitCommentNode>>text > OBTraitCommentNode>>text: > OBTraitNode > OBTraitNode>>actions > OBTraitNode>>addToTraitCompositionOf: > OBTraitNode>>color > OBTraitNode>>indent > OBTraitNode>>name > OBTraitNode>>remove > OBTraitNode>>species > OBTraitNode>>stringName > OBTraitNode>>surroundingHierarchy > OBTraitNode>>trait > OBTraitStructureBrowser > OBTraitStructureBrowser classSide>>addTo:class:comment:metaclass: > OBTraitStructureBrowser classSide>>defaultMetaNode > OBTraitStructureBrowser classSide>>defaultMetagraph > OBTraitStructureBrowser classSide>>hierarchicalMetaNodeWithSignifiers > OBTraitStructureBrowser classSide>>temp > OBTraitStructureBrowser classSide>>title > OBTraitStructureBrowser>>messageCategoryList > OBTraitStructureBrowser>>messageList > OBTraitStructureBrowser>>onClass:category: > OBTraitStructureBrowser>>onTrait:category: > OBTraitTransformationNode > OBTraitTransformationNode classSide>>on: > OBTraitTransformationNode>>actions > OBTraitTransformationNode>>categories > OBTraitTransformationNode>>classRef > OBTraitTransformationNode>>dropSelector > OBTraitTransformationNode>>localCategory > OBTraitTransformationNode>>setTransformation: > OBTraitTransformationNode>>stringName > OBTraitTransformationNode>>trait > OBTraitTransformationNode>>traits > OBTraitTransformationNode>>transformation > OBVirtualMethodCategoryNode > OBVirtualMethodCategoryNode classSide>>actionsForParent: > OBVirtualMethodCategoryNode classSide>>on:inClass: > OBVirtualMethodCategoryNode classSide>>on:inTrait: > OBVirtualMethodCategoryNode classSide>>onSignifier:inClass: > OBVirtualMethodCategoryNode>>definition > OBVirtualMethodCategoryNode>>methods > OBVirtualMethodCategoryNode>>setName:class:signifier: > OBVirtualMethodCategoryNode>>signifier > OBVirtualMethodCategoryNode>>signifyingName > OBVirtualMethodCategoryNode>>species > > Finding conflicts... > LazyListMorph>>display:atRow:on: (conflicts with Polymorph Widgets) > > Folktale > -------- > Loading ... > Finding conflicts... > > Magritte-Model > -------------- > Loading ... > Finding conflicts... > > OmniBrowser > ----------- > Loading ... > Finding conflicts... > Text>>colorAt: (conflicts with TraitsOmniBrowser) > > Installer > --------- > Loading ... > WARNING: You are about to load new versions of the following > packages that have unsaved changes in the image. If you continue, > you will lose these changes. > > Installer-Core > Finding conflicts... > > Monticello2-Core > ---------------- > Loading ... > Finding conflicts... > > PieChartMorph > ------------- > Loading ... > Finding conflicts... > > Shout > ----- > Loading ... > Finding conflicts... > > SandstoneDb > ----------- > Loading ... > Finding conflicts... > > Pier-Model > ---------- > Loading ... > Finding conflicts... > > PWS > --- > Loading ... > Finding conflicts... > > OmniBrowser-TraitsIntegration > ----------------------------- > Loading ... > Finding conflicts... > > VBRegex > ------- > Loading ... > Finding conflicts... > > SqCVS > ----- > Loading ... > Finding conflicts... > >

Dec. 20, 2008

[Pharo-project] Fwd: [squeak-dev] [ANN] ConflictFinder (help needed!)

by StÃ©phane Ducasse

Begin forwarded message: > From: Andreas Raab <andreas.raab(a)gmx.de> > Date: December 17, 2008 6:52:02 AM CEST > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > Subject: [squeak-dev] [ANN] ConflictFinder (help needed!) > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > > Folks - > > In light of Greg's recent issues with conflicts between packages I > spent this evening writing a little tool called ConflictFinder. What > it does is taking a set of actions and computes conflicts arising > from running these actions. In its simplest use it works like here: > > ConflictFinder findConflictsIn:{ > 'FooPackage' -> [(FileStream readOnlyFileNamed: 'Foo.st') fileIn]. > 'MantisFix1234' -> [Installer mantis ensureFix: 1234]. > 'Mumble' -> [MczInstaller installFileNamed: 'Foo-xyz. > 123.mcz']. > }. > > It prints the analysis to the transcript by default but you can > override its log file appropriately. Since I didn't know how to get > the universe browser to load stuff automatically, I decided to cheat > and run it like here to test it on the problem in question: > > ConflictFinder findConflictsIn:{ > 'SmallDEVS' -> [self notify: 'Please load SmallDEVS']. > 'Polymorph' -> [self notify: 'Please load Polymorph']. > }. > > After loading the packages manually when prompted the analysis > showed this result: > > LabelMorph (conflicts with SmallDEVS) > LabelMorph>>initialize (conflicts with SmallDEVS) > LabelMorph>>drawOn: (conflicts with SmallDEVS) > StringMorph>>minHeight (conflicts with SmallDEVS) > > So there is a conflict between LabelMorph in the packages *as well > as* StringMorph>>minHeight (which happens to be an equivalent > modification but shows that the tool does indeed unearth unexpected > conflicts). > > The next step would be to find someone who ties this into the > universe browser and just starts loading packags randomly. At which > point a concerted community action of just people reporting back > their results should be able of finding 90% of the conflicts in the > current PU in no time. > > Any volunteers for helping with this? > > Cheers, > - Andreas >

Dec. 20, 2008

[Pharo-project] Fwd: [squeak-dev] Re: Resume Problems

by StÃ©phane Ducasse

Begin forwarded message: > From: "Eliot Miranda" <eliot.miranda(a)gmail.com> > Date: December 19, 2008 7:52:21 PM CEST > To: "The general-purpose Squeak developers list" <squeak-dev(a)lists.squeakfoundation.org > > > Subject: Re: [squeak-dev] Re: Resume Problems > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > > Hi Zulq, > > I made sure this was fixed in VisualWorks. Steve Dahl and I > fixed this together. Here's an analogous fix for Squeak. The > essential change is to make Object>>doesNotUnderstand: check if the > MessageNotUnderstood exception was handled or not, so > > MessageNotUnderstood new > message: aMessage; > receiver: self; > signal. > ^ aMessage sentTo: self. > > is replaced with > > (exception := MessageNotUnderstood new) > message: aMessage; > receiver: self. > resumeValue := exception signal. > ^exception reachedDefaultHandler > ifTrue: [aMessage sentTo: self] > ifFalse: [resumeValue] > > HTH > > On Fri, Dec 19, 2008 at 8:13 AM, Zulq Alam <me(a)zulq.net> wrote: > Hi Klaus, > > > Klaus D. Witzel wrote: > Nah, the result has nothing to do with #on:do: resuming with 1, you > better > try > > [('abc' + 1) + 1] > on: MessageNotUnderstood > do: [:e | e resume: -1] > > which still says 2. This because someone, behind you back, put > #asNumber > arithmethic into ByteString ... now this attempts (Number readFrom: > 'abc') > which gives 0 for your +1 +1 and so 2. > > You may want to start DNU testing with ('abc' break; + 1) and then see > where it goes. > > Hmm... I think something is not right or at the very least the > semantics are subtly different than I expect. > > VisualWorks: > [Object new blah + 1] > on: MessageNotUnderstood > do: [:e | e resume: 1] " = 2 " > > [MessageNotUnderstood signal + 1] > on: MessageNotUnderstood > do: [:e | e resume: 1] " = 2 " > > Squeak: > [Object new blah + 1] > on: MessageNotUnderstood > do: [:e | e resume: 1] " infinite recursion!!! " > > [MessageNotUnderstood signal + 1] > on: MessageNotUnderstood > do: [:e | e resume: 1] " = 2 " > > > If I look at doesNotUnderstand: in both I see that in VW the resumed > value is returned. In Squeak is is not... surely this can't be right? > > As for my problem, I think a simpler solution is to pass an adaptor/ > proxy object to the block rather than the tag itself. This adaptor > can then marshal behaviour such that it will act as a message eating > null if it receives an MNU from the tag it's looking after. > > Thanks, > Zulq. > > >

Dec. 20, 2008

Re: [Pharo-project] Fwd: [Etoys] [RELEASE] Etoys 4.0

by StÃ©phane Ducasse

Ok so this is clear, mike do you know if we could get our hands on the changes Yoshiki did I could not understand his authoer Checker tools if somebody could investigate that we could then have an effort to fix Pharo. Stef On Dec 19, 2008, at 5:33 PM, Adrian Lienhard wrote: > The list for 1.0 is on the wiki: http://code.google.com/p/pharo/wiki/Milestones > > Adrian > > On Dec 19, 2008, at 17:28 , StÃ©phane Ducasse wrote: > >> I do not remember the list that we wrote on the board at Bern. >> I'm sure we sent it to the list. >> >> Stef >> >> On Dec 19, 2008, at 5:26 PM, Michael Rueger wrote: >> >>> >>> Hi all, >>> >>> did we agree whether to make sure Pharo 1.0 is license clean as >>> well? >>> Just can't remember... >>> >>> Michael >>> >>> _______________________________________________ >>> 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 >

Dec. 20, 2008