Question 1: Can I share the license 50-50 with my colleague?

Answer: No, for that you need a floating license and we currently do not offer floating licenses. The license model is single user licenses, this means that each license is tied to one person. And it doesn't really matter how much or how little the person is using the license.

You are allowed to activate the same license on multiple machines as long as it is the same person that is using it.

Question 2: Can I create normal LabVIEW classes with the GOOP Development Suite?

Answer: Sure, open the "Class Provider Options..." dialog by clicking on the green tools button or from the Tools->GOOP menu. Select Symbio LabVIEW Native as class provider. The next GOOP class you create will be a normal LabVIEW lvclass created from a class template so it has an Init method and a CleanUp method by default.

Question 3: Will the GOOP classes work on future LabVIEW versions?

Answer: No one can gaurantee that existing code will run on future LabVIEW versions. But Symbio has built in a way of that maintaining the GOOP 3 classes (the native classes is no problem since no extras is added to them). GOOP code needs future maintenance due to bug fixes or LV compatibility is:

1. The GOOP 3 Kernel:
C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\addons\_goop3.llb
these are run-time VIs used by all created GOOP 3 classes. If Symbio releases a new version of the GOOP kernel you will simply need to install this version and then you are all set to go.

2. The GOOP 3 class templates. The class templates are used as template VIs when a new class is created. They therefore become a part of your code. If Symbio releases a new version of the class templates, this will cause all classes created thereafter to use the new class templates. However, your existing code is unchanged. Therefore, we included an Update Class Template feature. This feature allows you to udate the class template for all existing classes to the latest installed class template. This feature saves you a huge bulk of manual labour and ensures Symbio can keep the GOOP 3 classes compatible with future LabVIEW versions.

Question 4: How do I uninstall the GOOP Development Suite?

Answer: Open the Product Information dialog from: Tools->GOOP. In the lower left corner there is an uninstall button.

For manual uninstall:

1. Delete the source code folder:
C:\Program Files\National Instruments\LabVIEW 8.5\resource\Framework\Providers\Endevo

2. Delete the license files folder:
C:\Documents and Settings\UserName\My Documents\LabVIEW Data\Endevo_GDS

3. Delete the GOOP 3 runtime VIs:
C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\addons\_goop3.llb

Question 5: What happens if I stop using the GOOP Development Suite?

Answer:Nothing, the code will continue to run. The native classes can be maintained by LabVIEW built-in features. The GOOP3 and OpenG classes will be harder to maintain without a tool. Method creation is ok, you can just copy and rename an existing method. But renaming a class or changing inheritance hierarchy is hardly feasible without the tool.

Using UML doesn't create any new code dependencies, it is just another way of creating the code.

Question 6:  Can I install the same license on several computers?

Answer: Yes, the licenses are single user licenses. This means that as long as it is the same user on the different machines, it is ok to install the same license on several computers.

Question 7: What is the difference between GOOP 3 and GOOP 2?

Answer: This is described in the GOOP Development Suite - manual. To obtain this manual, please contact tool_support@symbio.com.

Question 8: Why does the activation suddenly fail?

Answer: Symbio‘s license server counts the number of activations. The default setting allows the license to be activated on 5 different machines. This is normally sufficient. If you hit the limit just contact tool_support@symbio.com.

Question 9: What are the limitations in the Community Edition?

Answer: The GOOP Development Suite - Community Edition is a limited version of the UML Architect Edition. These are the limitations:

• Max 5 classes in a UML class diagram
• Max 10 classes in project, 5 of these can be GOOP3
• No update class to new template feature
• No support

The Community Edition license is not time limited and commercial usage is allowed.