Re: [Pharo-dev] call for help: answer on HN :)

Stephane Ducasse-3 wrote > I told them NOT to use github. > I told them that Bloc was alpha. I wonder if we could make those points more explicit. Maybe a welcome window disclaimer for Iceberg, since it's preinstalled? - Cheers, Sean -- Sent from:

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

Sorry for jumping in. I wasn't aware of a patch. Changing tz on Date seems like a mistake but I haven't been paying close attention to the reasoning behind the change. I defer. On Mon, Apr 9, 2018 at 2:20 PM, Sean P. DeNigris wrote: > Ron Teitelbaum wrote > >

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

I think #= is a bad selector for Date and should be avoided when determining whether something happens on a date, or whether two dates are the same. We all know March 24th in London covers a different 24 hours than March 24th in Hawaii but Date>>#= does not. I think whats needed are more

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

Hi Sean, On 9 April 2018 at 15:13, Sean P. DeNigris wrote: > Alistair Grant wrote >> I think using UTC would just move the problem by an hour. > > I'm not sure I understand. How so? I thought UTC is a constant reference > point unaffected by UTC

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

Ron Teitelbaum wrote > (DateAndTime fromString: '1990-01-01T00:00:00Z') asDate start -> > 1990-01-01T00:00:00-04:00 I don't understand. On Pharo 6.1, `(DateAndTime fromString: '1990-01-01T00:00:00Z') asDate start. "-> 1990-01-01T00:00:00+00:00"` The start DateAndTime instVar is exactly what the

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

On Mon, Apr 9, 2018 at 1:46 PM, Sean P. DeNigris wrote: > Sven Van Caekenberghe-2 wrote > > So you want to change '1/1/1990' asDate so that it does the equivalent of > > (DateAndTime fromString: '1990-01-01T00:00:00Z') asDate. > > Precisely. > > That won't work :)

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

Sven Van Caekenberghe-2 wrote > So you want to change '1/1/1990' asDate so that it does the equivalent of > (DateAndTime fromString: '1990-01-01T00:00:00Z') asDate. Precisely. Sven Van Caekenberghe-2 wrote > While you would not want to change Date today so that it does the > equivalent of

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

> On 9 Apr 2018, at 18:52, Sean P. DeNigris wrote: > > Sven Van Caekenberghe-2 wrote >> I think that making Date always UTC will probably not help, because you >> will want to be able to move between timezones > > Two things: > - I don't think changing timezones will be

Re: [Pharo-dev] Metacello/Iceberg Error: IceUndefinedRemote DNU #projectPath

Dennis Schetinin wrote > did you resolve the problem? I can't reproduce. I followed the same steps just now and it worked in Moose 6.1 on top of Pharo 60540 It did however give me a warning that there were unsaved changes in StateSpecs-DSL-ClassWords-Tests. When I tried to browse the changes in

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

Sven Van Caekenberghe-2 wrote > I think that making Date always UTC will probably not help, because you > will want to be able to move between timezones Two things: - I don't think changing timezones will be affected, because my proposal is only: "default to 0 offset for new Date[AndTime]

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

> On 9 Apr 2018, at 17:34, Aliaksei Syrel wrote: > > Must watch :) > > The Problem with Time & Timezones - Computerphile > https://www.youtube.com/watch?v=-5wpm-gesOY Haha, that is indeed hilarious. I guess there is no complete, absolute 100% correct answer for all

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

Must watch :) The Problem with Time & Timezones - Computerphile https://www.youtube.com/watch?v=-5wpm-gesOY On 9 April 2018 at 17:26, Sven Van Caekenberghe wrote: > > > > On 9 Apr 2018, at 15:19, Sean P. DeNigris wrote: > > > > Max Leske wrote > >>

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

> On 9 Apr 2018, at 15:19, Sean P. DeNigris wrote: > > Max Leske wrote >> Assuming UTC is probably just as wrong as assuming the local time zone. > > I'll modify your statement slightly. "Assuming UTC is */almost/* as wrong as > assuming the local time zone." > > I've

Re: [Pharo-dev] Metacello/Iceberg Error: IceUndefinedRemote DNU #projectPath

Hello Sean, did you resolve the problem? I experience the same trying to update Calypso in 6.1 via Metacello new > baseline: 'Calypso'; > repository: 'github://dionisiydk/Calypso'; > load. The stack: IceUndefinedRemote(Object)>>doesNotUnderstand: #projectPath >

Re: [Pharo-dev] Multiple Inheritance

Are you in the "release the Kraken" mood? :) I haven't used stateful traits, and barely traits at all (when I wanted to use it extensively the tools weren't ready). But I see Traits more as a mix-in approach, rather than a multiple inheritance one. Also, in my experience building software with

[Pharo-dev] Multiple Inheritance

I was just thinking about all the freedom brought by stateful traits, and the thought occurred: why not just simplify and remove another hurdle by having multiple inheritance with the conflict resolution and scoping of traits? Forgive me if I'm missing something obvious… - Cheers, Sean --

Re: [Pharo-dev] call for help: answer on HN :)

2018-04-09 15:28 GMT+02:00 Ben Coman : > > > On 9 April 2018 at 14:50, Thierry Goubier wrote: >> >> 2018-04-09 2:18 GMT+02:00 Esteban A. Maringolo : >> > Even if he is a troll, he pointed out many things that aren't given >> >

Re: [Pharo-dev] Did magritte change? Magritte-Morph-SeasnDeNigris.95 is not found

On Mon, Apr 9, 2018 at 2:07 PM, Sean P. DeNigris wrote: > Stephane Ducasse-3 wrote > > I will create one > > There is https://github.com/magritte-metamodel/magritte which I forked > from. > I wonder if we can make that canonical. It would be easy for me to sync my >

Re: [Pharo-dev] call for help: answer on HN :)

On 9 April 2018 at 14:50, Thierry Goubier wrote: > 2018-04-09 2:18 GMT+02:00 Esteban A. Maringolo : > > Even if he is a troll, he pointed out many things that aren't given > > priority because we're building "next great stuff" and with the limited

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

Max Leske wrote > Assuming UTC is probably just as wrong as assuming the local time zone. I'll modify your statement slightly. "Assuming UTC is */almost/* as wrong as assuming the local time zone." I've never seemed to be able to drive the essential point home when these discussions have come

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

Alistair Grant wrote > I think using UTC would just move the problem by an hour. I'm not sure I understand. How so? I thought UTC is a constant reference point unaffected by UTC (https://stackoverflow.com/a/5495816/424245) - Cheers, Sean -- Sent from:

Re: [Pharo-dev] Did magritte change? Magritte-Morph-SeasnDeNigris.95 is not found

Stephane Ducasse-3 wrote > I will create one There is https://github.com/magritte-metamodel/magritte which I forked from. I wonder if we can make that canonical. It would be easy for me to sync my changes back and from the README, it appears that most other Smalltalk load Magritte from elsewhere.

[Pharo-dev] [Pharo 7.0-dev] Build #758: 21682-DropListPresenter-ignores-disable-before-it-is-built

There is a new Pharo build available! The status of the build #758 was: FAILURE. The Pull Request #1185 was integrated: "21682-DropListPresenter-ignores-disable-before-it-is-built" Pull request url: https://github.com/pharo-project/pharo/pull/1185 Issue Url:

Re: [Pharo-dev] [ANN] New Pharo 6.1 version

> On 8 Apr 2018, at 20:25, Tudor Girba wrote: > > Great job, Esteban! well, is more like the great job of Martin, I just did the integration. But thanks is his name ;) cheers! Esteban > > Doru > >> On Apr 5, 2018, at 3:00 PM, Esteban Lorenzano

Re: [Pharo-dev] [ANN] New Pharo 6.1 version

hi, > On 8 Apr 2018, at 14:13, Peter Uhnák wrote: > > But why it's not a 6.2 version? It would be more clear since this is > continuation of version 6 with new changes. How one would revert to original > 6.1 if this new version isn't working for him? > > In the same way

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

Hi Sean, On 8 April 2018 at 15:32, Sean P. DeNigris wrote: > I was bitten by this very annoying bug again. As most of us probably know due > to the steady stream of confused ML posts in the past, the bug in summary is > that we have an incomplete timezone implementation

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

> On 9 Apr 2018, at 08:51, Max Leske wrote: > > Hi Sean, > On 8 April 2018 at 15:33:11, Sean P. DeNigris (s...@clipperadams.com) wrote: > >> I was bitten by this very annoying bug again. As most of us probably know >> due >> to the steady stream of confused ML posts in

[Pharo-dev] [Pharo 7.0-dev] Build #757: 21681-expandMacrosWith-shouldnt-truncate-strings

There is a new Pharo build available! The status of the build #757 was: SUCCESS. The Pull Request #1184 was integrated: "21681-expandMacrosWith-shouldnt-truncate-strings" Pull request url: https://github.com/pharo-project/pharo/pull/1184 Issue Url:

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

Hi Sean, On 8 April 2018 at 15:33:11, Sean P. DeNigris (s...@clipperadams.com) wrote: I was bitten by this very annoying bug again. As most of us probably know due to the steady stream of confused ML posts in the past, the bug in summary is that we have an incomplete timezone implementation

Re: [Pharo-dev] call for help: answer on HN :)

2018-04-09 2:18 GMT+02:00 Esteban A. Maringolo : > Even if he is a troll, he pointed out many things that aren't given > priority because we're building "next great stuff" and with the limited > resource you either stop to world to fix what's already made or you move >

Re: [Pharo-dev] Did magritte change? Magritte-Morph-SeasnDeNigris.95 is not found

I will create one, because at the end I was the guy that showed the moose meta model to lukas and pushed him when he started to work on Magritte. (magritte description described in themselves and general design are lukas ideas). Stef On Sun, Apr 8, 2018 at 2:06 PM, Peter Uhnák

Re: [Pharo-dev] [ANN] New Pharo 6.1 version

Thanks peter we should make this clearer. On Sun, Apr 8, 2018 at 2:13 PM, Peter Uhnák wrote: >> But why it's not a 6.2 version? It would be more clear since this is >> continuation of version 6 with new changes. How one would revert to original >> 6.1 if this new version

Re: [Pharo-dev] call for help: answer on HN :)

Yes me too and this is on our todo. Because I hate it. Now as usual the more we get help the faster we are. For example Pablo rewrote the FT logic to use FFI instead of the unstable plugin. And when he is doing this he is not doing something else. Same of streams and many other. Stef On Mon, Apr

[Pharo-dev] Esteban's ChangeLog week of 2 April 2018

Hello! This is my weekly ChangeLog, from 2 April 2018 to 8 April 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=2/4/2018=8/4/2018 ChangeLog = 5 April 2018: - *I closed [issue