- Pharo-dev - lists.pharo.org

[Ann] Stack Android VM
by Santiago Bragagnolo Oct. 26, 2016

Oct. 26, 2016

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 from github <https://github.com/sbragagnolo/pharo-vm> git clone --depth=1 https://github.com/sbragagnolo/pharo-vmcd 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

6 5

MetaLink to conditionally skip a method execution based on an arg
by Yuriy Tymchuk Oct. 26, 2016

Oct. 26, 2016

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

4 5

keeping threads on topic
by Tudor Girba Oct. 26, 2016

Oct. 26, 2016

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 www.feenk.com "Value is always contextual."

3 3

[ANN] Scale
by Santiago Bragagnolo Oct. 25, 2016

Oct. 25, 2016

Hi everybody. We are officially releasing a first version of scale. Scale is a command line handler that is there for making easier the life of the people that uses scripting in linux. As such, we only tested it so far in linux. It will be for sure easy to adapt it to mac because its a *nix, but not for windoze. *IMPORTANT REMARK*: scale is not meant to develop applications, it is meant to develop scripts in Pharo, to be launched from the command line. This means that scale does not provide a top level syntax to declare classes or methods: people should do that as any normal Pharo application. Scale should be used to invoke such applications. When would you use scale? - For example, to replace some bash scripts used for common boring tasks (and you are using python or ruby there :P) - Another example, would be when you want to replace bash scripts that chain things like: ./pharo eval --save "something" ./pharo eval --save "other something" ... Github: https://github.com/guillep/Scale Oneliner to install: (note it needs sudo) wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh | sudo bash In the repository there is some user level documentation based on examples and a list of available methods on the magical variable system. There are many examples as well on the repository. Last but not least, I'm using this project in others two projects, where it proof it self quite powerful what keeps me on maintaining Scale. These projects are: *Pharo Android VM building *https://github.com/sbragagnolo/pharo-vm Here I use it for automating the creation of a * new building image, * the creation of new resource image (for deploying on the android apk), * linking the android sources into the building directory * generating the code from the console *MakrosTool* https://github.com/sbragagnolo/MakrosTool MakrosTool is an extension of scale that adds a second magical variable for building up component reification in a ROS based environment. Santiago & Guille

6 13

TechTalk invite link
by Esteban Lorenzano Oct. 25, 2016

Oct. 25, 2016

https://discord.gg/88sbn83 <https://discord.gg/88sbn83> It will start in 20min as preview. Esteban

1 0

Notes about Pharo 6 release and new process for Pharo 7
by Esteban Lorenzano Oct. 25, 2016

Oct. 25, 2016

Time to send this to dev list: (btw, this has to do with what we are going to talk today in TechTalk). Hi, Last week we had a meeting where we tried to define current Pharo 6 efforts and the next Pharo 7 goals (in particular, how to revamp our process into something that fits better our numbers of today). The thing is there was no clear roadmap for Pharo 6 and we wanted to precise it. Also, during last years we put some pieces in place and we are ready to do the next big step (changing the Pharo process) but we need to work hard until we have it working (and we just have a draft of how we would want to work, I will talk about later), and we need to discuss, test, iterate before is working properly. Anyway, this is what we think: We need to put Pharo 6.0 development in âfeature freeze statusâ right now. Only things that needs to enter is: - Clements changes (full blocks, SISTA bytecode set, â¦) - 64bits - Bugfixes This way we can jump to work on the new process, that we think will take some months until we have it ready. NEW PROCESS: 1) Builds will be bootstrap based. This implies a change of mindset: pharo will be considered as a small kernel plus a set of maintained packages. This is important to remark because is a difference in our way of think: until now pharo is âthe imageâ, now it will be different because there is the possibility of build different images starting from the kernel and bootstrapping other packages. But of course, the standard-distributed image will be still a compound of the maintained packages (and tests will be ran against this amalgam to be sure everything continues working) 2) Sources will be moved to git. Concrete structure is TBD, but it will be an unique project (no submodules) for a start. This is because is hard to handle changes in multiple submodulesâ¦ Anyway I would like to have different source directories (to separate kernel from maintained packages :P) 3) Changes will be managed through Pull Requests (yay!) And of course there will be a validation process (travis based)â¦ - Iâm also thinking on push the built images into some place for people to be able to verify their errors in the built image (also we could do this)â¦ I mean, the build images for validationâ¦ of course the âintegratedâ images will be pushed allways. This implies a lot of work to make it work, build the tools we need and make us feel confortable with it, thatâs why we want to start as soon as possible. This way, when 7.0 starts in march, we are with the new process. So that. Opinions, suggestions? Esteban

3 5

[pharo-project/pharo-core]
by GitHub Oct. 25, 2016

Oct. 25, 2016

Branch: refs/tags/50762 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] 9733d5: 50762
by GitHub Oct. 25, 2016

Oct. 25, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 9733d5c59a3043f0425826f133fa7b71d24e3c2a https://github.com/pharo-project/pharo-core/commit/9733d5c59a3043f0425826f1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-25 (Tue, 25 Oct 2016) Changed paths: M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/baselines/baseline33_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/baselines/baseline34_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/baselines/baseline40_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/development_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version415_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version416_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version417_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version418_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version4191_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version419_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version420_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version421_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version422_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version423_.st M Glamour-Core.package/GLMAction.class/definition.st A Glamour-Core.package/GLMAction.class/instance/accessing/enabledCondition.st A Glamour-Core.package/GLMAction.class/instance/accessing/enabledCondition_.st A Glamour-Core.package/GLMAction.class/instance/testing/isEnabledOn_.st A Glamour-Core.package/GLMPresentation.class/instance/scripting actions/selectionAct_entitled_enabledWhen_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50761.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50762.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50761.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50762.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50762 19205 [Backport] Pharo 5: Enable / Disable options in context Menu in FastTable https://pharo.fogbugz.com/f/cases/19205 http://files.pharo.org/image/50/50762.zip

1 0

[pharo-project/pharo-core] 4a07c2: 60268
by GitHub Oct. 25, 2016

Oct. 25, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 4a07c2a919a25a29ecc26483fda83c7bf3ada95d https://github.com/pharo-project/pharo-core/commit/4a07c2a919a25a29ecc26483… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-25 (Tue, 25 Oct 2016) Changed paths: M Refactoring-Core.package/RBRefactoring.class/instance/preconditions/checkPreconditions.st M Refactoring-Core.package/RBRenameTemporaryRefactoring.class/instance/preconditions/preconditions.st M Refactoring-Core.package/RBRenameTemporaryRefactoring.class/instance/tranforming/renameNode_.st M Refactoring-Core.package/RBRenameTemporaryRefactoring.class/instance/tranforming/transform.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60267.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60268.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60267.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60268.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60268 19238 RBRenameTemporaryRefactoring do not set oldName if one of the optional precondition is not valid https://pharo.fogbugz.com/f/cases/19238 http://files.pharo.org/image/60/60268.zip

1 0

[pharo-project/pharo-core]
by GitHub Oct. 25, 2016

Oct. 25, 2016

Branch: refs/tags/60268 Home: https://github.com/pharo-project/pharo-core

1 0