[Pharo-users] Iceberg needs to gracefully revert to readonly

Hello! IMNSHO, now that Iceberg has three vendor-specific protocol (and before as well, because of people like me who do not have github account), Iceberg needs to gracefully revert to readonly access in case credentials are not present or do not allow full access to repository. This is prim

Re: [Pharo-users] Critical issues for Dr. Geo on P6

I don't share your enthusiasm. I once set up a satisfactory build environment for DrGeo, based on P3. As long as I stay with P3, I can concentrate on DrGeo code: write the code, then fire up a build script to deploy the application. Now porting to P6 is a pain: the infrastructure to deploy a d

Re: [Pharo-users] Critical issues for Dr. Geo on P6

On Fri, Jul 28, 2017 at 9:34 AM, Hilaire wrote: > I don't share your enthusiasm. > > I once set up a satisfactory build environment for DrGeo, based on P3. As > long as I stay with P3, I can concentrate on DrGeo code: write the code, > then fire up a build script to deploy the application. Now po

[Pharo-users] Shameful advertisement

Hi all, I was talking about Twitter in my previous email. This is a nice way to advertise the work of the community to others communities. Now some **shameful advertisement** : you can subscribe to my Twitter account here: https://twitter.com/SergeStinckwich I try my best to publish info about P

Re: [Pharo-users] Shameful advertisement

Hi Serge, Just wanted to say that you guys do a really nice job of advocating for Pharo and promoting it :). I joined the association now and will be sure to plug Pharo. It's great. I wouldn't build my current application at all if I didn't have Pharo/Glamour/Roassal as a base... it would be too

[Pharo-users] [ANN] Mustache moved to github

In the spirit of git notification…I moved mustache to github. https://github.com/noha/mustache Enjoy! Norbert

Re: [Pharo-users] Critical issues for Dr. Geo on P6

Just to chip in - I hope we can get past this bump (and I think it is a bump). I am actually ecstatic that recent improvements - a 64bit vm, a minimal image and git integration, have opened the door to Pharo working on AWS Lambda. Also having a CI system to help crank these things out is also a

Re: [Pharo-users] Critical issues for Dr. Geo on P6

Hilaire We invested 3 years of PhD of Guillermo + 8 months of hard work of christophe and guillermo. Pavel spent years to produce the mini image and now with the bootstrap it is opening a lot of possibilities. We will do it and it will work. And ***I LOVE THEIR WORK***. I DREAMED about it more tha

[Pharo-users] BaselineOfXxx equivalent of npm's devDependencies

Hello! I'd like to ask what is the equivalent of devDependencies (dependencies to be loaded only when developing, but not when in profuction / used as a dependency) of a baseline. My baseline method looks like: baseline: spec spec for: #common do: [ spec package: 'Towergame' wi

Re: [Pharo-users] Critical issues for Dr. Geo on P6

Changing too many things at once is indeed annoying. Now, I am ready to live with that but at one point, I think that we will have to move to something like I see done in other fast evolving ecosystems. In Hadoop for example, Hortonworks (a distribution) moved to a set of slow evolving substrate

Re: [Pharo-users] Critical issues for Dr. Geo on P6

> On 28 Jul 2017, at 15:13, p...@highoctane.be wrote: > > Changing too many things at once is indeed annoying. > > Now, I am ready to live with that but at one point, I think that we will have > to move to something like I see done in other fast evolving ecosystems. > > In Hadoop for example,

Re: [Pharo-users] BaselineOfXxx equivalent of npm's devDependencies

You need to specify groups for your project: spec group: 'default' with: #('Core' 'Tests' ); group: 'Core' with: #('Towergame' ); group: 'Tests' with: #('Towergame-Tests' 'Mocketry') Then your script will load default group with everything. And to load Core group use "load: #(Core)" instread of

Re: [Pharo-users] BaselineOfXxx equivalent of npm's devDependencies

And if you really have Towergame-Tests package then you will probably define it as spec package: 'Towergame-Tests' with: [ spec requires: #('Towergame' 'Mocketry') ]. And then Tests group can include only Towergame-Tests package because Mocketry will be loaded as dependency. 2017-07-28 15:39

Re: [Pharo-users] BaselineOfXxx equivalent of npm's devDependencies

On July 28, 2017 3:41:37 PM GMT+02:00, Denis Kudriashov wrote: >And if you really have Towergame-Tests package then you will probably >define it as > > spec package: 'Towergame-Tests' with: [ spec requires: #('Towergame' >'Mocketry') ]. > >And then Tests group can include only Towergame-Tests

Re: [Pharo-users] BaselineOfXxx equivalent of npm's devDependencies

On July 28, 2017 3:41:37 PM GMT+02:00, Denis Kudriashov wrote: >And if you really have Towergame-Tests package then you will probably >define it as > > spec package: 'Towergame-Tests' with: [ spec requires: #('Towergame' >'Mocketry') ]. > >And then Tests group can include only Towergame-Tests

Re: [Pharo-users] How to calculate someone's age elegantly? Does Duration work?

It still works, probably because dayOfMonth is not what you expected at first glance. For a date, you have 3 accessors, and i think you were expecting #dayNumber (January third, 1990) day. "Wednesday". (January third, 1990) dayOfMonth. "January 3" (January third, 1990) dayNumber. "3" On 27 Jul

Re: [Pharo-users] Critical issues for Dr. Geo on P6

Changes is ok. What annoying is announced new feature of P6, but not palpable for common mortal as me (whose main occupation is teaching to teenagers and programming a hobby): * Pharo can now be bootstrapped from source code managed by Git Will a new Pharo user entering Pharo programming ge

Re: [Pharo-users] Critical issues for Dr. Geo on P6

Serge, The only reason I decided to port DrGeo from Squeak to Pharo is because the project wanted to be business centric with features evolution. Changes was not annoying me, it is one reason I decided to switch to Pharo. But still after many years, I find Pharo frustrating for one willing to

Re: [Pharo-users] Critical issues for Dr. Geo on P6

The main problem is DrGeo is one a few software in the community to be deployed as a desktop app. All the others are dev software (Calypso, Roassal, MOOSE) or web-based app that don't need specific work for deployment. I need to deployed simulation engines that we are building with my team outs

Re: [Pharo-users] Critical issues for Dr. Geo on P6

On Fri, Jul 28, 2017 at 3:25 PM, Sven Van Caekenberghe wrote: > > > On 28 Jul 2017, at 15:13, p...@highoctane.be wrote: > > > > Changing too many things at once is indeed annoying. > > > > Now, I am ready to live with that but at one point, I think that we will > have to move to something like I

Re: [Pharo-users] How to calculate someone's age elegantly? Does Duration work?

Julián Sorry, I should have checked my facts before sounding off. I think defining dayOfMonth in the way you show is very counter-intuitive, but that is the definition and I should have checked. From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of Julián Maestri Se

Re: [Pharo-users] How to calculate someone's age elegantly? Does Duration work?

This continues to be a fascination little problem with many angles and solutions. Tim Sent from my iPhone > On 28 Jul 2017, at 21:31, PBKResearch wrote: > > Julián > > Sorry, I should have checked my facts before sounding off. I think defining > dayOfMonth in the way you show is very count

[Pharo-users] Pharo Seaside RESTful services pragma question

I am new to Pharo/Seaside and it has been a long time since I have used Smalltalk. I am trying to make a RESTful service and can’t get the pragmas to work the way I think it should. (This might be the problem already). Ie Here is my list method within class TeamMembers which is a direct subclas