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

> 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). This is expected for production code, but maybe not the workflow for everyone

Re: [Pharo-users] Pharo for Android

Thanks a lot. I will give it a try!! 2017-08-18 15:15 GMT-05:00 Stephane Ducasse : > Santiago Bragagnolo updated the VM but it is still using an old > pulling event system. > It is on our large todo to address this but it means a lot of work. > We want a better Android

Re: [Pharo-users] GTInspect auto-update in raw view?

However, we still need the update button. The automatic refresh only works for the Raw view. A general solution for the update is not yet implemented. Cheers, Andrei On Fri, Aug 18, 2017 at 10:21 PM, Stephane Ducasse wrote: > Cool > Because I hate so much this

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

On Fri, Aug 18, 2017 at 07:16:30PM +0200, H. Hirzel wrote: > Thank you, Bernhard and Markus for confirming that Pharo is not > reporting the correct version number. > > But do you think I probably got 6.1 when I installed it on the 9th August > with > > curl get.pharo.org | bash Yes, you

Re: [Pharo-users] YAML parser (2017)

On Fri, Aug 18, 2017 at 09:50:35PM +0200, H. Hirzel wrote: > Hello Peter > > Thank you for the answer. Good news that Phil Back has an done > upgraded version of the PetitYAML parser recently. > > I think what you describe as "mostly complete" will be very fine for > my purposes. > > On

Re: [Pharo-users] [Ann] Blog entry about using Pharo / Smalltalk to build a bot

Hi sergio Tx for your nice article. I hope you got success with Pharo. Could we write a small success story? Stef On Fri, Aug 18, 2017 at 2:54 PM, sergio ruiz wrote: > Oh! I like your approach.. > > Let me quickly clarify my situation. In that section of the article, I was

Re: [Pharo-users] GTInspect auto-update in raw view?

Cool Because I hate so much this update button :) Stef On Fri, Aug 18, 2017 at 7:22 PM, Andrei Chis wrote: > > > On Thu, Aug 17, 2017 at 9:24 AM, Esteban Lorenzano > wrote: >> >> >> On 17 Aug 2017, at 01:02, Aliaksei Syrel

Re: [Pharo-users] [Pillar] Installed the Pillar document preparation system into 6.1, how do I start using it?

On ven. 18 août 2017 at 22:09, H. Hirzel wrote: > Exactly. > > Section 7 of > > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html > > has an example > > > | wiki | > wiki := '!My

Re: [Pharo-users] Pharo for Android

Santiago Bragagnolo updated the VM but it is still using an old pulling event system. It is on our large todo to address this but it means a lot of work. We want a better Android support for sure but Now you can use Pharo on Android. I do not know if we have a jenkins job :(

Re: [Pharo-users] [Ann] Data activism, visualization and storytelling with reproducible research for undergrad journalism and communication sciences students

Cool! Let us know. Stef On Fri, Aug 18, 2017 at 7:17 PM, Offray Vladimir Luna Cárdenas wrote: > Hi :-), > > A little announcement, that can be interesting for several communities > and practices to bridge them and make them more visible (so, that's why > the cross

Re: [Pharo-users] [Pillar] Installed the Pillar document preparation system into 6.1, how do I start using it?

Exactly. Section 7 of https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html has an example | wiki | wiki := '!My Document'. PRPillarParser parse: wiki Or PRPillarParser parse: (FileSystem

Re: [Pharo-users] YAML parser (2017)

Hello Peter Thank you for the answer. Good news that Phil Back has an done upgraded version of the PetitYAML parser recently. I think what you describe as "mostly complete" will be very fine for my purposes. On 8/18/17, Peter Uhnak wrote: > Hi, > > Phil Back has kindly fixed

Re: [Pharo-users] [Pillar] Installed the Pillar document preparation system into 6.1, how do I start using it?

On ven. 18 août 2017 at 21:43, H. Hirzel wrote: > Thank you Cyril for the link to the tutorial. > > > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html > > I see that Pillar is a command line

Re: [Pharo-users] [Pillar] Installed the Pillar document preparation system into 6.1, how do I start using it?

Thank you Cyril for the link to the tutorial. https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html I see that Pillar is a command line tool. The welcome example taken from this tutorial is: Pharo.exe Pillar.image

Re: [Pharo-users] [Pillar] Installed the Pillar document preparation system into 6.1, how do I start using it?

On ven. 18 août 2017 at 19:44, H. Hirzel wrote: > Hello > > I installed Pillar through the catalog into Pharo 6.1, I assume. > > I had a look into the Help browser to find some documentation or a > link to the documentation. > > I did not find a menu entry in the world

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

Thanks Peter for the clarification. So this means as my 'About box' shows Pharo 6.0 version 60510 I have actually got 6.1. -- Hannes On 8/18/17, Peter Uhnak wrote: > I don't know what was the exact reasoning why it was chosen to stay this > way... > 60505 is

Re: [Pharo-users] What is proper fix for this?

On 17/08/17 03:49, Herby Vojčík wrote: > Guillermo Polito wrote: >> >> >> Just a thought out of thin air: wasn't filetree supposed to provide >> common ground for this kind of scenarios? If we shared a single >> repository in github that would save us a lot of discussion :P > > I'd prefer

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

I don't know what was the exact reasoning why it was chosen to stay this way... 60505 is still 6.0, so somewhere between 60506 and 60510 is the split. :-) Peter On Fri, Aug 18, 2017 at 04:21:24PM +0200, H. Hirzel wrote: > Hello > > Pharo 6.1 was released on the 24th July 2017. > Thread

Re: [Pharo-users] Pharo 6.1 catalog -- How is the catalog information updated?

I found http://catalog.pharo.org/ and the link 'a note to developers' Following that I see that a ConfigurationOfXYZ file needs to be in http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main So I assume if a newer version of a ConfigurationOfXYZ is put there, the catalog

[Pharo-users] [Pillar] Installed the Pillar document preparation system into 6.1, how do I start using it?

Hello I installed Pillar through the catalog into Pharo 6.1, I assume. I had a look into the Help browser to find some documentation or a link to the documentation. I did not find a menu entry in the world menu to open the tool. How do I start using the tool? --Hannes

Re: [Pharo-users] GTInspect auto-update in raw view?

On Thu, Aug 17, 2017 at 9:24 AM, Esteban Lorenzano wrote: > > On 17 Aug 2017, at 01:02, Aliaksei Syrel wrote: > > Hello Esteban, > > You can enable auto-refresh with: GTInspector enableStepRefresh > For performance reasons it is disabled by default. If

[Pharo-users] Pharo 6.1 catalog -- How is the catalog information updated?

Hello Where do I find information how the Pharo 6.1 catalog entries are maintained? Thank you in advance Hannes

[Pharo-users] [Ann] Data activism, visualization and storytelling with reproducible research for undergrad journalism and communication sciences students

Hi :-), A little announcement, that can be interesting for several communities and practices to bridge them and make them more visible (so, that's why the cross posting). At mid September I'm going to give a little workshop at a local university for undergrad journalism and communication

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

Thank you, Bernhard and Markus for confirming that Pharo is not reporting the correct version number. But do you think I probably got 6.1 when I installed it on the 9th August with curl get.pharo.org | bash on Ubuntu. Or should I just run the installation command again? --Hannes On

Re: [Pharo-users] [Ann] Blog entry about using Pharo / Smalltalk to build a bot

Yeah all that sounds familiar to me Its great you made this post because as you see its all about the illusion of popularity than actual popularity. Exposing Pharo like this is a great way to gain "popularity". My numbers by the way can be widely disputed however there is a common pattern here

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

Hello Stephan, > Yep. I tried with a clean 6.1 install. > The Moz2D library is downloaded, but does not seem to be installed > correctly Below is the list of dependencies for *64bit Ubuntu* and *32bit Pharo*: (on 64bit pharo it should theoretically work out of the box, except 64bit related

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

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 THERE_BE_DRAGONS_HERE Warning 18

[Pharo-users] Pharo for Android

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

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

> On 18 Aug 2017, at 14:53, Marcus Denker 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

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

> On 18 Aug 2017, at 16:36, Bernhard Pieber 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

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

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 : > > Hello > > Pharo 6.1 was released

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

> On 18 Aug 2017, at 15:41, Tim Mackinnon 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

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

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

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

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

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

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

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

The inspector extension are really cool ! > On 15 Aug 2017, at 01:27, Torsten Bergmann 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

Re: [Pharo-users] Problem compiling method source - genPushLiteral: out of range

> On 18 Aug 2017, at 11:34, Patrick Scherer wrote: > > Hello everyone, > > I'm trying to move some of our code from VA Smalltalk over to Pharo using a > self-made importer and have encountered the following issue I need help with: > > A few of our methods are very

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

> On 18 Aug 2017, at 13:08, Tim Mackinnon 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

Re: [Pharo-users] [Ann] Blog entry about using Pharo / Smalltalk to build a bot

Oh! I like your approach.. Let me quickly clarify my situation. In that section of the article, I was referring to my workplace. In my case, no one else in the dev department knows smalltalk. In a great many workplaces, devs don’t really want to learn a new language / framework without going

Re: [Pharo-users] ZnConstants class>>#httpStatusCodes and cloudflare

Hi Holger, It is probably not a good idea to be too strict here. I committed the following to #bleedingEdge === Name: Zinc-HTTP-SvenVanCaekenberghe.465 Author: SvenVanCaekenberghe Time: 18 August 2017, 2:11:25.092807 pm UUID: da9ed1c3-6713-0d00-bd88-7a0d0e6057cd Ancestors:

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

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

Re: [Pharo-users] Encoding Login information in your image (safely)

On Wed, Aug 16, 2017 at 02:24:15PM -0300, Esteban A. Maringolo wrote: > My solution in the cases where I was worried about a config file leak > was to mitigate the risk, by using symmetric encryption algorithms, > where the shared secret is split in two different strings and > concatenated at

Re: [Pharo-users] Problem compiling method source - genPushLiteral: out of range

The limitation is inherit in the object format/ instruction set, you can find some previous discussions at http://forum.world.st/Max-source-method-length-Max-string-length-Max-change-set-size-td3531169.html#a3535281 and

[Pharo-users] ZnConstants class>>#httpStatusCodes and cloudflare

Hi, I am currently using ZnClient to fetch data from a service behind "cloudflare" and sometimes the real/origin backend is unreachable/fails. Cloudflare has added additional[1] 5XX codes and ZnStatusLine>>#code: will signal an ZnUnknownHttpStatusCode because of that. I wonder how ZnClient

[Pharo-users] Problem compiling method source - genPushLiteral: out of range

Hello everyone, I'm trying to move some of our code from VA Smalltalk over to Pharo using a self-made importer and have encountered the following issue I need help with: A few of our methods are very large in size. For example, we have a method that creates a huge Dictionary with specific keys

Re: [Pharo-users] Parser failure on FFI pragmas declaration in Pharo 5

> > @Esteban: Would you accept a change to the FFI-Pharo5Compat to not use the > currentScope variable/reduce error checking? Or would you accept it in a > FFI-Pharo6Compat package? > I think it would help to be able to load the Nacl code in Pharo6 and then > fix it? But you can just switch

Re: [Pharo-users] YAML parser (2017)

Hi, Phil Back has kindly fixed the PetitYAML so it mostly works now. The only problem I've encountered was some weird misparsing of strings containing slashes, e.g. "5/". In any case: Install PetitParser (from Catalog or somewhere), load PetitYAML package (this is already loaded when loading

Re: [Pharo-users] Parser failure on FFI pragmas declaration in Pharo 5

> On 17. Aug 2017, at 19:37, Denis Kudriashov wrote: Hey! > Yes. > > Also simple solution can be to override compiler of problem classes to return > old compiler. > > I know it is better to rewrite code but it can be not simple task when there > are a lot of

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

> > What I think would have been good is to list all the updates that where done > between > releasing 6.0 and 6.1 *as part of the changelog* of 6.1 (even though they > were already > in the image that you got a minute before Pharo6.1 was released, as they > where released as > hot fixes

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

> On 24 Jul 2017, at 15:11, Hilaire wrote: > > Thanks guys. > > I hope it includes the fixes for the bugs impacting Dr. Geo. > Hello, I think there is a bit of a confusion of how we do fixed for Pharo6. I will explain: -> if people find bugs, they end up on the issue

Re: [Pharo-users] YAML parser (2017)

I am not looking for a complete implementation which is quite an effort but rather for a subset which does simple things such as parsing - a list of hashes (dictionaries), - a dictionary of dictionaries (nested to arbitrary depths), - multi-line comments --Hannes On 8/16/17, H. Hirzel