>From my perspective as a very new Turbine experimenter, actions should
probably only rarely add stuff to the context. They should mostly modify
attributes of components that are put in the context via the PullService or
via the Screen. When actions add things to the context, your templates
become dependent upon the actions, which is not a good thing IMHO.
Chris Felaco
Sr. Software Developer
Blue Dolphin Group
(508) 358-6758
Peter Lynch
<peterwlynch@ To: [EMAIL PROTECTED]
yahoo.com> cc:
Subject: Reasons For Action Classes
06/14/2001
04:32 PM
Please
respond to
turbine-user
Hi,
Someone asked me why the need to separate action
classes from screen class code. In other words, they
were wondering why not have the screen classes do all
the work? I was brain dead at the time so I think I
did not give a very compelling argument why....
So can anybody offer some compelling
reasons/advantages for this design as opposed to
having the screen classes do all the work of putting
and getting?
Thanks,
Peter
__________________________________________________
Do You Yahoo!?
Spot the hottest trends in music, movies, and more.
http://buzz.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- Reasons For Action Classes Peter Lynch
- Re: Reasons For Action Classes Scott McCrory
- Re: Reasons For Action Classes cfelaco
- Re: Reasons For Action Classes Jon Stevens
- Re: Reasons For Action Classes Jon Stevens
- Re: Reasons For Action Classes Travis Low
- RE: Reasons For Action Classes Frank Villarreal
- RE: Reasons For Action Classes Diethelm Guallar, Gonzalo
- Re: Reasons For Action Classes Jon Stevens
- RE: Reasons For Action Classes Myron Ahn
- Re: Reasons For Action Classes Jon Stevens
- RE: Reasons For Action Classes Myron Ahn
