March 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #674: 21521-File-out-and-file-in-code-leads-to-wrong-line-ending-in-the-image2

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #674 was: SUCCESS. The Pull Request #1049 was integrated: "21521-File-out-and-file-in-code-leads-to-wrong-line-ending-in-the-image2" Pull request url: https://github.com/pharo-project/pharo/pull/1049 Issue Url: https://pharo.fogbugz.com/f/cases/21521 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 9, 2018

[Pharo 7.0-dev] Build #673: 21216-Now-Trait-isBehaviour-returns-true-and-it-affects-ChangeSet-method

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #673 was: SUCCESS. The Pull Request #1039 was integrated: "21216-Now-Trait-isBehaviour-returns-true-and-it-affects-ChangeSet-method" Pull request url: https://github.com/pharo-project/pharo/pull/1039 Issue Url: https://pharo.fogbugz.com/f/cases/21216 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 9, 2018

[Pharo 7.0-dev] Build #672: 21515-Update-bootstrap-to-bootstrapImage-1.4-and-7.0-VM

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #672 was: SUCCESS. The Pull Request #1048 was integrated: "21515-Update-bootstrap-to-bootstrapImage-1.4-and-7.0-VM" Pull request url: https://github.com/pharo-project/pharo/pull/1048 Issue Url: https://pharo.fogbugz.com/f/cases/21515 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 9, 2018

[Pharo 7.0-dev] Build #671: 21494-Change-boostrap-to-not-load-Spec-Debugger

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #671 was: SUCCESS. The Pull Request #1034 was integrated: "21494-Change-boostrap-to-not-load-Spec-Debugger" Pull request url: https://github.com/pharo-project/pharo/pull/1034 Issue Url: https://pharo.fogbugz.com/f/cases/21494 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 9, 2018

[Pharo 7.0-dev] Build #670: 21042-file-out-does-not-work-from-browser

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #670 was: SUCCESS. The Pull Request #1044 was integrated: "21042-file-out-does-not-work-from-browser" Pull request url: https://github.com/pharo-project/pharo/pull/1044 Issue Url: https://pharo.fogbugz.com/f/cases/21042 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 9, 2018

Re: [Pharo-dev] [Pharo-users] [ANN] Cruiser: A Pharo app packager

by Ben Coman

A lot of people have been wanting something like this. Thanks Vincent. cheers -ben On 9 March 2018 at 03:29, <Vincent.Blondeau(a)lamresearch.com> wrote: > Hi Pharoers! > > > > I pleased to announce you the first release of Cruiser: a tool to package > your Pharo applications. The idea is to quickly convert an application from > a development environment to a production one. A production environment > means: > > - No writing on the disk > - No access to the source code (by the shortcuts, debugger,...) > - No error displaying on the interface > - The only thing accessible is the user application > > > > I let you discover it on: https://github.com/VincentBlondeau/Cruiser > > > > > > Do not hesitate to ask me questions or contribute to improve it! > > > > Cheers, > > > > > *Vincent Blondeau *Software Engineer, Software and Controls | Global > Product Group > Desk +1 510.572.7499 <(510)%20572-7499> > > > > *Lam Research Corporation *4650 Cushing Pkwy, Fremont, CA 94538 USA > <https://maps.google.com/?q=4650+Cushing+Pkwy,+Fremont,+CA+94538+USA&entry=g…> > | www.lamresearch.com > Connect with Lam Research: Facebook > <https://www.facebook.com/LamResearchCorporation> | Twitter > <https://twitter.com/lamresearch> | LinkedIn > <https://www.linkedin.com/company/lam-research> > > ------------------------------ > > > > NOTICE: This e-mail transmission may contain confidential information. If > you are not the intended recipient, or a person responsible for delivering > it to the intended recipient, you are hereby notified that any disclosure, > copying, distribution or use of any of the information contained in or > attached to this message is STRICTLY PROHIBITED. If you have received this > transmission in error, please immediately notify the sender and destroy the > original transmission and its attachments without reading them or saving > them to disk. Thank you. >

March 9, 2018

Re: [Pharo-dev] Metacello locking system

by Dale Henrichs

On 03/06/2018 10:51 AM, Cyril Ferlicot D. wrote: >> Cyril, >> >> For development I tend to use Metacello locking instead of hard-wired >> dependencies in the BaselineOf and that works very well --- it >> completely avoids the need to edit a baseline for development purposes >> and this approach works really well for me ... perhaps we can discuss >> this in more detail in a separate thread or even private email? This all >> seems to be more complicated for you guys than has been my experience >> and of course you guys _appear_ to be completely ignoring the Metacello >> locking feature so I'm curious why ... >> >> Dale >> > Hi Dale, > > As asked I start a new thread. > > I can see some possible reasons I do not use Metacello locking feature. > 1) I did not understand well enough what it was > 2) We have a way to work different and mine might be incompatible with > the lock feature > 3) I just did not see how it could help me > > To know which one is the reason I'll present you a little what I > understood of the lock feature and how I usually work and you'll be able > to advise me. > > For the lock feature: > > If I understood correctly it is a feature allowing to lock a certain > version of a project in the Metacello registry. For example if I load > Seaside 3.1, lock it and then install a project having Seaside 3.2 as > dependency, the lock will block the update of Seaside. Okay, this is how a lock for a ConfigurationOf works, but the effect of a lock on a BaselineOf is that the FileTree directory where the BaselineOf is loaded from becomes the "locked version" ... in other words locking a BaselineOf is really a lock on a git directory and whatever SHA you happen to have checked out in the location will be used ... and this means that you can explicitily checkout a particular tag in the git repo and that is the "locked version" > > Now how do I usually work: > > Let's take the example of MaterialDesignLite that I maintain. > > The master branch is a branch that should only contains stable MDL > versions. Ideally I would like for each commit of this branch to be > tagged with a semantic versionning tag. > > The development happen in the development branch and new features are > merged into this branch before making it to master. > > In general I prefer to have stricter dependencies in master than in > development. So the baseline in the development branch can be different > than in master. > > For all my projects I try to have a Jenkins building Pharo images for at > least master and development, and potentially big feature branches > before they are merged. The Jenkins also test the images. For development builds how do you specify/control the version of each of you 70 dependent projects for your Pharo build ... The use case for using locks would say that you have 70 cloned git repositories that you are using for development purposes: i.e, you anticipate the possibility that you will need to make active changes to anyone of those 70 cloned git repositories as you do your development and I assume that you are always operating on the head of the development branch for each of these 70 cloned repositories ... Then you would simply lock all 70 projects to the filetree directory for the projects and when you decide to update to the latest development branch of a particular project you do a git pull in that clone and your next build will use the new version of that project ... When you make a change from within the image and commit a new version in one of the projects ... again the next build will use the new SHA and so on ... Once you've done a lock to a cloned git repo, you don't need to do fiddle with the BaselineOf, you simply manipulate the version that is present in the cloned git repo to change which SHA you want to use and all builds will simple use the "current SHA" for each of projects ... and since you've got active clones being used, it is simple to commit from your current working image ... I know that I've simplified some things here and I still don't see what you do as an alternative to what I am suggesting with locks ... but hopefully I've given you a bit clearer picture of what I imagine, you could/should be doing? Dale

March 8, 2018

Re: [Pharo-dev] [Pharo-users] [ANN] Cruiser: A Pharo app packager

by Vincent.Blondeau＠lamresearch.com

Thx! That's not planned to do mobile apps for now. I was even not aware that mobile apps could be done with Pharo. But, if you feel the need to do it, any contribution is welcomed! Vincent From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Todd Blanchard Sent: Thursday, March 8, 2018 12:05 To: Pharo Development List <pharo-dev(a)lists.pharo.org> Cc: Thorgrimsson, Chris <Chris.Thorgrimsson(a)lamresearch.com>; Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] [Pharo-dev] [ANN] Cruiser: A Pharo app packager That is very cool. Any intentions to do mobile? Inspired by David Buck's post on his mobile VM. https://medium.com/@richardeng/mobile-smalltalk-c6f0cc712909<https://urldefense.proofpoint.com/v2/url?u=https-3A__medium.com_-40richarde…> On Mar 8, 2018, at 12:00 PM, Alexandre Bergel <alexandre.bergel(a)me.com<mailto:alexandre.bergel@me.com>> wrote: I saw a demo of it two weeks ago. This is really good stuff! Cruiser is about turning a Pharo app as a stand-alone application, as an .exe file from a user perspective, without knowing there is Pharo underneath. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bergel.eu_&d=DwMFAg…> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Mar 8, 2018, at 4:29 PM, Vincent.Blondeau(a)lamresearch.com<mailto:Vincent.Blondeau@lamresearch.com> wrote: Hi Pharoers! I pleased to announce you the first release of Cruiser: a tool to package your Pharo applications. The idea is to quickly convert an application from a development environment to a production one. A production environment means: * No writing on the disk * No access to the source code (by the shortcuts, debugger,...) * No error displaying on the interface * The only thing accessible is the user application I let you discover it on: https://github.com/VincentBlondeau/Cruiser<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_VincentBlon…> <image002.png> Do not hesitate to ask me questions or contribute to improve it! Cheers, Vincent Blondeau Software Engineer, Software and Controls | Global Product Group Desk +1 510.572.7499 Lam Research Corporation 4650 Cushing Pkwy, Fremont, CA 94538 USA | www.lamresearch.com<x-msg://107/www.lamresearch.com> Connect with Lam Research: Facebook<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_LamRe…> | Twitter<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_lamresearc…> | LinkedIn<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_compa…> ________________________________ NOTICE: This e-mail transmission may contain confidential information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and destroy the original transmission and its attachments without reading them or saving them to disk. Thank you.

March 8, 2018

[Pharo 7.0-dev] Build #669: 21517-New-traits-copy-all-class-side-methods-of-TraitedClass-to-all-subclasses-of-trait-users

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #669 was: SUCCESS. The Pull Request #1047 was integrated: "21517-New-traits-copy-all-class-side-methods-of-TraitedClass-to-all-subclasses-of-trait-users" Pull request url: https://github.com/pharo-project/pharo/pull/1047 Issue Url: https://pharo.fogbugz.com/f/cases/21517 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 8, 2018

Re: [Pharo-dev] [Pharo-users] [ANN] Cruiser: A Pharo app packager

by Tudor Girba

Very cool. Thanks! Doru > On Mar 8, 2018, at 8:29 PM, <Vincent.Blondeau(a)lamresearch.com> <Vincent.Blondeau(a)lamresearch.com> wrote: > > Hi Pharoers! > > I pleased to announce you the first release of Cruiser: a tool to package your Pharo applications. The idea is to quickly convert an application from a development environment to a production one. A production environment means: > â¢ No writing on the disk > â¢ No access to the source code (by the shortcuts, debugger,...) > â¢ No error displaying on the interface > â¢ The only thing accessible is the user application > > I let you discover it on: https://github.com/VincentBlondeau/Cruiser > > <image002.png> > > Do not hesitate to ask me questions or contribute to improve it! > > Cheers, > > Vincent Blondeau > Software Engineer, Software and Controls | Global Product Group > Desk +1 510.572.7499 > > Lam Research Corporation > 4650 Cushing Pkwy, Fremont, CA 94538 USA | www.lamresearch.com > Connect with Lam Research: Facebook | Twitter | LinkedIn > > > NOTICE: This e-mail transmission may contain confidential information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and destroy the original transmission and its attachments without reading them or saving them to disk. Thank you. -- www.tudorgirba.com www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

March 8, 2018