- Pharo-users - lists.pharo.org

Re: [Pharo-users] [ann] moldable brick editor - alpha

by stephan

On 12-08-17 10:47, Tudor Girba wrote: > Is this still an issue? Yep. I tried with a clean 6.1 install. The Moz2D library is downloaded, but does not seem to be installed correctly > Could you also try on another OS (just to make sure)? next step Stephan

Aug. 18, 2017

Pharo for Android

by Ricardo Pacheco

I read some info dated 2014 that there where some efforts to make Pharo able to run on Android. Will new versions of Pharo (6.1 & 7) support Android. Does anybody use succesfully the most recent version of Pharo on a Android tablet? Thanks

Aug. 18, 2017

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

by Esteban Lorenzano

> On 18 Aug 2017, at 14:53, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > The problem is that doing a release 6.1 takes half a day of work. We could improve that, but then with Pharo7 all this changed anyway, so we will not improve this process. > half day? apply murphy law for system estimation: - raise measure unit by one: day=week - double time: 1/2 = 1 it took me one week to deliver the 6.1 release :( this is something we will be fixing with 7.0 process: each image would be like a final image, then we will be able (or we *should* be able) to create a new release by just changing a file and pushing it. Esteban

Aug. 18, 2017

Re: [Pharo-users] Installation done last week: Do I have Pharo 6.0 or Pharo 6.1?

by Marcus Denker

> On 18 Aug 2017, at 16:36, Bernhard Pieber <bernhard(a)pieber.com> wrote: > > Hi Hannes, > > I think I read somewhere that the 6.1 release reports the version number 6.0 in the image. However, if that means you have got 6.1 I am not sure how to tell. > We should really make that more consentâ¦ e.g.. we should have a â61â directly here, too: http://files.pharo.org/image/ <http://files.pharo.org/image/> and image update number should be 61001 instead of continuing 60â¦ (or name them just 6 instead of 60). of course changing all that is a lot of workâ¦ it is a bit historically grown. it used to be that point releases happend ever year and all the infrastructure is not really good for doing it more frequently. So: yes, too improve. Marcus

Aug. 18, 2017

Re: [Pharo-users] Installation done last week: Do I have Pharo 6.0 or Pharo 6.1?

by Bernhard Pieber

Hi Hannes, I think I read somewhere that the 6.1 release reports the version number 6.0 in the image. However, if that means you have got 6.1 I am not sure how to tell. Cheers, Bernhard > Am 18.08.2017 um 16:21 schrieb H. Hirzel <hannes.hirzel(a)gmail.com>: > > Hello > > Pharo 6.1 was released on the 24th July 2017. > Thread [Pharo-dev] [ANN] Pharo 6.1 (summer) released! (35 messages so far). > My question short: Which version do I get when installing? > > Last week I on the the 9th August I did > > curl get.pharo.org | bash > > on Ubuntu 14.04-32bit. Installation was done fully automated. Very > smooth! Excellent! > > Just needed to do in a terminal window > ./pharo-ui > to start Pharo 6.x > > Now my question: > > 'Word menu' -> 'System' -> 'About' > > gives me > > Pharo 6.0 > Latest update: #60510 > > > Is the indication 'Pharo 6.0' just an omission in the release process > and it should say 'Pharo 6.1'? > Or did I still get 'Pharo 6.0' for some reason? > > Thank you for the answer in advance > > Hannes >

Aug. 18, 2017

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

by Marcus Denker

> On 18 Aug 2017, at 15:41, Tim Mackinnon <tim(a)testit.works> wrote: > > If you donât mind - let me try a second attempt at paraphrasing what you are saying (just to make sure Iâm clear, but it might help others too). > > We start each yearly cycle with an X0 new release (our current release is 6). Then there may be point releases 6.1, 6.2 etc where there is a breaking change (typically a new VM. Our last point release was 6.1). > > Thought the year (typically every few days) there are âhot fixesâ that causes an image number change (these have worked there way through the CI, and have triggered a new artefect). These images can be found at http://files.pharo.org/image/60/ <http://files.pharo.org/image/60/> (where 60 designates the last release cycle, we donât use point designations for this directory name). > > When you download the latest point release, you are getting all the major elements of that release plus any of the hot fixes that have occurred since that official release. So you have the most up to date version of a stable Pharo at the time that you download this file from: http://pharo.org/download <http://pharo.org/download> > yes > The implication of the above, is that if you want to revert to exactly what was present in the launch of an official point release, you will need to download the latest release from Pharo.org <http://pharo.org/> and then find the image number that corresponded to that release at http://files.pharo.org/image/60/ <http://files.pharo.org/image/60/> (is there an easy way to determine this and then find that file? Or is there an official archive of the first point release?). > > If you want to say up to date, you should periodically download the latest point release (or you can simply find that latest named image file from: http://files.pharo.org/image/60/ <http://files.pharo.org/image/60/> and use your current VM). > > If the above is the case - it seems like a reasonable way of operating, although it might be good to know what the exact image number was in the first issued point release (just for traceability). > > Have I now got it straight now? > Yes. And maybe it is not goodâ¦ maybe it would be better to accumulate the changes between the point release without changing the download and have the version numbers more prominent in the downloaded files (so that it is easy to find old versions, too). With Pharo7 we can improve this... Marcus

Aug. 18, 2017

Re: [Pharo-users] Loading and saving packages to filetree repos

by Thierry Goubier

Hi Luke, if you use gitfiletree with AltBrowser and configurations/baselines, then you'll see that you have a command to do the writing for you, without metadata and with a single git commit. Regards, Thierry Le 17/08/2017 Ã 13:25, Luke Gorrie a Ã©crit : > Hoi, > > I want to have a quick "cheat mode" for loading and saving the Smalltalk > packages in my project. This is to make life easy for newbies who are > not very familiar with Monticello and Metacello. > > The "cheat" is to assume that there is one filetree:// repository that > contains all of the relevant packages, and all we need to do is load or > save each of those packages in that repository. > > I have the loading part working already: > > repo := MCFileTreeRepository new directory: '/foo/bar/baz' > asFileReference. > repo allFileNames do: [ :file | > (repo versionFromFileNamed: file) load. > ]. > > but now I am wondering how to do the saving part? That is, given a path > to a filetree repo like '/foo/bar/baz', how do I save each package in > that repo i.e. export the code in the image? > > Ideally I would like the same operation to skip metadata that is likely > to cause conflicts when the code is checked into Git later e.g. package > timestamps and versions. > > Tips would be appreciated :). > > >

Aug. 18, 2017

Installation done last week: Do I have Pharo 6.0 or Pharo 6.1?

by H. Hirzel

Hello Pharo 6.1 was released on the 24th July 2017. Thread [Pharo-dev] [ANN] Pharo 6.1 (summer) released! (35 messages so far). My question short: Which version do I get when installing? Last week I on the the 9th August I did curl get.pharo.org | bash on Ubuntu 14.04-32bit. Installation was done fully automated. Very smooth! Excellent! Just needed to do in a terminal window ./pharo-ui to start Pharo 6.x Now my question: 'Word menu' -> 'System' -> 'About' gives me Pharo 6.0 Latest update: #60510 Is the indication 'Pharo 6.0' just an omission in the release process and it should say 'Pharo 6.1'? Or did I still get 'Pharo 6.0' for some reason? Thank you for the answer in advance Hannes

Aug. 18, 2017

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

by Tim Mackinnon

If you donât mind - let me try a second attempt at paraphrasing what you are saying (just to make sure Iâm clear, but it might help others too). We start each yearly cycle with an X0 new release (our current release is 6). Then there may be point releases 6.1, 6.2 etc where there is a breaking change (typically a new VM. Our last point release was 6.1). Thought the year (typically every few days) there are âhot fixesâ that causes an image number change (these have worked there way through the CI, and have triggered a new artefect). These images can be found at http://files.pharo.org/image/60/ <http://files.pharo.org/image/60/> (where 60 designates the last release cycle, we donât use point designations for this directory name). When you download the latest point release, you are getting all the major elements of that release plus any of the hot fixes that have occurred since that official release. So you have the most up to date version of a stable Pharo at the time that you download this file from: http://pharo.org/download <http://pharo.org/download> The implication of the above, is that if you want to revert to exactly what was present in the launch of an official point release, you will need to download the latest release from Pharo.org <http://pharo.org/> and then find the image number that corresponded to that release at http://files.pharo.org/image/60/ <http://files.pharo.org/image/60/> (is there an easy way to determine this and then find that file? Or is there an official archive of the first point release?). If you want to say up to date, you should periodically download the latest point release (or you can simply find that latest named image file from: http://files.pharo.org/image/60/ <http://files.pharo.org/image/60/> and use your current VM). If the above is the case - it seems like a reasonable way of operating, although it might be good to know what the exact image number was in the first issued point release (just for traceability). Have I now got it straight now? Tim > On 18 Aug 2017, at 13:53, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 18 Aug 2017, at 13:08, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> Thanks Marcus - and definitely we all appreciate that its holiday season and that a lot of this is driven by community and people donating their free time. >> >> Iâm still a bit unclear on the moving parts. To paraphrase what you have said: >> >> We start each yearly cycle with a X.0 new release. Then there may be point releases 6.1, 6.2 etc where there is a breaking change (typically a new VM I guess - but is there anything else that would cause a .x release?). >> >> Then there are âhot fixesâ that causes an image number change (these have worked there way through the CI, as it triggered a new build)? The implication is then that what I download from Pharo.org <http://pharo.org/> is the last point release, > > No, the download is always the latest (with all accepted fixes integrated). > >> but then I can go and find a newer image âhot fixâ if I want some of the latest more minor fixes (and I guess this then answers m .x question above - as I guess that if there was a major bug in the image it might also trigger a new point release so that new users would get that fix when downloading from pharo.org <http://pharo.org/>?) >> > The problem is that doing a release 6.1 takes half a day of work. We could improve that, but then with Pharo7 all this changed anyway, so we will not improve this process. > (and not do many releases of this kind for Pharo6). > >> So a reasonably active Pharo user (but not a more bleeding edge new release user) should typically download the latest image every month to stay current? >> > Normally you have a CI that builds from the latest pharo image + the latest commit from your repo and you start with that all couple of days/weeks (This is important > to make sure that you have a reproduce build, too). > >> We should encourage more seasoned users to also try a leading edge point release, and apply the latest hot fix image particularly in the latter part of year when we are trying to stabilise for the next release cycle. And then there are the instructions about taking the next leap for contributing backâ¦ >> >> Is this right? > > Not really. *all* fixes that go into the stable release go into the development release, too. So the releases of stable Pharo6 have not much todo with Pharo7, no need to run a special > Pharo6 when we stabilize Pharo7. Here it is important that people use Pharo7. > > Keep in mind that we try to do active development only in the development branch, so we talk about 20-30 fixes in total, many many are not really that important or are just important for > those who ran into them. > > So we should not be too complex about itâ¦ it worked fine like this the last years. > > Marcus >

Aug. 18, 2017

Re: [Pharo-users] [Github Repo] I just pushed template to quickly start Pharo / Teapot

by Sven Van Caekenberghe

The inspector extension are really cool ! > On 15 Aug 2017, at 01:27, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi sergio, > > why not use my existing "Tealight" project which is (similar to Teapot) also available from Pharo catalog. > It is still lightweight as it is just a few extensions to Teapot. > > You will find it here: > > https://github.com/astares/Tealight > > the page includes the full documentation and after reading it you should be able to see: > > - that you can even start the server quickly from the world menu after loading > - how easy it is to tinker and experiment with dynamic routes and Teapot in an interactive way > - how easy it is to provide a REST interface by having methods annotated with REST specific pragmas > - to even provide a versioned REST interface (also defined using pragmas) > > The document should easily explain all this, esepcially read "Defining a REST based interface". > > This project is around since last october now (see http://forum.world.st/ANN-Tealight-td4918431.html) > > > Lately I even added the possibility to remove one or all the dynamic routes in a teapot inspector > (see attached screenshot). That makes it even easier to experiment lively with a teapot instance > and different URLs one wants to catch. > > Have fun > Torsten > > > > > > > <routes.png>

Aug. 18, 2017