Re: [Pharo-dev] Printing in transcript inside a loop
Ah ok, thank you Mathieu! 2015-06-10 11:56 GMT+02:00 Matthieu Lacaton : > Hello, > > You need to fork it to be able to see the updates right away. > > An example : > > [ 1 to: 100 do: [ :i | > Transcript show: i asString. > (Delay forMilliseconds: 20) wait. > ] ] fork > > Cheers, > > Matthieu > > 2015-06-10 11:48 GMT+02:00 Sebastian Tleye : > >> Hi all, >> >> I want to print in the transcript from inside a loop, the problem I am >> seeing is that it does not print until the loop is finished. Is it a bug or >> do I have to configure something? >> >> This is a piece of code to exemplify it >> >> (1 to: 1) do: [ :i | >> Transcript show: i asString. >> ] >> >> Thanks in advance >> >> By the way, I am using Pharo 3. >> >> -- >> Sebastián Tleye >> > > -- Sebastián Tleye
[Pharo-dev] Printing in transcript inside a loop
Hi all, I want to print in the transcript from inside a loop, the problem I am seeing is that it does not print until the loop is finished. Is it a bug or do I have to configure something? This is a piece of code to exemplify it (1 to: 1) do: [ :i | Transcript show: i asString. ] Thanks in advance By the way, I am using Pharo 3. -- Sebastián Tleye
Re: [Pharo-dev] Doubt about NumericalMethods package
Thanks Serge, I'll take a look at the book 2015-02-25 12:29 GMT+01:00 Serge Stinckwich : > On Tue, Feb 24, 2015 at 10:31 PM, Sebastian Tleye > wrote: > > Hi, > > Dear Sebastian, > > > I've installed the NumericalMethods package and I am trying to use the > class > > DhbMultiVariableGeneralOptimizer to optimize a function. > > If I run the code of the test it works perfectly > > > > | fBlock finder result | > > fBlock := [ :x | |r| r := x * x. r = 0 ifTrue: [ 1] ifFalse: [ r sqrt > sin / > > r] ]. > > finder := DhbMultiVariableGeneralOptimizer maximizingFunction: fBlock. > > finder desiredPrecision: 0.01. > > finder origin: #(0.2 0.2 0.2) asVector; range: #(1 1 1) asVector. > > result := finder evaluate. > > > > however, if I want to set my own function, (for example the sum of the > > elements of the parameter. fBlock := [ :x | x sum ]) it is throwing an > error > > of ScriptOutOfBounds > > > > I am not sure If I am doing something wrong or there is a bug in the > > implementation. > > > > I haven't found too much documentation about how to use this package. > > > > Is there someone using this particular class? > > You can some information about the classes in Didier Besset book available > here: > > https://github.com/SquareBracketAssociates/NumericalMethods/releases/tag/snapshot-2015-01-26 > > This package is part of the SciSmalltalk distribution: > https://github.com/SergeStinckwich/SciSmalltalk > Please feel free to join the mailing-list here: > https://groups.google.com/forum/#!forum/scismalltalk > > I don't have time to look at your problem at the moment. > If you find an explanation or a bug fix, please tell us about this. > > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > > -- Sebastián Tleye
[Pharo-dev] Doubt about NumericalMethods package
Hi, I've installed the NumericalMethods package and I am trying to use the class DhbMultiVariableGeneralOptimizer to optimize a function. If I run the code of the test it works perfectly | fBlock finder result | fBlock := [ :x | |r| r := x * x. r = 0 ifTrue: [ 1] ifFalse: [ r sqrt sin / r] ]. finder := DhbMultiVariableGeneralOptimizer maximizingFunction: fBlock. finder desiredPrecision: 0.01. finder origin: #(0.2 0.2 0.2) asVector; range: #(1 1 1) asVector. result := finder evaluate. however, if I want to set my own function, (for example the sum of the elements of the parameter. fBlock := [ :x | x sum ]) it is throwing an error of ScriptOutOfBounds I am not sure If I am doing something wrong or there is a bug in the implementation. I haven't found too much documentation about how to use this package. Is there someone using this particular class? Thanks in advance! -- Sebastián Tleye
Re: [Pharo-dev] Create a user for jenkins
Thanks Christophe! 2015-02-10 14:50 GMT+01:00 Christophe Demarey : > Hi Sebastian, > > Le 10 févr. 2015 à 14:37, Sebastian Tleye a écrit : > > > Hi All, > > > > I'd like to see some of the jenkins jobs of Pharo to have an idea how > they were created, I don't have a user in jenkins and when I want to see > the jobs as an anonymous user (read-only) jenkins throws an > java.lang.NullPointerException error. > > You don't need permissions to browse jobs but you need them if you want to > browse jobs configuration. > > > How can I create a user? I only need a user to see how the jobs were > created, I don't need to create or modify jobs. > > Create an account on https://ci.inria.fr and ask to join the project you > are interested in (pharo-contribution for example). > > Regards, > Christophe > > -- Sebastián Tleye
[Pharo-dev] Create a user for jenkins
Hi All, I'd like to see some of the jenkins jobs of Pharo to have an idea how they were created, I don't have a user in jenkins and when I want to see the jobs as an anonymous user (read-only) jenkins throws an java.lang.NullPointerException error. How can I create a user? I only need a user to see how the jobs were created, I don't need to create or modify jobs. Thanks! Sebastián Tleye
Re: [Pharo-dev] Metacello + Filetree
Thanks Thierry and Dale, I created the ConfigurationClass from scratch and this time it worked, apparently there were something wrong. Thanks a lot :) 2015-02-07 20:42 GMT+01:00 Dale Henrichs : > The best way to resolve configuration errors is to run the validator: > > (MetacelloToolBox validateConfiguration: ) inspect. > > The class comment of MetacelloMCVersionValidator has information about the > various reason codes and between the two you should be able to figure out > how to repair the configuration. > > Let me know if you need additional help interpreting the validation report. > > Dale > > > On 2/7/15 11:29 AM, Thierry Goubier wrote: > > Hi Sebastian, > > It seems that something is amiss in the configuration. You are using a > baseline in the configuration? Are you using #common, #pharoX.x tags? I am > also a bit lost with some of Metacello errors, and it is usually just a > typo in one of the tags, or trying to use two baselines, etc... > > Thierry > > 2015-02-06 14:40 GMT+01:00 Sebastian Tleye : > >> Hi Thierry, >> >> I still have the same problem, I managed to install and configure >> GitFiletree, I can add a remote git repository, load packages from it, etc. >> Also, I created a new stable version with the versioner. If I open the >> repository with Monticello I can see the history of the the packages, not >> only the last one. >> However, It's still throwing the same error, it cannot resolve the name >> of the package that it needs. >> >> (By the way, the development version can be still loaded correctly) >> >> Any Idea of what can it be? >> I am not an expert in Metacello, so maybe is a problem with the >> Configuration file (in the baseline I tried both, reference to the remote >> git repository and to the local gitfiletree repository) >> >> >> 2015-02-05 13:38 GMT+01:00 Thierry Goubier : >> >>> >>> >>> 2015-02-05 13:26 GMT+01:00 Sebastian Tleye : >>> >>>> Ok, great, I'll try GitFileTree, we are using the standard port. >>>> >>> >>> Please ask if you need any help. Criticism on the lack of >>> documentation and missing features accepted :) >>> >>> Thierry >>> >>> >>>> >>>> Thanks! >>>> >>>> 2015-02-05 12:53 GMT+01:00 Serge Stinckwich >>> >: >>>> >>>>> Why not launching a kickstarter thing to have someone (you !) paid >>>>> to have a clean integration of git/pharo with documentation ? I guess >>>>> people, companies and associations like ESUG can give money for that. >>>>> >>>>> >>>>> Sent from my iPhone >>>>> >>>>> On 5 févr. 2015, at 12:38, Thierry Goubier >>>>> wrote: >>>>> >>>>> >>>>> >>>>> 2015-02-05 11:27 GMT+01:00 Sebastian Tleye >>>>> : >>>>> >>>>>> Thanks Yuriy and Thierry, >>>>>> >>>>>> I see what I can do, I was using Bitbucket until some time ago but >>>>>> now we moved our project to a private git server! >>>>>> >>>>> >>>>> If you are on a private server, then GitFileTree will work (except >>>>> if the git server is on a non-standard port: I will add support for that >>>>> in >>>>> the near future). >>>>> >>>>> Look for baselines and branches support to make your life (and your >>>>> configurations) simpler. >>>>> >>>>> As I said during PharoDays: we now have a good chunk of the >>>>> necessary infrastructure and we (the Pharo community) can develop >>>>> additional support if needed. Asking (funding) the consortium for that >>>>> could be a real cool way of contributing :) >>>>> >>>>> Thierry >>>>> >>>>> >>>>>> >>>>>> 2015-02-05 11:13 GMT+01:00 Thierry Goubier >>>>> >: >>>>>> >>>>>>> Hi Sebastian, >>>>>>> >>>>>>> filetree only gives you access to the latest version of your >>>>>>> packages, and you can't access the history without access to the >>>>>>> underlying >>>>>>> version control system you are using. >>>>>>> >>>>>>> This access for Metacello is
Re: [Pharo-dev] Metacello + Filetree
Hi Thierry, I still have the same problem, I managed to install and configure GitFiletree, I can add a remote git repository, load packages from it, etc. Also, I created a new stable version with the versioner. If I open the repository with Monticello I can see the history of the the packages, not only the last one. However, It's still throwing the same error, it cannot resolve the name of the package that it needs. (By the way, the development version can be still loaded correctly) Any Idea of what can it be? I am not an expert in Metacello, so maybe is a problem with the Configuration file (in the baseline I tried both, reference to the remote git repository and to the local gitfiletree repository) 2015-02-05 13:38 GMT+01:00 Thierry Goubier : > > > 2015-02-05 13:26 GMT+01:00 Sebastian Tleye : > >> Ok, great, I'll try GitFileTree, we are using the standard port. >> > > Please ask if you need any help. Criticism on the lack of documentation > and missing features accepted :) > > Thierry > > >> >> Thanks! >> >> 2015-02-05 12:53 GMT+01:00 Serge Stinckwich : >> >>> Why not launching a kickstarter thing to have someone (you !) paid to >>> have a clean integration of git/pharo with documentation ? I guess people, >>> companies and associations like ESUG can give money for that. >>> >>> >>> Sent from my iPhone >>> >>> On 5 févr. 2015, at 12:38, Thierry Goubier >>> wrote: >>> >>> >>> >>> 2015-02-05 11:27 GMT+01:00 Sebastian Tleye : >>> >>>> Thanks Yuriy and Thierry, >>>> >>>> I see what I can do, I was using Bitbucket until some time ago but now >>>> we moved our project to a private git server! >>>> >>> >>> If you are on a private server, then GitFileTree will work (except if >>> the git server is on a non-standard port: I will add support for that in >>> the near future). >>> >>> Look for baselines and branches support to make your life (and your >>> configurations) simpler. >>> >>> As I said during PharoDays: we now have a good chunk of the necessary >>> infrastructure and we (the Pharo community) can develop additional support >>> if needed. Asking (funding) the consortium for that could be a real cool >>> way of contributing :) >>> >>> Thierry >>> >>> >>>> >>>> 2015-02-05 11:13 GMT+01:00 Thierry Goubier : >>>> >>>>> Hi Sebastian, >>>>> >>>>> filetree only gives you access to the latest version of your packages, >>>>> and you can't access the history without access to the underlying version >>>>> control system you are using. >>>>> >>>>> This access for Metacello is available in two ways: via Metacello >>>>> github:// and bitbucket:// urls and tags or branches (but you need to be >>>>> using either github or bitbucket), or via GitFileTree if you are using >>>>> git. >>>>> >>>>> Thierry >>>>> >>>>> 2015-02-05 11:03 GMT+01:00 Sebastian Tleye >>>>> : >>>>> >>>>>> Hi, >>>>>> >>>>>> I am using a filetree repository for my project, also I have created >>>>>> a first stable version using the versioner tool. >>>>>> Everything was working fine until I commited more changes, now when I >>>>>> want to install the stable version is throwing an error saying that >>>>>> cannot >>>>>> resolve the package that it needs, however if I load the development >>>>>> version it works perfectly. >>>>>> >>>>>> To clarify a little, >>>>>> >>>>>> The development version tries to load >>>>>> Phadeo-ImporterExporters-SebastianTleye.12 and it works perfectly. The >>>>>> stable version tries to load Phadeo-ImporterExporters-SebastianTleye.10 >>>>>> and >>>>>> it throws an error saying that it cannot be resolve. >>>>>> >>>>>> Any Idea of what is happening? >>>>>> I read that filetree and Metacello are compatibles so I don't know >>>>>> what's the problem >>>>>> >>>>> >>>>> Hi sebastian >>>>> >>>>> >>>>>> >>>>>> Thanks in advance >>>>>> >>>>>> Sebastián Tleye >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Sebastián Tleye >>>> >>> >>> >> >> >> -- >> Sebastián Tleye >> > > -- Sebastián Tleye
Re: [Pharo-dev] Metacello + Filetree
Ok, great, I'll try GitFileTree, we are using the standard port. Thanks! 2015-02-05 12:53 GMT+01:00 Serge Stinckwich : > Why not launching a kickstarter thing to have someone (you !) paid to > have a clean integration of git/pharo with documentation ? I guess people, > companies and associations like ESUG can give money for that. > > > Sent from my iPhone > > On 5 févr. 2015, at 12:38, Thierry Goubier > wrote: > > > > 2015-02-05 11:27 GMT+01:00 Sebastian Tleye : > >> Thanks Yuriy and Thierry, >> >> I see what I can do, I was using Bitbucket until some time ago but now we >> moved our project to a private git server! >> > > If you are on a private server, then GitFileTree will work (except if the > git server is on a non-standard port: I will add support for that in the > near future). > > Look for baselines and branches support to make your life (and your > configurations) simpler. > > As I said during PharoDays: we now have a good chunk of the necessary > infrastructure and we (the Pharo community) can develop additional support > if needed. Asking (funding) the consortium for that could be a real cool > way of contributing :) > > Thierry > > >> >> 2015-02-05 11:13 GMT+01:00 Thierry Goubier : >> >>> Hi Sebastian, >>> >>> filetree only gives you access to the latest version of your packages, >>> and you can't access the history without access to the underlying version >>> control system you are using. >>> >>> This access for Metacello is available in two ways: via Metacello >>> github:// and bitbucket:// urls and tags or branches (but you need to be >>> using either github or bitbucket), or via GitFileTree if you are using git. >>> >>> Thierry >>> >>> 2015-02-05 11:03 GMT+01:00 Sebastian Tleye : >>> >>>> Hi, >>>> >>>> I am using a filetree repository for my project, also I have created a >>>> first stable version using the versioner tool. >>>> Everything was working fine until I commited more changes, now when I >>>> want to install the stable version is throwing an error saying that cannot >>>> resolve the package that it needs, however if I load the development >>>> version it works perfectly. >>>> >>>> To clarify a little, >>>> >>>> The development version tries to load >>>> Phadeo-ImporterExporters-SebastianTleye.12 and it works perfectly. The >>>> stable version tries to load Phadeo-ImporterExporters-SebastianTleye.10 and >>>> it throws an error saying that it cannot be resolve. >>>> >>>> Any Idea of what is happening? >>>> I read that filetree and Metacello are compatibles so I don't know >>>> what's the problem >>>> >>> >>> Hi sebastian >>> >>> >>>> >>>> Thanks in advance >>>> >>>> Sebastián Tleye >>>> >>> >>> >> >> >> -- >> Sebastián Tleye >> > > -- Sebastián Tleye
Re: [Pharo-dev] Metacello + Filetree
hahah ok! 2015-02-05 11:33 GMT+01:00 Yuriy Tymchuk : > Let us know about your solution, it can be interesting. > > Uko > > > On 05 Feb 2015, at 11:27, Sebastian Tleye > wrote: > > Thanks Yuriy and Thierry, > > I see what I can do, I was using Bitbucket until some time ago but now we > moved our project to a private git server! > > 2015-02-05 11:13 GMT+01:00 Thierry Goubier : > >> Hi Sebastian, >> >> filetree only gives you access to the latest version of your packages, >> and you can't access the history without access to the underlying version >> control system you are using. >> >> This access for Metacello is available in two ways: via Metacello >> github:// and bitbucket:// urls and tags or branches (but you need to be >> using either github or bitbucket), or via GitFileTree if you are using git. >> >> Thierry >> >> 2015-02-05 11:03 GMT+01:00 Sebastian Tleye : >> >>> Hi, >>> >>> I am using a filetree repository for my project, also I have created a >>> first stable version using the versioner tool. >>> Everything was working fine until I commited more changes, now when I >>> want to install the stable version is throwing an error saying that cannot >>> resolve the package that it needs, however if I load the development >>> version it works perfectly. >>> >>> To clarify a little, >>> >>> The development version tries to load >>> Phadeo-ImporterExporters-SebastianTleye.12 and it works perfectly. The >>> stable version tries to load Phadeo-ImporterExporters-SebastianTleye.10 and >>> it throws an error saying that it cannot be resolve. >>> >>> Any Idea of what is happening? >>> I read that filetree and Metacello are compatibles so I don't know >>> what's the problem >>> >> >> Hi sebastian >> >> >>> >>> Thanks in advance >>> >>> Sebastián Tleye >>> >> >> > > > -- > Sebastián Tleye > > > -- Sebastián Tleye
Re: [Pharo-dev] Metacello + Filetree
Thanks Yuriy and Thierry, I see what I can do, I was using Bitbucket until some time ago but now we moved our project to a private git server! 2015-02-05 11:13 GMT+01:00 Thierry Goubier : > Hi Sebastian, > > filetree only gives you access to the latest version of your packages, and > you can't access the history without access to the underlying version > control system you are using. > > This access for Metacello is available in two ways: via Metacello > github:// and bitbucket:// urls and tags or branches (but you need to be > using either github or bitbucket), or via GitFileTree if you are using git. > > Thierry > > 2015-02-05 11:03 GMT+01:00 Sebastian Tleye : > >> Hi, >> >> I am using a filetree repository for my project, also I have created a >> first stable version using the versioner tool. >> Everything was working fine until I commited more changes, now when I >> want to install the stable version is throwing an error saying that cannot >> resolve the package that it needs, however if I load the development >> version it works perfectly. >> >> To clarify a little, >> >> The development version tries to load >> Phadeo-ImporterExporters-SebastianTleye.12 and it works perfectly. The >> stable version tries to load Phadeo-ImporterExporters-SebastianTleye.10 and >> it throws an error saying that it cannot be resolve. >> >> Any Idea of what is happening? >> I read that filetree and Metacello are compatibles so I don't know what's >> the problem >> > > Hi sebastian > > >> >> Thanks in advance >> >> Sebastián Tleye >> > > -- Sebastián Tleye
[Pharo-dev] Metacello + Filetree
Hi, I am using a filetree repository for my project, also I have created a first stable version using the versioner tool. Everything was working fine until I commited more changes, now when I want to install the stable version is throwing an error saying that cannot resolve the package that it needs, however if I load the development version it works perfectly. To clarify a little, The development version tries to load Phadeo-ImporterExporters-SebastianTleye.12 and it works perfectly. The stable version tries to load Phadeo-ImporterExporters-SebastianTleye.10 and it throws an error saying that it cannot be resolve. Any Idea of what is happening? I read that filetree and Metacello are compatibles so I don't know what's the problem Thanks in advance Sebastián Tleye
Re: [Pharo-dev] Running from the command line in Windows
Well, I realized that the result is saved in a file called "stdout", I think this is good enough for me! 2014-10-29 9:44 GMT+01:00 Sebastian Tleye : > Hi Eliot, > > Thanks, I tried but is the same, I can run code but the result does not > appear in the console. > > 2014-10-28 18:30 GMT+01:00 Eliot Miranda : > >> Hi Sebastian, >> >> make sure you use a console VM. You can find non-Pharo console VMs >> at my site which you can test, e.g. >> http://www.mirandabanda.org/files/Cog/VM/VM.r3114/cogwin-14.42.3114.zip. >> The console VM is called SqueakConsole.exe >> >> On Tue, Oct 28, 2014 at 5:52 AM, Sebastian Tleye < >> sebastian.tl...@gmail.com> wrote: >> >>> Hi, >>> >>> I have a little question, >>> >>> I need to run a piece of code from the command line, if I do the >>> following in Mac it works >>> >>> ./Pharo --headless ../Resources/Pharo3.0.image eval '3+3' >>> >>> I see the result of the evaluation in the console, but if I do the same >>> in Windows it runs but it doesn't show the result in the console. >>> >>> Any clue of why this is happening? And how to solve it? >>> Thanks! >>> >> >> >> >> -- >> best, >> Eliot >> > > > > -- > Sebastián Tleye > -- Sebastián Tleye
Re: [Pharo-dev] Running from the command line in Windows
Hi Eliot, Thanks, I tried but is the same, I can run code but the result does not appear in the console. 2014-10-28 18:30 GMT+01:00 Eliot Miranda : > Hi Sebastian, > > make sure you use a console VM. You can find non-Pharo console VMs at > my site which you can test, e.g. > http://www.mirandabanda.org/files/Cog/VM/VM.r3114/cogwin-14.42.3114.zip. > The console VM is called SqueakConsole.exe > > On Tue, Oct 28, 2014 at 5:52 AM, Sebastian Tleye < > sebastian.tl...@gmail.com> wrote: > >> Hi, >> >> I have a little question, >> >> I need to run a piece of code from the command line, if I do the >> following in Mac it works >> >> ./Pharo --headless ../Resources/Pharo3.0.image eval '3+3' >> >> I see the result of the evaluation in the console, but if I do the same >> in Windows it runs but it doesn't show the result in the console. >> >> Any clue of why this is happening? And how to solve it? >> Thanks! >> > > > > -- > best, > Eliot > -- Sebastián Tleye
[Pharo-dev] Running from the command line in Windows
Hi, I have a little question, I need to run a piece of code from the command line, if I do the following in Mac it works ./Pharo --headless ../Resources/Pharo3.0.image eval '3+3' I see the result of the evaluation in the console, but if I do the same in Windows it runs but it doesn't show the result in the console. Any clue of why this is happening? And how to solve it? Thanks!
[Pharo-dev] How to ask files to the user?
Hi, I need to ask files to the user. I know that one way to do it is as follows UIManager default chooseFullFileNameMatching: nil label: 'Bla bla'. but this does not let the user to choose multiple files. it allows only one. How can I do to allow selection of multiple files? Thanks
Re: [Pharo-dev] Anonymous classes in Pharo 3 - must be instances of Class, not Behavior
2014-08-29 13:38 GMT+02:00 Oscar Nierstrasz : > > Following up: > > Behavior new compile: 't ^ true’ > > fails since #compile: is defined in TBehavior and depends on > #basicLocalSelectors which is defined only in Class, MetaClass and > TraitBehavior. > > It seems like #basicLocalSelectors should be abstract in TBehavior. > Alternatively the implementation should be moved to TBehavior and the field > localSelectors should be pushed up to Behavior. Am I missing something? > Yep, I think you are right. Last year I did a lot of modifications in Behavior, TBehavior, Class, etc. These changes were made to make classes and traits polymorphic. If I remember correctly, the instance variable localSelectors was not moved to Behavior because it was not possible to push up that instance variable (there were a lot of errors since it is one of the core classes). If you look at the traits hierarchy, localSelectors is in TraitBehavior, not in Trait. So moving the instance variable localSelectors to Behavior and then abstract basicLocalSelectors in TBehavior would be very good > Oscar > > On 29 Aug 2014, at 12:26 , Oscar Nierstrasz > wrote: > > > > > Hi folks, > > > > I was updating my lecture on Reflection for the Software Design and > Evolution course, and I see now that anonymous classes can no longer be > instances of Behavior but must be instances of Class. If you try to > compile a method on an instance of Behavior, it fails. > (basicLocalSelectors is not understood) > > > > Am I missing something? > > > > Cheers, > > Oscar > > > > testPrimitiveChangeClassTo > > | anonClass browser | > > > > anonClass := Class new. “must be Class, not Behavior" > > anonClass superclass: Browser. > > anonClass setFormat: Browser format. > > > > browser := Browser new. > > browser primitiveChangeClassTo: anonClass new. > > anonClass compile: 'thisIsATest ^ 2'. > > > > self assert: browser thisIsATest = 2. > > self should: [Browser new thisIsATest] > > raise: MessageNotUnderstood. > > > > > > >
Re: [Pharo-dev] Change superclass programatically
With refactoring I think it is also possible, however it requires more programming and understanding of the refactoring classes 2014-08-27 21:28 GMT+02:00 Martin McClure : > On 08/27/2014 12:23 PM, Martin McClure wrote: > >> On 08/27/2014 12:14 PM, Yuriy Tymchuk wrote: >> >>> Any ideas? >>> https://stackoverflow.com/questions/25535202/change- >>> superclass-programatically >>> >>> >>> >> It looks like sending #superclass: to the class would work. >> > > Yes, I verified this works, though I didn't try any tricky cases where the > old and new superclasses have different numbers of instvars, or instvars > with different names. I'd expect those cases to require more sophisticated > solutions. > > Regards, > > -Martin > > >
Re: [Pharo-dev] Videos ESUG2014
Now, if you meant the paper but not the presentation, then I don't know where they are :-) 2014-08-25 22:19 GMT+02:00 Sebastian Tleye : > Mmm, strange, here are the links (I don't know if there are any missing) > > Understanding Pharo's global state to move program through time and space > <https://www.youtube.com/watch?v=kqhvDwY_31k&list=UUO-vBhaKVZf0al-ISMMPvRw> > Live robot programming > <https://www.youtube.com/watch?v=ClPE3eKW8fk&list=UUO-vBhaKVZf0al-ISMMPvRw> > Toward a methodology to turm Smalltalk code to FPGA > <https://www.youtube.com/watch?v=qMSSmUv-cXY&list=UUO-vBhaKVZf0al-ISMMPvRw> > Towards agile cross-platform development > <https://www.youtube.com/watch?v=N4Zxy1CG5QQ&list=UUO-vBhaKVZf0al-ISMMPvRw> > The Moldable Inspector > <https://www.youtube.com/watch?v=m7Au4FUcGV4&list=UUO-vBhaKVZf0al-ISMMPvRw> > ClockSystem: Embedding Time in Smalltalk > <https://www.youtube.com/watch?v=XxMxWzhpIR8&list=UUO-vBhaKVZf0al-ISMMPvRw> > Reducing Waste in Expandable Collections: The Pharo Case > <https://www.youtube.com/watch?v=x0YJ2dsZdKg&list=UUO-vBhaKVZf0al-ISMMPvRw> > > https://www.youtube.com/watch?v=vJOvU1V5hZ4&list=UUO-vBhaKVZf0al-ISMMPvRw > > https://www.youtube.com/watch?v=hwUOwpidp0A&list=UUO-vBhaKVZf0al-ISMMPvRw > > https://www.youtube.com/watch?v=XWHq4IQ7gIQ&list=UUO-vBhaKVZf0al-ISMMPvRw > > https://www.youtube.com/watch?v=OkDOiGZ8R1E&list=UUO-vBhaKVZf0al-ISMMPvRw > > https://www.youtube.com/watch?v=V4CVp77yhUo&list=UUO-vBhaKVZf0al-ISMMPvRw > > https://www.youtube.com/watch?v=AUZQemqQphg&list=UUO-vBhaKVZf0al-ISMMPvRw > > > > > 2014-08-25 22:13 GMT+02:00 Chris Cunningham : > > Naive response, but no, I don't see them on YouTube. >> Nor at >> http://www.esug.org/wiki/pier/Conferences/2014 >> >> >> On Mon, Aug 25, 2014 at 1:06 PM, Sebastian Tleye >> wrote: >> >>> >>> >>> >>> 2014-08-25 1:39 GMT+02:00 Javier Pimás : >>> >>> Are the papers also available? >>>> >>> >>> Yeap, You don't see them? >>> >>>> >>>> Cheers, >>>> Javier >>>> >>>> >>>> On Sat, Aug 23, 2014 at 8:03 AM, stepharo wrote: >>>> >>>>> this is why you should put info in the slides :) >>>>> >>>>> >>>>> On 23/8/14 00:02, Igor Stasenko wrote: >>>>> >>>>>> Haha.. >>>>>> my name (and voice) is now [written] recorded [in stone] on internet. >>>>>> One step closer to world domination! :) >>>>>> >>>>>> Too bad, i was so dragged by presenting the stuff, that i forgot to >>>>>> give a credit to the guy, sitting next to me, who put a lot of effort to >>>>>> make Virtual CPU work. SHAME ON ME! :/ >>>>>> His name is Max Mattone - remember his name! >>>>>> And the list won't be complete without Clement Bera, who also >>>>>> contributed a lot to it as well. And many others in RMoD team. >>>>>> >>>>>> -- >>>>>> Best regards, >>>>>> Igor Stasenko. >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Javier Pimás >>>> Ciudad de Buenos Aires >>>> >>> >>> >> >
Re: [Pharo-dev] Videos ESUG2014
Mmm, strange, here are the links (I don't know if there are any missing) Understanding Pharo's global state to move program through time and space <https://www.youtube.com/watch?v=kqhvDwY_31k&list=UUO-vBhaKVZf0al-ISMMPvRw> Live robot programming <https://www.youtube.com/watch?v=ClPE3eKW8fk&list=UUO-vBhaKVZf0al-ISMMPvRw> Toward a methodology to turm Smalltalk code to FPGA <https://www.youtube.com/watch?v=qMSSmUv-cXY&list=UUO-vBhaKVZf0al-ISMMPvRw> Towards agile cross-platform development <https://www.youtube.com/watch?v=N4Zxy1CG5QQ&list=UUO-vBhaKVZf0al-ISMMPvRw> The Moldable Inspector <https://www.youtube.com/watch?v=m7Au4FUcGV4&list=UUO-vBhaKVZf0al-ISMMPvRw> ClockSystem: Embedding Time in Smalltalk <https://www.youtube.com/watch?v=XxMxWzhpIR8&list=UUO-vBhaKVZf0al-ISMMPvRw> Reducing Waste in Expandable Collections: The Pharo Case <https://www.youtube.com/watch?v=x0YJ2dsZdKg&list=UUO-vBhaKVZf0al-ISMMPvRw> https://www.youtube.com/watch?v=vJOvU1V5hZ4&list=UUO-vBhaKVZf0al-ISMMPvRw https://www.youtube.com/watch?v=hwUOwpidp0A&list=UUO-vBhaKVZf0al-ISMMPvRw https://www.youtube.com/watch?v=XWHq4IQ7gIQ&list=UUO-vBhaKVZf0al-ISMMPvRw https://www.youtube.com/watch?v=OkDOiGZ8R1E&list=UUO-vBhaKVZf0al-ISMMPvRw https://www.youtube.com/watch?v=V4CVp77yhUo&list=UUO-vBhaKVZf0al-ISMMPvRw https://www.youtube.com/watch?v=AUZQemqQphg&list=UUO-vBhaKVZf0al-ISMMPvRw 2014-08-25 22:13 GMT+02:00 Chris Cunningham : > Naive response, but no, I don't see them on YouTube. > Nor at > http://www.esug.org/wiki/pier/Conferences/2014 > > > On Mon, Aug 25, 2014 at 1:06 PM, Sebastian Tleye wrote: > >> >> >> >> 2014-08-25 1:39 GMT+02:00 Javier Pimás : >> >> Are the papers also available? >>> >> >> Yeap, You don't see them? >> >>> >>> Cheers, >>> Javier >>> >>> >>> On Sat, Aug 23, 2014 at 8:03 AM, stepharo wrote: >>> >>>> this is why you should put info in the slides :) >>>> >>>> >>>> On 23/8/14 00:02, Igor Stasenko wrote: >>>> >>>>> Haha.. >>>>> my name (and voice) is now [written] recorded [in stone] on internet. >>>>> One step closer to world domination! :) >>>>> >>>>> Too bad, i was so dragged by presenting the stuff, that i forgot to >>>>> give a credit to the guy, sitting next to me, who put a lot of effort to >>>>> make Virtual CPU work. SHAME ON ME! :/ >>>>> His name is Max Mattone - remember his name! >>>>> And the list won't be complete without Clement Bera, who also >>>>> contributed a lot to it as well. And many others in RMoD team. >>>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko. >>>>> >>>> >>>> >>>> >>> >>> >>> -- >>> Javier Pimás >>> Ciudad de Buenos Aires >>> >> >> >
Re: [Pharo-dev] Videos ESUG2014
2014-08-25 1:39 GMT+02:00 Javier Pimás : > Are the papers also available? > Yeap, You don't see them? > > Cheers, > Javier > > > On Sat, Aug 23, 2014 at 8:03 AM, stepharo wrote: > >> this is why you should put info in the slides :) >> >> >> On 23/8/14 00:02, Igor Stasenko wrote: >> >>> Haha.. >>> my name (and voice) is now [written] recorded [in stone] on internet. >>> One step closer to world domination! :) >>> >>> Too bad, i was so dragged by presenting the stuff, that i forgot to give >>> a credit to the guy, sitting next to me, who put a lot of effort to make >>> Virtual CPU work. SHAME ON ME! :/ >>> His name is Max Mattone - remember his name! >>> And the list won't be complete without Clement Bera, who also >>> contributed a lot to it as well. And many others in RMoD team. >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> >> > > > -- > Javier Pimás > Ciudad de Buenos Aires >
Re: [Pharo-dev] Does any of you try Pharo 3 in OS X Yosemite?
Hahah, yes, but there is a beta version that can be installed already 2014-08-25 16:53 GMT+02:00 Esteban Lorenzano : > you should not have any problem. > now… I would wait a bit until installing yosemite… until they actually > release it. Not because of pharo, but because of OSX ;) > > Esteban > > On 25 Aug 2014, at 16:50, Sebastian Tleye wrote: > > > I'd like to install OS X Yosemite but since I use Pharo to work I don't > want to have problems. > > >
[Pharo-dev] Does any of you try Pharo 3 in OS X Yosemite?
I'd like to install OS X Yosemite but since I use Pharo to work I don't want to have problems.
Re: [Pharo-dev] flatCollect:
Hi, flatCollect: is called by Collection>>gather: instead of renaming gather: what we did is add "flatCollect:" to keep compatibility. Take into account that if you change what flatCollect: returns it will affect all the methods that use "gather:" 2013/11/1 Gabriel Cotelli > I don't have a Pharo at hand now,but if species returns the class of the > collection, be carefull with SortedCollection because in that case the > sortBlock could not work with the collected objects. > > > On Fri, Nov 1, 2013 at 7:55 PM, Tudor Girba wrote: > >> Hi, >> >> I see that Pharo 3.0 has a Collection>>flatCollect:. This is great as the >> method proved to be very valuable in the context of Moose. >> >> However, the current Pharo implementation is less ideal: >> >> Collection>>flatCollect: aBlock >> ^ Array streamContents: >> [:stream | >> self do: [:ea | stream nextPutAll: (aBlock value: ea)]] >> >> The Moose one is: >> Collection>>flatCollect: aBlock >> "Evaluate aBlock for each of the receiver's elements and answer the >> list of all resulting values flatten one level. Assumes that aBlock >> returns some kind >> of collection for each element. Equivalent to the lisp's mapcan" >> "original written by a. Kuhn and released under MIT" >> | stream | >> self isEmpty ifTrue: [ ^ self copy ]. >> stream := (self species new: 0) writeStream. >> self do: [ :each | stream nextPutAll: (aBlock value: each) ]. >> ^ stream contents >> >> The difference is in the type returned. The Pharo one always returns >> Array, while the Moose one returns a collection of the same species as the >> receiver. >> >> Does anyone have anything against the Moose implementation? >> >> Doru >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > >
Re: [Pharo-dev] References to Obsolete classes
I agree, If you want to reference an obsolete class after removing the class A, then the source code of the method should also change, and say "AnObsoleteA" instead of "A" if the source code says "A" then i do not like to have a reference to "AnObsoleteA" 2013/10/4 Sabine Knöfel > Hi, > > I run into the same problem last week and endend up in reloading my code > in a new image. I prefer your suggestion. > > Sabine > > > Von meinem iPad gesendet > > Am 04.10.2013 um 12:04 schrieb Noury Bouraqadi : > > > Hi, > > > > Consider the following scenario: > > 1- create class A > > 2- create class B with a method m that references class A > > 3- delete class A . As a result B>>#m holds a reference to ObsoleteA > > 4- create a new class A. > > > > B>>#m continues to hold a reference to ObsoleteA. This is even more > disturbing, since the source of B>>#m displays A. > > > > Is this behavior desired? If yes, in which situations. because I'd > rather prefer to have B>>#m updated. This can be done, by moving the > association of a removed class (or global in the general case) from the > system dictionary to the Undeclared. > > > > Side note: just noticed that Undeclared is a dictionary. I was expecting > it to be a WeakSet. > > > > Noury > > Ecole des Mines de Douai > > http://car.mines-douai.fr/noury > > -- > > > > > > > > > > Afin de contribuer au respect de l'environnement, > > merci de n'imprimer ce courriel qu'en cas de necessite > > > > Please consider the environment before you print > > > > > > > > > >
Re: [Pharo-dev] [update 3.0] #30443
2013/10/3 Marcus Denker > > On Oct 3, 2013, at 5:15 PM, Marcus Denker wrote: > > > 30443 > > - > > > > 11757 NautilusMCBindings misses a reset method > > https://pharo.fogbugz.com/f/cases/11757 > > > > Now the image is 3MB Smaller… (and yes, cleaning up is just a workaround) > > +1 :D > Marcus > >
Re: [Pharo-dev] [Pharo-users] Pharo Sprint in Buenos Aires
The Pabellon 1 is closed on saturdays afternoon, but have you asked for Pabellon 2? I think it's open on saturdays (i don't know if it is possible to book a room) 2013/9/4 Guillermo Polito > Probably UTN? > > > On Wed, Sep 4, 2013 at 2:45 PM, Camillo Bruni wrote: > >> So it looks like we are going to do the Pharo sprint in Buenos Aires >> Saturday, the 14th of September. >> The question is now where do we meet? >> The original idea was to reserver a room at the UBA, but that is not >> possible the weekend. >> Any suggestions? >> >> On 2013-09-03, at 09:05, Mariano Martinez Peck >> wrote: >> >> > Cool. I'll be there, of course! >> > Keep us informed. >> > Cheers, >> > >> > >> > On Mon, Sep 2, 2013 at 10:42 PM, Camillo Bruni > >wrote: >> > >> >> everything is open so far, guido had the idea of reserving a room at >> the >> >> UBA, >> >> we will have more details tomorrow :) >> >> >> >> On 2013-09-02, at 21:24, Gisela Decuzzi >> wrote: >> >>> Great! The idea is to spend the full day? Or do you have any planed >> time? >> >>> >> >>> >> >>> 2013/9/2 Camillo Bruni >> >>> >> I spend a month in Buenos Aires working together with Guido Chari @ >> the >> UBA, >> we take this opportunity to organize a Pharo sprint outside France ;) >> >> We are in early preparation phase and the date nor location isn't >> fixed >> yet, >> so if you are motivated to join, can mark possible dates on this >> doodle: >> >> http://doodle.com/qey7iieqm5yr4wwy >> >> cheers, >> camillo >> >> >> >> >> >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> >> >
Re: [Pharo-dev] [update 3.0] #30338
There are some problems in NativeBoost if a method does not belong to the class itself, i don't understand the problem very well but that is what Igor and Stef told me. 2013/8/21 Camillo Bruni > On 2013-08-21, at 09:36, Marcus Denker wrote: > > 30338 > > - > > > > 11428 Remove a buggy redundant test in FuelTests > > https://pharo.fogbugz.com/f/cases/11428 > > > > 11417 Test for checking repeated code in superclasses must not watch in > nativeBoost classes > > https://pharo.fogbugz.com/f/cases/11417 > > why do we exclude NativeBoost from this sanity check? >
Re: [Pharo-dev] [update 3.0] #30337
was there any problem with this version? i don't see it in the server. 2013/8/19 Marcus Denker > 30337 > - > > 11394 Needed support for traits in ClassFactoryForTestCase > https://pharo.fogbugz.com/f/cases/11394 > > > Diff information: > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/SUnit-Tests-MarcusDenker.23.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/SUnit-Core-MarcusDenker.92.diff > >
Re: [Pharo-dev] [update 3.0] #30334
I think 11417 was not well integrated, the changes are not in the latest image. 2013/8/13 Stéphane Ducasse > [update 3.0] #30334 > 30334 > - > > - issue 11418 RBBrowserEnvironment definesClass: is unfinished > https://pharo.fogbugz.com/default.asp?11418 > > - issue 11417 Test for checking repeated code in superclasses must not > watch in nativeBoost classes > https://pharo.fogbugz.com/default.asp?11417 > > - issue 11415 More green tests for BehaviorTest and MetaclassTest > https://pharo.fogbugz.com/default.asp?11415 > Diff information: > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tests-StephaneDucasse.609.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Environment-StephaneDucasse.23.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Critics-StephaneDucasse.52.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/NativeBoost-Tests-StephaneDucasse.64.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/KernelTests-StephaneDucasse.546.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/HudsonBuildTools20-StephaneDucasse.41.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Generated-code-non-existing-package-StephaneDucasse.1.diff > > >
Re: [Pharo-dev] Uniformizing Pharo
I can add a rule for that, and check in the releaseTest if all the classes
are respecting it (as i did checking repeated code)
2013/8/12 Stéphane Ducasse
> Hi guys
>
> I started to be fed up about protocol inconsistencies. So I will propose a
> set of rules (and a tool - I'm working on it) to automatically categorize
> methods.
> The first on the list was printOn: in printing and I clean many methods
> already with a kind of happy smile on my face.
>
> Now we discussed today with esteban for initialize* we will use
> 'initialization'
> I hope that this is ok for you because I'm fed up to have the following:
>
> {269->'initialization'. 248->'initialize-release'. 48->'as yet
> unclassified'. 15->'accessing'. 14->'private'. 12->'initializing'.
> 2->'instance creation'. 2->'testing'. 2->'initalize-release'.
> 2->'protocol'. 2->'display'. 1->'cleaning'. 1->'intializing'. 1->'like
> fullCopy'. 1->'keymapping'. 1->'ui-building'. 1->'initialize - release'.
> 1->'initialization-release'. 1->'intialize'. 1->'styling'. 1->'scrolling'.
> 1->'morphic ui'. 1->'world state'. 1->#'parts bin'}
>
> Please enjoy this gift from life, I love so much 'like fullCopy' as a
> category for initialize that I'm a bit sad to
> clean this kind of poem (minimal haiku) so we will keep it for us :)
>
> Yes there is no little steps to get a bright system, every little clean is
> stop.
>
> No broken window! No dirt on the floor in Pharo.
>
> Stef
>
Re: [Pharo-dev] [update 3.0] #30326
At least the issue 11315 it was integrated :) 2013/8/7 Stéphane Ducasse > 30326 > - > > It probably works….but since the jenkins user interface is so bad I guess > that everything went well. May be we should have several PhD in CS > to understand Jenkins UI. I just have one PhD so I'm probably not > qualified enough. > > > - issue 11310 Browser newOnClass: is broken > https://pharo.fogbugz.com/default.asp?11310 > > - issue 11304 squeaksource3 should point to > http://ss3.gemtalksystems.com/ss/ > https://pharo.fogbugz.com/default.asp?11304 > > - issue 11315 Bad merged methods in version 30323 > https://pharo.fogbugz.com/default.asp?11315 > > - issue 11291 Announcer for Morphs should be Weak > https://pharo.fogbugz.com/default.asp?11291 > > Diff information: > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/ToolsTest-StephaneDucasse.denker.55.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-StephaneDucasse.1205.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-StephaneDucasse.223.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tools-StephaneDucasse.126.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-StephaneDucasse.55.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-StephaneDucasse.108.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Builder-StephaneDucasse.34.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-StephaneDucasse.880.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-StephaneDucasse.508.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-StephaneDucasse.66.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-StephaneDucasse.849.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-CriticBrowser-StephaneDucasse.103.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/KeyChain-StephaneDucasse.49.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Gofer-Core-StephaneDucasse.200.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Sequenceable-StephaneDucasse.151.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Announcements-Core-StephaneDucasse.44.diff > > >
Re: [Pharo-dev] [update 3.0] #30324
Hi Guille, It is a merging problem, this issue was made using changesets, and it seems that someone modified the method after the changesets were created. Doing the integration now, the method went back to its original code. I'll take a look at the changes for possible bugs. 2013/8/6 Guillermo Polito > I don't understand all those > > UsersManager>>initialize > + "Initialization code for UsersManager" > isn't that pretty obvious that the initialize method contains the > initialization code? :POr are they autogenerated or something? > sorry for the silly question :) > Guille > > > On Tue, Aug 6, 2013 at 2:46 PM, Esteban Lorenzano wrote: > >> 30324 >> - >> >> 11200 Repeated methods in superclasses, explicit requirement no >> implemented, repeated methods in traits >> https://pharo.fogbugz.com/f/cases/11200 >> >> (pass 2... fiuuu :P) >> >> Diff information: >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Traits-EstebanLorenzano.554.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/ToolsTest-EstebanLorenzano.denker.53.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-EstebanLorenzano.1203.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Text-Edition-EstebanLorenzano.4.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tests-EstebanLorenzano.604.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-EstebanLorenzano.221.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tools-EstebanLorenzano.124.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/SmartSuggestions-EstebanLorenzano.102.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Slot-EstebanLorenzano.368.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Shout-EstebanLorenzano.192.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/SUnit-UITesting-EstebanLorenzano.12.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/SUnit-Core-EstebanLorenzano.87.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Ring-Core-Kernel-EstebanLorenzano.130.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Regex-Core-EstebanLorenzano.24.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Tests-Critics-EstebanLorenzano.14.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Tests-Core-EstebanLorenzano.71.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Critics-EstebanLorenzano.50.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/RPackage-SystemIntegration-EstebanLorenzano.168.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-EstebanLorenzano.878.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Tools-Diff-EstebanLorenzano.98.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-TaskbarIcons-EstebanLorenzano.24.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/PackageInfo-EstebanLorenzano.105.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-EstebanLorenzano.504.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/NativeBoost-Win32-EstebanLorenzano.37.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/NativeBoost-Mac-EstebanLorenzano.10.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/NativeBoost-Core-EstebanLorenzano.133.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/NOCompletion-EstebanLorenzano.38.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Examples-EstebanLorenzano.6.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-EstebanLorenzano.64.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-EstebanLorenzano.847.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Metacello-MC-EstebanLorenzano.670.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Metacello-Core-EstebanLorenzano.500.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-CriticBrowser-EstebanLorenzano.101.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-Core-EstebanLorenzano.149.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/KeyChain-EstebanLorenzano.47.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/KernelTests-EstebanLorenzano.540.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-EstebanLorenzano.1550.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/GroupManager-EstebanLorenzano.47.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Graphics-Primitives-EstebanLorenzano.106.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Gofer-Core-EstebanLorenzano.198.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Core-EstebanLorenzano.106.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compiler-EstebanLorenzano.510.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/CollectionsTests-EstebanLorenzano.619.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Unordered-EstebanLorenzano.162.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/mai
Re: [Pharo-dev] Did canUnderstand: changed?
It's a bug i introduced in one of my changes, i am fixing it. 2013/8/4 Stéphane Ducasse > Hi > > why canUnderstand: now handles shouldNotImplement? > > Stef > >
Re: [Pharo-dev] [update 3.0] #30322
I think there is a problem in Monticello with this version 2013/8/1 Marcus Denker > 30322 > - > > 11282 Removal DependentFields references > https://pharo.fogbugz.com/f/cases/11282 > > Diff information: > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-MarcusDenker.878.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1550.diff > >
Re: [Pharo-dev] [update 3.0] #30304
I have commited a rule (and a test) that checks for duplicated code in a hierarchy, it could be useful. 2013/7/26 Marcus Denker > > On Jul 26, 2013, at 2:57 PM, Nicolas Cellier < > nicolas.cellier.aka.n...@gmail.com> wrote: > > +1 for the spirit of this change, such inheritance was a nest of potential > bugs > I'll try to review the diffs when I can... > > > There is still now lots of duplicated methods in the hierarchy… we need to > remove them > in a final step. > > > 2013/7/26 Marcus Denker > >> 30304 >> - >> >> 11234 LargeNegativeInteger inherits from LargePositiveInteger (part 2) >> https://pharo.fogbugz.com/f/cases/11234 >> >> >> Diff information: >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1539.diff >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Fuel-MarcusDenker.772.diff >> >> >> > >
Re: [Pharo-dev] About abuse of inheritance
2013/7/19 Igor Stasenko > I just stumbled upon this: > > Announcer subclass: #TxEditor > > > This is just plain wrong, as wrong as: > > Shampoo subclass: #Shower > > because every time you treat inheritance as something else as > _specialization_ you doing it wrong. > Inheritance is not about importing needed functionality, it should be > about specialization and only about it: > Completely agree! If you inherit only because of reuse functionality, use traits instead :-) - a superclass provides generic functionality, while subclasses > providing more and more specialized forms of it. > > Because if we don't follow that, then it is really hard to see and > follow a structure in design.. it is just random. > > And here's why: > > so since shower uses shampoo, as we concluded, then why not including > it via inheritance: > > Shampoo subclass: #Shower > > but then, Shower also uses Soap, so maybe it should be like that: > > Soap subclass: #Shower > > so, which superclass you prefer most? And how do you pick/prioritize > which element should be a superclass of Shower? > > To solve this dilemma, i think we will need multiple inheritance: > > (Shampoo, Soap) subclass: #Shower > > but thankfully, we don't have it in classic smalltalk model :) > > So, then maybe it should be something like that: > > Object subclass: #Shower > instanceVariableNames: 'soap shampoo' > ... > > Anyways, despite the obvious abuses, i'd like to ask community, in > what cases , you think (ab)using inheritance in a way > like above is justified? > Because maybe it is i, who doing it wrong? > > > -- > Best regards, > Igor Stasenko. > >
Re: [Pharo-dev] [update 3.0] #30282
:-) 2013/7/18 Damien Cassou > On Thu, Jul 18, 2013 at 4:19 PM, Esteban Lorenzano > wrote: > > 10889 ExplicitRequirement methods bug > > https://pharo.fogbugz.com/f/cases/10889/ > > > this bug has been present for many years. I'm very happy Sebastian > worked on it. Thank you Sebastian. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >
Re: [Pharo-dev] [regression reporter]regression occurred
fixing them... 2013/7/18 > > https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/354/ > > 2 regressions found. > Tests.Traits.TraitFileOutTest.testFileOutTrait > Tests.Traits.TraitTest.testPrinting > >
Re: [Pharo-dev] [update 3.0] #30267
Or moving those instance variables to their subclasses (Class and Metaclass) 2013/7/15 Camille Teruel > > On 13 juil. 2013, at 14:44, Camillo Bruni wrote: > > > If you put all methods from ClassDescriptions in traits and move them on > > Class and Metaclass there is no need for ClassDescription. > > Except for "instanceVariables" and "organization" ivs of ClassDescription. > Were you thinking about stateful traits? > > > If previously you want something that inherited from ClassDescription you > > can simply include the traits now. > > > > In the case of a Behavior subclass nothing changes. > > > > > On 2013-07-13, at 14:38, Stéphane Ducasse > wrote: > >> Why can't we keep ClassDescription. > >> Then in addition Behavior is a nice class to have to build strange > stuff. > >> > >> Stef > >> > >> On Jul 12, 2013, at 7:22 AM, Damien Cassou > wrote: > >> > >>> On Thu, Jul 11, 2013 at 6:36 PM, Esteban Lorenzano < > esteba...@gmail.com> wrote: > 11151 More changes needed to trait/classes polymorphism > https://pharo.fogbugz.com/f/cases/11151/ > >>> > >>> > >>> That's huge. Soon, we will be able to remove thr ClassDescription and > >>> Behavior classes. It makes sense because they are useless in the > >>> presence of traits. But do people want it? > >>> > >>> -- > >>> Damien Cassou > >>> http://damiencassou.seasidehosting.st > >>> > >>> "Success is the ability to go from one failure to another without > >>> losing enthusiasm." > >>> Winston Churchill > >>> > >> > >> > > > > > > >
Re: [Pharo-dev] [update 3.0] #30267
After all my changes you will only love them :) 2013/7/13 Stéphane Ducasse > I imagine that quite well :) but my love/hate relationship with trait > always bugs me :) > > > On Jul 13, 2013, at 2:44 PM, Camillo Bruni wrote: > > > If you put all methods from ClassDescriptions in traits and move them on > > Class and Metaclass there is no need for ClassDescription. > > > > If previously you want something that inherited from ClassDescription you > > can simply include the traits now. > > > > In the case of a Behavior subclass nothing changes. > > > > On 2013-07-13, at 14:38, Stéphane Ducasse > wrote: > >> Why can't we keep ClassDescription. > >> Then in addition Behavior is a nice class to have to build strange > stuff. > >> > >> Stef > >> > >> On Jul 12, 2013, at 7:22 AM, Damien Cassou > wrote: > >> > >>> On Thu, Jul 11, 2013 at 6:36 PM, Esteban Lorenzano < > esteba...@gmail.com> wrote: > 11151 More changes needed to trait/classes polymorphism > https://pharo.fogbugz.com/f/cases/11151/ > >>> > >>> > >>> That's huge. Soon, we will be able to remove thr ClassDescription and > >>> Behavior classes. It makes sense because they are useless in the > >>> presence of traits. But do people want it? > >>> > >>> -- > >>> Damien Cassou > >>> http://damiencassou.seasidehosting.st > >>> > >>> "Success is the ability to go from one failure to another without > >>> losing enthusiasm." > >>> Winston Churchill > >>> > >> > >> > > > > > > >
Re: [Pharo-dev] [update 3.0] #30267
I am writing a blog of the changes i have been doing, this particular change is not still there but it will be soon (today or on monday) :) 2013/7/12 Norbert Hartl > > Am 12.07.2013 um 07:22 schrieb Damien Cassou : > > > On Thu, Jul 11, 2013 at 6:36 PM, Esteban Lorenzano > wrote: > >> 11151 More changes needed to trait/classes polymorphism > >>https://pharo.fogbugz.com/f/cases/11151/ > > > > > > That's huge. Soon, we will be able to remove thr ClassDescription and > > Behavior classes. It makes sense because they are useless in the > > presence of traits. But do people want it? > > > Uff, I don't know if I want it because I hear it the first time and it > sounds shocking at first. Can you elaborate on this or give some pointers > for documents? > > thanks, > > Norbert > > >
Re: [Pharo-dev] [update 3.0] #30267
Exactly!! 2013/7/12 Damien Cassou > On Thu, Jul 11, 2013 at 6:36 PM, Esteban Lorenzano > wrote: > > 11151 More changes needed to trait/classes polymorphism > > https://pharo.fogbugz.com/f/cases/11151/ > > > That's huge. Soon, we will be able to remove thr ClassDescription and > Behavior classes. It makes sense because they are useless in the > presence of traits. But do people want it? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >
Re: [Pharo-dev] [Update 3.0] 30265
Excellent!! 2013/7/11 Esteban Lorenzano > 11151 More changes needed to trait/classes polymorphism > https://pharo.fogbugz.com/f/cases/11151/ > > (pass 2) > >
Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Launcher
Great, for me, that i am touching kernel classes, it will be very useful have something to manage images quickly!! 2013/7/8 Tudor Girba > Hi Damien, > > Nice :). > > I noticed two issues when playing with it: > - there is no feedback while downloading the image. This can be confusing. > - the launcher quits when launching another image (I am on Mac). This is > actually interesting, but it was surprising. I am not sure what is the > right solution here. > > And a question: How can we get more images available through this > interface? > > Cheers, > Doru > > > On Jul 8, 2013, at 10:11 AM, Damien Cassou > wrote: > > > Dear list, > > > > Erwan and I are proud to announce the first release of the Pharo > > Launcher, a cross-platform application that > > > > - lets you manage your Pharo images (launch, rename, copy and delete); > > - lets you download image templates (i.e., zip archives) from many > > different sources (Jenkins, files.pharo.org, and your local cache); > > - lets you create new images from any template. > > > > A screenshot is attached to this email. > > > > The idea behind the Pharo Launcher is that you should be able to > > access it very rapidly from your OS application launcher. As a result, > > launching any image is never more than 3 clicks away. > > > > Download: > https://ci.inria.fr/pharo-contribution/job/PharoLauncher/PHARO=30,VERSION=bleedingEdge,VM=vm/lastSuccessfulBuild/artifact/PharoLauncher.zip > > > > Please report bugs on the 'Launcher' project at > https://pharo.fogbugz.org > > > > You can contribute to this project. All classes and most methods are > > commented. There are unit tests. Please contribute! > > > > Source code: http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher > > CI: https://ci.inria.fr/pharo-contribution/job/PharoLauncher > > > > Things you can do to improve the system: > > > > - check if a template is already downloaded before downloading it > > - add a preference mechanism (for, e.g., quit after launch, definition > > of your own template groups, location of downloaded templates and > > images) > > - put the launcher in the Pharo Ubuntu package so that the launcher > > becomes a registered appliation of the system > > (https://launchpad.net/~pharo/+archive/stable) > > - make sure the pharo launcher does not load your personal scripts > > (like fonts and MC configuration) > > - add a toolbar to enhance the discoverability of the features > > (currently everything is in contextual menus) > > - make sure rename and copy actions propose default values > > - make sure no debugger pops up when a user press cancels or enter an > > invalid name > > - propose multiple kinds of sorting (last used, most frequently used, > > alphabetically on the name) > > - give some information about each template (build date, pharo version) > > > > -- > > Damien Cassou > > http://damiencassou.seasidehosting.st > > > > "Success is the ability to go from one failure to another without > > losing enthusiasm." > > Winston Churchill > > > > -- > www.tudorgirba.com > > "To utilize feedback, you first have to acquire it." > > >
Re: [Pharo-dev] We did it! SlotClassBuilder is active
Congrats!! This opens more doors to me since i we can have stateful traits now :) 2013/7/4 Damien Cassou > On Thu, Jul 4, 2013 at 11:17 AM, Martin Dias wrote: > > +1 for the blog post. I don't have too much to say of the plans for > > the future but I could write about the current state of the project. > > > yes please, current state description is already great. You may want > to write it in Pier format so that we get a nice chapter. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >
Re: [Pharo-dev] [update 3.0] #30215
Thanks :-) There are still some details to fix before continue with Trait and RGClass but quite easy 2013/6/23 Camillo Bruni > > On 2013-06-23, at 12:29, Damien Cassou wrote: > > > On Fri, Jun 21, 2013 at 6:16 PM, Esteban Lorenzano > wrote: > >> (pass 6, last?) > > > > > > looks like it was the last one. I would like to congratulate and thank > > Sebastian and you. This change was not easy at all and the results are > > important. For example, now, the RGClass class, the Trait class and > > the Class class will be truly polymorphic. > > > good job guys! this one was bugging me for a while, but I never had the > courage > to deal with it ;) >
Re: [Pharo-dev] [update 3.0] #30210
:-) Let's cross fingers to not break anything :P 2013/6/21 Camillo Bruni > very nice! :) > > thanks sebastion and Co! :) > > > On 2013-06-21, at 15:57, Esteban Lorenzano wrote: > > 30210 > > - > > > > 10976 kernel methods refactor > > https://pharo.fogbugz.com/f/cases/10976/kernel-methods-refactor > > > > (just part 1 of I don't know how many) > > > > Diff information: > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Traits-EstebanLorenzano.511.diff > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Ring-Core-Kernel-EstebanLorenzano.102.diff > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/RPackage-Core-EstebanLorenzano.226.diff > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-EstebanLorenzano.1486.diff > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusCommon-EstebanLorenzano.143.diff > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/FuelTests-EstebanLorenzano.320.diff > > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compiler-EstebanLorenzano.484.diff > > > > > > >
Re: [Pharo-dev] Modification on CollectionsExtensions
Great! Thank you! 2013/6/21 Tudor Girba > Thanks again. > > I committed the change you proposed. So, now we have flatCollect: using > writeStream. > > Cheers, > Doru > > > On Tue, Jun 11, 2013 at 3:18 PM, Sebastian Tleye wrote: > >> Hello, >> >> Fixing some bugs in Traits we realized that it would be good idea to use >> CollectionsExtensions package (it has some useful functions), also it would >> be great to include CollectionsExtensions in Pharo 3.0. >> >> One "problem" we found is that CollectionsExtensions is depending on a >> Nile Package (that's not a desired feature). >> In the method Collection>>flatCollect: there is a line refering to a nile >> function "nsWriteStream". >> >> If i change "nsWriteStream" for "writeStream" the dependency disapears. >> >> I also run all the tests and they are working, so i was wondering if it >> would be possible to commit the change. >> >> Thanks. >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >
Re: [Pharo-dev] Also "create method" in traits
:-) 2013/6/19 Damien Cassou > On Tue, Jun 18, 2013 at 3:48 PM, Sebastian Tleye wrote: > > Done :) > > You can download the fix and not suffer anymore :P > > > thank you Sebastian. It's very cool to see you in this mailing list. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >
Re: [Pharo-dev] Also "create method" in traits
Done :) You can download the fix and not suffer anymore :P 2013/6/18 Camillo Bruni > yes please :) > > https://pharo.fogbugz.com/default.asp?10951 > > On 2013-06-18, at 14:59, Camille Teruel wrote: > > On 18 juin 2013, at 14:56, Martin Dias wrote: > > > >> Hi > >> > >> I informally reported this "feature requirement" today to Sebastian, > >> but I wanted to post it to all. > >> > >> When the debugger is shown after a MNU, the developer can press the > >> button "Create method". A list of the superclasses is shown to the > >> developer, so he/she can choose in which class crate the method. In > >> addition to superclasses, it would be nice to show the traits that the > >> classes use, since developer might want to create the method there. > >> > >> Cheers, > >> Martín > >> > > > > +1 > > >
Re: [Pharo-dev] Modification on CollectionsExtensions
sorry, gather will call flatCollect: is not the same code. 2013/6/12 Sebastian Tleye > ok, i understood, > > Discussing with Marcus we believe that it would be better to keep > Collecition>>gather: and add Collection>>flatCollect: (with the same > implementation) and put a comment in gather: saying that is kept for > compatibility purposes. > > flatCollect: will be included in Pharo and will be removed from > CollectionExtensions. > > > > > 2013/6/12 Frank Shearar > >> On 12 June 2013 10:54, Frank Shearar wrote: >> > #gather: directly applies the stream fusion technique as its >> > implementation, so is faster than the current implementation of >> > #flatCollect: >> > >> > Stef's saying "why not move #gather:'s implemenation to #flatCollect:, >> > and make the old #gather: call the new #flatCollect:" >> >> Er, and that would mean moving #flatCollect: out of >> CollectionsExtensions into the base image. >> >> > frank >> > >> > On 12 June 2013 10:33, Sebastian Tleye wrote: >> >> As far as i know the implementation of gather: is faster than the >> >> implementation of flatCollect: >> >> >> >> >> >> 2013/6/12 Stéphane Ducasse >> >>> >> >>> Why not the inverse. >> >>> They are much more users of flatCollect: then gather: >> >>> >> >>> and again gather: sucks. It does not convey that this is a mapcan >> >>> ie happening the results of each iteration into the >> >>> >> >>> So flatCollect: is 10 times more explicit and better. >> >>> you flatten the results of the collect: >> >>> >> >>> Stef >> >>> >> >>> >> >>> I think the simplest solution is to keep both and that flatCollect >> >>> directly call gather: >> >>> >> >>> If you agree with that, I will correct the moose extension package >> >>> >> >>> >> >>> 2013/6/11 Stéphane Ducasse >> >>>> >> >>>> gather: sucks as a name. >> >>>> flatCollect: is much better so do not remove it. >> >>>> >> >>>> On Jun 11, 2013, at 4:53 PM, Sebastian Tleye >> wrote: >> >>>> >> >>>> If they are not different so a better way would be replace >> >>>> #flatenCollect: by #gather: >> >>>> but anyway, moose people should decide and commit the change since i >> am >> >>>> not a moose developer. >> >>>> >> >>>> >> >>>> 2013/6/11 Marcus Denker >> >>>>> >> >>>>> >> >>>>> On Jun 11, 2013, at 4:24 PM, Frank Shearar > > >> >>>>> wrote: >> >>>>> >> >>>>> > On 11 June 2013 14:18, Sebastian Tleye wrote: >> >>>>> >> Hello, >> >>>>> >> >> >>>>> >> Fixing some bugs in Traits we realized that it would be good >> idea to >> >>>>> >> use >> >>>>> >> CollectionsExtensions package (it has some useful functions), >> also it >> >>>>> >> would >> >>>>> >> be great to include CollectionsExtensions in Pharo 3.0. >> >>>>> > >> >>>>> > Is this the HPI library? I seem to recall TraitClasses [1] using >> it. >> >>>>> >> >>>>> CollectionExtension is from Moose. >> >>>>> >> >>>>> the Trait based Stream refactoring was done some years ago but has >> not >> >>>>> been used >> >>>>> or maintained. >> >>>>> >> >>>>> Marcus >> >>>> >> >>>> >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> Guillaume Larcheveque >> >>> >> >>> >> >> >> >> >
Re: [Pharo-dev] Modification on CollectionsExtensions
ok, i understood, Discussing with Marcus we believe that it would be better to keep Collecition>>gather: and add Collection>>flatCollect: (with the same implementation) and put a comment in gather: saying that is kept for compatibility purposes. flatCollect: will be included in Pharo and will be removed from CollectionExtensions. 2013/6/12 Frank Shearar > On 12 June 2013 10:54, Frank Shearar wrote: > > #gather: directly applies the stream fusion technique as its > > implementation, so is faster than the current implementation of > > #flatCollect: > > > > Stef's saying "why not move #gather:'s implemenation to #flatCollect:, > > and make the old #gather: call the new #flatCollect:" > > Er, and that would mean moving #flatCollect: out of > CollectionsExtensions into the base image. > > > frank > > > > On 12 June 2013 10:33, Sebastian Tleye wrote: > >> As far as i know the implementation of gather: is faster than the > >> implementation of flatCollect: > >> > >> > >> 2013/6/12 Stéphane Ducasse > >>> > >>> Why not the inverse. > >>> They are much more users of flatCollect: then gather: > >>> > >>> and again gather: sucks. It does not convey that this is a mapcan > >>> ie happening the results of each iteration into the > >>> > >>> So flatCollect: is 10 times more explicit and better. > >>> you flatten the results of the collect: > >>> > >>> Stef > >>> > >>> > >>> I think the simplest solution is to keep both and that flatCollect > >>> directly call gather: > >>> > >>> If you agree with that, I will correct the moose extension package > >>> > >>> > >>> 2013/6/11 Stéphane Ducasse > >>>> > >>>> gather: sucks as a name. > >>>> flatCollect: is much better so do not remove it. > >>>> > >>>> On Jun 11, 2013, at 4:53 PM, Sebastian Tleye > wrote: > >>>> > >>>> If they are not different so a better way would be replace > >>>> #flatenCollect: by #gather: > >>>> but anyway, moose people should decide and commit the change since i > am > >>>> not a moose developer. > >>>> > >>>> > >>>> 2013/6/11 Marcus Denker > >>>>> > >>>>> > >>>>> On Jun 11, 2013, at 4:24 PM, Frank Shearar > >>>>> wrote: > >>>>> > >>>>> > On 11 June 2013 14:18, Sebastian Tleye wrote: > >>>>> >> Hello, > >>>>> >> > >>>>> >> Fixing some bugs in Traits we realized that it would be good idea > to > >>>>> >> use > >>>>> >> CollectionsExtensions package (it has some useful functions), > also it > >>>>> >> would > >>>>> >> be great to include CollectionsExtensions in Pharo 3.0. > >>>>> > > >>>>> > Is this the HPI library? I seem to recall TraitClasses [1] using > it. > >>>>> > >>>>> CollectionExtension is from Moose. > >>>>> > >>>>> the Trait based Stream refactoring was done some years ago but has > not > >>>>> been used > >>>>> or maintained. > >>>>> > >>>>> Marcus > >>>> > >>>> > >>>> > >>> > >>> > >>> > >>> -- > >>> Guillaume Larcheveque > >>> > >>> > >> > >
Re: [Pharo-dev] Modification on CollectionsExtensions
As far as i know the implementation of gather: is faster than the implementation of flatCollect: 2013/6/12 Stéphane Ducasse > Why not the inverse. > They are much more users of flatCollect: then gather: > > and again gather: sucks. It does not convey that this is a mapcan > ie happening the results of each iteration into the > > So flatCollect: is 10 times more explicit and better. > you flatten the results of the collect: > > Stef > > > I think the simplest solution is to keep both and that flatCollect > directly call gather: > > If you agree with that, I will correct the moose extension package > > > 2013/6/11 Stéphane Ducasse > >> gather: sucks as a name. >> flatCollect: is much better so do not remove it. >> >> On Jun 11, 2013, at 4:53 PM, Sebastian Tleye wrote: >> >> If they are not different so a better way would be replace >> #flatenCollect: by #gather: >> but anyway, moose people should decide and commit the change since i am >> not a moose developer. >> >> >> 2013/6/11 Marcus Denker >> >>> >>> On Jun 11, 2013, at 4:24 PM, Frank Shearar >>> wrote: >>> >>> > On 11 June 2013 14:18, Sebastian Tleye wrote: >>> >> Hello, >>> >> >>> >> Fixing some bugs in Traits we realized that it would be good idea to >>> use >>> >> CollectionsExtensions package (it has some useful functions), also it >>> would >>> >> be great to include CollectionsExtensions in Pharo 3.0. >>> > >>> > Is this the HPI library? I seem to recall TraitClasses [1] using it. >>> >>> CollectionExtension is from Moose. >>> >>> the Trait based Stream refactoring was done some years ago but has not >>> been used >>> or maintained. >>> >>> Marcus >>> >> >> >> > > > -- > *Guillaume Larcheveque* > > >
Re: [Pharo-dev] Modification on CollectionsExtensions
+1 2013/6/12 Guillaume Larcheveque > I think the simplest solution is to keep both and that flatCollect > directly call gather: > > If you agree with that, I will correct the moose extension package > > > 2013/6/11 Stéphane Ducasse > >> gather: sucks as a name. >> flatCollect: is much better so do not remove it. >> >> On Jun 11, 2013, at 4:53 PM, Sebastian Tleye wrote: >> >> If they are not different so a better way would be replace >> #flatenCollect: by #gather: >> but anyway, moose people should decide and commit the change since i am >> not a moose developer. >> >> >> 2013/6/11 Marcus Denker >> >>> >>> On Jun 11, 2013, at 4:24 PM, Frank Shearar >>> wrote: >>> >>> > On 11 June 2013 14:18, Sebastian Tleye wrote: >>> >> Hello, >>> >> >>> >> Fixing some bugs in Traits we realized that it would be good idea to >>> use >>> >> CollectionsExtensions package (it has some useful functions), also it >>> would >>> >> be great to include CollectionsExtensions in Pharo 3.0. >>> > >>> > Is this the HPI library? I seem to recall TraitClasses [1] using it. >>> >>> CollectionExtension is from Moose. >>> >>> the Trait based Stream refactoring was done some years ago but has not >>> been used >>> or maintained. >>> >>> Marcus >>> >> >> >> > > > -- > *Guillaume Larcheveque* > >
Re: [Pharo-dev] Modification on CollectionsExtensions
If they are not different so a better way would be replace #flatenCollect: by #gather: but anyway, moose people should decide and commit the change since i am not a moose developer. 2013/6/11 Marcus Denker > > On Jun 11, 2013, at 4:24 PM, Frank Shearar > wrote: > > > On 11 June 2013 14:18, Sebastian Tleye wrote: > >> Hello, > >> > >> Fixing some bugs in Traits we realized that it would be good idea to use > >> CollectionsExtensions package (it has some useful functions), also it > would > >> be great to include CollectionsExtensions in Pharo 3.0. > > > > Is this the HPI library? I seem to recall TraitClasses [1] using it. > > CollectionExtension is from Moose. > > the Trait based Stream refactoring was done some years ago but has not > been used > or maintained. > > Marcus >
Re: [Pharo-dev] Modification on CollectionsExtensions
I don't know, i should see the implementation, i just want to remove the dependency between CollectionsExtensions and Nile and one way to do it is modifying #flatCollect: implementation. if they are the same #flatCollect: could be remove safely replaced. 2013/6/11 Camille Teruel > > On 11 juin 2013, at 15:18, Sebastian Tleye wrote: > > > Hello, > > > > Fixing some bugs in Traits we realized that it would be good idea to use > CollectionsExtensions package (it has some useful functions), also it would > be great to include CollectionsExtensions in Pharo 3.0. > > > > One "problem" we found is that CollectionsExtensions is depending on a > Nile Package (that's not a desired feature). > > In the method Collection>>flatCollect: there is a line refering to a > nile function "nsWriteStream". > > How this #flatCollect: is different from #gather: anyway? > > > > > If i change "nsWriteStream" for "writeStream" the dependency disapears. > > > > I also run all the tests and they are working, so i was wondering if it > would be possible to commit the change. > > > > Thanks. > > >
[Pharo-dev] Modification on CollectionsExtensions
Hello, Fixing some bugs in Traits we realized that it would be good idea to use CollectionsExtensions package (it has some useful functions), also it would be great to include CollectionsExtensions in Pharo 3.0. One "problem" we found is that CollectionsExtensions is depending on a Nile Package (that's not a desired feature). In the method Collection>>flatCollect: there is a line refering to a nile function "nsWriteStream". If i change "nsWriteStream" for "writeStream" the dependency disapears. I also run all the tests and they are working, so i was wondering if it would be possible to commit the change. Thanks.
Re: [Pharo-dev] Trait exclusions
Hi Frank,
Discussing with DamienC and Stef we agree it's a bug, we will fix it.
2013/6/4 Frank Shearar
> On 4 June 2013 10:19, Sebastian Tleye wrote:
> > Hi Frank, i am currently working improving the implementation of traits
> in
> > Pharo,
>
> Excellent!
>
> > 2013/5/31 Frank Shearar
> >>
> >> On 31 May 2013 12:32, Stéphane Ducasse
> wrote:
> >> >
> >> > On May 31, 2013, at 1:28 PM, Frank Shearar
> >> > wrote:
> >> >
> >> >> On 31 May 2013 12:01, Damien Cassou wrote:
> >> >>> Hi Frank,
> >> >>>
> >> >>> On Wed, May 29, 2013 at 11:45 PM, Frank Shearar
> >> >>> wrote:
> >> >>>> I have a Trait TGroup that requires #*, #identity and #inverse. I
> >> >>>> want
> >> >>>> to construct a TField by composing TGroup with itself. One TGroup
> >> >>>> will
> >> >>>> form the operations #*, #one, and #reciprocal while the other will
> >> >>>> form #+, #zero and #negated.
> >> >>>>
> >> >>>> I don't want #identity or #inverse, because these apply to one
> >> >>>> operation, and it makes TField's API ambiguous. That's what
> >> >>>> TraitExclusion is for.
> >> >>>
> >> >>> maybe a diagram would help
> >> >>
> >> >> In explaining the problem, or an an alternative to the crazy
> >> >> composition? I rather think that this - which doesn't work, and
> >> >> prompted the question in the first place - is rather readable... _and
> >> >> executable_:
> >> >>
> >> >>(TGroup @ {#* -> #+. #inverse -> #negated. #identity -> #zero} +
> >> >> TGroup @ {#inverse -> #reciprocal. #identity -> #zero}) - {#identity.
> >> >> #inverse}
> >> >>
> >> >> What I don't understand is
> >> >> (a) why exclusion only applies to the rightmost trait in the
> >> >> composition and
> >> >> (b) why aliases either break (in Pharo [1])
> >> >
> >> > do they?
> >>
> >> I'm not sure what "they" refers to. Assuming you meant "do aliases
> >> break in Pharo?" yes they do: the alias expects the new name to
> >> already exist in the method dictionary. So if you write your trait
> >>
> >> Trait named: #TMyTrait
> >> uses: TSomething @ {#aMethod -> #notWrittenYet}
> >> category: 'Thing'
> >>
> >> then you get a KeyNotFound because TMyTrait doesn't have
> >> #notWrittenYet in its method dictionary. It should be fairly easy to
> >> fix; I just raised the ticket.
> >
> >
> > Yes, i think this is a bug, i'll fix it.
>
> Thanks!
>
> >> If you meant "do exclusions only apply to the rightmost trait?", yes
> >> they do. The comment in both Pharo and Squeak say that - binds tighter
> >> than @ or +. That's fine. To me, that would mean that S + T @ {#m ->
> >> #z} - {#m} would remove #m from T. But I thought that (S + T @ {#m -
> >> #z}) - {#m} would mean "remove m from S + T @ {#m - #z}", but it
> >> doesn't. That might simply be a TraitComposition bug. I don't know,
> >> which is why I'm asking :)
> >
> >
> > It looks like a bug,
> >
> > a trait using
> > (S + T @ {#m->#z}) - {#m}
> >
> > is the same that a trait using
> > S + (T @ {#m->#z} - {#m})
> >
> > it seems it is not respecting parentheses...
>
> Yes, that's exactly it.
>
> frank
>
> >> >> or do nothing (in Squeak),
> >> >> where I'd expected to see implementations saying "self requirement".
> >> >
> >> > we removed self requirement because it was slow to compute in
> >> > interactive mode.
> >>
> >> Ah, ok. Fair enough!
> >>
> >> frank
> >>
> >> >> frank
> >> >>
> >> >> [1] https://pharo.fogbugz.com/default.asp?10803#78542
>
>
Re: [Pharo-dev] Trait exclusions
Hi Frank, i am currently working improving the implementation of traits in
Pharo,
2013/5/31 Frank Shearar
> On 31 May 2013 12:32, Stéphane Ducasse wrote:
> >
> > On May 31, 2013, at 1:28 PM, Frank Shearar
> wrote:
> >
> >> On 31 May 2013 12:01, Damien Cassou wrote:
> >>> Hi Frank,
> >>>
> >>> On Wed, May 29, 2013 at 11:45 PM, Frank Shearar <
> frank.shea...@gmail.com> wrote:
> I have a Trait TGroup that requires #*, #identity and #inverse. I want
> to construct a TField by composing TGroup with itself. One TGroup will
> form the operations #*, #one, and #reciprocal while the other will
> form #+, #zero and #negated.
>
> I don't want #identity or #inverse, because these apply to one
> operation, and it makes TField's API ambiguous. That's what
> TraitExclusion is for.
> >>>
> >>> maybe a diagram would help
> >>
> >> In explaining the problem, or an an alternative to the crazy
> >> composition? I rather think that this - which doesn't work, and
> >> prompted the question in the first place - is rather readable... _and
> >> executable_:
> >>
> >>(TGroup @ {#* -> #+. #inverse -> #negated. #identity -> #zero} +
> >> TGroup @ {#inverse -> #reciprocal. #identity -> #zero}) - {#identity.
> >> #inverse}
> >>
> >> What I don't understand is
> >> (a) why exclusion only applies to the rightmost trait in the
> composition and
> >> (b) why aliases either break (in Pharo [1])
> >
> > do they?
>
> I'm not sure what "they" refers to. Assuming you meant "do aliases
> break in Pharo?" yes they do: the alias expects the new name to
> already exist in the method dictionary. So if you write your trait
>
> Trait named: #TMyTrait
> uses: TSomething @ {#aMethod -> #notWrittenYet}
> category: 'Thing'
>
> then you get a KeyNotFound because TMyTrait doesn't have
> #notWrittenYet in its method dictionary. It should be fairly easy to
> fix; I just raised the ticket.
>
Yes, i think this is a bug, i'll fix it.
>
> If you meant "do exclusions only apply to the rightmost trait?", yes
> they do. The comment in both Pharo and Squeak say that - binds tighter
> than @ or +. That's fine. To me, that would mean that S + T @ {#m ->
> #z} - {#m} would remove #m from T. But I thought that (S + T @ {#m -
> #z}) - {#m} would mean "remove m from S + T @ {#m - #z}", but it
> doesn't. That might simply be a TraitComposition bug. I don't know,
> which is why I'm asking :)
It looks like a bug,
a trait using
(S + T @ {#m->#z}) - {#m}
is the same that a trait using
S + (T @ {#m->#z} - {#m})
it seems it is not respecting parentheses...
> >> or do nothing (in Squeak),
> >> where I'd expected to see implementations saying "self requirement".
> >
> > we removed self requirement because it was slow to compute in
> interactive mode.
>
> Ah, ok. Fair enough!
>
> frank
>
> >> frank
> >>
> >> [1] https://pharo.fogbugz.com/default.asp?10803#78542
>
>
Re: [Pharo-dev] Doubt about RING
Thanks Marcus! 2013/5/16 Marcus Denker > > On May 15, 2013, at 9:43 PM, Sebastian Tleye wrote: > > > Thanks Igor, i think you are right. > > I am not sure what "isObsolete" does, but for Ring classes, which are > created dinamically, it doesn't seem that "isObsolete" is useful. (at least > is my intuition) > > > > Obsolete classes happen if you delete a class, yet there are still > instances. This is needed as classes do not model history. > But > a) Ring classes are not directly instantiated (they are not > referenced from the header of the instances) > b) They even are able to model history very nicely > > So the obsolete concept makes no sense… an obsolete class might even have > a (Historical) Ring class associated with it > and Ring would have no problem at all. > > Marcus >
Re: [Pharo-dev] Doubt about RING
Thanks Igor, i think you are right. I am not sure what "isObsolete" does, but for Ring classes, which are created dinamically, it doesn't seem that "isObsolete" is useful. (at least is my intuition) 2013/5/15 Igor Stasenko > On 15 May 2013 11:29, Sebastian Tleye wrote: > > Hello > > > > I am making some modifications in the smalltalk meta-model and i need > > to replace classes with Ring classes (it is supposed to be possible since > > they are polymorphic) > > But i am having a little problem, all the classes know how to answer the > > message "isObsolete" > > but Ring classes doesn't, to solve this i have defined the method > > "isObsolete" in RGBehaviorDefinition > > but i am not sure which code does it need > > > > - if i copy and paste the code from Behavior, then i obtain more > > "doesNotUnderstand" messages > > since the code from Behavior>>isObsolete is "self instanceCount = 0" but > > Ring classes doesn't know how to answer "instanceCount" neither > > so i suspect this is not the right way to do it. > > > > - if i copy the code from Class, then it seems it works, but the result > from > > for example > > "Array isObsolete" is different of the result from "Array > asRingDefinition > > isObsolete" consequently > > well.. #isObsolete for model classes doesn't makes any sense. > i would just answer false to this message. > and i would ask why this message is ever sent. because this is not > something > essential to class model. > > > next messages obtain different results and finally a a > "doesNotUnderstand" > > message again. > > > > Am i doing something wrong? Any suggestion? > > > > -- > Best regards, > Igor Stasenko. > >
[Pharo-dev] Doubt about RING
Hello I am making some modifications in the smalltalk meta-model and i need to replace classes with Ring classes (it is supposed to be possible since they are polymorphic) But i am having a little problem, all the classes know how to answer the message "isObsolete" but Ring classes doesn't, to solve this i have defined the method "isObsolete" in RGBehaviorDefinition but i am not sure which code does it need - if i copy and paste the code from Behavior, then i obtain more "doesNotUnderstand" messages since the code from Behavior>>isObsolete is "self instanceCount = 0" but Ring classes doesn't know how to answer "instanceCount" neither so i suspect this is not the right way to do it. - if i copy the code from Class, then it seems it works, but the result from for example "Array isObsolete" is different of the result from "Array asRingDefinition isObsolete" consequently next messages obtain different results and finally a a "doesNotUnderstand" message again. Am i doing something wrong? Any suggestion?
[Pharo-dev] Doubt about RING
Hello I am making some modifications in the smalltalk meta-model and i need to replace classes with Ring classes (it is supposed to be possible since they are polymorphic) But i am having a little problem, all the classes know how to answer the message "isObsolete" but Ring classes doesn't, to solve this i have defined the method "isObsolete" in RGBehaviorDefinition but i am not sure which code does it need - if i copy and paste the code from Behavior, then i obtain more "doesNotUnderstand" messages since the code from Behavior>>isObsolete is "self instanceCount = 0" but Ring classes doesn't know how to answer "instanceCount" neither so i suspect this is not the right way to do it. - if i copy the code from Class, then it seems it works, but the result from for example "Array isObsolete" is different of the result from "Array asRingDefinition isObsolete" consequently next messages obtain different results and finally a a "doesNotUnderstand" message again. Am i doing something wrong? Any suggestion?
