On Mon, Sep 22, 2008 at 11:40 PM, william humphrey <[EMAIL PROTECTED]>wrote:
> I think that those guidelines along with > some others should really be consolidated into something that the > mothership > could recommend for our use. > Do you mean something like page 163 of the RevolutionUserGuide.pdf as accessed via the Rev 3.0 Help menu - User Guide. :-) At first I though a bit skimpy, and why is it at the end of the chapter Writing Revolution Code. Then I realised it's perfect. Because of the way I learn, if there'd been a whole heap of naming rules, script location conventions and library stack usage guidelines to wade through BEFORE I got to lick, stick, staple, tape and chewing gum together my first stack I probably would have pushed it all to the side and said, yeah, I'll check that out tomorrow - and there's always a tomorrow;-) I loved HC (and Rev) because it's like Lego, who says all the blue bricks have to go together or that I have to start with that main.m brick! Sure, there are huge advantages if you use naming conventions, and are selective where scripts reside; but not until you've learnt that Rev is an amazing tool that allows you to do things that you thought only geeks with a silicon thumb could do. Play first, learn rules later. _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
