From: <ou...@us...> - 2006-12-26 13:31:42
|
Revision: 1844 http://svn.sourceforge.net/jcl/?rev=1844&view=rev Author: outchy Date: 2006-12-26 05:31:36 -0800 (Tue, 26 Dec 2006) Log Message: ----------- Updating Readme.html. Splitting informations about experts out of general readme. Modified Paths: -------------- trunk/jcl/docs/Readme.html Added Paths: ----------- trunk/jcl/docs/Experts.html Added: trunk/jcl/docs/Experts.html =================================================================== --- trunk/jcl/docs/Experts.html (rev 0) +++ trunk/jcl/docs/Experts.html 2006-12-26 13:31:36 UTC (rev 1844) @@ -0,0 +1,160 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html lang="en-us"> +<head> + <title>Jedi Code Library Release 1.98</title> + <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> + <link rel="stylesheet" type="text/css" href="styles/default.css"> + <meta content="Project JEDI" name="author"> +</head> + +<body> +<hr><br> +<h1>Jedi Code Library</h1> +<p>Release 1.98<br> +Build 2172<br> +10-February-2006</p> +<hr><br> +<h3>Content of this file</h3> +<ul> + <li><a href="#about">About experts</a></li> + <li><a href="#debug">Debug Extension for JclDebug unit</a></li> + <li><a href="#version">Version control expert</a></li> + <li><a href="#xmm">XMM debug window</a></li> + <li><a href="#favorites">Favorite combobox in Open/Save dialogs</a></li> +</ul> +<hr><br> +<h3><a name="about">About experts</a></h3> +<p>For Delphi 5, Delphi 6, Delphi 7, C++Builder 5 and C++Builder 6, experts can +be installed as design time packages or dll experts. For C#Builder 1 and Delphi 8, +experts are installed as dll experts (those products don't load design time +packages). For Delphi 2005, Borland Developer Studio 2006 and Turbo Delphi Professional, +experts are installed as design time packages.</p> +<h3><a name="debug">Debug Extension for JclDebug unit</a></h3> +<p>The <tt>experts\debug </tt>folder contains an IDE expert which +assists to insert JCL Debug information into executable files. This can be +useful when use source location routines from JclDebug unit. These routines +need some kind of special information to be able provide source location for +given address in the process. Currently there are four options to get it work:</p> +<ol> + <li>Generate and deploy MAP file with your executable file. The file +is generated by the linker. It needs to be set in Project|Options +dialog -> Linker page, Detailed checkbox.</li> + <li>Generate and deploy JDBG file file with your executable file. +This is binary file based on MAP file but its size is typically about +12% of original MAP file. You can generate it by MapToJdbg tool in <tt>jcl\examples\windows\tools</tt> +folder. The advantage over MAP file is smaller size and better security +of the file content because it is not a plain text file and it also +contains a checksum. The IDE expert can automatically create this file +when the project is compiled (see below).</li> + <li>Insert JCL Debug info into executable file. The +size of added data is similar to JDBG file but it will be inserted +directly into the executable file. This is probably best option because +it combines small size of included data and no requirement of deploying +additional files. The IDE expert can automatically insert these informations +when the project is compiled (see below).</li> + <li>Generate Borland TD32 debug symbols. These symbols are stored +directly in the executable file but usually adds several megabytes so +the file is very large. The advantage is you don't have to deploy any +other file and it is easy to generate it by checking Include TD32 debug +info in Linker option page.</li> +</ol> +<p> +The IDE expert will add new item to IDE Project menu. For +Delphi 5, 6 and 7 it adds 'Insert JCL Debug data' check item at the end +of the Project menu. When the item is checked, everytime the project is +compiled by one of following commands: Compile, Build, Compile All Projects, +Build All Projects or Run necessary JCL debug data are automatically created +from the detailled MAP file. The behavior of this conversion can be customized in +the JCL options dialog (in the Tools menu of the IDE): the debug informations can +be exported as .jdbg files or inserted in the binary file. The expert outputs a +message in the IDE message view to display details about the data being generated.</p> +<p> +You can generate those debug data for packages and libraries as well +using the expert. Each executable file in the project can use different option +from those listed above. It is not necessary to generate any debug data for +Borland runtime packages because the source location code can use names of exported +functions to get procedure or method name. To get line number information for +Borland RTL and VCL/CLX units you have to check Use Debug DCUs checkbox in +Project|Options dialog -> Compiler tab. Unfortunately it is not +possible to get line number information for Borland runtime packages +because Borland does not provide detailed MAP files for them so you get +procedure or method name only.</p> +<p>In case you have more than one data source for an executable file by +an accident the best one is chosen in following order:</p> +<ol> + <li>JCL Debug data in the executable file</li> + <li>JDBG file</li> + <li>Borland TD32 symbols</li> + <li>MAP file</li> + <li>DBG and PDB debug informations (for system DLLs)</li> + <li>Library or Borland package export tables</li> +</ol> +<p>It is also possible to create JCL debug data programmatically from a MAP file +by using MakeJclDbg command line tool in jcl\examples\windows\delphitools folder. +This utility can either export data as a separate .jdbg file or insert them in the +executable. You can study included makefiles which uses this tool for building +delphitools examples.</p> +<p>To help using JclDebug exceptional stack tracking in application +simple dialog is provided in <tt>jcl\experts\debug\dialog</tt>folder. The dialog +replaces standard dialog displayed by VCL or CLX application when an unhandled +exception occurs. It has additional Detailed button showing the stack, list of +loaded modules and other system information. By adding the dialog to the +application exceptional stack tracking code is automatically initialized so you +don't have to care about it. You can also turn on logging to text file by setting +the Tag property of the dialog to '1'. There is also version for CLX +(ClxExceptDlg) but it works on Windows only. These dialogs are intended to be added to +Object Repository.</p> +<p><b>Short description of getting the JclDebug functionality in your +project:</b></p> +<ol> + <li>Close all running instances of Delphi +</li> + <li>Install JCL and IDE experts by the JCL Installer +</li> + <li>Run Delphi IDE and open your project +</li> + <li>Remove any TApplication.OnException handlers from your project(if any). +</li> + <li>Add new Exception Dialog by selecting File | New | Other ... | +Delphi Projects | Delphi Files, Select 'JCL Exception Dialog for XXX' (where XXX is +either Delphi or C++Builder depending on your project). A wizard will appear to +configure the options for this dialog. +</li> + <li>Check "Project" | "Insert JCL Debug data" menu item +</li> + <li>Do Project | Build</li> +</ol> +<hr><br> +<h3><a name="version">Version control expert</a></h3> +<p>A new expert integrating version control systems in the IDE was added. +It provides an integration of TortoiseCVS and TortoiseSVN inside the IDE, items +are added in the IDE menu and buttons can be placed in IDE toolbars via the +customize dialog, see below.</p> +<p>A dialog-box provides configuration options for JCL experts in the Tools menu.</p> +<p>It wraps <a href="http://tortoisecvs.sourceforge.net/">TortoiseCVS</a> +and <a href="http://tortoisesvn.sourceforge.net/">TortoiseSVN</a> commands in +actions that can be placed on IDE toolbars and in IDE menu.</p> +<p>This expert requires <a href="http://tortoisecvs.sourceforge.net/">TortoiseCVS</a> +or/and <a href="http://tortoisesvn.sourceforge.net/">TortoiseSVN</a> installed on the +system to properly work. Please refer to these products documentations for help +about using version control systems.</p> +<p>The structure of the "Jcl Version" menu can be customized in the JCL options +dialog (in the "Tools" menu).</p> +<hr><br> +<h3><a name="xmm">XMM debug window</a></h3> +<p>This dialog provides enhancement to the debugger of Delphi and C++Builder regarding +XMM registers. These registers were introduced in SSE instructions (and are still +used in SSE2, SSE3 and SSSE3 instructions). This dialog can be displayed by clicking +on menu View | Debug Windows | SIMD (keyboard shortcut Ctrl+Alt+D). +It is divided in to panes following the style of the FPU window: the left pane +displays content of registers and the right pane displays MXCSR flags. The format +of the registers can be modified from the context. All registers and flags can be +modified and changes will be applied to the debugged process.</p> +<hr><br> +<h3><a name="favorites">Favorite combobox in Open/Save dialogs</a></h3> +<p>This expert modifies the IDE Open/Save dialogs and add a combobox to store your +favorite directories. Items can be added and deleted using the button at the right +of the combobox.</p> +</body> +</html> + Property changes on: trunk/jcl/docs/Experts.html ___________________________________________________________________ Name: svn:keywords + URL HeadURL Author LastChangedBy Date LastChangedDate Rev Revision LastChangedRevision Id Name: svn:eol-style + native Modified: trunk/jcl/docs/Readme.html =================================================================== --- trunk/jcl/docs/Readme.html 2006-12-26 13:20:20 UTC (rev 1843) +++ trunk/jcl/docs/Readme.html 2006-12-26 13:31:36 UTC (rev 1844) @@ -1,131 +1,151 @@ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html lang="en-us"> <head> - <title>Jedi Code Library Release 1.97</title> + <title>Jedi Code Library Release 1.98</title> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <link rel="stylesheet" type="text/css" href="styles/default.css"> <meta content="Project JEDI" name="author"> </head> <body> -<hr> +<hr><br> <h1>Jedi Code Library</h1> -<p>Release 1.97<br> +<p>Release 1.98<br> Build 2172<br> 10-February-2006</p> <hr><br> -<h3>News</h3> -<p>JCL release 1.97 provide an updated support for all targets (including Borland -Developer Studio 2006) and an installation of some experts in C#Builder 1 and Delphi 8.</p> -<p>As always, multiple bugs have been fixed; for detailed change logs, -use the facilities of our CVS repository at <a href="http://sourceforge.net/projects/jcl/">SourceForge.net</a> +<h3>Content of this file</h3> +<ul> + <li><a href="#about">About this release</a></li> + <li><a href="#targets">Supported tools</a></li> + <li><a href="#notes">Installation notes</a></li> + <li><a href="#files">Distribution content</a></li> + <li><a href="#feedback">Giving your feedback</a></li> + <li><a href="#issues">Reporting bugs</a></li> + <li><a href="#releases">Downloads of stable sources</a></li> + <li><a href="#development">Development sources</a></li> + <li><a href="#contribute">Getting involved in JCL development</a></li> +</ul> +<hr><br> +<h3><a name="about">About this release</a></h3> +<p>JCL release 1.98 provide an updated support for all targets (including Borland +Developer Studio 2006 and Turbo Delphi) and an installation of some experts in C#Builder 1 and Delphi 8.</p> +<p>As always, multiple bugs have been fixed; for detailed change logs, +use the facilities of our Subversion repository at Sourceforge.net  +<a href="http://sourceforge.net/projects/jcl/">http://sourceforge.net/projects/jcl/</a> , see below.</p> <p><span style="FONT-WEIGHT: bold">Important:</span> </p> <ul> - <li><p>Note that the package naming has changed: the same package name is used by + <li><p>Note that the package naming has changed: the same package name is used by all versions of the compiler supporting suffixes (C++Builder 6, Delphi 6, Delphi 7, C#Builder 1, Delphi 8, Delphi 2005 and BDS 2006); a different suffix -is added for each target. The installer tries to remove old packages. -3rd party packages requiring old DJcl* resp. CJcl* packages need to be changed +is added for each target to the BPL file name (for BDS 2006, the library file is named jcl100.bpl). +The installer tries to remove old packages. 3rd party packages requiring old DJcl* resp. CJcl* packages need to be changed to accomodate the new naming scheme or they will cause conflicts in the IDE at load time. </p></li> - <li><p>DCP files are now created in the lib\target subdirectory of the JCL -installation. 3rd party packages requiring JCL packages need to have this path + <li><p>DCP files are now created in the lib\target subdirectory of the JCL +installation. 3rd party packages requiring JCL packages need to have this path in their "browse path" option to compile. </p></li> </ul> <p><span style="FONT-WEIGHT: bold">(Windows only) Installation options:</span></p> -<p>Packages compiled by the JCL installer don't contain any debug +<p>Packages compiled by the JCL installer don't contain any debug informations to keep their size as small as possible.</p> <p>The Jedi Code Library packages are required by some 3rd party packages (including the Jedi Visual Component Library - JVCL), the installer generates them if the "Packages" node is checked.</p> -<p>The installer can generate MAP informations for each package. These informations -can be linked into binaries to become JCL debug data. Once linked MAP files could -be deleted. These options are subnodes of the "Packages" node.</p> -<p><span style="FONT-WEIGHT: bold">Experts:</span></p> -<p>For Delphi 5, Delphi 6, Delphi 7, C++Builder 5 and C++Builder 6, experts can -be installed as design time packages or dll experts. For C#Builder 1 and Delphi 8, -experts are installed as dll experts (those products don't load design time -packages). For Delphi 2005 and Borland Developer Studio 2006, experts are -installed as design time packages.</p> -<p>A new expert integrating version control systems in the IDE was added. -It provides an integration of TortoiseCVS and TortoiseSVN inside the IDE, items -are added in the IDE menu and buttons can be placed in IDE toolbars via the -customize dialog, see below.</p> -<p>A dialog-box provides configuration options for JCL experts in the Tools menu.</p> +<p>The installer can generate MAP informations for each package. These informations +can be linked into binaries to become JCL debug data or be converted to .jdbg files. +Once linked MAP files could be deleted. These options are subnodes of the "Packages" node.</p> +<p>For BDS 2006, the compiler introduced a new option to make the same packages available in C++, +by checking the "Dual packages" option of the "Packages" node, you will be able to call functions +of the JCL from C++ code.</p> <p><span style="FONT-WEIGHT: bold">.net Framework support:</span></p> -<p>A subset of JCL units was worked over to support Delphi.Net (Delphi 2005 -& BDS 2006). The packages belong to the Jedi.Jcl namespace.</p> -<hr> -<h3>Supported Tools</h3> -<p><span style="FONT-WEIGHT: bold">Run time support:</span></p> +<p>A subset of JCL units was worked over to support Delphi.Net (Delphi 2005 +& BDS 2006). The packages belong to the Jedi.Jcl namespace. The installer can generate these +packages for Delphi 2005 and BDS 2006, it displays an other tab to configure options and directory. +The installation process is similar to the native targets.</p> +<hr><br> +<h3><a name="targets">Supported Tools</a></h3> +<p>The Jedi Code Library can be compiled and installed in the following environments</p> +<p><span style="FONT-WEIGHT: bold">Only runtime support:</span></p> <ul> - <li>Kylix 3</li> + <li>Kylix 3 (cf <a href="#notes">Installation notes</a>)</li> </ul> -<p><span style="FONT-WEIGHT: bold">Design time support (only experts):</span></p> +<p><span style="FONT-WEIGHT: bold">Only design-time support (only experts):</span></p> <ul> - <li>C#Builder 1 (refer to installation notes below). -</li> - <li>Delphi 8.net (refer to installation notes below).</li> + <li>C#Builder 1 (cf <a href="#notes">Installation notes</a>).</li> + <li>Delphi 8.net (cf <a href="#notes">Installation notes</a>).</li> </ul> <p><span style="FONT-WEIGHT: bold">Both supports (run time and design time):</span></p> <ul> - <li>Delphi version 5, 6, 7 -</li> - <li>C++Builder version 5 & 6 -</li> - <li>Delphi 2005 (Delphi Win32 and Delphi.net personalities) -</li> + <li>Delphi version 5, 6, 7</li> + <li>C++Builder version 5 & 6</li> + <li>Delphi 2005 (Delphi Win32 and Delphi.net personalities)</li> <li>Borland Developer Studio 2006 (Delphi Win32, C++ Builder Win32, Delphi.net and C#Builder personalities)</li> + <li>Turbo Delphi (explorer and professional - cf <a href="#notes">Installation notes</a>)</li> </ul> -<hr> -<h3>Notes</h3> +<hr><br> +<h3><a name="notes">Installation notes</a></h3> <ul> <li>Not every unit supports all tools. Look out for <tt>*.exc</tt> -files in the tool-specific <tt>lib/</tt>subdirectories for a list of units -excluded from compilation. -</li> - <li>Kylix 3/C++ installation is broken; the installer will fail when -it attempts to build the packages. Since the dreaded file open/save dialog Kylix -bug is haunting us again (wasn't it considered to be defeated as of Kernel 2.4.21?), -we are at present not investigating this further. -</li> - <li><a href="http://www.freepascal.org/"><b>Free Pascal</b></a> (FP) -support has not been updated for this release; most units from -source/common should work with FP 2.0, as tests with a 2.0 beta (1.9.8) -indicated, but this has not been verified. Note that there are no plans -to support FP versions from the 1.0 branch.</li> + files in the tool-specific <tt>lib/</tt>subdirectories for a list of units + excluded from compilation.</li> + <li>Kylix 3 Delphi/C++ installation is back but specific code has not been tested with the latest + versions of the kernel. Please ensure you use the flavor of the JCL with Unix EOL.</li> + <li>Free Pascal (<a href="http://www.freepascal.org/">http://www.freepascal.org/</a>) + support has not been updated for this release; most units from + source/common should work with FP 2.0, as tests with a 2.0 beta (1.9.8) + indicated, but this has not been verified. Note that there are no plans + to support FP versions from the 1.0 branch.</li> </ul> +<p><span style="FONT-WEIGHT: bold">Installation for Turbo Delphi</span></p> +<p>The Jedi Code Library can be compiled targetting Turbo Delphi Explorer and Turbo Delphi Professional. +Turbo Delphi Professional is recognized as BDS 2006, you have to download its command line compiler from +CodeGear website at <a href="http://www.codegear.com/Default.aspx?tabid=160">http://www.codegear.com/Default.aspx?tabid=160</a> +to install the full JCL on this tool</p> +<p>To install the JCL targetting Turbo Delphi Explorer, consider the following checks:</p> +<ol> + <li>If you have an other supported version of Delphi/C++Builder on this computer, it should automatically be + detected and the installer will process as usual.</li> + <li>If you only have Turbo Delphi Explorer (and no other tools) on the computer, the installer cannot be + compiled. You have to use the Turbo Explorer flavor of the JCL that contains a precompiled installer. However, + you will not be able to install any experts.</li> +</ol> <p><span style="FONT-WEIGHT: bold">Installation on C#Builder 1 and Delphi 8:</span></p> <ol> <li>These products cannot be used to build the JCL installer, you need an - other supported product to install JCL experts on these products.</li> + other supported product to install JCL experts on these products. +</li> <li>These products are not able to use the JCL library as a runtime library. - You cannot write managed applications and managed packages based on the JCL. + You cannot write managed applications and managed packages based on the JCL. </li> <li>These products are not shipped with their native compilers, you have to - download it from codecentral (<a href="http://cc.borland.com/">http://cc.borland.com</a>). - The item (<a href="http://codecentral.borland.com/Download.aspx?id=21333">21333</a>) + download it from codecentral (<a href="http://cc.codegear.com/">http://cc.codegear.com/</a>). + The item (<a href="http://codecentral.codegear.com/Download.aspx?id=21333">http://codecentral.codegear.com/Download.aspx?id=21333</a>) the native compiler to be installed in Delphi 8. - The item (<a href="http://codecentral.borland.com/Download.aspx?id=21334">21334</a>) + The item (<a href="http://codecentral.codegear.com/Download.aspx?id=21334">http://codecentral.codegear.com/Download.aspx?id=21334</a>) the native compiler to be installed in C#Builder 1. - These zip files have to be extracted in the products director using the standard pattern:</li> + These zip files have to be extracted in the products directory using the standard pattern:</li> </ol> <pre> Executable files (exe and dll) - BDS\X.0\bin Compiler files (dcp and dcu) - BDS\X.0\lib - Toolsapi source files - BDS\X.0\source\ToolsAPI. + Toolsapi source files - BDS\X.0\source\ToolsAPI </pre> -<hr> -<h3>JCL Distribution content</h3> -<pre>Install.bat - Compile and run JCL Installer (Win32) +<hr><br> +<h3><a name="files">Distribution content</a></h3> +<pre>Install.bat - Compile and run VCL version of the JCL Installer (Win32) QInstall.bat - Compile and run CLX version of JCL Installer (Win32) install.sh - Compile and run JCL Installer (Linux) bin - Common place for sample application EXE files lib - Common place for compiled units. docs - Readme (this file) and other documents -examples - JCL example applications +docs\Readme.html - This file +docs\Experts.html - Readme file about the experts +docs\MPL-1.1.txt - The Mozilla Public Licence (MPL) version 1.1 +docs\MPL FAQ.html - Frequently Asked Questions about the MPL +docs\cps.html - Cross Platform Strategy experts - JCL IDE experts source code experts\debug - JCL Debug IDE expert for using JclDebug unit experts\debug\dialog - Application exception dialog replacement @@ -136,17 +156,18 @@ experts\projectanalyzer - Project Analyzer IDE expert experts\useswizard - JCL uses wizard experts\versioncontrol - Integration of TortoiseCVS and TortoiseSVN in the IDE +examples - JCL example applications examples\common - CLX and Win32 example applications in Delphi examples\dotnet - JCL example applications for Delphi.net examples\windows - JCL example applications for Delphi.Win32 examples\windows\delphitools - Collection of system tools using JCL -help - Help file +help - Help file (distributed in a separate archive) install - Installer source code packages - JCL package sources source - JCL source code </pre> -<hr> -<h3>Feedback</h3> +<hr><br> +<h3><a name="feedback">Giving your feedback</a></h3> If you have any comments or suggestions we would appreciate it if you drop us a note. There are several ways to get in contact with us: <ul> @@ -157,164 +178,45 @@ or to <a href="mailto:jcl...@de...">jcl...@de...</a> This email account should not be used for support requests. If you need support please use either the newsgroups or the mailing list.</li> - <li>If you want to keep up to date about JCL then you can join the -JCL mailing list by going to <a href="http://www.egroups.com/group/JEDI-JCL">http://www.egroups.com/group/JEDI-JCL</a> -You can also use this list to voice your opinion, comments or suggestions. -</li> + <li>If you want to keep up to date about JCL then you can join the +JCL mailing list by going to <a href="http://tech.groups.yahoo.com/group/JEDI-JCL/">http://tech.groups.yahoo.com/group/JEDI-JCL/</a> +You can also use this list to voice your opinion, comments or suggestions.</li> </ul> <hr> -<h3>Issue Tracking</h3> -<p>An issue tracking tool can be accessed via ('Code Library' category):</p> -<p><a href="http://homepages.borland.com/jedi/issuetracker/">http://homepages.borland.com/jedi/issuetracker/</a></p> -<p>The general rule is: <b><font color="#ff0000">If you want to get a +<h3><a name="issues">Reporting bugs</a></h3> +<p>The general rule is: <b><font color="#ff0000">If you want to get a bug fixed you need to log it!</font></b></p> +<p>An issue tracking tool can be accessed via ('Code Library' category): +<a href="http://homepages.codegear.com/jedi/issuetracker/">http://homepages.codegear.com/jedi/issuetracker/</a></p> +<p>Please be aware that you are allowed there to enter feature request and code donations as well.</p> <p>The JEDI issue tracker is based up on the Mantis BugTracker Open Source project. More background information about it is available on its homepage <a href="http://mantisbt.sourceforge.net/">http://mantisbt.sourceforge.net</a></p> -<p>Please be aware that you are allowed there to enter feature request -and code donations as well.</p> -<hr> -<h3>Debug Extension for JclDebug unit</h3> -<p>The <tt>experts\debug </tt>folder contains an IDE expert which -assists to insert JCL Debug information into executable files. This can be -useful when use source location routines from JclDebug unit. These routines -need some kind of special information to be able provide source location for -given address in the process. Currently there are four options to get it work:</p> -<ol> - <li>Generate and deploy MAP file with your executable file. The file -is generated by the linker. It needs to be set in Project|Options -dialog -> Linker page, Detailed checkbox. -</li> - <li>Generate and deploy JDBG file file with your executable file. -This is binary file based on MAP file but its size is typically about -12% of original MAP file. You can generate it by MapToJdbg tool in <tt>jcl\examples\windows\tools</tt> -folder. The advantage over MAP file is smaller size and better security -of the file content because it is not a plain text file and it also -contains a checksum. -</li> - <li>Generate Borland TD32 debug symbols. These symbols are stored -directly in the executable file but usually adds several megabytes so -the file is very large. The advantage is you don't have to deploy any -other file and it is easy to generate it by checking Include TD32 debug -info in Linker option page. -</li> - <li>Insert JCL Debug info into executable file by the IDE expert. The -size of added data is similar to JDBG file but it will be inserted -directly into the executable file. This is probably best option because -it combines small size of included data and no requirement of deploying -additional files. In case you use this option you need install the -JclDebugIde expert.</li> -</ol> -<p> -The IDE expert will add new item to IDE Project menu. For -Delphi 5, 6 and 7 it adds 'Insert JCL Debug data' check item at the end -of the Project menu. When the item is checked, everytime the project is -compiled by one of following commands: Compile, Build, Compile All Projects, Build All -Projects or Run necessary JCL debug data are automatically inserted into the -executable. Moreover, for Build and Build All commands dialog with detailed -information of size of these data will be displayed.</p> -<p> -You can generate those debug data for packages and libraries as well -using the expert. Each executable file in the project can use different option -from those listed above. It is not necessary to generate any debug data for -Borland runtime packages because the source location code can use names of exported -functions to get procedure or method name. To get line number information for -Borland RTL and VCL/CLX units you have to check Use Debug DCUs checkbox in -Project|Options dialog -> Compiler tab. Unfortunately it is not -possible to get line number information for Borland runtime packages -because Borland does not provide detailed MAP files for them so you get -procedure or method name only.</p> -<p>In case you have more than one data source for an executable file by -an accident the best one is chosen in following order:</p> -<ol> - <li>JCL Debug data in the executable file -</li> - <li>JDBG file -</li> - <li>Borland TD32 symbols -</li> - <li>MAP file -</li> - <li>Library or Borland package exports</li> -</ol> -<p>It is also possible to insert JCL debug data programmatically to the -executable file by using MakeJclDbg command line tool in -jcl\examples\windows\delphitools folder. You can study included makefiles -which uses this tool for building delphitools examples.</p> -<p>To help using JclDebug exceptional stack tracking in application -simple dialog is provided in <tt>jcl\experts\debug\dialog</tt>folder. The dialog -replaces standard dialog displayed by VCL or CLX application when an unhandled -exception occurs. It has additional Detailed button showing the stack, list of -loaded modules and other system information. By adding the dialog to the -application exceptional stack tracking code is automatically initialized so you -don't have to care about it. You can also turn on logging to text file by setting -the Tag property of the dialog to '1'. There is also version for CLX -(ClxExceptDlg) but it works on Windows only. These dialogs are intended to be added to -Object Repository.</p> -<p><b>Short description of getting the JclDebug functionality in your -project:</b></p> -<ol> - <li>Close all running instances of Delphi -</li> - <li>Install JCL and IDE experts by the JCL Installer -</li> - <li>Run Delphi IDE and open your project -</li> - <li>Remove any TApplication.OnException handlers from your project(if any). -</li> - <li>Add new Exception Dialog by selecting File | New | Other ... | -Dialogs tab, Select 'Exception Dialog' or 'Exception Dialog with Send' -icon, Click OK button, Save the form (use ExceptionDialog.pas name, for -example) -</li> - <li>Check Project | Insert JCL Debug data menu item -</li> - <li>Do Project | Build</li> -</ol> -<hr> -<h3>Version control expert</h3> -<p>The JCL team is proud to release a new expert integrating version control actions -inside the Delphi/BCB/BDS IDE. It wraps <a href="http://tortoisecvs.sourceforge.net/">TortoiseCVS</a> -and <a href="http://tortoisesvn.sourceforge.net/">TortoiseSVN</a> commands in -actions that can be placed on IDE toolbars and in IDE menu.</p> -<p>This expert requires <a href="http://tortoisecvs.sourceforge.net/">TortoiseCVS</a> -or/and <a href="http://tortoisesvn.sourceforge.net/">TortoiseSVN</a> installed on the -system to work properly. Please refer to these products documentations for help -about using version control systems.</p> -<p>The structure of the "Jcl Version" menu can be customized in the JCL options -dialog (in the "Tools" menu).</p> -<hr> -<h3>Downloads of stable sources</h3> -<p>These sources are official JCL releases and file status can be considered as -stable for use in final applications. During the past years, there have been around 2 +<hr><br> +<h3><a name="releases">Downloads of stable sources</a></h3> +<p>These sources are official JCL releases and file status can be considered as +stable for use in final applications. During the past years, there have been around 2 or 3 releases per year.</p> <p>Jedi Code Library: File List on SourceForge: <a href="http://sourceforge.net/project/showfiles.php?group_id=47514">http://sourceforge.net/project/showfiles.php?group_id=47514</a> </p> -<hr> -<h3>Development sources</h3> -<p>These files are under active development and may cause some incompatibilities -and some conflicts with existing code. You should not use these files in final -applications. The JCL development team provides these files for testing and +<hr><br> +<h3><a name="development">Development sources</a></h3> +<p>These files are under active development and may cause some incompatibilities +and some conflicts with existing code. You should not use these files in final +applications. The JCL development team provides these files for testing and feedback from users.</p> - - <html> - <head></head> - <body> -<p>You can download snapshots of the CVS repository updated every day in the - <a href="http://jcl.sourceforge.net/daily">JCL daily page</a> -</p> - </body> - </html> -<p>To always have access to the most recent changes in the JCL, you -should install a CVS client (we recommend TortoiseCVS and WinCVS) and download -the CVS repository files to your computer. With the CVS client, you can update -your local repository at any time. For more instructions on how to set up CVS -and use it with JCL, see the <a href="http://sourceforge.net/docs/E04/">CVS instruction page</a>. -You can also access the CVS repository via the <a href="http://cvs.sourceforge.net/viewcvs.py/jcl/">web interface</a>. -</p> -<hr> -<h3>Getting involved in JCL development</h3> +<p>You can download snapshots of the Subversion repository updated every day in the JCL daily page + <a href="http://jcl.sourceforge.net/daily/">http://jcl.sourceforge.net/daily/</a></p> +<p>To always have access to the most recent changes in the JCL, you +should install a Subversion client (we recommend TortoiseSVN <a href="http://tortoisesvn.tigris.org/">http://tortoisesvn.tigris.org/</a> +and RapidSVN <a href="http://rapidsvn.tigris.org/">http://rapidsvn.tigris.org/</a>) and download the +SVN repository files to your computer as explained in the repository page of the JEDI Wiki at +<a href="http://homepages.codegear.com/jedi/wiki/index.php?title=Repository">http://homepages.codegear.com/jedi/wiki/index.php?title=Repository</a> +With the SVN client, you can update your local repository at any time. +You can also view the repository online via the web interface at <a href="http://jcl.svn.sourceforge.net/">http://jcl.svn.sourceforge.net/</a></p> +<hr><br> +<h3><a name="contribute">Getting involved in JCL development</a></h3> If you want to help out making JCL better or bigger or just plain cooler, there are several ways in which you can help out. Here are some of the things we need your help on: @@ -331,7 +233,7 @@ </ul> <p>JCL accepts donations from developers as long as the source fullfills the requirements set up by the JEDI and JCL teams. To read more about these -requirements, visit the page http://homepages.borland.com/jedi/jcl</p> +requirements, visit the page http://homepages.codegear.com/jedi/jcl</p> <p>You can also donate your time by writing help for the source already in JCL. We currently use Doc-o-Matic to create the finished help files but the actual help sources are plain text files in a simple to understand format. @@ -340,8 +242,9 @@ help text for the help items. If you are interested in writing help, contact us.</p> <p>If you want to help fix bugs in JCL, go to Mantis and check the bug report there. You can post replies as well as fixes directly in the bug report. One of the -JCL developers will pick up the report/fix and update the CVS repository if the fix is -satisfactory. If you report and fix a lot of bugs, you might even get developer -access to CVS so you can update the JCL files directly.</p> +JCL developers will pick up the report/fix and update the Subversion repository if the fi +is satisfactory. If you report and fix a lot of bugs, you might even get developer +access to SVN so you can update the JCL files directly.</p> </body> </html> + This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |