Yes, that is it, more or less.
A definition might be, "what is an application object", might be "a centralized place to store methods and properties which you require at the application-level".
This application object, of course, can again contain (as properties) objects required on a lower level; for instance, forms, toolbars.
>I want to develope my applications using an application object. I am not sure of all the benefits in using it. this is what I understand, yes/no.
>
>Enhances code reuse
>Conserves memory usage
>Allows rapid application development
>Reduces application bloat
>Cleaner shutdown for the application
>
>This will be a major paridine change in our development process. I need to help my boss understand the benefits of developing this way.
>
>Any help is appreciated. Thanks, Chuck
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
