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

[Holger Freyther]

> On 18. Aug 2017, at 20:14, Sven Van Caekenberghe  wrote:
> 
> Hi Holger,
> 
> It is probably not a good idea to be too strict here. I committed the 
> following to #bleedingEdge


thank you!

holger

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

[Ben Coman]

> 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 (e.g. hobbyists or people exploring datasets.)

On Fri, Aug 18, 2017 at 10:36 PM, Marcus Denker 
wrote:

>
> 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 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/ (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
>
>
> 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  and
> then find the image number that corresponded to that release at
> 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/ 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).
>

For major.minor.hotfix versioning, maybe the hotfixes that pass CI could
accumulate in a list that is loaded similar to the old System > Software
Update method,
so hotfixes are available without without having to throw away an image -
i.e. a new download is only required for a "major.minor" update.

A user might individually select a hotfix, but the default list gives a
standard order to load them.  Each change to that default list is
essentially a ".hotfix" point release.   This may provide the mechanism to
provide more longevity of Pharo versions. As part of their CI, anyone can
download the major.minor release and then the default hotfix list (or their
own list).  Older Pharo versions would tend to become more
community-supported.

cheers -ben

Re: [Pharo-users] Pharo for Android

[Ricardo Pacheco]

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 support for sure but 
> Now you can use Pharo on Android.
>
> I do not know if we have a jenkins job :(
>
> https://github.com/sbragagnolo/pharo-android-wrapper
>
> Stef
>
> On Fri, Aug 18, 2017 at 5:00 PM, Ricardo Pacheco
>  wrote:
> > 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] GTInspect auto-update in raw view?

[Andrei Chis]

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 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  wrote:
> >>
> >> Hello Esteban,
> >>
> >> You can enable auto-refresh with: GTInspector enableStepRefresh
> >> For performance reasons it is disabled by default. If you are curious
> why
> >> I think Andrei could explain a bit more :)
> >>
> >>
> >> I want to know why is disabled and more than that, when will we be able
> to
> >> make it enabled by default, as before.
> >
> >
> > Mostly because it was finished just before the Pharo 6 release.
> > I'd say we can enable it by default for Pharo 7 and see if there are any
> > issues.
> >
> > Cheers,
> > Andrei
> >
> >>
> >>
> >> Esteban
> >>
> >>
> >> Cheers,
> >> Alex
> >>
> >> On 17 August 2017 at 00:56, Esteban A. Maringolo 
> >> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Is there a way to enable the auto-update of instance variables display
> in
> >>> the GTInspector?
> >>>
> >>> There are cases where the instance is nil, I then initialize it
> somehow,
> >>> but the variable is still displayed as nil.
> >>>
> >>> I know there is an "Update" button, which BTW should be labeled
> "refresh"
> >>> instead, to do it manually, but hey, this is Smalltalk, we invented
> MVC :D
> >>>
> >>> We can consider the previous as a feature, but what I think it is a bug
> >>> is that if the variable is nil, and later it is initialized, nil is
> still
> >>> displayed, but when clicked the nodes below it shows the variables of
> the
> >>> new object in the instance variable.
> >>>
> >>> E.g.
> >>> 
> >>>
> >>> Is this a bug or a feature?
> >>>
> >>> Regards!
> >>>
> >>> Esteban A. Maringolo
> >>
> >>
> >>
> >
>
>

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

[Peter Uhnak]

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 will get the latest version which is 60510, which is 6.1.

You can download previous versions here http://files.pharo.org/image/60/

Peter

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

[Peter Uhnak]

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 8/18/17, Peter Uhnak  wrote:
> > 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 PP from catalog).
> 
> I just installed Pillar and that pulled in PetitParser. Not sure if it
> is a good idea now to re-install PetitParser again.
> 
> In particular there is only PetitParser catalog entry for Pharo 5.0,
> not 6.0 or 6.1

I don't know about this, you'd have to ask the Moose team (or whoever is 
responsible for PetitParser now)

> 
> I assume that can directly load the PetitYAML from the repository instead.
> Where do I find it?

Open Monticello Browser, find PetitParser repository and open it, select 
PetitYAML package, select the latest version, right click and load.

Peter

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

[Stephane Ducasse]

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
> 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 off to a developer summer camp or
> something like that.
>
> I have found that once a developer gets to a certain level of competence,
> they can quickly (in a weekend?) get up to speed on the use of a new
> language / framework to get their project done.
>
> For a long time, I felt the sting of the “most popular language lists” as
> companies wanted to start all projects in PHP so that if the senior devs
> moved on, they could just hire some kids “cheap, just out of school” to work
> on the project.
>
> i do think there are lots of things about to change Pharo’s place in the
> world, especially the Pharo MOOC..
>
> there was one claim you made in that post that got me thinking
>
> ""No one else knows Smalltalk."
>
> So I wonder how many developers amount to "no one".
>
>
>
>
> 
> peace,
> sergio
> photographer, journalist, visionary
>
> Public Key: http://bit.ly/29z9fG0
> #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
> http://www.Village-Buzz.com
> http://www.ThoseOptimizeGuys.com
> http://www.coffee-black.com
> http://www.painlessfrugality.com
> http://www.twitter.com/sergio_101
> http://www.facebook.com/sergio101

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

[Stephane Ducasse]

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  wrote:
>>
>> Hello Esteban,
>>
>> You can enable auto-refresh with: GTInspector enableStepRefresh
>> For performance reasons it is disabled by default. If you are curious why
>> I think Andrei could explain a bit more :)
>>
>>
>> I want to know why is disabled and more than that, when will we be able to
>> make it enabled by default, as before.
>
>
> Mostly because it was finished just before the Pharo 6 release.
> I'd say we can enable it by default for Pharo 7 and see if there are any
> issues.
>
> Cheers,
> Andrei
>
>>
>>
>> Esteban
>>
>>
>> Cheers,
>> Alex
>>
>> On 17 August 2017 at 00:56, Esteban A. Maringolo 
>> wrote:
>>>
>>> Hi all,
>>>
>>> Is there a way to enable the auto-update of instance variables display in
>>> the GTInspector?
>>>
>>> There are cases where the instance is nil, I then initialize it somehow,
>>> but the variable is still displayed as nil.
>>>
>>> I know there is an "Update" button, which BTW should be labeled "refresh"
>>> instead, to do it manually, but hey, this is Smalltalk, we invented MVC :D
>>>
>>> We can consider the previous as a feature, but what I think it is a bug
>>> is that if the variable is nil, and later it is initialized, nil is still
>>> displayed, but when clicked the nodes below it shows the variables of the
>>> new object in the instance variable.
>>>
>>> E.g.
>>> 
>>>
>>> Is this a bug or a feature?
>>>
>>> Regards!
>>>
>>> Esteban A. Maringolo
>>
>>
>>
>

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

[Cyril Ferlicot]

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 Document'.
> PRPillarParser parse: wiki
>
>
> Or
>
> PRPillarParser parse: (FileSystem workingDirectory / 'foo.pillar')
> readStream
>
>
> and then
>
>
> PRHTMLWriter write: document
>
>
> This put together gives
>
> PRHTMLWriter write: (
> PRPillarParser parse: (FileSystem workingDirectory /
> 'welcome.pillar')
> )
>
>
> If I inspect the result of this expression I get the HTML string.
>
> Thank you Cyril. This is what I was looking for.
>
> --Hannes
>


Happy to see it still works :)

I know there was work on Pillar after I wrote this. Maybe there is some
functionalities that will need more than those simple examples. By I am not
sure and I know that Stephane want to simplify it further.
-- 
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

Re: [Pharo-users] Pharo for Android

[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 support for sure but 
Now you can use Pharo on Android.

I do not know if we have a jenkins job :(

https://github.com/sbragagnolo/pharo-android-wrapper

Stef

On Fri, Aug 18, 2017 at 5:00 PM, Ricardo Pacheco
 wrote:
> 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] [Ann] Data activism, visualization and storytelling with reproducible research for undergrad journalism and communication sciences students

[Stephane Ducasse]

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 posting).
>
> At mid September I'm going to give a little workshop at a local
> university for undergrad journalism and communication sciences students
> using the Pharo live coding environment [1] and Roassal agile
> visualization engine [2] combined with Grafoscopio[3]. We're going to
> retake our Twitter Data Selfies project[4], as is usual with our
> recurrent Data Week[5] hackathon+workshop.
>
> [1] http://pharo.org/
> [2] http://agilevisualization.com/
> [3] http://mutabit.com/grafoscopio/index.en.html
> [4] http://mutabit.com/offray/blog/en/entry/ds-twitter-mockup
> [5] http://mutabit.com/dataweek/
>
> Also as usual, we will make real time memories, via etherpads, and more
> elaborated thematic ones via interactive notebooks that we will be
> sharing with you in (Fossil) source repositories and other "pocket
> infrastructures", under a permissive and solidary copy(far)left license.
> I'll give you more details as we advance.
>
> Cheers,
>
> Offray
>
>

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

[H. Hirzel]

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 workingDirectory / 'foo.pillar')
readStream


and then


PRHTMLWriter write: document


This put together gives

PRHTMLWriter write: (
PRPillarParser parse: (FileSystem workingDirectory / 'welcome.pillar')
)


If I inspect the result of this expression I get the HTML string.

Thank you Cyril. This is what I was looking for.

--Hannes




On 8/18/17, Cyril Ferlicot  wrote:
> 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 tool. The welcome example taken
>> from this tutorial is:
>>
>> Pharo.exe Pillar.image pillar export --to=html
>> --outputFile=welcome welcome.pillar
>>
>> How can I run a command like this from within Pharo in a "playground"
>> (former workspace)?
>>
>> Later on I plan to construct a simple GUI with text boxes for Pillar
>> sources and have some buttons executing these commands.
>>
>> --Hannes
>>
>>
>
> I remember writing a part "Pillar from Pharo" in this doc. I'm not sure it
> is still up to date but you can try to check part 7 of the doc I sent.
> --
> Cyril Ferlicot
> https://ferlicot.fr
>
> http://www.synectique.eu
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France
>

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

[H. Hirzel]

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 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 PP from catalog).

I just installed Pillar and that pulled in PetitParser. Not sure if it
is a good idea now to re-install PetitParser again.

In particular there is only PetitParser catalog entry for Pharo 5.0,
not 6.0 or 6.1

I assume that can directly load the PetitYAML from the repository instead.
Where do I find it?


> And then parse your string
>
> ```
> PPYAMLGrammar parse: '
> language: c
> sudo: false
> cache:
>   directories:
> - opensmalltalk-vm/.thirdparty-cache
> git:
>   depth: "5"'.
> ```
>
>
> "Dictionary(
>   'cache'->a Dictionary(
>   'directories'->#('opensmalltalk-vm/.thirdparty-cache')
>   )
>   'git'->a Dictionary(
>   'depth'->'5'
>   )
>   'language'->'c'
>   'sudo'->'false'
> )"
>

Thank you for the example.

> Take a look at PPYAMLGrammarTest>>testTravisYml too.
>
> Peter
>

--Hannes

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

[Cyril Ferlicot]

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 tool. The welcome example taken
> from this tutorial is:
>
> Pharo.exe Pillar.image pillar export --to=html
> --outputFile=welcome welcome.pillar
>
> How can I run a command like this from within Pharo in a "playground"
> (former workspace)?
>
> Later on I plan to construct a simple GUI with text boxes for Pillar
> sources and have some buttons executing these commands.
>
> --Hannes
>
>

I remember writing a part "Pillar from Pharo" in this doc. I'm not sure it
is still up to date but you can try to check part 7 of the doc I sent.
-- 
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

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

[H. Hirzel]

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 pillar export --to=html
--outputFile=welcome welcome.pillar

How can I run a command like this from within Pharo in a "playground"
(former workspace)?

Later on I plan to construct a simple GUI with text boxes for Pillar
sources and have some buttons executing these commands.

--Hannes



On 8/18/17, Cyril Ferlicot  wrote:
> 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 menu to open the tool.
>>
>> How do I start using the tool?
>>
>> --Hannes
>>
>> Hi,
>
> I did not check if it is up to date but there is a tutorial here:
>
> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html
>
> I hope this can help you to begin.
>
> There is no tool actually to use Pillar, you write your files and then
> there is command lines to generate the output wanted.
> --
> Cyril Ferlicot
> https://ferlicot.fr
>
> http://www.synectique.eu
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France
>

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

[Cyril Ferlicot]

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 menu to open the tool.
>
> How do I start using the tool?
>
> --Hannes
>
> Hi,

I did not check if it is up to date but there is a tutorial here:

https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html

I hope this can help you to begin.

There is no tool actually to use Pillar, you write your files and then
there is command lines to generate the output wanted.
-- 
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

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

[H. Hirzel]

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 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 [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
>>
>
>

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

[Offray Vladimir Luna Cárdenas]

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 on-premise git.smalltalkhub.com, but it's just me. :-(
>
>

Is not just you. I try also to maintain my own critical infrastructure,
like DVCS using Fossil, and I'm a huge promoter/believer in community
own infrastructure. Would be really nice to have git.smalltalkhub.com
using Gogs ( https://gogs.io/ ). The issue is that we're a small
community with small resources to have our own infrastructure :-/.

Cheers,

Offray

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

[Peter Uhnak]

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 [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
> 

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

[H. Hirzel]

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 information is updated in the Pharo catalog browser in the
image. Is this correct?

HH

On 8/18/17, H. Hirzel  wrote:
> Hello
>
> Where do I find information how the  Pharo 6.1 catalog entries are
> maintained?
>
> Thank you in advance
>
> Hannes
>

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

[H. Hirzel]

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?

[Andrei Chis]

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 you are curious why
> I think Andrei could explain a bit more :)
>
>
> I want to know why is disabled and more than that, when will we be able to
> make it enabled by default, as before.
>

Mostly because it was finished just before the Pharo 6 release.
I'd say we can enable it by default for Pharo 7 and see if there are any
issues.

Cheers,
Andrei


>
> Esteban
>
>
> Cheers,
> Alex
>
> On 17 August 2017 at 00:56, Esteban A. Maringolo 
> wrote:
>
>> Hi all,
>>
>> Is there a way to enable the auto-update of instance variables display in
>> the GTInspector?
>>
>> There are cases where the instance is nil, I then initialize it somehow,
>> but the variable is still displayed as nil.
>>
>> I know there is an "Update" button, which BTW should be labeled "refresh"
>> instead, to do it manually, but hey, this is Smalltalk, we invented MVC :D
>>
>> We can consider the previous as a feature, but what I think it is a bug
>> is that if the variable is nil, and later it is initialized, nil is still
>> displayed, but when clicked the nodes below it shows the variables of the
>> new object in the instance variable.
>>
>> E.g.
>> 
>>
>> Is this a bug or a feature?
>>
>> Regards!
>>
>> Esteban A. Maringolo
>>
>
>
>

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

[H. Hirzel]

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

[Offray Vladimir Luna Cárdenas]

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 sciences students
using the Pharo live coding environment [1] and Roassal agile
visualization engine [2] combined with Grafoscopio[3]. We're going to
retake our Twitter Data Selfies project[4], as is usual with our
recurrent Data Week[5] hackathon+workshop.

[1] http://pharo.org/
[2] http://agilevisualization.com/
[3] http://mutabit.com/grafoscopio/index.en.html
[4] http://mutabit.com/offray/blog/en/entry/ds-twitter-mockup
[5] http://mutabit.com/dataweek/

Also as usual, we will make real time memories, via etherpads, and more
elaborated thematic ones via interactive notebooks that we will be
sharing with you in (Fossil) source repositories and other "pocket
infrastructures", under a permissive and solidary copy(far)left license.
I'll give you more details as we advance.

Cheers,

Offray

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

[H. Hirzel]

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 8/18/17, Marcus Denker  wrote:
>
>> 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 consent… e.g.. we should have a “61”
> directly here, too:
>
> 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
>
>
>

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

[Dimitris Chloupis]

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 that pretty much every other "popular language top 20" agrees
on , that "popular" languages , according to Tiobe Index top 20, dont even
make 50% of the actual languages people use. I have seen several language
ranks, like PYPI (which of course is highly biased in favour of Python) ,
poplang etc.

They all agree on this. The disagree on how much popular each language is ,
or how many developers are out there, but what they do not disagree on is
that popular languages take only half of the pie.

50% is far lower than expected, I expected top 10 to concentrate at least
70%.  The inability of the top 20 to do that just blows my mind.

The reason why there are not many people using Smalltalk is not because PHP
is popular. Quite the opposite , its not that popular in reality . The
reason is that even "unpopular" languages take only a pathetic 0-1% user
base there are still thousands upon thousands of them out there which is
what helps them to make that other 50%.

So the question that arises, and this is what surprised me , is not "why
people use popular languages" ?

But rather "why people use unpopular languages". Because if 1 in 2 coders
use languages that are less than 1% thats is kinda of big deal.

Which also collapses the stereotype of hype addicted coder. Instead we see
a coder that likes to try a variety of things.

Which in turn that Pharo is as "threatened" by popular language as much as
it is by unpopular languages.

Unpopular languages are not used so much on big project as main languages
but they are used for much more minor tasks.

We should not forget how Python started. It did not became popular because
it was used as a programming language. Actually its creator has been quoted
in the early history of Python stating that he designed the language only
to be a scripting language and to be used for very small task of only a few
lines of code. NOT , I repeat , NOT as a programming language. This is his
actual word.

Which is how he explained the minimalism of the syntax, he also targeted
Python to education to help people started coding.

World domination was never in his plans at all. Even later he still
insisted that Python should never been used as a replacement for C. Yet
scientists have done this very thing, as Python is extremely popular with
scientists.

This shows the power of small beginnings and I think this is also can teach
a very important lesson for Pharo that filling the small gaps , targeting
the minor tasks can be a massive boost to the popularity of the language.

Because more and more people used python for just a replacement to bash or
just for doing something simple, then started slowly and steadily using it
for more and more complex tasks.

This sneaky tactic can be a great way to promote pharo to your coworkers.
No need to convert your entire project to PHP. Just start using Pharo for
minor tasks, maybe clean up the code, analyse and visualise the code base
with Roassal , parse some text files etc.

This way your coworkers will stat seeing you using this obscure language
with no need for you to start ranting how amazing Pharo is and no need for
them to learn Pharo. Instead of seeing something that is too good to be
true they will see something that "just works".

Of course you did something much better and built an entire project on
Pharo which is why I think your blog posts is such a great advertisement
for Pharo. Well done :)

On Fri, Aug 18, 2017 at 3:55 PM sergio ruiz  wrote:

> 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 off to a developer summer
> camp or something like that.
>
> I have found that once a developer gets to a certain level of competence,
> they can quickly (in a weekend?) get up to speed on the use of a new
> language / framework to get their project done.
>
> For a long time, I felt the sting of the “most popular language lists” as
> companies wanted to start all projects in PHP so that if the senior devs
> moved on, they could just hire some kids “cheap, just out of school” to
> work on the project.
>
> i do think there are lots of things about to change Pharo’s place in the
> world, especially the Pharo MOOC..
>
> there was one claim you made in that post that got me thinking
>
> ""No one else knows Smalltalk."
>
> So I wonder how many developers amount to "no one".
>
>
>
>
> 
> peace,
> sergio
> photographer, journalist, visionary
>
> Public Key: http://bit.ly/29z9fG0
> #BitMessage BM-NBaswViL21xqgg9ST

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

[Aliaksei Syrel]

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 issues)


> sudo dpkg --add-architecture i386;
> sudo apt-get update;
> export PKG_CONFIG_PATH=/usr/lib/i386-linux-gnu/pkgconfig/;
>
> echo "Installing c++ libraries";
> sudo apt install libstdc++6:i386;
>
> echo "Installing GTK-2.0...";
> sudo apt-get install libgtk2.0-0:i386;
> echo "Installing GTK-3.0...";
> sudo apt-get install libgtk-3-0:i386;
>
> echo "Installing libGL...";
> sudo apt-get install libglu1-mesa:i386;


We have travis Build which is green:

https://github.com/syrel/Sparta/blob/master/.travis.yml
https://travis-ci.org/syrel/Sparta

On Windows users should install Visual C++ Redistributable for Visual
Studio 2015: (reduces binary size by >10mb)
https://www.microsoft.com/en-US/download/details.aspx?id=48145

On OSX works out of the box

Cheers,
Alex

On 18 August 2017 at 17:01, stephan  wrote:

> 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
>
>

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

[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

THERE_BE_DRAGONS_HERE
Warning
18 August 2017 4:56:07.371972 pm

VM: unix - i686 - linux-gnu - CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017
StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017
VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $

Image: Pharo6.0 [Latest update: #60510]

MozServices class>>start
	Receiver: MozServices
	Arguments and temporary variables: 

	Receiver's instance variables: 
		superclass: 	Object
		methodDict: 	a MethodDictionary(#ffiLibraryName->MozServices>>#ffiLibraryName )
		format: 	0
		layout: 	a FixedLayout
		instanceVariables: 	nil
		organization: 	a ClassOrganization
		subclasses: 	nil
		name: 	#MozServices
		classPool: 	a Dictionary()
		sharedPools: 	an OrderedCollection()
		environment: 	a SystemDictionary(lots of globals)
		category: 	#'Sparta-Moz2D'
		traitComposition: 	TMozLibrary
		localSelectors: 	a Set()
		isRunning: 	false


MozLibraryLinuxInstaller(MozLibraryInstaller)>>install
	Receiver: a MozLibraryLinuxInstaller
	Arguments and temporary variables: 
		pluginPath: 	File @ /home/stephan/Desktop/pharo6.1/bin/lib/pharo/5.0-20170720194...etc...
	Receiver's instance variables: 
a MozLibraryLinuxInstaller

MozLibraryInstaller class>>install
	Receiver: MozLibraryInstaller
	Arguments and temporary variables: 

	Receiver's instance variables: 
		superclass: 	Object
		methodDict: 	a MethodDictionary(#download->MozLibraryInstaller>>#download #downl...etc...
		format: 	0
		layout: 	a FixedLayout
		instanceVariables: 	nil
		organization: 	a ClassOrganization
		subclasses: 	{MozLibraryLinuxInstaller. MozLibraryMacInstaller. MozLibraryWindow...etc...
		name: 	#MozLibraryInstaller
		classPool: 	a Dictionary()
		sharedPools: 	an OrderedCollection()
		environment: 	a SystemDictionary(lots of globals)
		category: 	#'Sparta-Moz2D-Library'
		traitComposition: 	{}
		localSelectors: 	nil


[ :each | each method methodClass baseClass perform: each method selector ] in BaselineOfSparta>>postLoadSparta:
	Receiver: a BaselineOfSparta
	Arguments and temporary variables: 
		aSpecLoader: 	a MetacelloFetchingMCSpecLoader(linear load : 
	linear load : base...etc...
		pragmas: 	an OrderedCollection()
		each: 	
	Receiver's instance variables: 
		project: 	BaselineOfSparta(baseline [BaselineOfSparta], )


OrderedCollection>>do:
	Receiver: an OrderedCollection()
	Arguments and temporary variables: 
		aBlock: 	[ :each | each method methodClass baseClass perform: each method select...etc...
		index: 	1
	Receiver's instance variables: 
		array: 	an Array( nil nil nil nil nil nil nil nil nil)
		firstIndex: 	1
		lastIndex: 	1


BaselineOfSparta>>postLoadSparta:
	Receiver: a BaselineOfSparta
	Arguments and temporary variables: 
		aSpecLoader: 	a MetacelloFetchingMCSpecLoader(linear load : 
	linear load : base...etc...
		pragmas: 	an OrderedCollection()
	Receiver's instance variables: 
		project: 	BaselineOfSparta(baseline [BaselineOfSparta], )


[ :aLoader | self project configuration perform: selector with: aLoader ] in MetacelloMCVersionSpec(MetacelloSpec)>>doItBlock:
	Receiver: spec postLoadDoIt: #'postLoadSparta:'.
spec repository: 'github://syrel/sparta/src'.
spec ...etc...
	Arguments and temporary variables: 
		selector: 	#postLoadSparta:
		aLoader: 	a MetacelloFetchingMCSpecLoader(linear load : 
	linear load : baseline...etc...
	Receiver's instance variables: 
		project: 	BaselineOfSparta(baseline [BaselineOfSparta], )
		loader: 	a MetacelloLoadingMCSpecLoader
		mutable: 	nil
		versionString: 	'baseline'
		blessing: 	nil
		description: 	nil
		author: 	nil
		timestamp: 	nil
		preLoadDoIt: 	nil
		postLoadDoIt: 	spec value: #postLoadSparta:
		packageList: 	spec	add: [
		spec 
			name: 'core';
			includes: #('Sparta-Core' ...etc...
		importName: 	nil
		importArray: 	nil
		repositories: 	spec
repository: 'github://syrel/sparta/src'
		packages: 	nil


BlockClosure>>valueWithPossibleArgs:
	Receiver: [ :aLoader | self project configuration perform: selector with: aLoader ]
	Arguments and temporary variables: 
		anArray: 	an Array(a MetacelloFetchingMCSpecLoader(linear load : 
	linear load :...etc...
	Receiver's instance variables: 
		outerContext: 	MetacelloMCVersionSpec(MetacelloSpec)>>doItBlock:
		startpc: 	75
		numArgs: 	1


[ block
	valueWithPossibleArgs:
		(Array with: aPostloadDirective loader with: aPostloadDirective spec) ] in MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadPostloadDirective:
	Receiver: linear load : 
	linear load : baseline [BaselineOfSparta]
		load : Sparta-Core-Aliaksei

[Pharo-users] Pharo for Android

[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

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

[Esteban Lorenzano]

> 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 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

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

[Marcus Denker]

> 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 consent… e.g.. we should have a “61” directly 
here, too:

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

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

[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 :
> 
> 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
> 

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

[Marcus Denker]

> 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 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/  (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 
>  
> 

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  and then find 
> the image number that corresponded to that release at  
> 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/  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

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

[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 :).

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

[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

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

[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/  (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 
 

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  and then find the image 
number that corresponded to that release at  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/  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  wrote:
> 
> 
>> 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 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  
>> 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 ?)
>> 
> 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
> 

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

[Sven Van Caekenberghe]

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 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
> 
> 
> 
> 
> 
> 
> 

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

[Marcus Denker]

> 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 large in size. For example, we have a method 
> that creates a huge Dictionary with specific keys and values on startup and 
> stores it in a class variable for immediate access. 
> This method works fine in VA Smalltalk, but if I attempt to compile the same 
> source code in Pharo (programmatically or via copy paste using the interface) 
> I'm getting 'Error: genPushLiteral: index index 256 is out of range 0 to 255' 
> in OpalEncoderForV3PlusClosures. I'm getting the same error for some other 
> methods.
> 
> If I understand this correctly, the method simply exceeds the maximum number 
> of literals, but it works fine in VA Smalltalk. Is there a way to increase 
> this limit or bypass this issue without having to rework our implementation?
> 
Hello,

Can you try to change (in the preferences) the Bytecode Backend to “SistaV1” 
(this is the new byte code set that will be the default at some point in the 
future).

Marcus

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

[Marcus Denker]

> 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 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  
> 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 ?)
> 
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

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

[sergio ruiz]

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 off to a developer summer camp or something 
like that.

I have found that once a developer gets to a certain level of competence, they 
can quickly (in a weekend?) get up to speed on the use of a new language / 
framework to get their project done.

For a long time, I felt the sting of the “most popular language lists” as 
companies wanted to start all projects in PHP so that if the senior devs moved 
on, they could just hire some kids “cheap, just out of school” to work on the 
project.

i do think there are lots of things about to change Pharo’s place in the world, 
especially the Pharo MOOC..

there was one claim you made in that post that got me thinking

""No one else knows Smalltalk." 

So I wonder how many developers amount to "no one".





peace,
sergio
photographer, journalist, visionary

Public Key: http://bit.ly/29z9fG0
#BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
http://www.Village-Buzz.com
http://www.ThoseOptimizeGuys.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101

signature.asc
Description: Message signed with OpenPGP using AMPGpg

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

[Sven Van Caekenberghe]

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: Zinc-HTTP-SvenVanCaekenberghe.464

Allow for non-standard, not-predefined HTTP status line codes as long as they 
are between 100 and 599
===
Name: Zinc-Tests-SvenVanCaekenberghe.240
Author: SvenVanCaekenberghe
Time: 18 August 2017, 2:11:44.677301 pm
UUID: ad74fcc4-6713-0d00-bd89-fc2d0e6057cd
Ancestors: Zinc-Tests-SvenVanCaekenberghe.239

Allow for non-standard, not-predefined HTTP status line codes as long as they 
are between 100 and 599
===

Sven

> On 18 Aug 2017, at 11:44, Holger Freyther  wrote:
> 
> 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 should deal with these errors? IIRC the HTTP RFC 
> specifies error classes and without knowing what "525" means one can know 
> that the request was not successful and that the server is at "fault"?
> 
> Should ZnStatusLine handle an unknown code gracefully? E.g. >>#reason: seems 
> to do that already?
> 
> 
> have a nice weekend
> 
>   holger
> 
> [1] https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#Cloudflare

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

[Tim Mackinnon]

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  is the last 
point release, 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 ?)

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?

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? 

Tim

> On 18 Aug 2017, at 08:56, Marcus Denker  wrote:
> 
>> 
>> 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 before).
>> 
> 
> The changelog of things done between releasing 6.0 and the release of 6.1:
> 
> 20262 Update Iceberg to 0.5.4
>   https://pharo.fogbugz.com/f/cases/20262
> 
> 20268 update iceberg v0.5.5
>   https://pharo.fogbugz.com/f/cases/20268
>   
> 20226 TabMorph should use stepping mechanism for animating background building
>   https://pharo.fogbugz.com/f/cases/20226
> 
> 20238 Run out of memory the image hangs without out of memory warning
>   https://pharo.fogbugz.com/f/cases/20238
>   
> 20218 Master branch (Pharo 6) needs to be safely merged into development 
> branch (Pharo 7).
>   https://pharo.fogbugz.com/f/cases/20218
>   
> 20187 Request use of block in certain methods
>   https://pharo.fogbugz.com/f/cases/20187
> 
> 20188 Request representation of integer literal without float exponent
>   https://pharo.fogbugz.com/f/cases/20188
> 
> 20182 Extra dot in literal array
>   https://pharo.fogbugz.com/f/cases/20182
> 
> 18760 Failing test: WeakAnnouncerTest>>#testNoDeadWeakSubscriptions
>   https://pharo.fogbugz.com/f/cases/18760
> 
> 20186 Request removal of extra statement separators (dot)
>   https://pharo.fogbugz.com/f/cases/20186
>   
> 20185 Request pipe after block argments
>   https://pharo.fogbugz.com/f/cases/20185
> 
> 20183 TraitDescription>>fileOutLocalMethodsInCategory:on: method temp var 
> name overlap
>   https://pharo.fogbugz.com/f/cases/20183
> 
> 20184 Request space between argument and selector in StdioStream>>next:
>   https://pharo.fogbugz.com/f/cases/20184
>   
> 20167 Regression with PNGReaderWriter in P6
>   https://pharo.fogbugz.com/f/cases/20167
> 
> 20198 inner structure access does not work on multiple architecture
>   https://pharo.fogbugz.com/f/cases/20198
>   
> 20110 AllocationTest>>#testOutOfMemorySignal not well suited to 64-bit
>   https://pharo.fogbugz.com/f/cases/20110
> 
> 20096 Add script pragma to SpaceTally>>printSpaceAnalysis
>   https://pharo.fogbugz.com/f/cases/20096
> 
> 20174 In the debug halo of a morph: clicking on "inspect morph" and "explore 
> morph" bring up the same window.
>   https://pharo.fogbugz.com/f/cases/20174
>   
> 20093 Missing source stamp makes changes hard to view
>   https://pharo.fogbugz.com/f/cases/20093
> 
> 20148 transforming deprecations should take #showWarning into account
>   https://pharo.fogbugz.com/f/cases/20148
>   
> 20146 ZnHTTPSTests>>#testGetPharoVersion started to fail
>   https://pharo.fogbugz.com/f/cases/20146
>   
> 
> 
> 

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

[Pierce Ng]

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 runtime. The image, in turn holds the encryption key

Take a look at SpsSplitPasswordStore, which is a simple secret splitter.

  http://ss3.gemtalksystems.com/ss/SpsSplitPasswordStore.html/
  http://samadhiweb.com/blog/2013.08.11.splitpasswordstore.html

Can be adapted to encrypt/decrypt the secret, with the cipher key also split,
perhaps with one part stored in the image and another part fetched online from
somewhere.

I haven't touched the code in a while, but the Pharo 5 image that runs my blog
is using this for the RFBServer passwords.

Pierce

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

[Henrik Sperre Johansen]

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
http://forum.world.st/More-than-256-literals-referenced-td4676669.html#a4676972

One alternative is to change the compiler to create a literal array to hold
all literals > 255 and rewrite accesses to indexes above 254 as something
like 
genPushLiteral: 255
pushLiteral #at:
pushConst: X
messageSend
, but as long as we're talking about a single digit number of cases, and not
translating 200+ UI specs, it is probably a lot easier (albeit, maybe a
little slower) to rewrite the code in a way which works in both dialects
without using a large number of literals, say:

MyClass class >> #initializeStaticVals
dict := Dictionary new.
initializerPairs := #(
Key1 2 
Key2 4
).
1 to: initializerPairs size by: 2 do: [:ix | dict at: (initializerPairs at:
ix) put: (initializerPairs at: ix +1)].
MyClassVar := dict.

(Haven't seen a support layer package for VA, sorry)

Cheers,
Henry



--
View this message in context: 
http://forum.world.st/Problem-compiling-method-source-genPushLiteral-out-of-range-tp4961986p4962020.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

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

[Holger Freyther]

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 should deal with these errors? IIRC the HTTP RFC 
specifies error classes and without knowing what "525" means one can know that 
the request was not successful and that the server is at "fault"?

Should ZnStatusLine handle an unknown code gracefully? E.g. >>#reason: seems to 
do that already?


have a nice weekend

holger

[1] https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#Cloudflare

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

[Patrick Scherer]

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 and values on startup and
stores it in a class variable for immediate access.
This method works fine in VA Smalltalk, but if I attempt to compile the
same source code in Pharo (programmatically or via copy paste using the
interface) I'm getting '*Error: genPushLiteral: index index 256 is out of
range 0 to 255*' in OpalEncoderForV3PlusClosures. I'm getting the same
error for some other methods.

If I understand this correctly, the method simply exceeds the maximum
number of literals, but it works fine in VA Smalltalk. Is there a way to
increase this limit or bypass this issue without having to rework our
implementation?


Offtopic: Does anybody if there is a package which adds a support layer for
imported VA Smalltalk code? I know there is one for Pharo->VA on
VASTGoodies but I couldn't find one for the other way around.

Kind regards,
Patrick Scherer

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

[Denis Kudriashov]

>
> @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 default compiler. Is not works for you?

2017-08-18 10:20 GMT+02:00 Holger Freyther :

>
> > 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 ffi-methods.
>
>
> I ran into this problem with the wonderful (as it had a SHA256
> implementation) NaCl bindings.
>
>
> Pharo5:
>  * RBParser still has the currentScope variable and can import it
>  * Syntax highlighting ends in an exception (which I disabled)
>
> Pharo6:
>  * RBParser doesn't have currentScope anymore so I patched it out
>  * Syntax highlighting seems to work fine
>
>
> @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?
>
>
> what do you think?
>
> holger
>

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

[Peter Uhnak]

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 PP from catalog).

And then parse your string

```
PPYAMLGrammar parse: '
language: c
sudo: false
cache:
  directories:
- opensmalltalk-vm/.thirdparty-cache
git:
  depth: "5"'.
```


"Dictionary(
'cache'->a Dictionary(
'directories'->#('opensmalltalk-vm/.thirdparty-cache')
)
'git'->a Dictionary(
'depth'->'5'
)
'language'->'c'
'sudo'->'false'
)"


Take a look at PPYAMLGrammarTest>>testTravisYml too.

Peter



On Fri, Aug 18, 2017 at 09:45:00AM +0200, H. Hirzel wrote:
> 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  wrote:
> > Are there any news about a YAML parser for Pharo 5 / 6.1?
> >
> > --Hannes
> >
> > On 5/29/17, Peter Uhnak  wrote:
> >> Hi,
> >>
> >> do we have a working parser for YAML?
> >>
> >> There's PPYAMLGrammar (in PetitParser), however it doesn't seem to work
> >> in
> >> Pharo 6 at all (not even tests pass).
> >> In Pharo 5 the tests are green, but using it on YAML content still
> >> fails...
> >> with small fix I managed it to "pass", however the output seems to be a
> >> very
> >> fine-grained AST decomposition and not the expected output
> >> (dictionaries/arrays).
> >>
> >> So do we have some else/working?
> >>
> >> YAML specs have BNF descriptions, so maybe SmaCC can generate it? (I
> >> don't
> >> know SmaCC, so maybe this is not how it works.)
> >>
> >> Thanks,
> >> Peter
> >>
> >>
> >
> 

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

[Holger Freyther]

> 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 ffi-methods.


I ran into this problem with the wonderful (as it had a SHA256 implementation) 
NaCl bindings.


Pharo5:
 * RBParser still has the currentScope variable and can import it
 * Syntax highlighting ends in an exception (which I disabled)

Pharo6:
 * RBParser doesn't have currentScope anymore so I patched it out
 * Syntax highlighting seems to work fine


@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?


what do you think?

holger

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

[Marcus Denker]

> 
> 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 before).
> 

The changelog of things done between releasing 6.0 and the release of 6.1:

20262 Update Iceberg to 0.5.4
https://pharo.fogbugz.com/f/cases/20262

20268 update iceberg v0.5.5
https://pharo.fogbugz.com/f/cases/20268

20226 TabMorph should use stepping mechanism for animating background building
https://pharo.fogbugz.com/f/cases/20226

20238 Run out of memory the image hangs without out of memory warning
https://pharo.fogbugz.com/f/cases/20238

20218 Master branch (Pharo 6) needs to be safely merged into development branch 
(Pharo 7).
https://pharo.fogbugz.com/f/cases/20218

20187 Request use of block in certain methods
https://pharo.fogbugz.com/f/cases/20187

20188 Request representation of integer literal without float exponent
https://pharo.fogbugz.com/f/cases/20188

20182 Extra dot in literal array
https://pharo.fogbugz.com/f/cases/20182

18760 Failing test: WeakAnnouncerTest>>#testNoDeadWeakSubscriptions
https://pharo.fogbugz.com/f/cases/18760

20186 Request removal of extra statement separators (dot)
https://pharo.fogbugz.com/f/cases/20186

20185 Request pipe after block argments
https://pharo.fogbugz.com/f/cases/20185

20183 TraitDescription>>fileOutLocalMethodsInCategory:on: method temp var name 
overlap
https://pharo.fogbugz.com/f/cases/20183

20184 Request space between argument and selector in StdioStream>>next:
https://pharo.fogbugz.com/f/cases/20184

20167 Regression with PNGReaderWriter in P6
https://pharo.fogbugz.com/f/cases/20167

20198 inner structure access does not work on multiple architecture
https://pharo.fogbugz.com/f/cases/20198

20110 AllocationTest>>#testOutOfMemorySignal not well suited to 64-bit
https://pharo.fogbugz.com/f/cases/20110

20096 Add script pragma to SpaceTally>>printSpaceAnalysis
https://pharo.fogbugz.com/f/cases/20096

20174 In the debug halo of a morph: clicking on "inspect morph" and "explore 
morph" bring up the same window.
https://pharo.fogbugz.com/f/cases/20174

20093 Missing source stamp makes changes hard to view
https://pharo.fogbugz.com/f/cases/20093

20148 transforming deprecations should take #showWarning into account
https://pharo.fogbugz.com/f/cases/20148

20146 ZnHTTPSTests>>#testGetPharoVersion started to fail
https://pharo.fogbugz.com/f/cases/20146

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

[Marcus Denker]

> 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 tracker
-> Some of these get fixed. If a fix is ready, we will integrate it very
quickly. This means that only the update number changes, not the
main version number (these are bug fixes, they do not change APIs).

A good name for these updates is “hot fixes”.
They are announced to the dev list only with the automatic lists that are send
for each update.

We integrated already quite some into Pharo6 like that. The release was I think
around #60500, while 6.1 was done around #60510

Then there are cases that are more grave: 6.1 was done because it contains 
bigger
changes.

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 before).

Now if the image includes all fixes needed for DrGeo depends on a) has that 
issue been
fixed and b) if yes was all massaging done to have the update actually 
integrated.

(what does not help is that it is holiday time, e.g. I did not read emails and 
did *nothing*
 from end of Juli to yesterday, this does not help but was really, really 
needed).

Marcus

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

[H. Hirzel]

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  wrote:
> Are there any news about a YAML parser for Pharo 5 / 6.1?
>
> --Hannes
>
> On 5/29/17, Peter Uhnak  wrote:
>> Hi,
>>
>> do we have a working parser for YAML?
>>
>> There's PPYAMLGrammar (in PetitParser), however it doesn't seem to work
>> in
>> Pharo 6 at all (not even tests pass).
>> In Pharo 5 the tests are green, but using it on YAML content still
>> fails...
>> with small fix I managed it to "pass", however the output seems to be a
>> very
>> fine-grained AST decomposition and not the expected output
>> (dictionaries/arrays).
>>
>> So do we have some else/working?
>>
>> YAML specs have BNF descriptions, so maybe SmaCC can generate it? (I
>> don't
>> know SmaCC, so maybe this is not how it works.)
>>
>> Thanks,
>> Peter
>>
>>
>