January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Best way for change a window style

by StÃ©phane Ducasse

How do you save the ui once designed because I'm thinking that we could ask one of our guy here to help (implementing a kind of UIBuilder). Stef On Jan 5, 2011, at 2:18 AM, nullPointer wrote: > > Finally I implemented the posibility of create a custom windows in > CLFramework. > > The final visual result fails in somethings, but seems the original: > > http://forum.world.st/file/n3174741/example.png > > http://www.youtube.com/watch?v=QAu6fPyz1b0 > http://www.youtube.com/watch?v=Gb9NoWFdhXo > http://www.youtube.com/watch?v=5CpUnIH9KVw > -- > View this message in context: http://forum.world.st/Best-way-for-change-a-window-style-tp3032341p3174741.… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 5, 2011

Re: [Pharo-project] Best way for change a window style

by StÃ©phane Ducasse

This is really good On Jan 5, 2011, at 2:18 AM, nullPointer wrote: > > Finally I implemented the posibility of create a custom windows in > CLFramework. > > The final visual result fails in somethings, but seems the original: > > http://forum.world.st/file/n3174741/example.png > > http://www.youtube.com/watch?v=QAu6fPyz1b0 > http://www.youtube.com/watch?v=Gb9NoWFdhXo > http://www.youtube.com/watch?v=5CpUnIH9KVw > -- > View this message in context: http://forum.world.st/Best-way-for-change-a-window-style-tp3032341p3174741.… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 5, 2011

Re: [Pharo-project] Generators for Pharo Xmax wish)

by StÃ©phane Ducasse

On Jan 5, 2011, at 8:55 AM, Noury Bouraqadi wrote: > Hi, > > Before integrating some code into Pharo the first step is to check that the licence is MIT. from Squeak it is since they publish in MIT. Having tests and class comments would be a good check. > > Noury > On 5 janv. 2011, at 00:22, Miguel CobÃ¡ wrote: > >> The easiest way to get this code into pharo core is to create a mcz >> package, put it on PharoInbox on squeaksource and create a ticket in >> code.google.com/p/pharo referencing it and taggint it Fixed, this way >> StÃ©phane or Markus can harvest it to the core image. >> If the mcz package is overkill, then a simple fileout of the package in >> squeak attached to the ticket will do. >> >> Maybe in the long term a project on squeaksource should be created (if >> not exists) and new changes to to it and from there pulled to squeak and >> pharo. >> >> Cheers >> >> El mar, 04-01-2011 a las 15:43 -0700, Ralph Boland escribiÃ³: >>> I earlier posted a Xmas wish that Pharo add generators >>> (steal the generators code from Squeak). >>> No one appeared to be familiar with them. >>> The generators code was added to Squeak by Andreas Raas. >>> The class Generator can be found in Squeak as a subclass >>> of Stream. It's about 140 lines of code and, as I said before, >>> is really useful and needed in order for me to port some of the >>> packages I am developing from Squeak to Pharo. >>> Class Generator is tested in class GeneratorTest which also serves >>> as examples of uses of Generators. >>> So please, someone go steal the code! >>> And stealing is easy. For example I stole the following comment on >>> class Generator directly from the class comment: >>> >>> " >>> A Generator transforms callback interfaces into stream interfaces. >>> >>> When a producer algorithm provide results as callbacks (blocks) and a >>> consumer algorithm expects streamable input, a Generator transforms >>> one into the other, for example: >>> >>> | generator | >>> generator := Generator on: [:g| Integer primesUpTo: 100 do:[:prime| g >>> yield: prime]]. >>> [generator atEnd] whileFalse:[Transcript show: generator next]. >>> " >>> >>> Regards, >>> >>> Ralph Boland >>> >> >> -- >> Miguel CobÃ¡ >> http://twitter.com/MiguelCobaMtz >> http://miguel.leugim.com.mx >> >> >> >> > >

Jan. 5, 2011

Re: [Pharo-project] Generators for Pharo Xmax wish)

by StÃ©phane Ducasse

On Jan 4, 2011, at 11:43 PM, Ralph Boland wrote: > I earlier posted a Xmas wish that Pharo add generators > (steal the generators code from Squeak). > No one appeared to be familiar with them. > The generators code was added to Squeak by Andreas Raas. > The class Generator can be found in Squeak as a subclass > of Stream. It's about 140 lines of code and, as I said before, > is really useful and needed in order for me to port some of the > packages I am developing from Squeak to Pharo. > Class Generator is tested in class GeneratorTest which also serves > as examples of uses of Generators. > So please, someone go steal the code! Ralph please package it, open ticket, so that we have tracability. > And stealing is easy. We are not stealing we are reusing. And Generator are probably coming from GNU Smalltalk. > For example I stole the following comment on > class Generator directly from the class comment: > > " > A Generator transforms callback interfaces into stream interfaces. > > When a producer algorithm provide results as callbacks (blocks) and a > consumer algorithm expects streamable input, a Generator transforms > one into the other, for example: > > | generator | > generator := Generator on: [:g| Integer primesUpTo: 100 do:[:prime| g > yield: prime]]. > [generator atEnd] whileFalse:[Transcript show: generator next]. > " > > Regards, > > Ralph Boland >

Jan. 5, 2011

Re: [Pharo-project] Issue 3506 in pharo: TextMorph's #autoFit: and #wrapFlag: are confusing

by StÃ©phane Ducasse

thanks sean! On Jan 4, 2011, at 11:44 PM, Sean P. DeNigris wrote: > > Fix in inbox > SLICE-Issue-3506-TextMorphs-autoFit-and-wrapFlag-are-confusing-SeanDeNigris.1 > > Added comments for TextMorph's #autoFit: and #wrapFlag: > -- > View this message in context: http://forum.world.st/Issue-3506-in-pharo-TextMorph-s-autoFit-and-wrapFlag-… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 5, 2011

Re: [Pharo-project] ConfigurationOfPharo: now with Mocketry, Autotest, XMLSupport and Helps

by StÃ©phane Ducasse

thanks laurent With Olivier auverlot friday we will take soup and use it as a casee study to write an help and a good structure. Stef On Jan 4, 2011, at 10:46 PM, laurent laffont wrote: > Hi, > > I've updated ConfigurationOfPharo 1.2-beta2: > Added: > - Mocketry > - XMLSupport > - Autotest > - Shortcuts-Help > > more tests and Help. > > I've put methods in categories. > > Can someone check ? > > For independent Help packages, shouldn't we create a ConfigurationOfPharoHelp ? > > Cheers, > > Laurent Laffont > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/

Jan. 5, 2011

Re: [Pharo-project] Pharo and CommandShell on OSX ?

by John M McIntosh

Ok a couple of years back Eliot had me compile up a AioPlugin for os-x I've send that to Esteban Lorenzano. I note that from a plugin perspective os-x is well unix. The os-x application loader code will either take a bundle or a library etc etc. it really doesn't care what form the binary is from pure ancient unix to post modern os-x bundle. Some people *think* os-x is special, well yes/no, it's is unix, yet the UI isn't x-windows so various things in osprocess won't fly, forking a UI based app freaks things out as it's ok for x-windows but that concept is lost on window server. Still the aioplugin as a bundle or dynlib, we don't care. On 2011-01-05, at 12:00 AM, Igor Stasenko wrote: > What i have learned , that AioPlugin should be included in VM, so > osprocess plugin will use more elegant way of working :) -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Jan. 5, 2011

Re: [Pharo-project] [Pharo-users] Minimal pharo

by Luc Fabresse

Hi all, Yes, I agree with Adrian, all cleanings should be integrated. Perhaps in #cleanUpForProduction that already integrates some elements pointed by Mariano. #Luc 2011/1/5 Adrian Lienhard <adi(a)netstyle.ch> > > On Jan 4, 2011, at 22:42 , Mariano Martinez Peck wrote: > > > ps: I wonder if any of those scripts should be added to ScriptLoader > > Yes, that would be good! Like this we can improve them and other people can > contribute. > > Esteban, could you share your experience with unloading packages? I assume > you had to also reorganize packages to make them cleanly unloadable? If yes > these changes should be integrated to improve the modularization. > > Cheers, > Adrian >

Jan. 5, 2011

[Pharo-project] Monticello and source origin

by Torsten Bergmann

When I create a changeset and file it out I can see the image (Pharo/Squeak and version) that was used to create the code in the header. Currently when I find an MCZ somewhere on the web I'm not able to see if Pharo 1.0 or Pharo 1.2 or Squeak 4.1 was used to create it. At least I havent found something when I check "package", "version", "snapshot.bin" or "snapshot"/source in the ZIP. Would'nt it make sense to add something like this? Thx Torsten -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

Jan. 5, 2011

Re: [Pharo-project] Pharo and CommandShell on OSX ?

by Igor Stasenko

On 5 January 2011 04:12, David T. Lewis <lewis(a)mail.msen.com> wrote: > On Tue, Jan 04, 2011 at 08:03:42PM -0300, Esteban Lorenzano wrote: >> ah... I think (if I understood well) the real problem is that OSProcess >> were implementing it's own aio things and now it is relying (correctly) >> in AioPlugin... so, before that, it wasn't important if AioPlugin was >> present, and now it is (btw... UnixOSProcessPlugin don't really need >> AioPlugin, it switches to an ugly but necessary polling when absent) >> >> Cheers, >> Esteban > > Yes, that's right. The first version of OSProcess (from 1999) had > OSProcess and the OSProcessPlugin. Over time, it grew and I split > it into packages. Now CommandShell and OSProcess are the image side > packages, and OSProcessPlugin, AioPlugin, and XDisplayControlPlugin > provide the VM plugin support. All of it is written in Smalltalk, > including the plugins. > > Originally, CommandShell was part of OSProcess. And originally, > AioPlugin and XDisplayPlugin were part of OSProcessPlugin. > > CommandShell uses OSProcess (but loads and runs without it). > OSProcess uses mainly OSProcessPlugin, but also AioPlugin if > available. OSProcess also uses XDisplayControlPlugin when running > on X11, expecially to support #forkSqueak. > > The X window system is separate from the operating system, > therefore the XDisplayControlPlugin is separate from the > OSProcessPlugin. The aio functions are separate from the > operating system (they are part of Ian's Unix support code, > but not OS functions per se), so the AioPlugin is also separate > from the OSProcessPlugin. > What i have learned , that AioPlugin should be included in VM, so osprocess plugin will use more elegant way of working :) > At the higher level, things that relate directly to operating > system functions and to the representation of OS processes > are part of OSProcess. Things that relate to the pipes, unix > shell syntax, file name globbing, command line parsing, and > shell window display are part of CommandShell. > yes, but it is much nicer to use asynchronous IO for speaking with those pipes etc, than synchronous, because VM don't needs to be (b)locked each time. > Dave > > -- Best regards, Igor Stasenko AKA sig.

Jan. 5, 2011