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

Re: [Pharo-project] Nile tests red - Pharo 1.3

by StÃ©phane Ducasse

On May 5, 2011, at 8:47 AM, Markus Fritsche wrote: > Hello Setf + list, > > on the google project page it says that "sendig via email" is okay, in > the document it says fax or, preferred, snail-mail - is it okay to > email the license agreement? If yes, to which address? mine. Stef > > Regards, Makrus > > 2011/5/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> thanks alain!!! >> did you sign the license agreement? >> >> Setf >> >> On May 4, 2011, at 10:28 PM, Alain_Rastoul wrote: > ------------------------ Dr. StÃ©phane Ducasse -- Directeur de Recherche (Senior Researcher) INRIA - USTL - CNRS UMR 8022 stephane.ducasse(a)inria.fr http://stephane.ducasse.free.fr/ http://rmod.lille.inria.fr/ **NEW ***Tel 00 33 (0)3 20 43 42 56 - Fax 33 3 59 57 78 50 "if you knew today was your last day on earth, what would you do different? ... especially if, by doing something different, today might not be your last day on earth" Calvin&Hobbes European Smalltalk User Group: http://www.esug.org/ Open Source Smalltalks: http://www.pharo-project.org/ Moose Analysis platform: http://www.moosetechnology.org/

May 5, 2011

[Pharo-project] Popularity of Smalltalk in Software Industry

by sourav roy

Hi All,I have just started my career in Software/IT industry and got into a project which involes enhancement/maintainance of product built in Smalltalk.I was never exposed to this language before and have no idea if it is used in the Industry as popularly as JAVA and .NET and looks like its a DEADlanguage for the industry. I may be wrong but i need some clarification about it. I just want to know that why smalltalk is not so popular as the other OOPs Languages and what is the future prospect of one if he/she is into Smalltalk development.Looking for some positive note so that it may give me some entho for working with Smalltalk. Thanks&Regards, Sourav RoyGet Yourself a cool, short @in.com Email ID now!

May 5, 2011

Re: [Pharo-project] [squeak-dev] Personalized systems with Treated

by StÃ©phane Ducasse

Chris can you create a bug entry report and add your changeset there so that we have it in our radar. Contrarily to want people may think we are not spying what squeak does we are paying attention to make sure that we make progress for our vision. So I imagine that in the future if people want to be compatible with us they will have to push to us fixes that they think is ok. Now about the TreatedInbox: pay attention these are just the fixed proposed that we pushed there once integrated or not. So once a issue is closed the code is there and its integrated version in Pharo. The problem you mention is true for a lot of system, in Moose they are using special version of system packages. On May 5, 2011, at 4:35 AM, Chris Muller wrote: > To support Magma 1.2, I introduced some changes to OrderedCollection > into the Squeak trunk some time ago. To deliver Magma to Pharo users, > I needed to have these same enhancements in Pharo 1.1 and 1.2. But > they were already released, so how was this solved? > > My first instinct was to deliver a change-set; the classical way to > modify the system. But I know dirty packages are unattractive, and > besides that the only way to achieve one-click load of something > involving a change-set + MC-packages in Pharo is with a SAR - overkill > since Magma is just MC packages; no resources. I really wanted to > release Magma 1.2 to Pharo with just a Gofer script. > > So, I decided to import the same changes I made to Squeak's > OrderedCollection into Pharo's and then save that new version to the > Inbox and adjusted my Gofer script for loading Magma to merge that > version of Collections from repositories: Pharo, Inbox, TreatedInbox. > > I knew they would accept it, thank you Pharo, BUT it's nice to know > that I could actually deliver my application without having to wait > for it to be integrated, or worry even if it didn't get accepted; that > chain of repositories should work immediately and forever, no matter > the outcome of acceptance. > > Thanks to MC merging, this is as unintrusive as it can be; in case > someone runs with their own "personalizations" to the Collections > package, loading Magma won't clobber them; nor will updating with > official Pharo-released patches, because those are merged too. > > With the context of this experience, I came to view the "Treated" > repository with a new respect; enabling a non-core developer to > personalize system packages for my application.. > > - Chris >

May 5, 2011

Re: [Pharo-project] new Cog VMs uploaded

by StÃ©phane Ducasse

>> >>> You should be able to extract the code and use it in Pharo/Squeak >>> without issue, even if it is GPL. What you can't do is include it in >>> the distribution, since it isn't MIT. You also shouldn't study the >>> code and write your own version of it - I believe that would be a >>> derivative work, which would likely make it a GPL derivative. >> >> so it does not exist and this is better because GPL is viral and we do not want it. >> > > I finding it really funny that GPL were invented to help open-source > to rise and spread, > and now its just stands in your way, as any other closed-source > proprietary one... GPL is more than free software it is a nearly a societal model that I respect. > >>> However, if it was extracted, and you brought it in to do profiling, >>> and then removed it afterwards, that shouldn't be an issue at all. >>> Just remember to remove it after you no longer need it - that way the >>> GPL code won't accidentally creep into the Pharo/Squeak code-base. >>> >>> Basically, this would be a great example of a project that should be >>> an external project and not part of core (or dev). >> >> the problem is that this kind of philosophy goes against the spirit of smalltalk >> of been able to read and learn the code and modify it. > > > I think that Teleplace has not much choice under which license to > release this code, > because as long as you using even portion of GPL-ed code, you are > forced to use GPL as well. And also it avoids that you can do business with it without contributing back which I understand well too. I do not criticize teleplace decision. I just warn us against using any code from there.

May 5, 2011

[Pharo-project] Personalized systems with Treated

by Chris Muller

To support Magma 1.2, I introduced some changes to OrderedCollection into the Squeak trunk some time ago. To deliver Magma to Pharo users, I needed to have these same enhancements in Pharo 1.1 and 1.2. But they were already released, so how was this solved? My first instinct was to deliver a change-set; the classical way to modify the system. But I know dirty packages are unattractive, and besides that the only way to achieve one-click load of something involving a change-set + MC-packages in Pharo is with a SAR - overkill since Magma is just MC packages; no resources. I really wanted to release Magma 1.2 to Pharo with just a Gofer script. So, I decided to import the same changes I made to Squeak's OrderedCollection into Pharo's and then save that new version to the Inbox and adjusted my Gofer script for loading Magma to merge that version of Collections from repositories: Pharo, Inbox, TreatedInbox. I knew they would accept it, thank you Pharo, BUT it's nice to know that I could actually deliver my application without having to wait for it to be integrated, or worry even if it didn't get accepted; that chain of repositories should work immediately and forever, no matter the outcome of acceptance. Thanks to MC merging, this is as unintrusive as it can be; in case someone runs with their own "personalizations" to the Collections package, loading Magma won't clobber them; nor will updating with official Pharo-released patches, because those are merged too. With the context of this experience, I came to view the "Treated" repository with a new respect; enabling a non-core developer to personalize system packages for my application.. - Chris

May 5, 2011

Re: [Pharo-project] new Cog VMs uploaded

by Igor Stasenko

On 4 May 2011 23:39, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi chris > > >> You should be able to extract the code and use it in Pharo/Squeak >> without issue, even if it is GPL. Â What you can't do is include it in >> the distribution, since it isn't MIT. Â You also shouldn't study the >> code and write your own version of it - I believe that would be a >> derivative work, which would likely make it a GPL derivative. > > so it does not exist and this is better because GPL is viral and we do not want it. > I finding it really funny that GPL were invented to help open-source to rise and spread, and now its just stands in your way, as any other closed-source proprietary one... >> However, if it was extracted, and you brought it in to do profiling, >> and then removed it afterwards, that shouldn't be an issue at all. >> Just remember to remove it after you no longer need it - that way the >> GPL code won't accidentally creep into the Pharo/Squeak code-base. >> >> Basically, this would be a great example of a project that should be >> an external project and not part of core (or dev). > > the problem is that this kind of philosophy goes against the spirit of smalltalk > of been able to read and learn the code and modify it. I think that Teleplace has not much choice under which license to release this code, because as long as you using even portion of GPL-ed code, you are forced to use GPL as well. >> >> -Chris >> -- Best regards, Igor Stasenko AKA sig.

May 5, 2011

Re: [Pharo-project] [COTDC] 58 - TextPrinter

by Chris Cunningham

On Wed, May 4, 2011 at 12:18 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > On Tue, May 3, 2011 at 9:21 PM, laurent laffont <laurent.laffont(a)gmail.com> > wrote: >> >> Today:Â TextPrinter > > I've seen it has been deprecated on recent PharoCore. > Laurent. > Hmm, ok. Of course, the only reason I used it was to call it to get various paper sizes and to refresh my memory on how to use the printer interface. I've never used it for its intended purpose, though. -Chris

May 4, 2011

Re: [Pharo-project] Nile tests red - Pharo 1.3

by StÃ©phane Ducasse

thanks alain!!! did you sign the license agreement? Setf On May 4, 2011, at 10:28 PM, Alain_Rastoul wrote: > Hi, > > I have a changeset to fix most tests -all except one at this time- of Nile, > most of the red tests are the same errors related to NewParagraph, > NSTranscripter, so the changeset is very small but I don't the procedure to > submit a fix ? > Do I add a comment to the issue at code.google with the attached changeset ? > http://code.google.com/p/pharo/issues/detail?id=4051 > > Do someone review the code (as I am new to Pharo and don't know much of Nile > , Transcripter ) ? > Do someone - ... who? ... - incorporate the changeset in the sources of the > package ? > > TIA > > Alain > > > >

May 4, 2011

Re: [Pharo-project] [update 1.3] #13182

by StÃ©phane Ducasse

thanks laurent!!!!! On May 4, 2011, at 9:45 PM, laurent laffont wrote: > 13182 > ----- > > COTDC integration > - 49 - ClassFactoryWithOrganization - A.Bergel > - 50 - LongTestCase (fix waiting for review - issue #4132) - L.Laffont > - 51 - TestCaseAnnouncement, TestCaseStarted, TestCaseEnded - A.Bergel > - 52 - PCXReadWriter (deprecated) - G.Polito > - 53 - AnimatedGIFReadWriter - L.Laffont > - 54 - BMPReadWriter - L.Laffont > - 55 - IdentityGlyphMap (removed) - L.Laffont > - 56 - HostFont (removed) - C.Cunningham > - 57 - ColorMap - F.Olivero > - 58 - TextPrinter (deprecated) > > > Laurent Laffont - @lolgzs > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ > Developer group: http://cara74.seasidehosting.st >

May 4, 2011

Re: [Pharo-project] new Cog VMs uploaded

by StÃ©phane Ducasse

Hi chris > You should be able to extract the code and use it in Pharo/Squeak > without issue, even if it is GPL. What you can't do is include it in > the distribution, since it isn't MIT. You also shouldn't study the > code and write your own version of it - I believe that would be a > derivative work, which would likely make it a GPL derivative. so it does not exist and this is better because GPL is viral and we do not want it. > However, if it was extracted, and you brought it in to do profiling, > and then removed it afterwards, that shouldn't be an issue at all. > Just remember to remove it after you no longer need it - that way the > GPL code won't accidentally creep into the Pharo/Squeak code-base. > > Basically, this would be a great example of a project that should be > an external project and not part of core (or dev). the problem is that this kind of philosophy goes against the spirit of smalltalk of been able to read and learn the code and modify it. > > -Chris >

May 4, 2011