> 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
https://pharo.fogbugz.com/f/cases/20321/Add-build-number-to-SystemVersion
https://github.com/pharo-project/pharo/pull/212
Do you know that there is #nextVersion method in FileReference?
2017-08-18 22:04 GMT+02:00 Stephane Ducasse :
> Hi
>
> I really like (when I save little data files) to have a simple versioning.
> For example for my game collection I have
> Games.1.ston
> Games.2.ston
> ...
> and I like that this
>>
>>
>> We also notice that this is strange that we cannot access to the old
>> method when we
>> - take a method
>> - change the selector
>> and start to reimplement something (in that case we cannot access the
>> old method definition).
>>
>
> Did you just typed new selector without accepting ch
>
> We also notice that this is strange that we cannot access to the old
> method when we
> - take a method
> - change the selector
> and start to reimplement something (in that case we cannot access the
> old method definition).
>
Did you just typed new selector without accepting changes?
> In th
2017-08-18 22:07 GMT+02:00 Stephane Ducasse :
> Quentin told me that when he is compiling with command+s he gets
> another method.
> I could not really understand but it was strange.
>
Yes, it is strange. Tell me if you will find reproducible case.
>
> We also notice that this is strange that w
Hi torsten
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.
Excellent. Because with my first contribution I broke filet
https://pharo.fogbugz.com/f/cases/20062/Open-a-package-extending-a-class-via-the-extension-protocol
https://github.com/pharo-project/pharo/pull/208
Quentin told me that when he is compiling with command+s he gets
another method.
I could not really understand but it was strange.
We also notice that this is strange that we cannot access to the old
method when we
- take a method
- change the selector
and start to reimplement something (in that c
We should add this in a class comment and probably a menu somewhere.
On Fri, Aug 18, 2017 at 10:05 PM, Stephane Ducasse
wrote:
> Tx denis.
>
> Stef
>
> On Fri, Aug 18, 2017 at 9:40 PM, Denis Kudriashov
> wrote:
>> Hi Stef.
>>
>> Yes, you need disable plugins. It is not available from settings b
Tx denis.
Stef
On Fri, Aug 18, 2017 at 9:40 PM, Denis Kudriashov wrote:
> Hi Stef.
>
> Yes, you need disable plugins. It is not available from settings browser.
> Use scripts:
>
> ClyInheritanceAnalyzerEnvironmentPlugin disable.
> ClyCriticEnvironmentPlugin disableMethodGroup
>
>
> But according
Hi
I really like (when I save little data files) to have a simple versioning.
For example for my game collection I have
Games.1.ston
Games.2.ston
...
and I like that this is managed for me by the system.
I harvested this functionality from squeak long time ago.
I rewrote it fast and dirty in Phar
Hi Stef.
Yes, you need disable plugins. It is not available from settings browser.
Use scripts:
ClyInheritanceAnalyzerEnvironmentPlugin disable.
ClyCriticEnvironmentPlugin disableMethodGroup
But according to your logic method icons (up/down arrows) should be
disabled too. Right now they are sti
Hi denis
The extra protocols are super confusing for newbies.
Is there a setting to remove the critiques (because it flickers) from
the protocols.
Can we remove the overrides and inherited?
I do not care to know that I overrides initialize from Object for example.
When you learn a system you do n
I have the impression that we should rethink the meta interface of
classes and reflective calls.
On Fri, Aug 18, 2017 at 10:44 AM, Denis Kudriashov wrote:
> Hi
>
> I wrote proposal in issue
>
> 2017-08-18 0:52 GMT+02:00 Tim Mackinnon :
>>
>> Is this a goal we can all share for 7.0?
>>
>> Sort out
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 issu
> 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 m
Hi Tim,
> On Aug 18, 2017, at 4:08 AM, 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
> 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 ther
On Fri, Aug 18, 2017 at 3:40 PM, Torsten Bergmann wrote:
> Hi,
>
> first: thanks you Guille for answering my questions and providing more
> documentation
> on your wiki.
>
> Guille also cared yesterday on addressing the build number problem:
> https://github.com/pharo-project/pharo/pull/212
>
> B
Henry,
You wrote directly to me:
> I wish to use JSON for type encoding between different language environments,
> currently Squeak and Java. Unfortunately I cannot load the software in Pharo,
> at this time. I brought NeoJSON over into my package to work locally, and I
> made some changes. As
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 c
> 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:
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
Hi,
when running Pharo in production you might want to install the image and a VM
from distribution packages. So far there were no current public packages and
during the last months I have modernized the debian packaging and recently
added CentOS rpm packaging as well. The process of generating
Hi
I wrote proposal in issue
2017-08-18 0:52 GMT+02:00 Tim Mackinnon :
> 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
>
> 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 befor
> 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 th
28 matches
Mail list logo
