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

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

by StÃ©phane Ducasse

>> > > you mean that it was reverse-engineered to determine the specs for > stamp field by looking at it? > wow. :) probably try and error trying to parse all the methods in the system. >>>> > Let me clarify, what i proposing. > > Entries like: > > ADPCMCodec methodsFor: 'private' stamp: 'zz (auto pragmas 12/08) 3/2/2004 07:58' > > should look like: > > ADPCMCodec methodsFor: 'private' author: 'zz' comment: 'auto pragmas > 12/08' timestamp:'3/2/2004 07:58' > > and we can leave a potential for future extensions, by taking a > message pattern which starts from > #methodsFor: .... > > and store all keywords which follows it like 'author' 'comment' 'timestamp' > in a dictionary, with key/value pairs. > > Also, it would be nice to simply evaluate this using smalltalk > compiler, but doing a trick with substituting global name bindings > like ADPCMCodec with proxies, which understand these messages. > Then you will have a clean and extensible changeset/smalltalk source > code reader. > What could be simpler? Sounds good and we need to handle not compliant methods. Next question is what do we do for 1.2. Because how can tools relying on time work? Finally point: I have more and more problem to get Timestamp a subclass of DateAndTime. It looks to me like Car inherits from Wheel. Stef

Dec. 29, 2010

Re: [Pharo-project] Issue 3490 in pharo: ConfigurationOfPharo still uses Preferences

by pharo＠googlecode.com

Updates: Status: Invalid Comment #2 on issue 3490 by marianopeck: ConfigurationOfPharo still uses Preferences http://code.google.com/p/pharo/issues/detail?id=3490 Yes, because of history. It is used by versions and baselines of pharo 1.0 and 1.1. But, as you can see, none of the version/baselines 1.2 use it. So, it is ok.

Dec. 29, 2010

[Pharo-project] Issue 3493 in pharo: Remove definitely MessagesNames and MethodFinder

by pharo＠googlecode.com

Status: Accepted Owner: marianopeck Labels: Milestone-1.3 New issue 3493 by marianopeck: Remove definitely MessagesNames and MethodFinder http://code.google.com/p/pharo/issues/detail?id=3493 In Pharo 1.2, we remove those guys from the menu. Now in 1.3 we should really remove them (remove its code).

Dec. 29, 2010

Re: [Pharo-project] source.lukas-renggli.ch is down

by Philippe Marschall

On 29.12.2010 11:01, StÃ©phane Ducasse wrote: > We know. I will reask again for our web-dav server. You're actually working in a big bank, aren't you Stef? I can tell by the time it takes you to get a web-dav server ;-) Cheers Philippe

Dec. 29, 2010

Re: [Pharo-project] Issue 3492 in pharo: Remove MessagesNames and MethodFinder from menu

by pharo＠googlecode.com

Updates: Status: Fixed Labels: Milestone-1.2 Comment #1 on issue 3492 by marianopeck: Remove MessagesNames and MethodFinder from menu http://code.google.com/p/pharo/issues/detail?id=3492 Fix in inbox: Name: SLICE-Issue-3492-RemoveMessagesNamesAndMethodFInderFromMenu-Marinao.1 Author: Marinao Time: 29 December 2010, 11:05:47 am UUID: 569da32e-dcb9-4f0f-8ea2-6e433f5ec55a Ancestors: Fix to issue 3492

Dec. 29, 2010

[Pharo-project] Issue 3492 in pharo: Remove MessagesNames and MethodFinder from menu

by pharo＠googlecode.com

Status: Accepted Owner: marianopeck New issue 3492 by marianopeck: Remove MessagesNames and MethodFinder from menu http://code.google.com/p/pharo/issues/detail?id=3492 imagine it is your first time you open pharo...you will have THREE tools which looks similar. You don't know its differences, nor which to use. And the menu is starting to be long. we must at least remove them from the menu (not the code), Poeple that prefer MessagesSend / MethodFInder know how to put them back on the menu or open them by hand. In 1.3 we defintly remove the code.

Dec. 29, 2010

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

by Igor Stasenko

On 29 December 2010 10:54, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Dec 28, 2010, at 8:48 PM, Igor Stasenko wrote: > >> On 28 December 2010 19:04, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>> >>> >>> On Tue, Dec 28, 2010 at 8:47 AM, <pharo(a)googlecode.com> wrote: >>>> >>>> Comment #3 on issue 3485 by stephane.ducasse: VMMaker does not load on >>>> Pharo 1.2 >>>> http://code.google.com/p/pharo/issues/detail?id=3485 >>>> >>>> The documented format is: >>>> >>>> Timestampstrings can be of the form: >>>> Â Â Â Â Â Â Â Â <authorname><date><time>. >>>> Â Â Â Â Â Â Â Â <authorname><date> >>>> Â Â Â Â Â Â Â Â <date><time> >>>> Â Â Â Â Â Â Â Â <date><time><authorname> >>>> Â Â Â Â Â Â Â Â <date><authorname> >>>> Â Â Â Â Â Â Â Â <historical> >>>> >> wow thats incredible.. >> >> can you add there support for: >> >> <author-><time><-name><date> >> >> cause i prefer this format for myself? :) > > > In fact I do not know where this information is coming from. > May be johan when he tried to recover what was stored in the strings. > you mean that it was reverse-engineered to determine the specs for stamp field by looking at it? wow. :) >>> 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? >> >> Information is useful, if it can be understood by system , which can >> extract three distinct fields, >> like <author> Â <comment> <date&time> >> but when information looks like a soup where different things put in >> random order and random <historical> format, >> then it is just garbage. > > Yes structuring a bit would help tool builders else forget it, all our tools will be try and error. > I like that structure: <author> Â <comment> <date&time> it makes sense > Let me clarify, what i proposing. Entries like: ADPCMCodec methodsFor: 'private' stamp: 'zz (auto pragmas 12/08) 3/2/2004 07:58' should look like: ADPCMCodec methodsFor: 'private' author: 'zz' comment: 'auto pragmas 12/08' timestamp:'3/2/2004 07:58' and we can leave a potential for future extensions, by taking a message pattern which starts from #methodsFor: .... and store all keywords which follows it like 'author' 'comment' 'timestamp' in a dictionary, with key/value pairs. Also, it would be nice to simply evaluate this using smalltalk compiler, but doing a trick with substituting global name bindings like ADPCMCodec with proxies, which understand these messages. Then you will have a clean and extensible changeset/smalltalk source code reader. What could be simpler? -- Best regards, Igor Stasenko AKA sig.

Dec. 29, 2010

Re: [Pharo-project] How I can do SWF files playing in pharo?

by Hilaire Fernandes

Sophie use Quicktime to play external media Hilaire Le 28/12/2010 20:34, Denis Kudriashov a Ã©crit : > Thank you. I will try sophie code > > 2010/12/28 Sean P. DeNigris > <sean(a)clipperadams.com > <mailto:sean@clipperadams.com>> > > > I checked OpenSophie. I was able import a Flash movie, but when I > played it, > the sound played for just a moment and the video only updated when I > clicked > pause or play. I don't know what version it is, but the file I imported > was: H.264, 320 x 216, Millions; AAC, Stereo, 22.050 kHz. I had > written a > short blog post on how to dig into Sophie at > http://seandenigris.com/blog/?p=696. > > If you come up with anything, let me know. I am also very interested in > getting Flash (and other media) to play in-image. > > HTH, > Sean > -- > View this message in context: > http://forum.world.st/How-I-can-do-SWF-files-playing-in-pharo-tp3161269p316… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Education 0.2 -- http://blog.ofset.org/hilaire

Dec. 29, 2010

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

by pharo＠googlecode.com

Comment #6 on issue 3489 by marianopeck: Pharo 1.2-dev still uses Preferences in BaseSoundSystem http://code.google.com/p/pharo/issues/detail?id=3489 Actually, if you take a pharo dev 1.2, there are still 20 references to Preferences :(

Dec. 29, 2010

Re: [Pharo-project] Issue 453 in pharo: we need a way to fold a package into the system

by pharo＠googlecode.com

Comment #5 on issue 453 by marianopeck: we need a way to fold a package into the system http://code.google.com/p/pharo/issues/detail?id=453 ups...sorry my answer was for another issue

Dec. 29, 2010