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

Re: [Pharo-project] Pharo latest announcement

by Adrian Lienhard

Hi Skrish, I don't understand your question. Version 1.0 is the current stable one and 1.1 is the unstable one. Adrian On Apr 19, 2010, at 13:47 , Sudhakar Krishnamachari wrote: >> >> >> Is it inadvertent for the version is showing up as 1.0 instead of 1.1...? >> at >> http://pharo-project.org/home >> "Version 1.0 (stable) >> >> Pharo 1.0 was released on April 15, 2010. Download the one-click image and >> get Pharo up and running within seconds." >> <http://pharo-project.org/pharo-download/release-1-0> >> >> -Skrish >> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 19, 2010

Re: [Pharo-project] Setup package fixes

by Sean P. DeNigris

Tudor Girba wrote: > > Indeed, please commit it directly in the Setup project. > Done. I didn't know the etiquette of posting to someone else's repository! It even sounds wrong ;-) Sean -- View this message in context: http://n4.nabble.com/Setup-package-fixes-tp2015309p2015802.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 19, 2010

Re: [Pharo-project] Pharo latest announcement

by Sudhakar Krishnamachari

> > > Is it inadvertent for the version is showing up as 1.0 instead of 1.1...? > at > http://pharo-project.org/home > "Version 1.0 (stable) > > Pharo 1.0 was released on April 15, 2010. Download the one-click image and > get Pharo up and running within seconds." > <http://pharo-project.org/pharo-download/release-1-0> > > -Skrish >

April 19, 2010

Re: [Pharo-project] Setup package fixes

by Tudor Girba

Indeed, please commit it directly in the Setup project. Cheers, Doru On 19 Apr 2010, at 03:54, Levente Uzonyi wrote: > On Sun, 18 Apr 2010, Sean P. DeNigris wrote: > >> >> I sent some fixes to the package owner, but also posted a link to >> the mcz >> file http://seandenigris.com/files/Setup-SeanDeNigris.47.mcz >> here , in case >> anyone wants it. > > Why did't you upload it to the squeaksource repository directly? (http://squeaksource.com/setup.html > ) > >> >> * Fix - Setup>>installDevelopment - changed from Installer (which >> is not >> pre-installed in Pharo 1.0) to Gopher. >> * Fix - Setup>>installSpecificUser - Changed "Author >> initials" (depreciated >> in Pharo 1.0) to "author fullName". >> - changed all author initials to full names, except jre because I >> didn't >> know what it stood for. > > Probably Jorge Ressia. > > > Levente > >> >> I tested it against Pharo-Core 1.0 & PharoCore-1.1-11312-UNSTABLE. >> I tried >> to port it to Squeak 4.1, but got various errors, so I backed out the >> changes. But if you are interested, I can send them to you. >> >> Sean >> -- >> View this message in context: http://n4.nabble.com/Setup-package-fixes-tp2015309p2015309.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Obvious things are difficult to teach."

April 19, 2010

Re: [Pharo-project] Issue tracking system

by Geert Claes

Great, I have just added the Gjallar mailing list to the other Nabble Smalltlalk onlne forums. http://n4.nabble.com/Gjallar-f2015723.html http://n4.nabble.com/Gjallar-f2015723.html GÃ¶ran, if you can export the the archive Nabble is able to import it as a .mbox file. -- View this message in context: http://n4.nabble.com/Issue-tracking-system-tp2013457p2015728.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 19, 2010

Re: [Pharo-project] [Vm-dev] Re: we need help for rome

by Bert Freudenberg

On 19.04.2010, at 10:42, StÃ©phane Ducasse wrote: > > > On Apr 18, 2010, at 11:57 PM, Bert Freudenberg wrote: > >> On 18.04.2010, at 20:14, stephane ducasse wrote: >>> >>> >>> Thanks Bert >>> >>>> >>>> I think only the first 4 inst vars are actually used by the plugin: >>>> >>>> http://squeakvm.org/svn/squeak/trunk/platforms/unix/src/plugins/RomePlugin/… >>>> #define CanvasHandleIndex 0 >>>> #define CanvasTargetIndex 1 >>>> #define CanvasFlagsIndex 2 >>>> #define CanvasStrokeColorIndex 3 >>>> #define CanvasInstSize 8 >>> >>> how did you get that information? from the image side or C code? >>> Because I tried to see but unsure. >> >> It's in the C code I linked above. I just reordered it for better readability. > > Yes I saw my question was more how do we identify code that is not used anymore? > We just do the closure over the published primitives and the rest means that it is useful. > My question was how did you identify that only 4 inst were used and not more. If you look at the RomePlugin class you see that 8 class vars are defined. But in the generated C code, only the first four are declared. That is because the Slang translator only exports the used ones. That's how I know the others are unused - they were not exported :) >>>> The proper fix would be to modify RomePlugin class>>initializeInstVarIndices to not generate the indices, but simply hard-code only the used ones (setting CanvasInstSize to 4), and change the comparison John mentioned below to <=. Also remove the unused *Index class vars. Now that there are plugins in the wild, hard-coding the indices is a good idea anyway. During development, the flexible generator version was useful, but not anymore. > > > Ok I will browse the RomePlugin class with Cyrille and Jean-Baptiste > > >>> I browsed a bit the C code and I'm learning so may be my questions are not clever, but >>> >>> - do we need the pango primitives for ROME? >>> Apparently Pango may use Cairo for fonts rendering but do Rome needs that? >>> So is it simpler to use fonts via pango than cairo. >> >> Pango provides word/paragraph layout. Many non-latin scripts (e.g. Devanagari) require "glyph shaping", there is no one-to-one mapping between Unicode characters and glyphs rendered in context. Pango can do that. I'm not aware of any other renderer in Squeak that would support this (Yoshiki added it for OLPC). Well, maybe the Unicode plugin from Scratch could do it too, not sure. >> >>> - then what about FormInstSize? >>> >>> (interpreterProxy->slotSizeOf(formOop)) < FormInstSize >>> does it mean >> >> Same thing. The instance variables actually used by the plugin should be hard coded. Otherwise the same would happen as in Sophie - some inst vars were added to the Canvas, so the inst size compiled into the plugin became larger than necessary. >> >> Btw, by now you probably have guessed that a workaround for the Mac issue would be to add 5 dummy inst vars to RomePluginCanvas just to make the plugin happy. > > Yes. In fact my question was more is FormInstSize used (or are the functionality using FormInstSize used)? If you see it in the C code then yes, it is used. > I have problems to see how we can clean the C code. > All my questions should be interpreted with this slant. Well, no need to "clean the C code" because it is just generated. Clean the RomePlugin class instead :^) >>> It doesn't need to be "in sync". But maybe I do not understand the question. > > Sorry was not clear. > My question is how Cairo supports backwards compatibility? > What happens if the plugin expect a different version of Cairo on the machine? > May be they do not change their interface? Many projects are better about backwards compatibility than we are ;) Generally, once an API was added, it is *never* removed or changed in the same major version of a library. Only additions are allowed in point releases. This ensures code can dynamically link to older binaries and not break with newer releases. Also, the major version is part of the library name (executables actually link against bla.so.1 not bla.so) so multiple major versions of the same library can co-exist on a system. So major releases can remove or change existing API. In short, I wouldn't worry about it - I'm not sure in cairo's particular case but in general that's how it works. There is something to be said about published vs. public interfaces, and in Smalltalk we usually don't respect either ... - Bert -

April 19, 2010

Re: [Pharo-project] we need help for rome

by StÃ©phane Ducasse

sophie used the impara ones. So now this is good that we merged and check in the rome one. And probably repackage everything in Athens. Stef > > StÃ©phane Ducasse a Ã©crit : >> Ok I will ask cyrille if he can have a look at the c :) >> >> Stef >> >> On Apr 18, 2010, at 11:23 PM, John M McIntosh wrote: >> >> >>> Well hey I'm just the guy tapping the compile button, er no support agreement here... >>> Likely the original plugin code came via >>> MCHttpRepository >>> location: 'http://source.impara.de/Rome' >>> user: '' >>> password: '' >>> >> >> This is strange because I think that alain took it from there too. >> May be not. >> > I took it from squeaksource, not from source.impara.de. > so two repositories. > why ? > does someone knows ? > Cheers > Alain >> Stef >> >> >> >>> If someone wants to make the required fixes to the plugin code, and the smalltalk code I *think* I can build a new plugin.. Likely this won't affect Sophie users (if any) because that's a one click app. However this means an update to the mac vm's and other platforms in order to ensure the smalltalk class in a Pharo image matches expectations. >>> On 2010-04-18, at 10:45 AM, Bert Freudenberg wrote: >>> >>> >>>> I think only the first 4 inst vars are actually used by the plugin: >>>> >>>> http://squeakvm.org/svn/squeak/trunk/platforms/unix/src/plugins/RomePlugin/… >>>> #define CanvasHandleIndex 0 >>>> #define CanvasTargetIndex 1 >>>> #define CanvasFlagsIndex 2 >>>> #define CanvasStrokeColorIndex 3 >>>> #define CanvasInstSize 8 >>>> >>>> So on Linux, Rome does use the "right" size. John appears to have used a Sophie image to generate his Plugin, which makes this fail (though I could not find his Rome plugin in the Mac OS platform code so can't verify that theory). >>>> >>>> The proper fix would be to modify RomePlugin class>>initializeInstVarIndices to not generate the indices, but simply hard-code only the used ones (setting CanvasInstSize to 4), and change the comparison John mentioned below to <=. Also remove the unused *Index class vars. Now that there are plugins in the wild, hard-coding the indices is a good idea anyway. During development, the flexible generator version was useful, but not anymore. >>>> >>>> - Bert - >>>> >>>> >>> -- >>> =========================================================================== >>> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 >>> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >>> =========================================================================== >>> >>> >>> >>> >>> >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 19, 2010

Re: [Pharo-project] we need help for rome

by Alain Plantec

StÃ©phane Ducasse a Ã©crit : > Ok I will ask cyrille if he can have a look at the c :) > > Stef > > On Apr 18, 2010, at 11:23 PM, John M McIntosh wrote: > > >> Well hey I'm just the guy tapping the compile button, er no support agreement here... >> >> Likely the original plugin code came via >> >> MCHttpRepository >> location: 'http://source.impara.de/Rome' >> user: '' >> password: '' >> > > This is strange because I think that alain took it from there too. > May be not. > I took it from squeaksource, not from source.impara.de. so two repositories. why ? does someone knows ? Cheers Alain > Stef > > > >> If someone wants to make the required fixes to the plugin code, and the smalltalk code I *think* I can build a new plugin.. Likely this won't affect Sophie users (if any) because that's a one click app. However this means an update to the mac vm's and other platforms in order to ensure the smalltalk class in a Pharo image matches expectations. >> >> On 2010-04-18, at 10:45 AM, Bert Freudenberg wrote: >> >> >>> I think only the first 4 inst vars are actually used by the plugin: >>> >>> http://squeakvm.org/svn/squeak/trunk/platforms/unix/src/plugins/RomePlugin/… >>> #define CanvasHandleIndex 0 >>> #define CanvasTargetIndex 1 >>> #define CanvasFlagsIndex 2 >>> #define CanvasStrokeColorIndex 3 >>> #define CanvasInstSize 8 >>> >>> So on Linux, Rome does use the "right" size. John appears to have used a Sophie image to generate his Plugin, which makes this fail (though I could not find his Rome plugin in the Mac OS platform code so can't verify that theory). >>> >>> The proper fix would be to modify RomePlugin class>>initializeInstVarIndices to not generate the indices, but simply hard-code only the used ones (setting CanvasInstSize to 4), and change the comparison John mentioned below to <=. Also remove the unused *Index class vars. Now that there are plugins in the wild, hard-coding the indices is a good idea anyway. During development, the flexible generator version was useful, but not anymore. >>> >>> - Bert - >>> >>> >> -- >> =========================================================================== >> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 >> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >> =========================================================================== >> >> >> >> >> > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

April 19, 2010

Re: [Pharo-project] Help on collaborator Active book

by StÃ©phane Ducasse

thanks > > > Fixing underscores @ > http://book.pharo-project.org/book/TipsAndTricks/FixingUnderscores > * I wasn't sure whether this was an instruction, a suggestion, or merely an > option. Is this necessary? personal preference? Again, some background > would help. I fixed that. > > Traits @ http://book.pharo-project.org/book/Traits: > * This one I found very tough. Especially the initial part of the > BulletinBoard example. I wasn't sure how I would play with the example in > my own image. For instance, what should the subclass of BulletinBoard be? > > * "BoardListener new listenAndReact > makes sure that each time the method announceNewAddedItem is executed on the > created bulletinBoard, the event is received by the listener." Does it? It > seems to just write to the Transcript, and not be connected to the listener > at all. > > * "Open an inspector on the expression above" - which expression? > > * "! Going deeper > When applying a trait to a class it may face different situations." > > * "!!Using Alias to access a hidden method" This section (the beginning > anyway), seemed to describe something different than the title here. > > It's great to have a resource like this - let's squeeze all the juice out of > it. I will fix the rest later. > > Sean > -- > View this message in context: http://n4.nabble.com/Help-on-collaborator-Active-book-tp2014707p2015363.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 19, 2010

Re: [Pharo-project] we need help for rome

by StÃ©phane Ducasse

Ok I will ask cyrille if he can have a look at the c :) Stef On Apr 18, 2010, at 11:23 PM, John M McIntosh wrote: > Well hey I'm just the guy tapping the compile button, er no support agreement here... > > Likely the original plugin code came via > > MCHttpRepository > location: 'http://source.impara.de/Rome' > user: '' > password: '' This is strange because I think that alain took it from there too. May be not. Stef > > If someone wants to make the required fixes to the plugin code, and the smalltalk code I *think* I can build a new plugin.. Likely this won't affect Sophie users (if any) because that's a one click app. However this means an update to the mac vm's and other platforms in order to ensure the smalltalk class in a Pharo image matches expectations. > > On 2010-04-18, at 10:45 AM, Bert Freudenberg wrote: > >> >> I think only the first 4 inst vars are actually used by the plugin: >> >> http://squeakvm.org/svn/squeak/trunk/platforms/unix/src/plugins/RomePlugin/… >> #define CanvasHandleIndex 0 >> #define CanvasTargetIndex 1 >> #define CanvasFlagsIndex 2 >> #define CanvasStrokeColorIndex 3 >> #define CanvasInstSize 8 >> >> So on Linux, Rome does use the "right" size. John appears to have used a Sophie image to generate his Plugin, which makes this fail (though I could not find his Rome plugin in the Mac OS platform code so can't verify that theory). >> >> The proper fix would be to modify RomePlugin class>>initializeInstVarIndices to not generate the indices, but simply hard-code only the used ones (setting CanvasInstSize to 4), and change the comparison John mentioned below to <=. Also remove the unused *Index class vars. Now that there are plugins in the wild, hard-coding the indices is a good idea anyway. During development, the flexible generator version was useful, but not anymore. >> >> - Bert - >> > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > >

April 19, 2010