Here is the list of new features:

• Class member variables are now included in the tree.
• Types are now included in the tree.
• Local function variables are now included in the tree.
• References to variables are now supported.
• Multiple script browsers can be opened for different databases.
• Database path is now displayed in the title bar.

All these features are really great.  My favorite is the types and local variables.  I do have a couple of improvements that I would like to see.

1. Collapsed by default (window shade mode)
2. Ability to refresh the browser without having to close and re-open
3. Remember the placement for multiple windows.  I would like to see first opened window have a spot, and if the second is opened it would have it is last position.  If the first is closed the second would move to the first windows position.
4. Option to display or hide private variables and methods, these should be hiden by default since they are unusable

I find myself using Script Browser every day helping me remember those properties and functions that I know I have built but don't use that often. The other little annoyance is the select of text in the Designer's script editor and Teamstudio's Script Browser. This is one of those little inconveniences because the left parenthesis is selected in script browser but not in the editor. Do you have any other feature that you would like to see.

New features in 1.02

• Window is now re-sizeable
• Window shade mode (double click in caption bar) now reacts to mouseover events. The Script Browser window expands when mouse is over the window, and contracts when the mouse leaves.

Fixes in 1.02

• The Toolbar icon installs more efficiently.
• Goto Definition now selects the correct function on R6.0.x
• References feature corrected to find all occurrences of a function.

Check out the database title it is a new developer tool I am working on. It assist in copying reusable design elements in to templates.

Teamstudio has also made some name changes in the last version or two so both names will show to help with the switch. The other annoying thing about the implementation of Teamstudio's tools is that they lock Designer while they are open. In one of Teamstudio's beta release they were testing the ability to launch a tool in Modal mode which would not lock Designer. This was very nice feature, but it was not implemented because it had some bugs according to them. The one Teamstudio icon that I implemented uses the modal implementation and I never had a problem.

I started using a profile document to store the last selected option. The profile document will allow each database to have its last selection remembered. This might seem like a little over kill but there will be some constancy between all Smiley Tools: Edit Document Fields and Toolbar Functions in the near future.

For this article I have split up the code into two sections: Teamstudio Modal, Teamstudio Standard. Use what ever fits your needs.

Teamstudio Modal (allows the use of Notes/Domino)

Teamstudio Standard

You can browse by Class, Library and Calls. The calls tab is very nice to see where a function or method is being used. There is even an option navigate to the call or definition.

via: http://www.eknori.de

If you have ever used Teamstudio you will notice there could eight different icons to choose from. Over the past four years that I have been using Teamstudio I have frequently clicked on the wrong icon. After wasting time to close down the tool and select a different one. I created one icon that would contain all options and prompt me which tool I wanted to open.

So now I have something like this:

The standard Teamstudio icons are on the right. The new icon will display the following prompt to select the tool to use.

The other annoying thing about implementation Teamstudio's tools is that they lock Designer while they are open. In one of Teamstudio's beta release they were testing the ability to launch a tool in Modal mode which would not lock Designer. This was very nice feature, but it was not implemented because it had some bugs according to them. The one Teamstudio icon that I implemented uses the modal implementation and I never had a problem.
For this article I have split up the code into three sections: Teamstudio Modal, Teamstudio Standard, and Original Teamstudio's Posting. Use what ever fits your needs.

Teamstudio Modal (allows the use of Notes/Domino)

Teamstudio Standard

Original Teamstudio's Posting

The current posting at Teamstudio for Run *Non-Modal* and *Modeless* Versions of Teamstudio Products from a Single Smarticon (You will need to log in)

The link has the following disclaimer on it:
[Editor's note: The modeless (or non-modal) versions of these Teamstudio for Notes products are not supported by the company. Under certain special circumstances crashes have occasionally been reported]