Tips

From Lingoport Wiki
Revision as of 20:43, 9 February 2012 by Olibouban (talk | contribs) (Prevent in-place OLE editors)
Jump to: navigation, search

Create a new Project

You can create a project by pointing to a source code directory in disk, or importing files in the Workbench workspace, which is more used by software engineers ready to refactor code. Importing files in the workspace can be done from files on disk or files in a source code control system, like CVS or SVN

Create a Project by pointing to source code on disk

 File > New > Project -- <Wizard> General > Project

De-select "Use Default Location" and "Browse" to the location of your source code on disk. Name the project and click Finish. If this is the first project, there are no Globalyzer configuration created yet to associate to this project. click ‘New’ To associate scanning logic to the new project click

Scan > Manage Scan

and follow the wizard.


Check out a project

File > New > Project...

and select the source code control system, such as CVS or SVN if you have installed as an extension to the out of the box Workbench.

Note: to add an extension such as SVN:

Help > Install new Software ...

and, for SVN, add "Subclipse - http://subclipse.tigris.org/update_1.6.x/" or another plugin or your choice.

Generating Reports

Prevent possible OLE Error when generating reports

By default, on Windows, OLE applications like Microsoft Word or Excel open as in-place editors. When generating a report, It is possible to get an OLE error when using the default settings because of the specifics of your system. Here are a couple of tips to avoid that error:

Prevent in-place OLE editors

Window > Preferences > General > Editors 

You can force OLE applications to open as stand-alone applications by unchecking the "Allow in-place system editors" option on the preference page.

Prevent opening by default the reports

Window > Preferences > Globalyzer

and uncheck the "Display Report after Export"

Change the file association

Window > Preferences > General > Editors > File associations 

and associate the editor with the offending extension