Update of /cvsroot/opengtoolkit/deab/developer docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv12593/developer docs
Modified Files:
DEAB Glossary.htm
Log Message:
added some term definitions to the Glossary
Index: DEAB Glossary.htm
===================================================================
RCS file: /cvsroot/opengtoolkit/deab/developer docs/DEAB Glossary.htm,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** DEAB Glossary.htm 3 Nov 2004 12:46:44 -0000 1.4
--- DEAB Glossary.htm 5 Nov 2004 04:24:13 -0000 1.5
***************
*** 31,36 ****
<p><a name="Ambiguous_VI"></a><b>Ambiguous VI</b> -
a VI which has at least one caller that expected it to have been loaded from different location on disk. This can be caused by having two instances of the Ambiguous VI on disk, but usually is caused by an application hierarchy that was reorganized (folder structures changed) on disk and was not re-saved.</p>
! <p><a name="Build_Root" id="Build_Root"></a><b>Build Root</b> -</p>
! <p><a name="EXE" id="EXE"></a><b>EXE</b> - An executable program.</p>
<p><a name="External_Subroutine" id="External_Subroutine"></a><b>External Subroutine</b> -
A binary file containing common code to be called from several CINs. Typically
--- 31,36 ----
<p><a name="Ambiguous_VI"></a><b>Ambiguous VI</b> -
a VI which has at least one caller that expected it to have been loaded from different location on disk. This can be caused by having two instances of the Ambiguous VI on disk, but usually is caused by an application hierarchy that was reorganized (folder structures changed) on disk and was not re-saved.</p>
! <p><a name="Build_Root" id="Build_Root"></a><b>Build Root</b> - The (configurable) path where the built software product is to be created all destination locations are specified relative to the build root.</p>
! <p><a name="EXE" id="EXE"></a><b>EXE</b> - An executable program. On windows this usually has an *.exe file extension. On Linux, executables will probably not have any file extension. On Macintosh, they will probably have a *.app extension.</p>
<p><a name="External_Subroutine" id="External_Subroutine"></a><b>External Subroutine</b> -
A binary file containing common code to be called from several CINs. Typically
***************
*** 48,52 ****
ordinary VIs opened).
</p>
! <p><a name="Icon_File" id="Icon_File"></a><b>Icon File</b> -</p>
<p><a name="Log_Dir" id="Log_Dir"></a><b>Log Dir</b> - A directory, to which
DEAB writes a log file.</p>
--- 48,52 ----
ordinary VIs opened).
</p>
! <p><a name="Icon_File" id="Icon_File"></a><b>Icon File</b> - In windows an icon file contains several icon images. Icon files in windows have an *.ico file extension. </p>
<p><a name="Log_Dir" id="Log_Dir"></a><b>Log Dir</b> - A directory, to which
DEAB writes a log file.</p>
***************
*** 58,70 ****
suffix pattern that will generate a unique suffix containing date/time of a
build, so each build will write new log file.</p>
! <p><a name="Name_Mangle" id="Name_Mangle"></a><b>Name Mangle</b> -</p>
! <p><a name="Namespace" id="Namespace"></a><b>Namespace</b> -</p>
! <p><a name="Project_Root" id="Project_Root"></a><b>Project Root</b> -</p>
<p><a name="Resource"></a><b>Resource File</b> - General term used to designate
! non-VI files to which a VI can be linked. Typically, resource file is Help File,
! Run-Time menu, Shared Library, etc. </p>
! <p><a name="Shared_Library" id="Shared_Library"></a><b>Shared Library</b> -</p>
! <p><a name="Source_Root" id="Source_Root"></a><b>Source Root</b> -</p>
! <p><a name="Support_File" id="Support_File"></a><b>Support File</b> -</p>
</body>
</html>
--- 58,70 ----
suffix pattern that will generate a unique suffix containing date/time of a
build, so each build will write new log file.</p>
! <p><a name="Name_Mangle" id="Name_Mangle"></a><b>Name Mangle</b> - Name mangling is the process of renaming a file according to some convention. The DEAB uses the convention <em>OriginalFilePrefix</em>.vi --> <em>OriginalFilePrefix</em>__<em>NameSpace</em>.vi, where a double-underscore ("_") character seperates the original file name prefix and the namespace. This is done to create a unique <a href="#Namespace">namespace</a> for the application. </p>
! <p><a name="Namespace" id="Namespace"></a><b>Namespace</b> - In LabVIEW, no VIs in memory can share the same name. This is referred to as a global namespace. By <a href="#Name_Mangle">Name Mangling</a>, we can create unique namespaces for applications. This allows two built applications to be in memory, which share source VIs having the same name.</p>
! <p><a name="Project_Root" id="Project_Root"></a><b>Project Root</b> - The (configurable) path where the software product is located. Relative paths such as the <a href="#Source_Root">Source Root</a> and <a href="#Build_Root">Build Root</a> are specified relative to the Project Root.</p>
<p><a name="Resource"></a><b>Resource File</b> - General term used to designate
! non-VI files to which a VI can be linked. Typically, resource file is <a href="#Help_File">Help File</a>,
! Run-Time menu, <a href="#Shared_Library">Shared Library</a>, etc. </p>
! <p><a name="Shared_Library" id="Shared_Library"></a><b>Shared Library</b> - <font size="-1">A file that contains routines that can be dynamically loaded and shared by applications. In LabVIEW, shared libraries are called using the Call Library Function primitive.</font> In Windows shared libary files are called Dynamic Linked Libraries and have a *.dll file extension. In Linux, shared libraries have a *.so file extension. In Mac OS 9 shared libraries have a .shlb file extension and in Mac OS X, they have a *.framework file extension. </p>
! <p><a name="Source_Root" id="Source_Root"></a><b>Source Root</b> -The (configurable) path where the software product source files are kept. Source file paths are specified relative to the Source Root. </p>
! <p><a name="Support_File" id="Support_File"></a><b>Support File</b> -A support file is a file which is part of the built software product, but is not a VI, CTL, or other file that LabVIEW has knowledge of. Since this file can not be located using LabVIEW it must be explicitly specified as a Support File. </p>
</body>
</html>
|
