I'm going in the direction of the Job. I started by doing some clean up in
the implementation, together with Guille in a useful pair-programming
session. The issue needs approval for integration:
https://pharo.fogbugz.com/f/cases/15833/Remove-Notifications-from-Job-implementation
Martín
On Wed,
Thanks for the discussion. I'm considering the ideas; I want to propose
something concrete very soon.
If I understand well, the two positions are:
* to extend Job with a 'description' object;
* to extend system announcements, so they know their 'parent' announcement;
in both cases, the subscribe
Hi Eliot,
Le 13/06/2015 06:54, Eliot Miranda a écrit :
Hi Thierry,
On Jun 11, 2015, at 8:16 AM, Thierry Goubier mailto:thierry.goub...@gmail.com>> wrote:
2015-06-11 16:49 GMT+02:00 Ben Coman mailto:b...@openinworld.com>>:
Just a *very* divergent thought that I'm not sure is a good ide
Hi Thierry,
On Jun 11, 2015, at 8:16 AM, Thierry Goubier wrote:
>
>
> 2015-06-11 16:49 GMT+02:00 Ben Coman :
>>
>> Just a *very* divergent thought that I'm not sure is a good idea...
>> maybe the parent announcement could hold the announcer of its
>> children.
>
> The problem is then that al
2015-06-11 16:49 GMT+02:00 Ben Coman :
>
> Just a *very* divergent thought that I'm not sure is a good idea...
> maybe the parent announcement could hold the announcer of its
> children.
>
The problem is then that all tools which are not interested in the parent
announcement because they only dea
On Thu, Jun 11, 2015 at 2:29 AM, Max Leske wrote:
>
> On 10 Jun 2015, at 17:13, Martin Dias wrote:
>
> Hi everybody,
>
> I'm writing you to discuss about a new feature for Pharo. I would like to
> know your opinions and ideas. Thanks in advance.
>
> My point is that there are operations like "MC
Hi Martin,
I believe your job example express better what you need, so what I would
propose would be a notion of parent in the normal code announcements,
containing, in a hierarchical way, the higher level context information.
But implementing that parent in the announcements will be difficult, s
@Max: I watched the presentation but I'm not sure how to apply it in this
case. (Last exam!? good!)
@Ben: I agree that there are not only 2 levels, high-level and low-level
announcements but a hierarchy. For example, a "MCVersionLoad" could have a
"MetacelloProjectLoad" as a parent.
@Chris (and a
On Wed, Jun 10, 2015 at 11:29 AM, Max Leske wrote:
>
> On 10 Jun 2015, at 17:13, Martin Dias wrote:
>
> Hi everybody,
>
>
>
> The other thing would be to clean up the announcer situation… Maybe the
> announcers should be hierarchical, not the announcements. Doru did a
> presentation at ESUG ab
> On 10 Jun 2015, at 17:13, Martin Dias wrote:
>
> Hi everybody,
>
> I'm writing you to discuss about a new feature for Pharo. I would like to
> know your opinions and ideas. Thanks in advance.
>
> My point is that there are operations like "MC version load", "change set
> file in", "RB refa
On Wed, Jun 10, 2015 at 11:13 PM, Martin Dias wrote:
> Hi everybody,
>
> I'm writing you to discuss about a new feature for Pharo. I would like to
> know your opinions and ideas. Thanks in advance.
>
> My point is that there are operations like "MC version load", "change set
> file in", "RB refact
Hi everybody,
I'm writing you to discuss about a new feature for Pharo. I would like to
know your opinions and ideas. Thanks in advance.
My point is that there are operations like "MC version load", "change set
file in", "RB refactoring execution", or "class copy" that produce code
change announc
12 matches
Mail list logo
