- Pharo-dev - lists.pharo.org

[Pharo-project] Text>>fromString: and String>>asText
by Fernando olivero Aug. 3, 2010

Aug. 3, 2010

Name: SLICE-Issue-2745-TextFromStringAddingBlackAttribute-FernandoOlivero.1 Author: FernandoOlivero Time: 3 August 2010, 3:32:02 pm UUID: 85d642dd-87c1-4cab-9aa2-629ab10a6bd8 Ancestors: Dependencies: Collections-Text-FernandoOlivero.37 Added the black color attribute to all text's, created sending #asText ( which in turn sends Text>>fromString: ). Which produces a transparent color when rendered sending: aCanvas paragraph: paragraph bounds: bounds color: self fillStyle I've added the black color attribute by default.

1 0

[Pharo-project] [update 1.2] #12075
by StÃ©phane Ducasse Aug. 3, 2010

Aug. 3, 2010

12075 ----- - Issue 2296: Point>>closeTo. Thanks Alexandre Bergel and Henrik Johanssen. - SUnit Announcement post fix. - Issue 2617: Fix restart in blocks in debugger. Thanks Henrik Johanssen. - Issue 2364: FileList menu more... is bogus. Thanks Carlo Teixeira - Issue 1767: Method Finder gives UndefinedObject error on search. Thanks Alexandre Bergel. Thanks Marcus, patchinko and Gary. Stef

1 0

[Pharo-project] Something I don't see in ImageSegment
by Mariano Martinez Peck Aug. 3, 2010

Aug. 3, 2010

Hi. ImageSegment uses GC to compute the out pointers. Basically, to a given array of roots (a graph) it does: 1) It marks the rootArray and all root objects by turning on the Garbage Collector bit in the object header of those particular objects. 2) Then does a mark pass over all objects. This will stop at our marked roots leaving our segment unmarked in their shadow. 3) Finally, it unmarks the rootArray and all root objects. 4) Only external objects are now marked. The unmarked objects in the graph of objects of the arrays are those who will be put in the WordArray (the segment) and those who are marked to the outPointers. However, I don't see where step 2) is done in Interpreter >> primitiveStoreImageSegment In a piece of such method it does: "Then do a mark pass over all objects. This will stop at our marked roots, thus leaving our segment unmarked in their shadow." savedYoungStart := youngStart. youngStart := self startOfMemory. "process all of memory" "clear the recycled context lists" freeContexts := NilContext. freeLargeContexts := NilContext. self markAndTraceInterpreterOops. "and special objects array" youngStart := savedYoungStart. "Finally unmark the rootArray and all root objects." self longAt: arrayOfRoots put: ((self longAt: arrayOfRoots) bitAnd: AllButMarkBit). ......continue....... But here I see it is only marking Interpreter oops, not all objects. And I don't see where all objects are marked even in the code that follows this little piece. You can see the comment: "Then do a mark pass over all objects" and even without the comment it makes sense to mark all objects in order to detect outPointers. Does anyone has a hint? Thanks Mariano

3 7

[Pharo-project] Limitation of number os literals in a method?
by nullPointer Aug. 3, 2010

Aug. 3, 2010

I get that error when I try save a CLView builded with the UIBuilder More than 256 literals referenced. You must split or otherwise simplify this method. The 257th literal is: 128 Select Proceed to continue, or close this window to cancel the operation. How I can solve that problem? The method than I try save is generated programmatically... Thanks -- View this message in context: http://forum.world.st/Limitation-of-number-os-literals-in-a-method-tp230874… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

5 11

[Pharo-project] Fwd: [Communities] Re: Colstme in June
by Norbert Hartl Aug. 3, 2010

Aug. 3, 2010

Begin forwarded message: > As promised a short reminder for the upcoming 4th Cologne Smalltalk Meetup. The poll about the date is still open at [1] and the deadline will be a week from now. More about it at [2]. > > Cheers, > Alex > > [1] http://www.doodle.com/cskz2yetns5x359v > [2] http://colstme.selfish.org

1 0

[Pharo-project] [update 1.2] #12074
by StÃ©phane Ducasse Aug. 3, 2010

Aug. 3, 2010

12074 ----- - Issue 2169: FileDirectory>>matchingEntries: criteria is broken. Thanks CarloTeixeira. - Issue 2738: Browse instance/?/class button should provide fly by help. Thanks Torsten Bergmann. - Issue 1068: Mac: Quit from host menu not working anymore. Thanks Mike Roberts. - Issue 2721: Extending SUnit to emit announcement. Thanks Alexandre Bergel Thanks. I like all the discussions we have to produce a better system. Stef

1 0

[Pharo-project] Problem with InstructionPrinter?
by James Ladd Aug. 3, 2010

Aug. 3, 2010

Hi All, InstructionPrinter printInstructionsOn: doesnt print anything for variable accessor methods. Is this correct and expected? I have a class with an instance variable called 'first' and I have a method called 'first' which simply answers the instance variable. first ^ first When I dump the bytecode for this I get nothing. However, when I add the following to the method the result is as expect, ie: the instance variable is answered. first |x| x := 1. ^ first 13 <76> pushConstant: 1 14 <68> popIntoTemp: 0 15 <00> pushRcvr: 0 16 <7C> returnTop Why is there no bytecode for the simpler case? Rgs, James.

2 1

Aug. 2, 2010

hi guys I know that some of you would like to contribute but are busy, scared ... I spent three hours to go over the bug entries. Feel free to pick one and fix it: So now you can easily contribute. Just do it. Stef Some easy fixes: -------------- for the fixes based on squeak changed, it often requires to check the code and run pharo tests. http://code.google.com/p/pharo/issues/detail?id=2603 Issue 2603 isRunningCog http://code.google.com/p/pharo/issues/detail?id=2704 Issue 2704: Tests for broken withNoLineLongerThan: behavior. http://code.google.com/p/pharo/issues/detail?id=2693 http://code.google.com/p/pharo/issues/detail?id=2661 Issue 2661: File name correction for unix to allow http://code.google.com/p/pharo/issues/detail?id=2706 Issue 2706: Mirror primitive tests succeed on the Cog VMs. http://code.google.com/p/pharo/issues/detail?id=1746 Issue 1746: ReferenceStream>>readOnlyFileNamed: is missing http://code.google.com/p/pharo/issues/detail?id=1767 Issue 1767: Method Finder gives UndefinedObject error on search http://code.google.com/p/pharo/issues/detail?id=1765 Issue 1765: JPEGReadWriter>>#decompressionTest should be made into a Sunit Test http://code.google.com/p/pharo/issues/detail?id=2265 Issue 2265: to check MCWorkingCopyBrowser from Squeak http://code.google.com/p/pharo/issues/detail?id=2063 Issue 2063: NumberTest http://code.google.com/p/pharo/issues/detail?id=2266 Issue 2266: MessageNames selectorListIndex http://code.google.com/p/pharo/issues/detail?id=2176 Issue 2176: Integrated DirectoryEntry>>attributes http://code.google.com/p/pharo/issues/detail?id=2296 Issue 2296: Point>>closeTo http://code.google.com/p/pharo/issues/list?cursor=2573 Issue 2573: Make it possible to run cleanup non-interactively. http://code.google.com/p/pharo/issues/detail?id=2609 Issue 2609: getSystemAttribute: 2 -> documentPath Some important ones: ------------------ http://code.google.com/p/pharo/issues/detail?id=2579 http://code.google.com/p/pharo/issues/detail?id=2698 http://code.google.com/p/pharo/issues/detail?id=2662 Issue 2662: value: primitives http://code.google.com/p/pharo/issues/detail?id=1801 Issue 1801: Rescue Sophie Undo framework http://code.google.com/p/pharo/issues/detail?id=2177 Issue 2177: Generalize stream protocol #readInto:startingAt:count: http://code.google.com/p/pharo/issues/detail?id=1921 Issue 1921: Class>>Binding Fix Issue 1981: Raising DuplicateError Exception in class builder http://code.google.com/p/pharo/issues/detail?id=1981 http://code.google.com/p/pharo/issues/detail?id=2146 Issue 2146: Fix SystemChangeNotification for traits. http://code.google.com/p/pharo/issues/detail?id=1899 Issue 1899: MethodDictionary improvement http://code.google.com/p/pharo/issues/detail?id=2315 Method Dictionary Compact protocol to investigate http://code.google.com/p/pharo/issues/list?cursor=2313 Issue 2313: HashedCollectionIntegrityTest http://code.google.com/p/pharo/issues/detail?id=2583 Issue 2583: COG - MessageTally Issue 2619: ignore vm parameters with nil value in MessageTally, so it can be used in Cog http://code.google.com/p/pharo/issues/detail?id=2584 COG- COG- LargeNegativeInteger to be compact at 5 http://code.google.com/p/pharo/issues/detail?id=2567 Issue 2567: evaluate the finalizers outside the protected block in WeakRegistry http://code.google.com/p/pharo/issues/detail?id=2564 Issue 2564: WeakKeyDictionary finalizeValue tests http://code.google.com/p/pharo/issues/list?cursor=2551 weakstructure http://code.google.com/p/pharo/issues/detail?id=2620 Issue 2620: BlockClosure asContext losing bound variable? http://code.google.com/p/pharo/issues/detail?id=2617 Issue 2617: Fix restart in blocks in debugger http://code.google.com/p/pharo/issues/detail?id=2618 Issue 2618: a bit faster DependentsArray >> #select:

6 9

[Pharo-project] Alien on Pharo 1.2 on Mac
by Luc Fabresse Aug. 2, 2010

Aug. 2, 2010

Hi all, We provide a usable version of Alien to Pharo 1.2 (all tests green on OSX). We committed the corrected package on the Ocean squeaksource repository : http://squeaksource.com/Ocean (Alien-Core-LucFabresse.64.mcz) We didn't look in details to the method SystemDictionary>>recreateSpecialObjectsArray introduced by Alien-Core-63. It is now unsed because Smalltalk points to a SmalltalkImage. This need to be checked before possibly removal. Another point would be to update the metacello configuration ConfigurationOfAlien. Luc and Noury

3 4

[Pharo-project] ProgressDisplay package features
by Ralph Boland Aug. 2, 2010

Aug. 2, 2010

Cool Can you tell us some of the added features? Stef > I recently released the first draft of my package ProgressDisplay to > SqueakSource. > It is like SystemProgressMorph et. al. but with a lot of bells and > whistles added. > It is not a suitable replacement for SystemProgressMorph though because it is > too large and specific for that. Well you asked for it: 1) You can pass an applyBlock rather than a duringBlock. The progressDisplay then applies the apply block to each element to each of the users values updating the display as it does so. The users values can be the values min..max or the values of a stream. 2) You can set a jump value k such that the display is updated once for each k times a display update request is sent. The minimum time that must pass before the display is updated is settable (it is fixed with SystemProgressMorph). Finally, a check is made that a display request update will actually modify the progressBar before the modification is performed. These changes were made because with SystemProgressMoprh, in some circumstances, the progressBar could take excessive amounts of time. However the last of these changes was probably all that was needed. 3) You can set the progressDisplay to catch user interrupts. Unfortunately this doesn't work correctly currently. The interrupt is caught but not processed until the progressBar closes. :-( I don't know how to fix this so suggestions or a fix most welcome. 4) You can set the start point to be other than at the beginning. If you start not at the beginning then you can set the progressDisplay to wrap once the end is reached. This is a weird feature but I need it for when I run a large collection of tests (not SUnit tests but similar). Say I run 1000 tests and the 900th test fails. I fix the problem and rerun the tests. I don't want to start at test one, I want to start at test 900, run tests 900-1000 and then run tests 1-899. The ProgressDisplay supports this and is the main reason I created it. 5) I have added an exception EarlyCompletionExit. This exception will be caught by progressDisplay if generated and result in the current progressBar being closed cleanly. If there is only one progressBar the entire display is closed. 6) If you want you can display the current value being processed and the total. The current value can be the user's value, the count of processed values, count of the number of user values remaining to be processed, the estimate of the amount of time remaining, or the time remaining estimate alternating with one of user value, count, countDown. The current value and total can be labelled if desired. The start poin, if not the beginning, can also be labelled. 7) The display does not flicker as much as SystemProgressMorph though this could still be improved. 8) Anything else I have forgotten. There are large number of examples in class RunnProgressMorphExample which is a subclass of ExampleCase. In my image ExampleCase is an subclass of CodeCase and TestCase is also a subclass of CodeCase. Someday I hope to have TestCase refactored to have CodeCase as a superclass in Squeak/Pharo. The examples use a number of utility classes which will eventually be moved to other packages. Some of them are: 1) ArrayPermutationsStream. Generates the permutations of a SequenceableCollection in a stream. Iteration, not recursion, is used. Ordering is not Lexicographic. 2) RangeList. Stores a sorted list of values where consecutive values are stored by listing them as an Interval. Example: 1,5-9,12,15,31-90 Example: $a,$c,$k-$t,$z This class is not complete. There are two subclasses: NumberRangeList and PositiveNumberRangeList also not complete. 3) NumberRangeListStream. Stream version of NumberRangeList. 4) NumericMultiplicityPartitionStream. For a given integer n, generates all numeric partitions of n (sums of positive numbers that add up to n) in lexicographic order. This can be combined with method SequenceableCollection>>multisetPermutationsDo: to generate arrays of size n containing combinations of the elements of 1..n with replacement (i.e. duplicates allowed). In another package I plan to use this for generating large numbers of test cases. There are also a scattering of useful methods in places like Object, Nil, and SequenceableCollection. Hope this helps. Ralph Boland

3 2