Planning/design/estimating checklists

[Keith Clarke]

Thanks, Kee, Mark and Richard for the responses.
Kee's feedback is exactly the kind of 'top tip' that I was thinking about. It is specific to LiveCode and with very clear 'Why", 'What', 'Where', 'When' and 'How'. 
I'm sure that a couple of top tips from the experts here would go along way towards creating some checklists for folks moving from high-level design or pseudo-code to actual LiveCode stacks, cards, etc.
Best,
Keith..  

On 24 Dec 2010, at 16:22, Kee Nethery wrote:

> I include a script in every card I ever create:
> 
> on sanitize
> -- reset everything to the state I want it to be when it gets distributed
> end sanitize
> 
> I've heard of another doing the same thing with
> 
> on stripandship
> 
> Then on the very first card I have two scripts that are
> 
> on sanitize
> sanitizeFirst
> repeat with x = 2 to the number of cards
>  go to card x
>  sanitize
> end repeat
> end sanitize
> 
> on sanitizeFirst
> -- reset everything to the state I want it to be when it gets distributed
> end sanitizeFirst
> 
> Several things happen with this.
> 1. I am assured that I reset things the way I want them
> 2. I can test each card's sanitize script independently to make sure it does everything I want
> 3. If a card does not have a sanitize script, I get an error and I make a sanitize script for it
> 4. I don't have to remember anything other than when I create a new field or button, I need to add it to the sanitize script so that it gets set appropriately before I distribute it.
> 
> Works for me.
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode