October 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] How to try Bloc?

by Dimitris Chloupis

No idea how you managed to install it, it gives me a missing ' error same setup, macos sierra, pharo 6 latest ConfigurationOfBloc (Pharo/Bloc repo) loadDevelopment On Wed, Oct 26, 2016 at 11:42 AM Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi > > I tried image from CI (both stable and dev) and I tried version by loading > config in latest Pharo 6. > Both are not working for me. I run basicExamples: > > - ci version said that this is some nil object inside > > - config version just crashed. > > > Do you have instructions how to run it? > > I tried it on Sierra Mac. > > Best regards, > Denis >

Oct. 26, 2016

[Bloc] Hierarchy of BiEvent

by Denis Kudriashov

Hi. I look at dev version of Bloc and have questions about events. There is duplicated hierarchy of OSEvent and BlEvent. For example for OSKeyDownEvent and OSMouseButtonPressEvent there are same events from Block: BlKeyDownEvent and BlMouseDownEvent. Bloc of course add many new events like BlDragEvent and BlDblClickEvent. But why we not manage all events equally? why we need this distinction? Also I was so much surprized about keyboard modifiers. In OS there is OSStateModifiers with smart boolean states like leftShiftPressed, leftAltPressed which are decoded from integer bits of raw SDL event. And in Bloc it is BlKeyModifiers which are created from OSStateModifier. And here is most amazing thing: BlKeyModifiers encode smart boolean flags about keys back into integer bits. So we have: SDL event int => OSStateModifiers booleans => BlKeyModifiers int Why it is done like this? And currently BlKeyModifiers lost many states from OSStateModifiers.

Oct. 26, 2016

Re: [Pharo-dev] roundTo: strange behavior

by ClÃ©ment Bera

I think the right way to solve these issues is not to think about it like a Math problem. We need to write tests showing bugs and doing lots of coverage. Then, we can look into other programming languages (Java, Ruby, Python, etc), port an implementation and ensure it's correct. This is the kind of things where people have spent days to get right and efficient. The goal is not to figure how to do it better but how to port the best implementation out there. On Wed, Oct 26, 2016 at 9:58 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > 2016-10-26 9:14 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> Hi nicolas >> >> So what is the solution? We can integrate fast a solution. >> I would really like to see them fix in Pharo 60. >> I'm writing a book for newbie and this is the third time I change one >> chapter >> so may be I should stop and throw away this chapter. >> >> > 1) for Fraction: > > round: numberOfWishedDecimal > v := 10 raisedTo: numberOfWishedDecimal. > ^ ((self * v) rounded / v) asFloat > > or just replace asFloat if you wish to remain exact: > > round: numberOfWishedDecimal > v := 10 raisedTo: numberOfWishedDecimal. > ^ ((self * v) rounded / v) asScaledDecimal: numberOfWishedDecimal > > 2) for Float, it is in 15471: > > round: numberOfWishedDecimal > | v maxNumberOfDecimals | > maxNumberOfDecimals := self class precision - 1 - (self exponent max: > self class emin). > maxNumberOfDecimals < numberOfWishedDecimal ifTrue: [^self]. > v := 10 raisedTo: numberOfWishedDecimal. > ^ ((self asFraction * v) rounded / v) asFloat > > or if Fraction already answers a Float: > > round: numberOfWishedDecimal > | maxNumberOfDecimals | > maxNumberOfDecimals := self class precision - 1 - (self exponent max: > self class emin). > maxNumberOfDecimals < numberOfWishedDecimal ifTrue: [^self]. > ^ self asFraction round: numberOfWishedDecimal > > It's slower than current implementation, but will round exactly to the > nearest Float. > It's possible to have faster implementation up to 22 decimals if you > provide a fused-multiply-accumulate primitive... > > > You see I'm not good in math so even if I try hard I will not have a good >> solution. >> This is the same for marcus and most people in our team. >> I reopened these issues. >> >> Stef >> >> >> >> 2016-10-25 23:22 GMT+02:00 stepharo <stepharo(a)free.fr>: >> >>> Ok for the advice >>> >>> Now round: aNumberOfDigits seems to work fine. >>> >>> Stef >>> >>> >> No it's not, but issues are timing out too fast ;) >> https://pharo.fogbugz.com/f/cases/15471/Can-t-round-Float-fm >> ax-to-2-decimal-places >> https://pharo.fogbugz.com/f/cases/15472/Fraction-rounding-to >> -n-decimal-places-is-inexact >> https://pharo.fogbugz.com/f/cases/15473/Float-round-to-n-dec >> imal-places-is-not-in-agreement-with-printShowingDecimalPlaces >> >> I hate to say that, but try in python, they got it right... >> >> >> >>> Le 25/10/16 Ã 11:05, Henrik Johansen a Ã©crit : >>> >>> +1. >>> >>> Unless you're dealing with fixed precision* entities, it's usually >>> better to specify digits to display in printing methods themselves >>> (#printShowingDecimalPlaces: & friends in base image). >>> As per previous discussions around this that arise every second year or >>> so, rounding the number itself (as long as we're dealing with floats) will >>> never work as you want reliably. >>> >>> Cheers, >>> Henry >>> >>> * And in that case, you'd use ScaledDecimals >>> >>> On 23 Oct 2016, at 7:08 , phil(a)highoctane.be wrote: >>> >>> I use the Printf package for that. >>> >>> v := 65.456. >>> 'With 2 decimal digits: %5.2f, or 3 like this: %6.3f' >>> printf: {v. v}. >>> >>> With 2 decimal digits: 65.45, or 3 like this: 65.456 >>> >>> It is in http://www.smalltalkhub.com/#!/~philippeback/HOExtras >>> >>> Printf >>> >>> I am just used to C printf and well, I like the way it works. >>> >>> Phil >>> >>> >>> >> >> >

Oct. 26, 2016

How to try Bloc?

by Denis Kudriashov

Hi I tried image from CI (both stable and dev) and I tried version by loading config in latest Pharo 6. Both are not working for me. I run basicExamples: - ci version said that this is some nil object inside - config version just crashed. Do you have instructions how to run it? I tried it on Sierra Mac. Best regards, Denis

Oct. 26, 2016

Re: [Pharo-dev] roundTo: strange behavior

by Nicolas Cellier

2016-10-26 9:14 GMT+02:00 stepharo <stepharo(a)free.fr>: > Hi nicolas > > So what is the solution? We can integrate fast a solution. > I would really like to see them fix in Pharo 60. > I'm writing a book for newbie and this is the third time I change one > chapter > so may be I should stop and throw away this chapter. > > 1) for Fraction: round: numberOfWishedDecimal v := 10 raisedTo: numberOfWishedDecimal. ^ ((self * v) rounded / v) asFloat or just replace asFloat if you wish to remain exact: round: numberOfWishedDecimal v := 10 raisedTo: numberOfWishedDecimal. ^ ((self * v) rounded / v) asScaledDecimal: numberOfWishedDecimal 2) for Float, it is in 15471: round: numberOfWishedDecimal | v maxNumberOfDecimals | maxNumberOfDecimals := self class precision - 1 - (self exponent max: self class emin). maxNumberOfDecimals < numberOfWishedDecimal ifTrue: [^self]. v := 10 raisedTo: numberOfWishedDecimal. ^ ((self asFraction * v) rounded / v) asFloat or if Fraction already answers a Float: round: numberOfWishedDecimal | maxNumberOfDecimals | maxNumberOfDecimals := self class precision - 1 - (self exponent max: self class emin). maxNumberOfDecimals < numberOfWishedDecimal ifTrue: [^self]. ^ self asFraction round: numberOfWishedDecimal It's slower than current implementation, but will round exactly to the nearest Float. It's possible to have faster implementation up to 22 decimals if you provide a fused-multiply-accumulate primitive... You see I'm not good in math so even if I try hard I will not have a good > solution. > This is the same for marcus and most people in our team. > I reopened these issues. > > Stef > > > > 2016-10-25 23:22 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> Ok for the advice >> >> Now round: aNumberOfDigits seems to work fine. >> >> Stef >> >> > No it's not, but issues are timing out too fast ;) > https://pharo.fogbugz.com/f/cases/15471/Can-t-round-Float- > fmax-to-2-decimal-places > https://pharo.fogbugz.com/f/cases/15472/Fraction-rounding- > to-n-decimal-places-is-inexact > https://pharo.fogbugz.com/f/cases/15473/Float-round-to-n- > decimal-places-is-not-in-agreement-with-printShowingDecimalPlaces > > I hate to say that, but try in python, they got it right... > > > >> Le 25/10/16 Ã 11:05, Henrik Johansen a Ã©crit : >> >> +1. >> >> Unless you're dealing with fixed precision* entities, it's usually better >> to specify digits to display in printing methods themselves >> (#printShowingDecimalPlaces: & friends in base image). >> As per previous discussions around this that arise every second year or >> so, rounding the number itself (as long as we're dealing with floats) will >> never work as you want reliably. >> >> Cheers, >> Henry >> >> * And in that case, you'd use ScaledDecimals >> >> On 23 Oct 2016, at 7:08 , phil(a)highoctane.be wrote: >> >> I use the Printf package for that. >> >> v := 65.456. >> 'With 2 decimal digits: %5.2f, or 3 like this: %6.3f' >> printf: {v. v}. >> >> With 2 decimal digits: 65.45, or 3 like this: 65.456 >> >> It is in http://www.smalltalkhub.com/#!/~philippeback/HOExtras >> >> Printf >> >> I am just used to C printf and well, I like the way it works. >> >> Phil >> >> >> > >

Oct. 26, 2016

Re: [Pharo-dev] roundTo: strange behavior

by stepharo

Hi nicolas So what is the solution? We can integrate fast a solution. I would really like to see them fix in Pharo 60. I'm writing a book for newbie and this is the third time I change one chapter so may be I should stop and throw away this chapter. You see I'm not good in math so even if I try hard I will not have a good solution. This is the same for marcus and most people in our team. I reopened these issues. Stef > > > 2016-10-25 23:22 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > Ok for the advice > > Now round: aNumberOfDigits seems to work fine. > > Stef > > > > No it's not, but issues are timing out too fast ;) > https://pharo.fogbugz.com/f/cases/15471/Can-t-round-Float-fmax-to-2-decimal… > https://pharo.fogbugz.com/f/cases/15472/Fraction-rounding-to-n-decimal-plac… > https://pharo.fogbugz.com/f/cases/15473/Float-round-to-n-decimal-places-is-… > > I hate to say that, but try in python, they got it right... > > > Le 25/10/16 Ã 11:05, Henrik Johansen a Ã©crit : >> +1. >> >> Unless you're dealing with fixed precision* entities, it's >> usually better to specify digits to display in printing methods >> themselves (#printShowingDecimalPlaces: & friends in base image). >> As per previous discussions around this that arise every second >> year or so, rounding the number itself (as long as we're dealing >> with floats) will never work as you want reliably. >> >> Cheers, >> Henry >> >> * And in that case, you'd use ScaledDecimals >> >>> On 23 Oct 2016, at 7:08 , phil(a)highoctane.be >>> <mailto:phil@highoctane.be> wrote: >>> >>> I use the Printf package for that. >>> >>> v := 65.456. >>> 'With 2 decimal digits: %5.2f, or 3 like this: %6.3f' >>> printf: {v. v}. >>> >>> With 2 decimal digits: 65.45, or 3 like this: 65.456 >>> >>> It is in http://www.smalltalkhub.com/#!/~philippeback/HOExtras >>> <http://www.smalltalkhub.com/#%21/%7Ephilippeback/HOExtras> >>> >>> Printf >>> >>> I am just used to C printf and well, I like the way it works. >>> >>> Phil > >

Oct. 26, 2016

Re: [Pharo-dev] [Ann] Stack Android VM

by stepharo

I want to thank Inria to have listen to me (and it was not that simple) to let Santiago work on that. So please use it and show us that you use it. Stef Le 23/10/16 Ã 22:03, Santiago Bragagnolo a Ã©crit : > Still far from production. But since i would happy to have some > feedback, I'm happy to show you some progress on the android VM. Not > yet release. But we have already a way of compiling and deploying an > image into an android device. > > You can check it in this repo github. > https://github.com/sbragagnolo/pharo-vm/ > > The building steps are detailed on the README-Android.md file. > > > Building the Stack AndroidVM > > 1. > > Download the sources fromgithub > <https://github.com/sbragagnolo/pharo-vm> > > git clone --depth=1https://github.com/sbragagnolo/pharo-vm > cd pharo-vm > 2. > > Set-up your environment: This script will download the SDK > installer and NDK R10 > > cd android/scripts > ./setupAndroidEnvironment.st > > This script downloads the content from > > * 'http://dl.google.com/android/repository/android-ndk-r10e-linux-x86_64.zip'. > * 'http://dl.google.com/android/android-sdk_r24.4.1-linux.tgz'. > > After this process you should have available the environment > variables ANDROID_NDK_HOME and ANDROID_SDK_HOME. Ensure this by > checking your .bashrc file at the user's home directory. > > 3. > > Create a new image: this image will be created by pointing to this > local git repository > > cd android/scripts > ./newImage.st > 4. > > Link sources to the build folder: The Android vm relies on a Java > wrapper. This sources must be accessible from the build folder. > > cd android/scripts > ./linkSources.st > 5. > > Generate the sources of the stack vm: This script executes the > generator of the image created on int the 3rd step. > > cd android/scripts > ./generateStackAndroidMake.st > 6. > > Generate the resource image for deployment: This script download > and suites up an image for deployment on the folder > build/assets/SmalltalkRessources > > cd android/scripts > ./newResourceImage.st > > This image created in this point is downloaded with it related VM > for editing and loading the code you want to deploy, or configure > the things you want. > > 7. > > The VM compilation: This script generates the libraries with the > VM code. > > cd build > ./build.sh > 8. > > The Java wrapper compilation and Android Application packaging > > cd build > ./package.sh > 9. > > Installing into your device. If you want to generate an APK file > with your custom name, you will need to deal with the > AndroidManifest.xml before runing the package.sh script :) > > cd build/bin > adb install -r StackActivity-debug.apk > > > - Im currently working on the JIT version of the VM, that still > avoiding me :). > But you have as well the instruction on the same README-Android.me file. > > > Santiago > > > > > >

Oct. 26, 2016

Re: [Pharo-dev] MetaLink to conditionally skip a method execution based on an arg

by Nicolai Hess

Am 23.10.2016 9:22 vorm. schrieb "Yuriy Tymchuk" <yuriy.tymchuk(a)me.com>: > > Iâve also described the question with examples on SO: https://stackoverflow.com/questions/40200546/conditionally-skip-a-method-wi… > Answered on SO. @marcus: Maybe instead links should continue with the original code, if their condition does not hold? >> On 22 Oct 2016, at 23:13, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> Hi. >> >> Imagine I have method a: and I want to skip the execution (return self or nil or whatever) when a: is evaluated with parameter 0. I have tried to add a meta link which will run instead of the method with a condition, but the condition did not workâ¦ I have tried to implement the metallic method to do nothing if the arg is 0 otherwise to perform the method, but I end up with an infinite loopâ¦ >> >> Did anybody do something like that already? Any suggestions? >> >> Uko > >

Oct. 26, 2016

Re: [Pharo-dev] keeping threads on topic

by Jimmie Houchin

Thanks for the information. I personally don't have a problem with the ability to search. I have the entire mailing list in a single mailbox in Thunderbird. However the problem with data and searching is how clean is the data, the quality of the metadata, and the constraints you can put on your search parameters. If we can have smaller messages in which the message concerns the topic in the subject, and the message contains primarily the context of the prior emails necessary for the topic. Then we are far better off in our search efforts. Our search results will be cleaner, have fewer false positives and fewer messages to wade through to find what we want. I took a look at your link. The advanced search does offer some nice ways to constrain a search. But if the message and topic of a particular message don't match it will be a false positive. Good mailing list habits are valuable. Thanks again for the link. I am not always at my computer with its resources. And many people would not do what I do anyway. Jimmie Houchin On 10/25/2016 10:22 PM, Dimitris Chloupis wrote: > The forum has a very nice search facility > > http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > > On Wed, 26 Oct 2016 at 06:11, Jimmie Houchin <jlhouchin(a)gmail.com > <mailto:jlhouchin@gmail.com>> wrote: > > On 10/23/2016 12:11 AM, Tudor Girba wrote: > > Hi, > > > > The communication traffic around Pharo is constantly increasing > and it is harder and harder to keep up with everything that is > happening. > > > > On the one hand this is great because it shows that our project > is growing healthily. On the other hand, it makes it harder for > people to find the relevant thread and participate in discussions. > This is problematic given that this mailing list is for discussing > development issues that require specific expertise. > > > > To address this, I kindly ask everyone to keep a thread as much > as possible on the topic meant by the title of the thread. > > > > Cheers, > > Tudor > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com> > > www.feenk.com <http://www.feenk.com> > > > > "Value is always contextual." > > I agree. > > We all know frequently threads take unforeseen directions. If you are > going to take a thread in a direction not on topic with the title, > then > give your email a new title appropriate with the new topic. > > This helps people to better keep up with the mailing list as they can > better discern what messages are of interest to them or not. It also > helps people with particular knowledge know if messages if the message > is something they may need to respond to. > > It also helps the mailing list archives be more valuable for people > searching for answers. > > In addition I would like to encourage people to limit the quoted > material of the email to that which is important to or the context of > what they are replying to. So many emails are replies to long and > increasingly longer emails due to quoting of complete emails only to > make brief comments about small portion of the email. > > These mailing lists are an incredibly valuable resource. They are the > first place I search to find answers. These few simple things can help > them to be cleaner and more valuable as people will more easily find > what they are looking for. > > Thanks. > > Jimmie Houchin > >

Oct. 26, 2016

Re: [Pharo-dev] [Ann] Stack Android VM

by Jimmie Houchin

Thanks for working on this. I greatly look forward to being able to use Pharo on my devices. Exciting times. Jimmie Houchin On 10/23/2016 03:03 PM, Santiago Bragagnolo wrote: > Still far from production. But since i would happy to have some > feedback, I'm happy to show you some progress on the android VM. Not > yet release. But we have already a way of compiling and deploying an > image into an android device. > > You can check it in this repo github. > https://github.com/sbragagnolo/pharo-vm/ > > The building steps are detailed on the README-Android.md file. [snip] https://github.com/sbragagnolo/pharo-vm

Oct. 26, 2016