Hi!
Just to make things clear, AXAnnouncements
- is not "a port of the original announcement implementation"
- is (more or less) based on Vassili Bykov's blog
(http://www.cincomsmalltalk.com/userblogs/vbykov/blogView?searchCategory=Announcements%20Framework)
just like the Announcements pack
> Just to make things clear, AXAnnouncements
> - is not "a port of the original announcement implementation"
Ok, excellent. Just trying to avoid possible issues.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
___
Pharo-project mailing list
Pharo-
> http://axdemo.seasidehosting.st/
I get a: Error: "/seaside/" not found.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
___
Pharo-project m
http://axdemo.seasidehosting.st/seaside/ax
or
http://axdemo.seasidehosting.st/browse
2009/10/30 Alexandre Bergel
> > http://axdemo.seasidehosting.st/
>
> I get a: Error: "/seaside/" not found.
>
> Alexandre
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://w
Hi!
On Fri, 30 Oct 2009, Alexandre Bergel wrote:
>> http://axdemo.seasidehosting.st/
>
> I get a: Error: "/seaside/" not found.
>
Try this: http://axdemo.seasidehosting.st/seaside/ax
or this: http://axdemo.seasidehosting.st/seaside/browse :)
Cheers,
Levente
Works better.
Thanks,
Alexandre
On 30 Oct 2009, at 13:10, Cédrick Béler wrote:
> http://axdemo.seasidehosting.st/seaside/ax
>
> or
>
> http://axdemo.seasidehosting.st/browse
>
> 2009/10/30 Alexandre Bergel
> > http://axdemo.seasidehosting.st/
>
> I get a: Error: "/seaside/" not found.
>
> Alex
Levente
what I would really love :)
is if you could provide some extensions to the new version based on
your experience.
I think that Announcements are a bit limited right now. Then the core
would be enhanced and we
could clarified the license.
Stef
On Oct 30, 2009, at 1:25 AM, Levente Uzony
what would be good is to have a small discussion on the key and
minimal features that could be added to Announcements,
add some tests and code.
Stef
On Oct 31, 2009, at 5:17 PM, Stéphane Ducasse wrote:
> Levente
>
> what I would really love :)
> is if you could provide some extensions to the ne
AXAnnouncements is pretty small and accompanied with tests.
So why not integrate it + removing 'AX' prefix because, as decided previously,
it should be in Pharo core?
2009/10/31 Stéphane Ducasse :
> what would be good is to have a small discussion on the key and
> minimal features that could be ad
This could be a possibility now I think that this is nice that people
get a chance to check it and discuss.
Stef
On Oct 31, 2009, at 10:02 PM, Igor Stasenko wrote:
> AXAnnouncements is pretty small and accompanied with tests.
> So why not integrate it + removing 'AX' prefix because, as decided
2009/10/31 Stéphane Ducasse :
> This could be a possibility now I think that this is nice that people
> get a chance to check it and discuss.
>
yes, please decide. :) Because from that decision, we could then plan
a new system-change annoucements layer
+ package system.
In current core image, Anno
I think that Axa needs a good cleaning brush. So let us see what we
can get.
Stef
On Oct 31, 2009, at 10:23 PM, Igor Stasenko wrote:
> 2009/10/31 Stéphane Ducasse :
>> This could be a possibility now I think that this is nice that people
>> get a chance to check it and discuss.
>>
>
> yes, plea
> In current core image, Announcements is quite small (just around 10
> methods totally) and i doubt it provides enough
> flexibility which would not require adding & reinventing additional
> useful stuff on top of it.
I have used these announcements in many large projects and I never
needed to ad
2009/11/1 Lukas Renggli :
>> In current core image, Announcements is quite small (just around 10
>> methods totally) and i doubt it provides enough
>> flexibility which would not require adding & reinventing additional
>> useful stuff on top of it.
>
> I have used these announcements in many large
> But if it so stripped to bare-bones, then where the benefits to use
> exactly Announcements?
I would rather like to hear what this "more wide functionality" is all about?
So far you only argued that big is better. I don't buy that.
This is old, but "Small is the new big" ;-)
A smaller infrast
Yes for weak, I agree for set may be some people use that.
Now I would like to hear levente usage of announcement.
And igor having a simple but COMMON infrastructure is important
so we need the core.
Now I would also like to know the cost of always broadcasting. I do not
remember correctly but in
2009/11/1 Lukas Renggli :
>> But if it so stripped to bare-bones, then where the benefits to use
>> exactly Announcements?
>
> I would rather like to hear what this "more wide functionality" is all about?
>
i don't know. I just not buying 'use this' because its good. I need to
know why its so good
2009/11/1 Igor Stasenko :
> 2009/11/1 Lukas Renggli :
>>> But if it so stripped to bare-bones, then where the benefits to use
>>> exactly Announcements?
>>
>> I would rather like to hear what this "more wide functionality" is all about?
>>
>
> i don't know. I just not buying 'use this' because its
> Obviously i can't. Because if i make all of the tree to be a subclass
> of LoggedAnnouncement, then all of them
> will be logged, while i want only some of them.
You are missing the point of announcements: they are not supposed to
do anything, they are only supposed to notify interested parties
Indeed, the main and only goal of Announcement is to provide an object-
oriented (Exception-like) way to handle notifications.
I have used the Announcements implementation of Lukas on several
occasions and I did not feel the need for anything else.
You indeed should subclass Announcement for a
2009/11/1 Lukas Renggli :
>> Obviously i can't. Because if i make all of the tree to be a subclass
>> of LoggedAnnouncement, then all of them
>> will be logged, while i want only some of them.
>
> You are missing the point of announcements: they are not supposed to
> do anything, they are only supp
2009/11/1 Tudor Girba :
> Indeed, the main and only goal of Announcement is to provide an object-
> oriented (Exception-like) way to handle notifications.
>
> I have used the Announcements implementation of Lukas on several
> occasions and I did not feel the need for anything else.
>
> You indeed s
> Oh, wait.. you mean that if i want, say 35 out of 50 announcement
> kinds to be logged, then
> i need to do something like:
>
> logblock := [:announcement | ... ].
> announcer on: AnnouncementKind1 do: logblock.
> announcer on: AnnouncementKind2 do: logblock.
>
> announcer on: AnnouncementKi
you see you find a use of Set :)
Stef
On Nov 1, 2009, at 6:17 PM, Lukas Renggli wrote:
>> Oh, wait.. you mean that if i want, say 35 out of 50 announcement
>> kinds to be logged, then
>> i need to do something like:
>>
>> logblock := [:announcement | ... ].
>> announcer on: AnnouncementKind1 do:
2009/11/1 Lukas Renggli :
>> Oh, wait.. you mean that if i want, say 35 out of 50 announcement
>> kinds to be logged, then
>> i need to do something like:
>>
>> logblock := [:announcement | ... ].
>> announcer on: AnnouncementKind1 do: logblock.
>> announcer on: AnnouncementKind2 do: logblock.
>> .
2009/11/1 Stéphane Ducasse :
> you see you find a use of Set :)
>
IMO, this is a find where you should not use Set :)
> Stef
>
> On Nov 1, 2009, at 6:17 PM, Lukas Renggli wrote:
>
>>> Oh, wait.. you mean that if i want, say 35 out of 50 announcement
>>> kinds to be logged, then
>>> i need to do
At Sun, 1 Nov 2009 19:35:57 +0200,
Igor Stasenko wrote:
>
> 2009/11/1 Lukas Renggli :
> >> Oh, wait.. you mean that if i want, say 35 out of 50 announcement
> >> kinds to be logged, then
> >> i need to do something like:
> >>
> >> logblock := [:announcement | ... ].
> >> announcer on: Announcement
2009/11/1 Yoshiki Ohshima :
> At Sun, 1 Nov 2009 19:35:57 +0200,
> Igor Stasenko wrote:
>>
>> 2009/11/1 Lukas Renggli :
>> >> Oh, wait.. you mean that if i want, say 35 out of 50 announcement
>> >> kinds to be logged, then
>> >> i need to do something like:
>> >>
>> >> logblock := [:announcement |
> Another question , which Stephane noted already, is the overhead of
> broadcasting.
First of all, announcements are magnitudes faster than the ancient
change-update and trigger frameworks.
The problem of broadcasting does not apply to announcements, because
the observer only registers and recei
Yes after writing that I thought that it was already based on on:send:
so you only broadcast to the person that register.
>> Another question , which Stephane noted already, is the overhead of
>> broadcasting.
>
> First of all, announcements are magnitudes faster than the ancient
> change-update a
2009/11/1 Lukas Renggli :
>> Another question , which Stephane noted already, is the overhead of
>> broadcasting.
>
> First of all, announcements are magnitudes faster than the ancient
> change-update and trigger frameworks.
>
i having zero interest in ancient stuff. This topic is about announceme
2009/11/1 Igor Stasenko :
> 2009/11/1 Lukas Renggli :
>>> Another question , which Stephane noted already, is the overhead of
>>> broadcasting.
>>
>> First of all, announcements are magnitudes faster than the ancient
>> change-update and trigger frameworks.
>>
>
> i having zero interest in ancient
On Sun, Nov 01, 2009 at 10:07:59PM +0100, Lukas Renggli wrote:
> > Another question , which Stephane noted already, is the overhead of
> > broadcasting.
>
> First of all, announcements are magnitudes faster than the ancient
> change-update and trigger frameworks.
Is this true? I would expect anno
2009/11/2 Nicolas Cellier :
> 2009/11/1 Igor Stasenko :
>> 2009/11/1 Lukas Renggli :
Another question , which Stephane noted already, is the overhead of
broadcasting.
>>>
>>> First of all, announcements are magnitudes faster than the ancient
>>> change-update and trigger frameworks.
>>>
>
At Sun, 1 Nov 2009 20:22:48 +0200,
Igor Stasenko wrote:
>
> > If "can be logged" means to have #canBeLogged method that returns
> > true, you could also say (given that you provide a default
> > implementation of #canBeLogged at a/the root):
> >
> > logblock := [:announcement | announcement canBe
2009/11/2 Yoshiki Ohshima :
> At Sun, 1 Nov 2009 20:22:48 +0200,
> Igor Stasenko wrote:
>>
>> > If "can be logged" means to have #canBeLogged method that returns
>> > true, you could also say (given that you provide a default
>> > implementation of #canBeLogged at a/the root):
>> >
>> > logblock :
> Igor, even if you open a shiny new Pharo image, I'm afraid you'll have
> to contemplate plenty of ancient code.
> Note sure the most ancient the most dusty though ;).
>
> FIY, st80 MVC was broadcasting to 99% of ignorers with a long chain of
> this kind:
> self changed: aSymbol SENT FROM THE MOD
>>
> Oh yeah, i seen that code, and Dependents class var in Object class,
> which is a dictionary of dictionaries...
> This model, as well as morphic extensions, takes roots from Self's
> morphic, where you can easily extend
> any object state by adding new slots to it. In smalltalk we don't have
>
> Now I would also like to know the cost of always broadcasting. I do
> not
> remember correctly but in vassili'blog there were some points to avoid
> that.
> Because in the past, in Smalltalk the dependency where broadcasting to
> all the
> dependents and this was inadequate and after they intro
>> Now I would also like to know the cost of always broadcasting. I do
>> not
>> remember correctly but in vassili'blog there were some points to
>> avoid
>> that.
>
> Yes, broadcasting was the reason why OBPackageBrowser was slow
> before we refactored it.
Actually, the sloppiness came from
2009/11/2 Stéphane Ducasse :
>>>
>> Oh yeah, i seen that code, and Dependents class var in Object class,
>> which is a dictionary of dictionaries...
>> This model, as well as morphic extensions, takes roots from Self's
>> morphic, where you can easily extend
>> any object state by adding new slots
On Monday, November 2, 2009, Igor Stasenko wrote:
> 2009/11/2 Stéphane Ducasse :
>>> Oh yeah, i seen that code, and Dependents class var in Object class,
>>> which is a dictionary of dictionaries...
>>> This model, as well as morphic extensions, takes roots from Self's
>>> morphic, where you
2009/11/2 Lukas Renggli :
> On Monday, November 2, 2009, Igor Stasenko wrote:
>> 2009/11/2 Stéphane Ducasse :
>
Oh yeah, i seen that code, and Dependents class var in Object class,
which is a dictionary of dictionaries...
This model, as well as morphic extensions, takes roots fr
>>> I implemented a new announcer, which covers all functionality of the
>>> original one
>>> (all tests is green) but in addition enables you to subscribe directly via
>>> #subscribe:
>>> and receive #handle: message in case of announcements.
>>> Of course, the decision whether to handle or ignore
2009/11/2 Lukas Renggli :
I implemented a new announcer, which covers all functionality of the
original one
(all tests is green) but in addition enables you to subscribe directly via
#subscribe:
and receive #handle: message in case of announcements.
Of course, the deci
At Mon, 2 Nov 2009 19:18:09 +0100,
Lukas Renggli wrote:
>
> > Please, can you elaborate, what you consider 'broken features' and why?
> > I am also not a fan of using flawed stuff.
>
> Weak objects are flawed in Pharo and Squeak. If you have an unbounded
> number of weak references it can quickly
Igor Stasenko wrote:
> 2009/11/1 Tudor Girba :
>
>> Indeed, the main and only goal of Announcement is to provide an object-
>> oriented (Exception-like) way to handle notifications.
>>
>> I have used the Announcements implementation of Lukas on several
>> occasions and I did not feel the need fo
2009/11/2 Yoshiki Ohshima :
> At Mon, 2 Nov 2009 19:18:09 +0100,
> Lukas Renggli wrote:
>>
>> > Please, can you elaborate, what you consider 'broken features' and why?
>> > I am also not a fan of using flawed stuff.
>>
>> Weak objects are flawed in Pharo and Squeak. If you have an unbounded
>> numb
2009/11/2 Alain Plantec :
> Igor Stasenko wrote:
>> 2009/11/1 Tudor Girba :
>>
>>> Indeed, the main and only goal of Announcement is to provide an object-
>>> oriented (Exception-like) way to handle notifications.
>>>
>>> I have used the Announcements implementation of Lukas on several
>>> occasion
I just uploaded the modified announcer code + new tests.
Please check the
http://www.squeaksource.com/PharoInbox/Announcements-Slice-Igor_Stasenko.1.mcz
and send a feedback
--
Best regards,
Igor Stasenko AKA sig.
___
Pharo-project mailing list
Pharo-
2009/11/3 Igor Stasenko :
> I just uploaded the modified announcer code + new tests.
> Please check the
>
> http://www.squeaksource.com/PharoInbox/Announcements-Slice-Igor_Stasenko.1.mcz
>
> and send a feedback
>
oh.. for those who interested , but too lazy (or busy) to check it out..
- added a ge
51 matches
Mail list logo
