Best Practices

[Andre Garzia]

On Nov 6, 2005, at 8:02 PM, Erin D. Smale wrote:

>
> Also, the feedback cements my need to dive into the message  
> hierachy and really wrap my head around it. I have Richard's  
> article on tap and Dan's material is a good read. Geez...you guys  
> were serious when you said message hierachy was important. ;-)
>
> Thanks to all for your helpful explanations to and patience with  
> this newbie.

Erin,

a very useful resource for understanding the message path, is the  
primer made by Dar Scott, I think it's the best resource ever. By  
carefully planning where your code goes, you can save a lot of  
coding. As time goes, you'll begin to develop your own style. There  
are coders here that make heavy use of libraries, others will insert  
all on stackscript and just hook the UI to it, others will make so  
many twists in the message path that their code will resemble a tight  
chain of whispers. The cool thing of Transcript is that it allows you  
to adapt Rev for your tastes and not the other way arround.

There's a scripting style guide that is used by many here that tells  
about how to prefix variables and stuff like that. Also the  
RevInterop group makes a nice guide that allows our stacks to  
interoperate in a sane way.

I remember when I first saw the message primer, before reading it,  
someone said: "in the end, you'll love the message path", and yes, I  
do love it.

Cheers
andre