Thanks for the dialogue guys, very insightful. Coming from a dynamic language background for the server side, I don't get that warm and fuzzy feeling reminiscent of suckling a mother's teet, that others (read java coders) do from compiler checks. I live in the run-time baby! Baz
On Wed, Sep 17, 2008 at 12:47 AM, Stefan Richter <[EMAIL PROTECTED]>wrote: > Point taken. However we do work in teams on many projects and the > benefits of using the note system far outweigh the downsides (if there are > any) in my opinion. I can only speak from my personal experience, and in > that we've never had problems with wrongly casted note bodies. > > I guess it's down to personal preference. > > Stefan > > > > On 17 Sep 2008, at 08:33, Ralf Bokelberg wrote: > > Yep Stefan > > I think type safety is much more important, if you work in teams. I > never had a type problem, when i worked on my own, since i knew all > the necessary types. But if you have a team it makes things much > easier. > > Cheers > Ralf. > > On Wed, Sep 17, 2008 at 9:26 AM, Stefan Richter <[EMAIL > PROTECTED]<stefan%40muchos.co.uk>> > wrote: > > Valid points, but Baz definitely points to an itch that many have tied to > > scratch before. > > > > I use PureMVC primarily now for my projects and the only time I need > custom > > events is to talk from my view component to its Mediator. Most of the > time I > > do not need custom events at all. From the Mediator on PureMVC uses > > Notifications (also called notes) which pass around a body that holds any > > type of object. Sure, I need to keep track of what I put into the note in > > order to cast it to the right type when I read it back out but I must say > > this system works very well. In fact I do not recall a single runtime > error > > that was due to casting of note bodies. > > Cheers > > Stefan > > > > > > >
