Anyway, select a database on the workspace, or select one in the Designer database pane on the left, click the (blank) Toolbar icon, and the Teamstudio browser starts; it's pretty quick too, taking about ten seconds to open a mail database (18 Script Libraries). At that point, it's a wee bit ho-hum, and it's not quite obvious what it has to offer. Figure C shows what you get; a collapsible list of all the entry points and external symbols in every Script Library in the database.

FIGURE C

Here you see the contents of the Script Library. Click picture for a larger image.

Note that shown in the example are four Initialize subs, and more importantly, where each one can be found.

Now re-open it on a database that contains a class definition; and--at last--the class structure is explained. Now we start to cook, as you can see Figure D.

FIGURE D

A class, NotesFTPSession, and other functions are contained in the NotesFTP Script Library. Click picture for a larger image.

Notice the NotesFTP Script Library contains a class, NotesFTPSession, and within that some functions and properties. The icons separate properties from public and private subs. So far so good. You can copy the actual reference statement by clicking Copy to Clipboard, and pasting it into your code, so that you have the definition of the sub or function at hand while you write your call, and then delete it when you're finished.

But there's more. Right-clicking on an entry displays a two-entry context menu, shown in Figure E.

FIGURE E

The right-click context menu. Click picture for a larger image.

This is where the magic really starts. Goto Definition opens the selected reference in Domino Designer, placing you right at the correct point in the code, as you can see in Figure F.

FIGURE F

The Goto Definition context menu opens the reference in Domino Designer. Click picture for a larger image.

You now have all of Designer at hand. I think this shows a good design decision on Teamstudio's part--that of not emulating what Designer can do in their tool, but instead leveraging Designer by getting Designer to display the actual code.

References, the second choice, is an even more valuable function, especially to any developer faced with a database they don't know and a problem to solve. References shows you where a sub or function is used, across the whole database. In Figure G, you'll see that the entry ListFieldList, part of library ServiceFunctions, is called in a whole number of places.

FIGURE G

References shows you where each item is called, across the entire database. Click picture for a larger image.

Clicking on any entry listed in the Find References window takes you right to the actual call, in Domino Designer. Very cool.

While you're working, the browser stays open on top of the window it was opened from; open it from the Notes client, and it stays on top of the client. Open it in Designer and it stays there too, but you can only have one instance open, and only one database. To get it to open a new database, just select a new one and click the Toolbar icon again. Double-clicking the title bar collapses it to a small placeholder window, getting it out of the way. Closing the Notes properties box also closes the Script Browser.