
11.7 Using a New Revision

We've checked in a new revision of our module lookfeel . Now let's run our example application again. Just reload it in the browser, and we see:

Netscape: Introduction

File Edit View Go Communicator

Location:

Introduction

This is our main application page.

Home page Other stuff

Automatic dependency checking

We've got the new look and feel - the extra link at the bottom and the new background color - without having touched the example file in any way . The next time we ran example , Vortex automatically noted that although example itself hadn't changed, a module it uses was updated since the last time example was compiled. So the script was automatically re-compiled to take advantage of the new lookfeel functions.

This is extremely helpful in a large development environment. We might have dozens of scripts all over the place that use the lookfeel module. If the auto-recompile didn't happen, we'd have to go look for them all and recompile them manually. As a module author, we might not even have any idea where the application scripts are. With modules, that's not a problem: as soon as we check in a new revision, scripts that use it are notified.

Let's modify example to take advantage of our simpler look syntax (next page):

Back: Checking In a New Revision

Next: Function Scope in Modules