December 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3485 in pharo: VMMaker does not load on Pharo 1.2

by pharo＠googlecode.com

Updates: Status: Fixed Comment #9 on issue 3485 by johanbri...(a)me.com: VMMaker does not load on Pharo 1.2 http://code.google.com/p/pharo/issues/detail?id=3485 Verified the attached changeset.

Dec. 30, 2010

[Pharo-project] [ANN] SqueakMovieMorph (Alpha) plays any video file playable by QuickTime

by DeNigris Sean

Installation: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfFFI'; load. ((Smalltalk at: #ConfigurationOfFFI) project latestVersion) load. Gofer new squeaksource: 'SophieGoldDig'; package: 'SpdQT'; load. Then, blow your mind by playing a video in-image with: aURI := URI fromString: 'file:///path/to/video.ext'. movie := QuickTimeMovie openMovieFromURI: aURI. m := SqueakMovieMorph openOn: movie. Pharo 1.1.1 - there will be two errors â for both, go into the debugger and remove the isFinalizationSupported checks. See http://seandenigris.com/blog/?p=723 for details. Sean DeNigris sean(a)clipperadams.com

Dec. 30, 2010

Re: [Pharo-project] Issue 2445 in pharo: recent submission tools does not contain the recents message

by pharo＠googlecode.com

Comment #15 on issue 2445 by marianopeck: recent submission tools does not contain the recents message http://code.google.com/p/pharo/issues/detail?id=2445 yes, can call it from #cleanUpForRelease ;) But I can do it if you are busy, don't worry.

Dec. 30, 2010

Re: [Pharo-project] put back Pharo 1.0 colors for Shout [WAS] Re: what happened with Shout colors in Pharo 1.1?

by Mariano Martinez Peck

Done. Next Pharo1.2 images should have this change... Name: Shout-MarianoMartinezPeck.98 Author: MarianoMartinezPeck Time: 30 December 2010, 4:43:24 pm UUID: de55ed1a-3f90-4e9b-bcb8-54f3175a35c8 Ancestors: Shout-FranciscoOrtizPenaloza.97 Put back the original Shout colors of Pharo 1.0 instead of Pharo 1.1 cheers mariano On Thu, Dec 30, 2010 at 3:37 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > On Dec 30, 2010, at 2:23 PM, Mariano Martinez Peck wrote: > > > > > > > On Thu, Dec 30, 2010 at 2:12 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > ok :) > > I know that people love the greenish color (I just hate it). > > but this is ok :) > > > > > > But wait...green is only used for comment. And in both cases it is the > same (pharo 1.0 and 1.1). So...you are discussing about something else ;) > No just the greenish color of the text :) > > > > So...can I go ahead for this change and put back the colors of Pharo 1.0 > ? > > yes ;) > > > > > I changed the title so that people can read it. > > > > cheers > > > > mariano > > >

Dec. 30, 2010

Re: [Pharo-project] Issue 2445 in pharo: recent submission tools does not contain the recents message

by pharo＠googlecode.com

Comment #14 on issue 2445 by Benjamin.VanRyseghem.Pharo: recent submission tools does not contain the recents message http://code.google.com/p/pharo/issues/detail?id=2445 There is a method to clean the RecentMessageList named MethodReference>>#clearAll. I will renamed it cleanUp this evening if you want ^^ (I'm a little bit busy right now ^^)

Dec. 30, 2010

Re: [Pharo-project] Issue 3485 in pharo: VMMaker does not load on Pharo 1.2

by StÃ©phane Ducasse

***Thanks*** johan. this is what I thought. Archeology over inconsistency. Stf On Dec 30, 2010, at 11:56 AM, Johan Brichau wrote: > wow.... let me take a step back here. > > First of all, *nothing* was ever imposed nor banned. > As far as I'm concerned, SourceReference is a work in progress and the timestamp format that it parses has been reconstructed using archeology over different sources. > > Going back 2 spaces and parsing from there is what I did at first but that soon proved to be *not* correct. Please see formats 2,4 & 5. I did not invent those formats but found them in the sources. > It seems there are different formats out there and the goal was to extract timestamps from as many methods as possible. > > I'll improve the way it extracts timestamps and make a graceful fallback. > > Johan > > On 30 Dec 2010, at 10:38, StÃ©phane Ducasse wrote: > >> Eliot >> >> johan is not that idiot. So far when I see what they built for their company this is more the inverse. >> He spent several days trying to figure out how to manage decently the source. I will check with him what they did but they probably tried to extract information from all the methods in the system. >> >> >> changeStamp >> "Answer a string to be pasted into source code to mark who changed it and when." >> ^ Author fullName , ' ' , Date today mmddyyyy, ' ', >> ((String streamContents: [:s | Time now print24: true on: s]) copyFrom: 1 to: 5) >> >> Now how can I identify a comment from a person and and action? >> Beginning until a space? >> date end until a space? >> >> We can do that. It looks like a hack to me. >> >> People are building tools to **help** us but if we push on them unstructured data then we push the shit on them. >> Let's take a simple example: benjamin smart, young student rewrote the recentMessage tools and the finder for fun. Now the >> state of MethodReference and its clunky use made something trivial just a big pain. I do not even talk about the change format >> which need scanner invocation to distinguish between a class def and a doit. >> So if we do not offer a good infrastructure we will be stuck for years with old tools. Some people do not like change at all >> but we value it for the better. >> >> >> >> >> On Dec 30, 2010, at 12:47 AM, Eliot Miranda wrote: >> >>> >>> >>> On Wed, Dec 29, 2010 at 1:51 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> The documented format is: >>>> >>>> Timestampstrings can be of the form: >>>> <authorname><date><time>. >>>> <authorname><date> >>>> <date><time> >>>> <date><time><authorname> >>>> <date><authorname> >>>> <historical> >>>> >>>> >>>> Says /who/? When I created all these timestamps to document a refactoring change there was no documented restriction on timestamps I could see. Why impose restrictions which have little value? Why needlessly break compatibility? That timestamp *contains useful information*. Why ban it? >>>> >>>> If you *want* VMMaker to load in Pharo you need to ensure that Pharo supports the timestamps *that exist* not the timestamps you want to impose on the community. >>> >>> Eliot we do not impose anything to the community. Please do not bash us we have enough to do without that! >>> >>> Steph, /I'm/ not bashing. I got bashed. Suddenly the comments I'd put in VMMaker were to be banned by Pharo. Look, the timestamp syntax if any, is defined by Utilities class>>changeStamp, along with the implicit restriction that the changeStamp can't contain an exclamation point, or it'll break parsing. Utilities class>>changeStamp is essentially anything followed by date and time, because there are /no/ restrictions on what one sets the Author initials to be (some people use full name, some people use initials, some people use put other stuff in there, but it's free apart from the $!). So to parse date and time one has to start at the end of the timestamp, go back two spaces and parse from there (ooh, difficult ;) ). There's no need for anything else. Why make life difficult for the community by imposing syntax when none existed before? All you'll do is make work and frustrate people. Is Pharo about helping or hindering? I think it's about helping, but the above syntax restrictions don't feel like that. KISS, right? If you want to find the date or time in a timestamp start at the end, and leave the beginning free from interpretation. >>> >>> 2Â¢ >>> >>> >>> Apparently the code was like that and people (may be johan) started to make sense out of it. >>> >>> Stef >>> >> >> > >

Dec. 30, 2010

Re: [Pharo-project] put back Pharo 1.0 colors for Shout [WAS] Re: what happened with Shout colors in Pharo 1.1?

by StÃ©phane Ducasse

On Dec 30, 2010, at 2:23 PM, Mariano Martinez Peck wrote: > > > On Thu, Dec 30, 2010 at 2:12 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > ok :) > I know that people love the greenish color (I just hate it). > but this is ok :) > > > But wait...green is only used for comment. And in both cases it is the same (pharo 1.0 and 1.1). So...you are discussing about something else ;) No just the greenish color of the text :) > > So...can I go ahead for this change and put back the colors of Pharo 1.0 ? yes ;) > > I changed the title so that people can read it. > > cheers > > mariano

Dec. 30, 2010

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

by pharo＠googlecode.com

Comment #8 on issue 3489 by laurent.laffont: Pharo 1.2-dev still uses Preferences in BaseSoundSystem http://code.google.com/p/pharo/issues/detail?id=3489 On Hudson server ? https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/…

Dec. 30, 2010

Re: [Pharo-project] Issue 3485 in pharo: VMMaker does not load on Pharo 1.2

by pharo＠googlecode.com

Comment #8 on issue 3485 by johanbri...(a)me.com: VMMaker does not load on Pharo 1.2 http://code.google.com/p/pharo/issues/detail?id=3485 - Improved the parser to return the epoch datetime whenever it cannot extract a timestamp - Timestamp is computed lazily instead of all the time (should improve performance of MethodReference whenever a timestamp is not needed) I have to check the fixes in a latest image again. Once that is done, I will tag this issue as fixed (but now I have to run... will do it later today) Attachments: SourceReferenceTimeStampParserFix.1.cs 4.7 KB

Dec. 30, 2010

Re: [Pharo-project] Issue 2445 in pharo: recent submission tools does not contain the recents message

by pharo＠googlecode.com

Updates: Cc: Benjamin.VanRyseghem.Pharo Benjamin.VanRyseghem Comment #13 on issue 2445 by marianopeck: recent submission tools does not contain the recents message http://code.google.com/p/pharo/issues/detail?id=2445 Marcus, I sent this email but Benjamin didn't answer yet: http://forum.world.st/RecentMessages-history-should-be-cleaned-in-ScriptLoa…

Dec. 30, 2010