- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [squeak-dev] Re: Kinect and Etoys

by Ricardo Moran

The latest stable 1.1.1. I will look at it tomorrow and try to find out more. On Wed, Jan 19, 2011 at 6:38 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > hi ricardo, > > which version are you using? > > Stef > > On Jan 19, 2011, at 10:32 PM, Ricardo Moran wrote: > > > I forgot to say it works in Squeak and Pharo (although in Pharo it's > *painfully* slow, I don't know why yet...) > > > > Cheers > > Richo > > > > On Wed, Jan 19, 2011 at 6:04 PM, Ricardo Moran <richi.moran(a)gmail.com> > wrote: > > Hi guys! > > I want to tell you some exciting news. Thanks to the ESUG Innovation > Technology Awards we've been able to buy ourselves a Microsoft Kinect. We > don't have a Xbox 360 yet, but that doesn't mean we can't have a little fun > with it. Who needs and Xbox if you can use Kinect with Etoys? :) > > > > After seeing Stephen Howell's great work using Kinect with Scratch, we > followed his steps and made it available for Etoys as well. > > See it for yourselves: http://www.youtube.com/watch?v=YnqqaHvbeqg > > > > You can find installation steps in our blog: > http://tecnodacta.com.ar/gira > > > > Cheers! > > Richo > > > > > >

Jan. 19, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by StÃ©phane Ducasse

Can somebody try by defining these methods !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! stylerStyled: styledCopyOfText textMorph contents runs: styledCopyOfText runs . "textMorph paragraph recomposeFrom: 1 to: textMorph contents size delta: 0." "caused chars to appear in wrong order esp. in demo mode. remove this line when sure it is fixed" textMorph updateFromParagraph. selectionInterval ifNotNil:[ textMorph editor selectInvisiblyFrom: selectionInterval first to: selectionInterval last; storeSelectionInParagraph; setEmphasisHere]. textMorph editor blinkParen. self scrollSelectionIntoView ! ! !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! stylerStyledInBackground: styledCopyOfText "It is possible that the text string has changed since the styling began. Disregard the styles if styledCopyOfText's string differs with the current textMorph contents string" textMorph contents string = styledCopyOfText string ifTrue: [self stylerStyled: styledCopyOfText]! ! I think that we found a bug in MC since the category where named: 'shout' (not with * so that the changes do not belong to the package of shout but really the one of PluggableTextMorph. On Jan 19, 2011, at 10:34 PM, StÃ©phane Ducasse wrote: >>> PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: > > > this is probably with a MC problem because in > Issue 3486: PluggableTextMorph should be able to support text styling > > we payed attention to have it. > http://code.google.com/p/pharo/issues/detail?id=3486 > > Benjamin can you have a look? > > Stef >

Jan. 19, 2011

Re: [Pharo-project] [squeak-dev] Re: Kinect and Etoys

by StÃ©phane Ducasse

hi ricardo, which version are you using? Stef On Jan 19, 2011, at 10:32 PM, Ricardo Moran wrote: > I forgot to say it works in Squeak and Pharo (although in Pharo it's *painfully* slow, I don't know why yet...) > > Cheers > Richo > > On Wed, Jan 19, 2011 at 6:04 PM, Ricardo Moran <richi.moran(a)gmail.com> wrote: > Hi guys! > I want to tell you some exciting news. Thanks to the ESUG Innovation Technology Awards we've been able to buy ourselves a Microsoft Kinect. We don't have a Xbox 360 yet, but that doesn't mean we can't have a little fun with it. Who needs and Xbox if you can use Kinect with Etoys? :) > > After seeing Stephen Howell's great work using Kinect with Scratch, we followed his steps and made it available for Etoys as well. > See it for yourselves: http://www.youtube.com/watch?v=YnqqaHvbeqg > > You can find installation steps in our blog: http://tecnodacta.com.ar/gira > > Cheers! > Richo > >

Jan. 19, 2011

[Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by StÃ©phane Ducasse

>> PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: this is probably with a MC problem because in Issue 3486: PluggableTextMorph should be able to support text styling we payed attention to have it. http://code.google.com/p/pharo/issues/detail?id=3486 Benjamin can you have a look? Stef

Jan. 19, 2011

[Pharo-project] ConfigurationOf Question

by StÃ©phane Ducasse

hi guys what should be the load or loadDefault definition if I want to load the latest version as defined by a method of this style? version02: spec <version: '0.2'> spec for: #common do: [ spec repository: 'http://www.squeaksource.com/Soup'. spec package: 'Soup-Core' with: 'Soup-Core-StephaneDucasse.8'; package: 'Soup-Tests-Core' with: 'Soup-Tests-Core-StephaneDucasse.2'; package: 'Soup-Help' with: 'Soup-Help-StephaneDucasse.2' ]. AM I correct to believe that load "self load" ^self project latestVersion load execute version02: if this is the last method version? Stef

Jan. 19, 2011

Re: [Pharo-project] TextConverter 1.2 bug

by StÃ©phane Ducasse

It was in an old converter that was loaded by soup and overriding the code .... Stef On Jan 19, 2011, at 9:56 PM, Igor Stasenko wrote: > On 19 January 2011 21:37, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> when I execute >> CP1252TextConverter new in 1.1 it works >> Now in 1.2 I get DNU charcode > > charcode or charCode? > > Character>>charCode > > ^ (value bitAnd: 16r3FFFFF). > > is in Pharo1.2-12306 > >> >> >> CP1252TextConverter>>nextPut: aCharacter toStream: aStream >> aStream isBinary ifTrue: [^ aCharacter storeBinaryOn: aStream]. >> aCharacter charCode < 128 >> ifTrue: [aStream basicNextPut: aCharacter] >> ifFalse: [aStream basicNextPut: ((Character value: (self fromSqueak: aCharacter) charCode))]. >> >> aCharacter = $^ >> (self fromSqueak: aCharacter) = 128 >> >> Does anybody have an idea? >> >> Thanks in advance. >> >> Stef >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Jan. 19, 2011

Re: [Pharo-project] About XML Support in the 1.2

by Alain Plantec

> PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: I've the same problem when I load Moose and/or Petit with the following scripts: Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault. Gofer new renggli: 'petit'; package: 'ConfigurationOfPetitParser'; load. (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault. Cheers Alain Le 19/01/2011 21:56, laurent laffont a Ã©crit : > On Wed, Jan 19, 2011 at 9:29 PM, Tudor Girba <tudor.girba(a)gmail.com > <mailto:tudor.girba@gmail.com>> wrote: > > Thanks, indeed. > > Does this mean that the next build will take this into account or > must something else get changed as well? > > > Next build will takes this in account. > > The problem is that the build fails now. > > On my machine, while loading > AutomaticMethodCategorizer-MarianoMartinez.29 I get the error: > > > PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: > > SHTextStylerST80(SHTextStyler)>>style: > > PluggableTextMorph>>setText: > > PluggableTextMorph>>on:text:accept:readSelection:menu: > > PluggableTextMorph class>>on:text:accept:readSelection:menu: > > Workspace>>embeddedInMorphicWindowLabeled: > > Workspace(StringHolder)>>openAsMorphLabel: > > Workspace(StringHolder)>>openLabel: > > AutomaticMethodCategorizer class>>showFirstInstallationInstructions > > AutomaticMethodCategorizer class>>initialize > > MCMethodDefinition>>postloadOver: > > ..... > > > > Laurent > > > Cheers, > Doru > > > On 19 Jan 2011, at 21:24, StÃ©phane Ducasse wrote: > > > thanks laurent! > > > > On Jan 19, 2011, at 9:19 PM, laurent laffont wrote: > > > >> I've copied latest ConfigurationOfXMLSupport in > MetacelloRepository. > >> > >> ConfigurationOfPharo-LaurentLaffont.121 > >> > >> XMLSupport: > >> - update to release 1.1.6 > >> - add project 'XMLSupport Tests' in group 'Dev Tools Tests' > >> > >> All 361 tests green. > >> > >> Laurent Laffont > >> > >> > >> On Wed, Jan 19, 2011 at 1:18 PM, Tudor Girba > <tudor.girba(a)gmail.com <mailto:tudor.girba@gmail.com>> wrote: > >> The last version 1.1.6 is marked as #release. > >> > >> Cheers, > >> Doru > >> > >> > >> On 19 Jan 2011, at 12:26, laurent laffont wrote: > >> > >>> I put ConfigurationOfXMLSupport version 1.0 because blessing > was #release. But I agree to change. > >>> > >>> Laurent > >>> > >>> On Wed, Jan 19, 2011 at 12:15 PM, Marcus Denker > <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > >>> > >>> On Jan 19, 2011, at 11:43 AM, Tudor Girba wrote: > >>> > >>>> Indeed, this is a problem for Moose in general. We depend on > XMLSupport, but now we cannot update it in PharoDev. I would also > strongly support the idea of removing XMLSupport from PharoDev. > >>>> > >>> > >>> What would be important: we need the latest version in Pharo > 1.2... else how can we ever have a version where the tests are green? > >>> (not of XML, but in general) > >>> > >>> Marcus > >>> > >>>> Cheers, > >>>> Doru > >>>> > >>>> > >>>> On 19 Jan 2011, at 11:32, Fabrizio Perin wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> I have a problem with the XMLSupport version from Pharo 1.2. > >>>>> > >>>>> The problem is that I need to work with one of the last > version of XMLSupport but in the pharo image 1.2 is loaded an old > version of XMLSupport (I mean a version from Jan 2010). I did try > to load a newer version of XMLSupport using > ConfigurationOfXMLSupport but some errors make this operation > impossible. > >>>>> So either Pharo-dev 1.2 load a newer (possibly the last) > version of XMLSupport by default or Pharo-dev 1.2 should not load > XMLSupport at all. > >>>>> > >>>>> I think that doesn't make sense to use by default such an > old version, also considering that the last XMLSupport has nice > and useful features like the XMLPluggableElementFactory. > >>>>> > >>>>> By avoiding to load XMLSupport in Pharo-dev 1.2 by default > you let people free to use the version that they like. > >>>>> > >>>>> Thanks, > >>>>> > >>>>> Fabrizio > >>>>> > >>>> > >>>> -- > >>>> www.tudorgirba.com <http://www.tudorgirba.com> > >>>> > >>>> "We cannot reach the flow of things unless we let go." > >>>> > >>>> > >>>> > >>>> > >>> > >>> -- > >>> Marcus Denker -- http://www.marcusdenker.de > >>> INRIA Lille -- Nord Europe. Team RMoD. > >>> > >>> > >>> > >> > >> -- > >> www.tudorgirba.com <http://www.tudorgirba.com> > >> > >> "If you interrupt the barber while he is cutting your hair, > >> you will end up with a messy haircut." > >> > >> > >> > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Being happy is a matter of choice." > > > > >

Jan. 19, 2011

Re: [Pharo-project] Any Clue..

by Igor Stasenko

On 19 January 2011 17:38, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Of course. Â But the IDE should be smart enough to prevent disaster. on linux, if there is no proper exclusive write-file locking supported through primitives, one could always create a .lock file and put a process id there. so before opening a .changes file for writing any image first should check if there are a .lock file and if value stored in it has same proc id as currently running one. and after closing .changes file it should delete .lock file. oh.. except that probably there is no way to obtain process id .. there is no such primitive if i remember correctly. Not a big deal.. you can use a GUID generated at image startup time to obtain same effect. But all this logic can be implemented in image. > > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Yanni Chiu [yanni(a)rogers.com] > Sent: Wednesday, January 19, 2011 11:22 AM > To: pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Any Clue.. > > On 19/01/11 8:48 AM, Schwab,Wilhelm K wrote: >> Sig, >> >> Are we discussing the same OS? Â What you are describing matches my experience on Windows; on Linux, AFAIK, one can just stomp all over the files and leave a mess. Â Perhaps something has changed to make it safer since I last trashed an image that way. >> >> I agree that there are times when it does not matter, so any safety mechanism needs to be optional, or better yet tied to a development session vs. a deployed session. >> >> Bill > > I run a common .image file that is interpreted multiple times with a > different start up script. There is no .changes file. This works on > MacOSX and Ubuntu. This is the behaviour I want to have, so such a > "safety mechanism" would definitely need to be optional. > > -- > Yanni > > > > -- Best regards, Igor Stasenko AKA sig.

Jan. 19, 2011

Re: [Pharo-project] Issue 3543 in pharo: Merge latest Glamour theme

by pharo＠googlecode.com

Comment #4 on issue 3543 by tudor.gi...(a)gmail.com: Merge latest Glamour theme http://code.google.com/p/pharo/issues/detail?id=3543 Ok, now I copied version 23 and 24 in PharoInbox. I hope it works now.

Jan. 19, 2011

Re: [Pharo-project] splitters in table layout

by Tudor Girba

Indeed, you are right! This happens in the Pharo 1.2 12303 (attached the PharoDebug.log), but not in 12292. Does anyone know what changed in between? Cheers, Doru On 19 Jan 2011, at 21:52, Andreas Wacknitz wrote: > > Am 19.01.2011 um 21:01 schrieb Tudor Girba: > >> Strange. I just did the followings and it worked just fine: >> >> 1. downloaded 12303: >> https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/67/artifa… >> >> 2. filed in the attached CS >> >> 3. executed >> >> >> | m leftMorph scroll | >> m := PanelMorph new. >> m >> hResizing: #shrinkWrap; >> vResizing: #spaceFill; >> changeTableLayout; >> listDirection: #leftToRight. >> m addMorphBack: (leftMorph := Morph new >> color: Color red; >> minimumExtent: 150@10; >> extent: 150@10; >> hResizing: #rigid; "shown for clarity, is the default" >> vResizing: #spaceFill). >> m addMorphBack: (EdgeGripMorph new >> width: ProportionalSplitterMorph splitterWidth; >> hResizing: #rigid; "not the default this time, vResizing is also #spaceFill by default" >> target: leftMorph). >> m addMorphBack: (Morph new >> color: Color green; >> minWidth: 100; >> hResizing: #shrinkWrap; >> vResizing: #spaceFill). >> >> scroll := GeneralScrollPane new >> changeScrollerTableLayout; >> scrollTarget: m. >> scroll openInWindow. >> >> >> Cheers, >> Doru >> >> <GeneralScrollPaneLayout.2.cs> >> > > Hi Doru, > > I repeated your steps from above. When I execute the code in a Workspace a little dialog will open. > It has a horizontal scroll bar that I can use. As soon as I move the splitter I will get the aforementioned DNU. > I am on Mac OS 10.6.6. > > Regards, > Andreas > > > >> On 19 Jan 2011, at 20:10, Andreas Wacknitz wrote: >> >>> Am 19.01.11 09:54, schrieb Tudor Girba: >>>> That is strange. Are you using Pharo 1.2? >>> Yes (pharo-dev at 12303). >>> >>> Andreas >>> >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 18 Jan 2011, at 21:33, Andreas Wacknitz wrote: >>>> >>>>> >>>>> Am 18.01.2011 um 20:58 schrieb Tudor Girba: >>>>> >>>>>> Yes, you missed a changeset Gary sent in the aligning morphs thread (he actually sent two, and you should pick the second one). >>>>>> >>>>>> Cheers, >>>>>> Doru >>>>>> >>>>> Ah, thank you. I have found two messages with changesets from January 11th, 2011. >>>>> After I filein the second changeset alas I will get a DNU Morph>>doFastWindowReframe: when I move the splitter... >>>>> >>>>> Regards, >>>>> Andreas >>>>> >>>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "To lead is not to demand things, it is to make them happen." >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "In a world where everything is moving ever faster, >> one might have better chances to win by moving slower." >> >> >> > > -- www.tudorgirba.com "Obvious things are difficult to teach."

Jan. 19, 2011