- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Easy issue to fix: 12063

by btc＠openinworld.com

Marcus Denker wrote: > This is a nice issue for someone to do that wants to start with something simple: > > 12063 ConfigurationBrowser window about message is wrong (and dated) > https://pharo.fogbugz.com/f/cases/12063 > > > > > I'll have a go at it, but I'd like some wider discussion as its turned up something new for me to learn... Interestingly the text-at-issue does not appear when searching the source with Finder. I traced it to... ClassOrganization>>comment comment ifNil: [^ '']. ^ comment string ifNil: [''] where `comment` is a RemoteString such that evaluating the following in a Workspace... | sourceFileNumber filePositionHi theFile| sourceFileNumber := 2. filePositionHi := 11619939. theFile := (SourceFiles at: sourceFileNumber) readOnlyCopy. ^ [ filePositionHi > theFile size ifTrue: [ self error: 'RemoteString past end of file' ]. theFile position: filePositionHi. theFile nextChunk] ensure: [ theFile close ] returns the text-at-issue, and where `theFile` is... MultiByteFileStream: 'C:\Users\Ben\AppData\Roaming\pharo\images\30649\30649.changes' So to proceed my naive reaction would be to add the required text to be returned by a class method (feedback anyone?) but, I am really curious... * how is it likely that this situation came about? * is it common to be grabbing text like this from the changes file? cheers, Ben

Dec. 17, 2013

Re: [Pharo-dev] [ANN] Phratch 1.0beta

by Tudor Girba

Please do not change the name :). Google "phratch" and you will see that there are only 2000 results, and many of them relate to your project. You do not want to lose that. Doru On Tue, Dec 17, 2013 at 4:06 PM, jannik laval <jannik.laval(a)gmail.com>wrote: > > 2013/12/17 kilon alios <kilon.alios(a)gmail.com> > >> Tried your installation instructions on Pharo 3 latest build and I get >> this error >> >> The method AbstractFileReference>>ensureDirectory has been deprecated. >> Use ensureCreateDirectory >> > > > This deprecation should be new :) > Phratch works on Pharo2.0. > I can load it on the latest one click of Pharo3.0 also. > > >> >> this is the full stack trace >> >> MorphicUIManager>>warningDefaultAction: >> Deprecation(Warning)>>defaultAction >> Deprecation>>defaultAction >> UndefinedObject>>handleSignal: >> MethodContext(ContextPart)>>handleSignal: >> MethodContext(ContextPart)>>handleSignal: >> MethodContext(ContextPart)>>handleSignal: >> Deprecation(Exception)>>signal >> FileLocator(Object)>>deprecated:on:in: >> FileLocator(AbstractFileReference)>>ensureDirectory >> PhratchFileChooserDialog class>>userPhratchProjectsDir in Block: [ >> (homeDir / phratchFolderName) ensureDirectory ] >> BlockClosure>>on:do: >> BlockClosure>>ifError: >> PhratchFileChooserDialog class>>userPhratchProjectsDir >> PhratchFileChooserDialog class>>getDefaultFolderForType: >> PhratchFrameMorph>>newPhratchProject >> PhratchFrameMorph>>startup >> PhratchFrameMorph class>>open >> UndefinedObject>>DoIt >> OpalCompiler>>evaluate >> SmalltalkEditor>>evaluateSelectionAndDo: >> SmalltalkEditor>>evaluateSelection >> PluggableTextMorph>>doIt in Block: [ textMorph editor evaluateSelection ] >> PluggableTextMorph>>handleEdit: in Block: [ result := editBlock value ] >> TextMorphForEditView(TextMorph)>>handleEdit: >> PluggableTextMorph>>handleEdit: >> PluggableTextMorph>>doIt >> Workspace(Object)>>perform:orSendTo: >> ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: in Block: [ ... >> BlockClosure>>ensure: >> >> I cannot open Phratch because of this error. Each time I follow the >> instructions >> >> PhratchFrameMorph open. >> >> >> I get the same error. >> >> I am on win7 64bit. >> >> Also a note , personal opinion, I dont like the name. To be sincere I >> never liked "Scratch" as a name either. It sounded to me like an allergy. >> But "Phratch" as a name makes even less sense. >> > > Ok, I understand your point. Now I have no better name. Any idea ? > But should we change the name ? > That are open questions. > > Cheers, > Jannik > > >> >> >> >> >> >> On Tue, Dec 17, 2013 at 4:02 PM, Hilaire Fernandes < >> hilaire.fernandes(a)gmail.com> wrote: >> >>> Le 16/12/2013 22:45, jannik.laval a Ã©crit : >>> > I continue to develop Phratch, the port of Scratch in Pharo. >>> > Phratch is a visual programming language on top of Pharo. >>> > >>> >>> It is fantastic you ported and keep improving this Smalltlak Jewel on >>> Pharo ;). >>> >>> Thanks >>> >>> Hilaire >>> >>> >>> >>> -- >>> Dr. Geo http://drgeo.eu >>> >>> >>> >> > > > -- > > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://car.mines-douai.fr/ > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 17, 2013

Re: [Pharo-dev] [ANN] Phratch 1.0beta

by jannik laval

2013/12/17 kilon alios <kilon.alios(a)gmail.com> > Tried your installation instructions on Pharo 3 latest build and I get > this error > > The method AbstractFileReference>>ensureDirectory has been deprecated. > Use ensureCreateDirectory > This deprecation should be new :) Phratch works on Pharo2.0. I can load it on the latest one click of Pharo3.0 also. > > this is the full stack trace > > MorphicUIManager>>warningDefaultAction: > Deprecation(Warning)>>defaultAction > Deprecation>>defaultAction > UndefinedObject>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > Deprecation(Exception)>>signal > FileLocator(Object)>>deprecated:on:in: > FileLocator(AbstractFileReference)>>ensureDirectory > PhratchFileChooserDialog class>>userPhratchProjectsDir in Block: [ > (homeDir / phratchFolderName) ensureDirectory ] > BlockClosure>>on:do: > BlockClosure>>ifError: > PhratchFileChooserDialog class>>userPhratchProjectsDir > PhratchFileChooserDialog class>>getDefaultFolderForType: > PhratchFrameMorph>>newPhratchProject > PhratchFrameMorph>>startup > PhratchFrameMorph class>>open > UndefinedObject>>DoIt > OpalCompiler>>evaluate > SmalltalkEditor>>evaluateSelectionAndDo: > SmalltalkEditor>>evaluateSelection > PluggableTextMorph>>doIt in Block: [ textMorph editor evaluateSelection ] > PluggableTextMorph>>handleEdit: in Block: [ result := editBlock value ] > TextMorphForEditView(TextMorph)>>handleEdit: > PluggableTextMorph>>handleEdit: > PluggableTextMorph>>doIt > Workspace(Object)>>perform:orSendTo: > ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: in Block: [ ... > BlockClosure>>ensure: > > I cannot open Phratch because of this error. Each time I follow the > instructions > > PhratchFrameMorph open. > > > I get the same error. > > I am on win7 64bit. > > Also a note , personal opinion, I dont like the name. To be sincere I > never liked "Scratch" as a name either. It sounded to me like an allergy. > But "Phratch" as a name makes even less sense. > Ok, I understand your point. Now I have no better name. Any idea ? But should we change the name ? That are open questions. Cheers, Jannik > > > > > > On Tue, Dec 17, 2013 at 4:02 PM, Hilaire Fernandes < > hilaire.fernandes(a)gmail.com> wrote: > >> Le 16/12/2013 22:45, jannik.laval a Ã©crit : >> > I continue to develop Phratch, the port of Scratch in Pharo. >> > Phratch is a visual programming language on top of Pharo. >> > >> >> It is fantastic you ported and keep improving this Smalltlak Jewel on >> Pharo ;). >> >> Thanks >> >> Hilaire >> >> >> >> -- >> Dr. Geo http://drgeo.eu >> >> >> > -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/

Dec. 17, 2013

Re: [Pharo-dev] [ANN] Phratch 1.0beta

by jannik laval

These plugins are included in Scratch and I reused them. I separated the source code of them in a different package. You can find them in the repository http://smalltalkhub.com/mc/JLaval/Phratch/main. The package is named PhratchPrimitiveSources. Cheers 2013/12/17 phil(a)highoctane.be <phil(a)highoctane.be> > As of teaching, I try to get my wife to get acquainted to it. Math teacher. > > I also see things like CameraPlugin.dll and Mpeg3Plugin.dll > ScratchPlugin.dll which aren't in the stock Pharo VM (2.0) > > Is the code for these in the stock vm repo or elsewhere (with your own > version)? > > > Phil > > > > > -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/

Dec. 17, 2013

Re: [Pharo-dev] 34 "priority" issues for Pharo3

by btc＠openinworld.com

Marcus Denker wrote: > Sometimes itâs really strangeâ¦ people seem to really think that releasing software contains a âreading minds > from the distanceâ phase of bug discovery. > > Marcus > > Not able to read minds yet? I've logged an issue for it. cheers -ben

Dec. 17, 2013

Re: [Pharo-dev] Please stop top posting... (was Re: Tell me about your workflow)

by Sergi Reyner

2013/12/17 Frank Shearar <frank.shearar(a)gmail.com> This battle was lost a decade ago, I'm afraid. > This wasnÂ´t even a battle until someone decided that top-posting was an amazingly good thing. Thanks to that, we now have posts/mails that sometimes donÂ´t contain even a full sentence of original content, and are followed by loads of quoted text, with signatures, headers, images... you name it. I stop reading some threads because of the excessive amount of irrelevant quoted text, and the inverted order of "response to something" followed by "something that prompted the response. That, if there is a quote at all... Back in the day (I am talking about BBSs, Fidonet and related networks, dating back to the 80s), people took pride in having a very low content to quote ratio, but we were also very careful to quote everything needed to make sense of the response. No more, no less. The early days of Internet email werenÂ´t as bad, either. I came to the conclusion, some years ago, that I will continue to strive to quote properly, and the rest of the world is free to do whatever they want. And I am then free to just ignore messages or threads that are too much trouble for me to follow. Cheers, Sergi

Dec. 17, 2013

Re: [Pharo-dev] 34 "priority" issues for Pharo3

by Guillermo Polito

I'm checking https://pharo.fogbugz.com/f/cases/11756/When-removing-intance-variables-fro… I've reproduced it and writing a test for it now... But I don't fully understand how the new class builder propagates changes to subclasses. On Tue, Dec 17, 2013 at 8:23 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On 17 Dec 2013, at 08:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > 2) Your favourite issue is not in this list? â> make sure it is tagged > for pharo3 *and* has a > > priority higher than âwould be niceâ. > > > > I should repeat and stress *very very violently* that community action is > *really* needed here. > > If your issue that you think is oh so important (but you just *think*, you > do not *communicate*), > it will nevertheless *not* be fixed. Even if you think that it is obvious. > Because you thinking does not lead > to someone acting (other than you yourself, of course). > > Sometimes itâs really strangeâ¦ people seem to really think that releasing > software contains a âreading minds > from the distanceâ phase of bug discovery. > > Marcus >

Dec. 17, 2013

Re: [Pharo-dev] [ANN] Phratch 1.0beta

by kilon alios

Tried your installation instructions on Pharo 3 latest build and I get this error The method AbstractFileReference>>ensureDirectory has been deprecated. Use ensureCreateDirectory this is the full stack trace MorphicUIManager>>warningDefaultAction: Deprecation(Warning)>>defaultAction Deprecation>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: Deprecation(Exception)>>signal FileLocator(Object)>>deprecated:on:in: FileLocator(AbstractFileReference)>>ensureDirectory PhratchFileChooserDialog class>>userPhratchProjectsDir in Block: [ (homeDir / phratchFolderName) ensureDirectory ] BlockClosure>>on:do: BlockClosure>>ifError: PhratchFileChooserDialog class>>userPhratchProjectsDir PhratchFileChooserDialog class>>getDefaultFolderForType: PhratchFrameMorph>>newPhratchProject PhratchFrameMorph>>startup PhratchFrameMorph class>>open UndefinedObject>>DoIt OpalCompiler>>evaluate SmalltalkEditor>>evaluateSelectionAndDo: SmalltalkEditor>>evaluateSelection PluggableTextMorph>>doIt in Block: [ textMorph editor evaluateSelection ] PluggableTextMorph>>handleEdit: in Block: [ result := editBlock value ] TextMorphForEditView(TextMorph)>>handleEdit: PluggableTextMorph>>handleEdit: PluggableTextMorph>>doIt Workspace(Object)>>perform:orSendTo: ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: in Block: [ ... BlockClosure>>ensure: I cannot open Phratch because of this error. Each time I follow the instructions PhratchFrameMorph open. I get the same error. I am on win7 64bit. Also a note , personal opinion, I dont like the name. To be sincere I never liked "Scratch" as a name either. It sounded to me like an allergy. But "Phratch" as a name makes even less sense. On Tue, Dec 17, 2013 at 4:02 PM, Hilaire Fernandes < hilaire.fernandes(a)gmail.com> wrote: > Le 16/12/2013 22:45, jannik.laval a Ã©crit : > > I continue to develop Phratch, the port of Scratch in Pharo. > > Phratch is a visual programming language on top of Pharo. > > > > It is fantastic you ported and keep improving this Smalltlak Jewel on > Pharo ;). > > Thanks > > Hilaire > > > > -- > Dr. Geo http://drgeo.eu > > >

Dec. 17, 2013

Re: [Pharo-dev] [ANN] Phratch 1.0beta

by Hilaire Fernandes

Le 16/12/2013 22:45, jannik.laval a Ã©crit : > I continue to develop Phratch, the port of Scratch in Pharo. > Phratch is a visual programming language on top of Pharo. > It is fantastic you ported and keep improving this Smalltlak Jewel on Pharo ;). Thanks Hilaire -- Dr. Geo http://drgeo.eu

Dec. 17, 2013

Re: [Pharo-dev] Another very simple issue: 11387 Ancient files

by Guillermo Polito

I would tag that for 4.0... what do you think? Better not do that kind of changes in beta :) On Tue, Dec 17, 2013 at 2:13 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > This issue was opened in August. > > It looks to be *really* quick and easy to either fix or reject as invalid: > > any takers? > > It looks like some files are very old and not used anymore. I can compile > on linux without these filesa: > > platforms/unix/config/config.sub > platforms/unix/config/config.guess > processors/IA32/bochs/config.guess > processors/IA32/bochs/config.sub > platforms/unix/config/ltconfig > platforms/unix/config/ltmain.sh > processors/IA32/bochs/ltmain.sh > > Please consider removing them. > > > >

Dec. 17, 2013