Re: [Pharo-dev] Lowering the pain of newbies

Is this a goal we can all share for 7.0? Sort out the expert tools (like git etc), but equally enable that simplicity you expect for a child/newbie/expert... I'm in! Tim Sent from my iPhone > On 17 Aug 2017, at 20:52, Stephane Ducasse wrote: > > Hi guys > > my son

Re: [Pharo-dev] Lowering the pain of newbies

On Thu, Aug 17, 2017 at 05:23:28PM -0300, Esteban A. Maringolo wrote: > What are the odds? 100%, this _always_ happens to some student. (You just need to omit a single semicolon and you've just broke it.)

Re: [Pharo-dev] Pharo behind ALLSTOCKER marketplace

Thank you for the very enlightening post. A quick followup question regarding your transaction data using an RDB and complex queries using Neo4j. Do you have a mechanism for maintaining/synchronizing data updated via transactions (into the RDB) in the the Neo4j database? Tom -- View this

Re: [Pharo-dev] Lowering the pain of newbies

What are the odds? The ability to break a system in a few steps seems to be an inherited trait. My daughter (2 years old) was randomly punching my keyboard and caused a segfault that I couldn't reproduce afterwards. Regards! Esteban A. Maringolo 2017-08-17 16:52 GMT-03:00 Stephane Ducasse

Re: [Pharo-dev] Lowering the pain of newbies

On jeu. 17 août 2017 at 21:53, Stephane Ducasse wrote: > Hi guys > > my son coded in Pharo 60 > > testGuessUrlPart > > |dg8| > dg8 := GameItem new; > name: 'Dragon Quest VIII : Journey Of The Cursed King'; > console: 'PS2'.

[Pharo-dev] Lowering the pain of newbies

Hi guys my son coded in Pharo 60 testGuessUrlPart |dg8| dg8 := GameItem new; name: 'Dragon Quest VIII : Journey Of The Cursed King'; console: 'PS2'. self assert: dg8 guessUrlPart equals: 'dragonquestviiijourneyofthecursedking' and guess

Re: [Pharo-dev] 19609 FileReference>>base should be before last separator

2017-08-17 20:43 GMT+02:00 Eliot Miranda : > Hi Stef, > > On Thu, Aug 17, 2017 at 8:08 AM, Stephane Ducasse > wrote: > >> I do not know but I imagine that I added basenameWithoutExtension because >> I found the name much much clearer. I would

Re: [Pharo-dev] 19609 FileReference>>base should be before last separator

Hi Stef, On Thu, Aug 17, 2017 at 8:08 AM, Stephane Ducasse wrote: > I do not know but I imagine that I added basenameWithoutExtension because > I found the name much much clearer. I would have never guessed that > base is the basename without the extension. > While

Re: [Pharo-dev] Adding build info into pharo runtime

Hi Guille,   looks good - I approved the change on the PR. Thanks a lot and have a happy holiday! Regards T.   Gesendet: Donnerstag, 17. August 2017 um 17:59 Uhr Von: "Guillermo Polito" An: "Discusses Development of Pharo" Betreff: 

Re: [Pharo-dev] ZnEasy question

Hi Milton, > On 5 Aug 2017, at 03:15, milton mamani wrote: > > Hi to all > > I want to use the next instruction in my code > > response := ZnEasy get: > 'https://archive.softwareheritage.org/api/1/origin/git/url/https://github.com/hylang/hy'. > response. > > The

Re: [Pharo-dev] Initial Feedback on Pharo 7 contribution process

> On 17 Aug 2017, at 17:37, Alistair Grant wrote: > > On Thu, Aug 17, 2017 at 11:54:57AM +0200, Pavel Krivanek wrote: >> >> >> 2017-08-17 10:44 GMT+02:00 Torsten Bergmann : >> >>Hi, >> >>even when contributing to Pharo 7.0 is still very very

[Pharo-dev] Adding build info into pharo runtime

Hi all, as asked by Torsten, I spent some time adding build info into the pharo runtime. https://pharo.fogbugz.com/f/cases/20321/Add-build-number-to-SystemVersion https://github.com/pharo-project/pharo/pull/212 Tests are green

Re: [Pharo-dev] 19609 FileReference>>base should be before last separator

Hi Stef, On Thu, Aug 17, 2017 at 05:08:40PM +0200, Stephane Ducasse wrote: > I do not know but I imagine that I added basenameWithoutExtension because > I found the name much much clearer. I would have never guessed that > base is the basename without the extension. > > Stef Thanks for the

Re: [Pharo-dev] Initial Feedback on Pharo 7 contribution process

On Thu, Aug 17, 2017 at 11:54:57AM +0200, Pavel Krivanek wrote: > > > 2017-08-17 10:44 GMT+02:00 Torsten Bergmann : > > Hi, > > even when contributing to Pharo 7.0 is still very very cumbersome I was > able > to sort out most of the problems and contribute

Re: [Pharo-dev] Issue that may break Epicea

Ahh!! Yes, there is a test that fails from time to time, but nothing to do with that PR I think. Actually, Martin if you have some time to check, there is a cyclothymic test that fails randomly on the CI. Maybe the test needs to be more robust. On Thu, Aug 17, 2017 at 5:03 PM, Stephane Ducasse

Re: [Pharo-dev] 19609 FileReference>>base should be before last separator

I do not know but I imagine that I added basenameWithoutExtension because I found the name much much clearer. I would have never guessed that base is the basename without the extension. Stef On Wed, Aug 16, 2017 at 9:46 PM, Alistair Grant wrote: > Hi All, > > I've just

Re: [Pharo-dev] Issue that may break Epicea

I do not know but tests broke when I integrated the changes. On Thu, Aug 17, 2017 at 10:59 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Why would it break epicea? > > There is no major change in API. Only the method #createDirectory is > removed, but the only users are internal to

Re: [Pharo-dev] [Pharo-users] including Pillar in Pharo image by default

I remember my 10 year self struggling learning to code basic back in 1988 on an Amstrad CPC 6128 with Locomotive Basic that required entering line numbers before the code statement. IDEs , code editors and what else were unheard of for me at least and even if they did exist would be nowhere near

Re: [Pharo-dev] [Pharo-users] including Pillar in Pharo image by default

On Thu, Aug 17, 2017 at 4:25 PM Esteban Lorenzano wrote: > hi Dimitris (good to see you around ;) ), > > Not going anywhere , just taking a break from Pharo :) > thing is… we want to improve our tools. > > great > And improve tools sometime means to add stuff (I’m not

Re: [Pharo-dev] [Pharo-users] including Pillar in Pharo image by default

Got an architecture discussion with a client this morning and a lot of pain they face is that there are too many choices out there on some platforms. A batteries included distro with one good framework doing its thing nicely if really a good thing to have. It reduces the amount of choice and

Re: [Pharo-dev] Can we have subclasses of Process?

EventualProcess is in eventual_test [*], as example. Do not run RefsTest>>#testFailedArithmaticwithEventualArgument or will segfault vm. - HH [*] - http://www.squeaksource.com/TurquoiseTesting/eventual_test-hh.4.mcz On Thu, Aug 17, 2017 at 08:33, Guillermo Polito

Re: [Pharo-dev] Issue that may break Epicea

Hm, I'll take it into account anyway, thanks. I miss coding in Pharo! I have to reserve some aftenoon to work in some epicea open issues. Cheers, Martin On Thu, Aug 17, 2017 at 5:59 AM, Guillermo Polito wrote: > Why would it break epicea? > > There is no major change

Re: [Pharo-dev] [Pharo-users] including Pillar in Pharo image by default

> On 17 Aug 2017, at 15:24, Esteban Lorenzano wrote: > > hi Dimitris (good to see you around ;) ), > > thing is… we want to improve our tools. > > And improve tools sometime means to add stuff (I’m not very happy with it > either, I would like to remove more than what I

Re: [Pharo-dev] [Pharo-users] including Pillar in Pharo image by default

hi Dimitris (good to see you around ;) ), thing is… we want to improve our tools. And improve tools sometime means to add stuff (I’m not very happy with it either, I would like to remove more than what I add, but it is like that). For example, if we want to have good class comments, we need

Re: [Pharo-dev] Path * '' vs. Path workingDirectory

On Mon, Aug 14, 2017 at 4:11 PM, Alistair Grant wrote: > Hi Guille, > > Thanks for your reply. > > > On Mon, Aug 14, 2017 at 01:44:41PM +0200, Guillermo Polito wrote: > > > > > > On Sun, Aug 13, 2017 at 5:54 PM, Alistair Grant > wrote: > > > >

Re: [Pharo-dev] Can we have subclasses of Process?

I think there is no technical limitation for it, AFAIK, the VM never checks the class of a process. I also proposed something like that in this paper: http://guillep.github.io/files/publications/Poli14b-IWST-GlobalStateClassification.pdf On Thu, Aug 17, 2017 at 2:24 PM, Max Leske

Re: [Pharo-dev] Can we have subclasses of Process?

I've used subclasses of process for the debugger stuff without problems. Max On 17 August 2017 at 14:05:14, Denis Kudriashov (dionisi...@gmail.com) wrote: Hi. Is it allowed to subclass Process? I remember that there were some problems with it but I could not find any information. Generally

[Pharo-dev] Can we have subclasses of Process?

Hi. Is it allowed to subclass Process? I remember that there were some problems with it but I could not find any information. Generally I think about system processes which can be represented by concrete subclasses. For example explicit UIProcess can be used to remove many #isUIProcess

Re: [Pharo-dev] [Pharo-users] including Pillar in Pharo image by default

Is it really necessary ? I am more a modular guy , I would love to get an image that 0.1% the size of the current one and offer me a convenient package manager to install the tools I like. I have used Pillar ALOT probably more than any other Pharo library because I was doing Pharo documentation

Re: [Pharo-dev] @About posting here

Could not agree more with entirety of your post. Especially the part of the massive improvement of Pharo version 1 vs 6 are like and day. Documentation wise even Unreal with its massive community and one of the most profitable game companies pouring massive resources has many doc problems. In

Re: [Pharo-dev] FileSystem fix integration

FileSystem needs love, Thanks! On Wed, Aug 16, 2017 at 9:22 PM, Alistair Grant wrote: > Hi Stef, > > On Wed, Aug 16, 2017 at 08:43:24PM +0200, Stephane Ducasse wrote: > > May be you already see it but > > - https://pharo.fogbugz.com/f/cases/19609/FileReference- >

Re: [Pharo-dev] Initial Feedback on Pharo 7 contribution process

Hi, > On 17 Aug 2017, at 11:28, Guillermo Polito wrote: > > > > On Thu, Aug 17, 2017 at 10:44 AM, Torsten Bergmann > wrote: > Hi, > > even when contributing to Pharo 7.0 is still very very cumbersome I was able > to sort

Re: [Pharo-dev] Initial Feedback on Pharo 7 contribution process

2017-08-17 10:44 GMT+02:00 Torsten Bergmann : > Hi, > > even when contributing to Pharo 7.0 is still very very cumbersome I was > able > to sort out most of the problems and contribute already a few smaller > things. > > Unfortunately there is not much communication on what is

Re: [Pharo-dev] Initial Feedback on Pharo 7 contribution process

On Thu, Aug 17, 2017 at 10:44 AM, Torsten Bergmann wrote: > Hi, > > even when contributing to Pharo 7.0 is still very very cumbersome I was > able > to sort out most of the problems and contribute already a few smaller > things. > > Unfortunately there is not much communication

Re: [Pharo-dev] Issue that may break Epicea

Why would it break epicea? There is no major change in API. Only the method #createDirectory is removed, but the only users are internal to the library. In my latest image there are no Epicea users of it. On Wed, Aug 16, 2017 at 8:59 PM, Stephane Ducasse wrote: > Hi

[Pharo-dev] Initial Feedback on Pharo 7 contribution process

Hi, even when contributing to Pharo 7.0 is still very very cumbersome I was able to sort out most of the problems and contribute already a few smaller things. Unfortunately there is not much communication on what is currently in the pipe or planned on easing the process - which can easily lead

Re: [Pharo-dev] [Pharo-users] including Pillar in Pharo image by default

Even though I've initiated this discussion I kind of stopped reading because everyone started discussing completely unrelated things... The initial point was "we are using github/gitlab more and more, lets leverage it more" New, lets separate the concepts at play here... "Pillar -