William, I was one of those that kept loosing my code. The guideline I use these days is:
* Utility code that is related to the application goes into the stack script * Generic code that can be used by any application goes into a library stack * Cards and controls only got event code, like mouseUps, preOpenStuffs and impromptu code that is just related to those codes (Ex: pretty printer for a field in a card). This may not be the best and my stack scripts tend to get bigger and bigger, but, I know where things should be. GLX 2 has a nice feature where you click a command or function and it jumps to where it is defined, this is a must and I can't stress how useful this actually is! Cheers andre On Mon, Sep 22, 2008 at 12:40 PM, william humphrey <[EMAIL PROTECTED]> wrote: > I wonder if it is really bad that the very powerful programming environments > let us do stuff we (or at least I) could never have imagined possible > before. I'm only saying this because in other forums sometimes people say > "oh scripting that's not programming". My answer to them is usually "Why > aren't you writing machine code in hex -- that would be the most efficient". > In any case it's still difficult to write a really good program even using > a great environment like RunRev so they shouldn't worry about the unwashed > masses coming to their table. I do remember that some of the amateur stacks > made by Hypercard were used as an example saying that is why Hypercard was > killed by Apple. And wasn't Pascual designed to try to force programmers to > be more logical and not end up with lazy convoluted code? > > About the only complaint I have with RunRev is it allows you to put your > code everywhere (don't want to give that feature up either) but someone else > coming along to look at your stack can take a very long time to figure it > out if there is some code in a card, some in a stack, some in buttons etc. > > > Maybe RunRev mothership should publish some guidelines on how scripting > should be done to try and prevent that problem? I know that there are some > excellent guidelines on writing clear scripts on someone's website. The > recommended consistently naming variables depending on whether they were > global, an array, or temporary. I think that those guidelines along with > some others should really be consolidated into something that the mothership > could recommend for our use. > _______________________________________________ > 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 > -- http://www.andregarzia.com All We Do Is Code. _______________________________________________ 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
