Failed to load latest commit information.
archive Moved JvMessageControl.pas and JvControlComponent to archive Aug 4, 2016
bin Changes required for D2009/C2009 support, merged from the 3.35 branch Sep 9, 2008
common Include files for Tokyo Mar 23, 2017
converter deleted mime-type for text files Aug 9, 2006
dcu Useless files for SVN Apr 17, 2006
design RAD Studio 10.2 Tokyo compatibility Mar 22, 2017
devtools RAD Studio 10.2 Tokyo compatibility Mar 22, 2017
dict Pierre Y. changes to JvChangeNottify and misc changes Aug 31, 2004
examples Added JvThreadDialog samples into the demo May 15, 2017
help Clean up. May 17, 2014
images Mantis 5087: Added Severity and a few other improvements Oct 11, 2010
include XE8 support Apr 11, 2015
install Mantis #6635: 64bit compatibility issues (Installer) Jun 8, 2018
lib Output folders for Tokyo Mar 23, 2017
locale links replaced Aug 4, 2016
packages c6 requires the dbrtl package to be able to link FMTBcd.obj Apr 9, 2018
resources Started component integration Mantis #5037: JvExplorerBar Nov 28, 2010
run Mantis #6631: Drag and Drop privilege elevation Jun 9, 2018
HooksAndHacks.txt * Mantis #5937: TJvComboEdit unpublished properties NumbersOnly and T… Sep 24, 2012
InstallVerbose.bat Added "InstallVerbose.bat" that shows the user why their Delphi versi… Aug 4, 2016
clean.bat RAD Studio 10.2 Tokyo compatibility Mar 22, 2017
install.bat Syntax fix and SkipCmdStarter if already compiled Aug 5, 2016
jvcl3.txt *** empty log message *** Sep 30, 2003
make.proj Fixed wrong "EditionDirVersion" property. Jan 27, 2018
makemodified.bat Allow the batch files to be started from a different current directory Sep 29, 2011
readme.htm links replaced Aug 4, 2016
todo.txt moving JvgProcess to Archive May 16, 2006


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <title>Release Notes for JEDI VCL</title>
  <link href="help/styles/default.css" type="text/css" rel="STYLESHEET">
<h1>Release Notes for JEDI VCL</h1>
<h2>Other release notes included in this distribution</h2>
  <li><a href="help/install.htm">Install</a>. Contains information on
how to install JVCL. </li>
    <p align="left"><a href="help/license.htm">License</a>. Contains
information on the JVCL usage and distribution
license. </p>
  <li><a href="help/migrating.htm">Migrating</a>. Contains information
on how to migrate your
applications from previous versions of JVCL and/or previous versions
of&nbsp;components that has been added&nbsp;in this&nbsp;release of
  <li><a href="help/BCB%20Compatibility%20Guide.html">BCB Compatibility
Guide</a>. Describes how to install JVCL in C++Builder.</li>
  <li><a href="help/JvExVCL.html">JvExVCL description</a>. Describes
how to use the JvExVCL (layer for VCL and VisuaLCLX) in your own code.</li>
  <li><a href="help/Build%20Status.html">Build status</a>. Contains
information on the current build status of the JVCL for supported
Delphi and
BCB versions.</li>
  <li><a href="help/localization.html">Localization</a>. Contains
information on how to enable localization support in JVCL.</li>
<h2>Changes in this version</h2>
<h4>New folder structure</h4>
<p>The files in JVCL is arranged according to a new folder
structure.&nbsp;Previous versions of JVCL put all source files into one
folder and all packages into another. The number of units in JVCL has
forced us to divide this further in the current version. The current
folder structure looks like this:</p>
<p>&nbsp; <b>&lt;root&gt;</b> - contains important documents, like
this readme&nbsp;</p>
<p>&nbsp; <b>\archive</b> - old components (not installed) for those
cases where you
are unable to migrate to a newer version or replacement&nbsp;</p>
<p>&nbsp; <b>\bin</b> - output folder for binaries (from \examples)</p>
<p>&nbsp; <b>\common</b> - contains common units, like API
translations, INC files and the like</p>
<p>&nbsp; <b>\converter</b> - DAT files for JVCLConvert (in
<p>&nbsp; <b>\dcu</b> - output folder for dcu files (from \examples)</p>
<p>&nbsp; <b>\design</b> - contains units only used at design-time</p>
<p>&nbsp; <b>\devtools</b> - contains the sources for various useful
<p>&nbsp; <b>\Dict</b> - dictionary files for TJvSpellChecker</p>
<p>&nbsp; <b>\examples</b> - all available demos</p>
<p>&nbsp; <b>\help</b> - contains the help file(s) and additional
<p>&nbsp; <b>\images</b> - original images and rc files for the
palette icons</p>
<p>&nbsp; <b>\Includes</b> - C/C++ include files for UIB</p>
<p>&nbsp; <b>\install</b> - source scripts and utilities for the
<p>&nbsp; <b>\lib</b></p>
<p>&nbsp;&nbsp;&nbsp; <b>\c5</b> - dcu and obj output for BCB5 packages</p>
<p>&nbsp;&nbsp;&nbsp; <b>\c6</b> - dcu and obj output for BCB6 packages</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d5</b> - dcu output for Delphi 5 packages</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d6</b> - dcu output for Delphi 6 packages</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d7</b> - dcu output for Delphi 7 packages</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d9</b> - dcu output for Delphi 2005 packages</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d10</b> - dcu output for Delphi/C++Builder 2006 packages</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d11</b> - dcu output for RAD Studio 2007 packages</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d12</b> - dcu output for RAD Studio 2009 packages</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d14</b> - dcu output for RAD Studio 2010 packages</p>
<p>&nbsp; <b>\locale</b> - contains the DxGettext template and some
ready to use translations</p>
<p>&nbsp; <b>\packages</b></p>
<p>&nbsp;&nbsp;&nbsp; <b>\bin</b> - bootstrapping tools</p>
<p>&nbsp;&nbsp;&nbsp; <b>\c5</b> - packages for C++Builder 5</p>
<p>&nbsp;&nbsp;&nbsp; <b>\c6</b> - packages for C++Builder 6</p>
<p>&nbsp;&nbsp;&nbsp; <b>\c6per</b> - modified packages for C++Builder 6 Personal Edition</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d5</b> - packages for Delphi 5</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d5std</b> - modified packages for Delphi 5 Standard</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d6</b> - packages for Delphi 6</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d6per</b> - modified packages for Delphi 6 Personal Edition</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d7</b> - packages for Delphi 7</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d7per</b> - modified packages for Delphi 7 Personal Edition<br>
<p>&nbsp;&nbsp;&nbsp; <b>\d9</b> - packages for Delphi 2005</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d9per</b> - modified packages for Delphi 2005 Personal Edition<br>
<p>&nbsp;&nbsp;&nbsp; <b>\d10</b> - packages for Delphi/C++Builder 2006</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d11</b> - packages for RAD Studio 2007</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d12</b> - packages for RAD Studio 2009</p>
<p>&nbsp;&nbsp;&nbsp; <b>\d14</b> - packages for RAD Studio 2010</p>
<p>&nbsp;&nbsp;&nbsp; <b>\xml</b> - Source xml files for the packages.
All the packages are generated from these files.</p>
<p>&nbsp; <b>\Resources</b> - contains res, dcr and other resource
files used at either run or design time</p>
<p>&nbsp; <b>\run</b> - contains units used at run-time</p>
<p>Depending on which distribution of JVCL you download, some folders
and files
might not be created on your system.</p>
<h4><a name="Theming"></a>Theming</h4>
<p>Several visual JVCL controls supports XP theming (more will likely
be added subsequently). Theming is automatically activated for users of
Delphi 7 (and above) and you don't need to do anything special in this
case. For earlier versions of Delphi (5 and 6), you need to download
Mike Lischke's ThemeManager package and configure the JVCL theming
support manually. To activate JVCL theming, proceed as follows:</p>
  <li>Download ThemeManager from <a
  <li>Open ThemeManager?.dpk (where "?" is the Delphi version) and
change the compile options to "Explicit rebuild".</li>
  <li>(Re)build and install the ThemeManager package.</li>
  <li>For manual installation: Open with a text editor and
remove the dot in {.$DEFINE
JVCLThemesEnabled}. </li>
  <li>(Re)build the jvcl packages.</li>
If you want theming support in C++ Builder 5 and 6, you will need to
manually create the appropriate DCP file for the installation to
succeed instead of the steps two and three in the above list. Here are
the steps for BCB5, thanks to Carmelo Viavattene :<br>
  <li>In the ThemeManager directory, copy ThemeManagerD5.dpk to
ThemeManagerC5.dpk and ThemeManagerD5D.dpk to ThemeManagerC5D.dpk</li>
  <li>Do the same with the .res files<br>
  <li>With a text editor, open ThemeManagerC5.dpk and do the following
    <li><span style="font-style: italic;">package ThemeManagerD5;</span>
by <span style="font-style: italic;">package ThemeManagerC5;</span></li>
    <li><span style="font-style: italic;">{$IMPLICITBUILD ON} </span>by
      <span style="font-style: italic;">{$IMPLICITBUILD OFF}</span></li>
  <li>With a text editor, open ThemeManagerC5D.dpk and do the following
    <li><span style="font-style: italic;">package ThemeManagerD5D;</span>
by <span style="font-style: italic;">package ThemeManagerC5D;</span></li>
    <li><span style="font-style: italic;">requires ThemeManagerD5 </span>by
      <span style="font-style: italic;">requires ThemeManagerC5</span><br>
    <li><span style="font-style: italic;">{$IMPLICITBUILD ON} </span>by
      <span style="font-style: italic;">{$IMPLICITBUILD OFF}</span></li>
  <li>Open a command prompt and go in the folder where the newly
created packages (dpk files) are located</li>
  <li>Run these commands, replacing $(ROOT) by the root folder of your
BCB5 installation (c:\program files\CBuilder5 by default):</li>
    <li>$(ROOT)\bin\dcc32 ThemeManagerC5.dpk</li>
    <li>$(ROOT)\bin\dcc32 ThemeManagerC5D.dpk</li>
  <li>Copy the two newly created files to $(ROOT)\projects\bpl</li>
  <li>Copy the eight newly created OBJ files from
$(ROOT)\projects\intermed to $(ROOT)\projects\lib</li>
  <li>Now in the ThemeManager source directory, edit TmSchema.hpp and
do the following replacement:</li>
    <li><span style="font-style: italic;">#include "tmschema.h" </span>by
      <span style="font-style: italic;">#include
  <li>Also edit UxTheme.hpp and do the following replacement:<br>
    <li><span style="font-style: italic;">#include "uxtheme.h"</span>
by <span style="font-style: italic;">#include "..\cbuilder\uxtheme.h"</span></li>
Theming should now be activated for those JVCL controls that
supports it. Note that you still need to be running on Windows XP with
a manifest file for your project to see any theming.<br>
All strings that get displayed to the user are stored in resource
strings. If you want the JVCL to display those strings in other
languages, you should use DxGettext as this is the only localization
method supported by the JVCL group. You must turn on the use of
DxGettext in and recompile the JVCL packages for the support
be complete. Please refer to the <a href="help/localization.html">localization</a>
documentation for more details on this topic.<br>
<h4>CLX support</h4>
<p>CLX support was dropped in Version 3.33</p>
<h4>Available distributions</h4>
<p>The JVCL is&nbsp;available in three different distributions. These
<ul dir="ltr">
  <li><strong>Minimum&nbsp;</strong>- only contains the files needed to
install the components </li>
  <li><strong>Medium </strong>- same as Minimum but also includes the
demo folders </li>
  <li><strong>Full </strong>- contains everything in the CVS
repository as well as the latest release of JCL</li>
<p dir="ltr">&nbsp;</p>
<p dir="ltr">Each of the "stand-alone" packages are also available as
separate distributions (see USEJVCL below for a list of stand-alone
In case we get enough requests, we might also provide each package as a
<p dir="ltr">&nbsp;</p>
<h4>New package layout</h4>
<p>Previous versions of JVCL had one run-time and one design-time
package for each version of supported compilers (i.e one pair for
Delphi 5, another pair for Delphi 6 etc). The current&nbsp;JVCL,
however, is split into a larger set of smaller packages, where each
package&nbsp;contains logically related components. Each run-time
package also has a matching design-time package with the registration
code and any design-time editors required by the run-time package. The
following packages are currently available:</p>
<table border="0" cellpadding="2" cellspacing="2" width="100%">
      <th>Required JVCL packages (packages in parenthesisses are
required by the design-time package)</th>
      <td>Contains the core units used by a large part of the JVCL</td>
      <p>Core support units</p>
      <td>System related components</td>
      <td>"Standard" or enhanced standard controls</td>
      <p>TJvToolBar<sup> 3.</sup></p>
      <td>JvCore, JvSystem</td>
      <td>Visual controls</td>
      <td>JvCore, JvStdCtrls</td>
      <td>Non-visual components</td>
      <td>JvCore, JvSystem (JvStdCtrls)</td>
      <td>Custom controls and "advanced" components</td>
      <p>TJvLookOutButton </p>
      <td>JvCore, JvCtrls, JvSystem, </td>
      <td>Dialog components</td>
      <td>JvCore, JvSystem, JvStdCtrls</td>
      <td>Encryption and Compression components</td>
      <td>Multimedia and graphic components</td>
      <p>TJvID3v1 and&nbsp;TJvID3v2</p>
      <td>JvCore, JvCmp, JvCtrls, JvSystem</td>
      <td>HMI Components</td>
      <td> TJvLED
      <td>Network and Internet technology components</td>
      <td>JvCore, (JvStdCtrls)</td>
      <td>Application and Form related components</td>
      <td>JvCore, JvSystem, JvStdCtrls, (JvCmp, JvMM, JvCtrls)</td>
      <td>JvDB <sup>5.</sup><br>
      <td>Generic DB access and DB controls</td>
      <td>JvCore, JvStdCtrls,</td>
      <td>JvBDE <sup>5.</sup><br>
      <td>BDE specific components and controls</td>
      <td>JvCore, JvDB, JvDlgs</td>
      <td>Components and units related to JvInterpreter</td>
      <td>JvCore, JvCtrls, JvCustom</td>
      <td>Units for band object development</td>
      <td>Band object wizard</td>
      <td>JvPlugin related components</td>
      <p>Plugin wizard</p>
      <td>Jans Delphi Components</td>
      <td>Globus Delphi Components</td>
      <p>TJvgExportDBETable <sup>5.</sup><br>
      <p>TJvgDBGrid <sup>5.</sup><br>
      <p>TJvgVertDBSGrid <sup>5.</sup><br>
      <p>TJvgQRLabel <sup>5.</sup><br>
      <p>TJvgQRDBText <sup>5.</sup><br>
      <p>TJvgMyQRPreview <sup>5.</sup><br>
      <td>JvCore, JvSystem, JvStdCtrls, (JvCtrls, JvCustom, JvDlgs,
      <td>Print Preview Components</td>
      <td>Page style components</td>
      <td>Validator and Error Indicator components</td>
      <td>UIB (Unified Interbase) Components</td>
      <td>JvCore <sup>4.</sup><br>
      <td>Wizard component and RouteMaps formerly known as "K Wizard"</td>
      <td>JvCore <sup>4.</sup></td>
      <td>Set of PIM components formerly known as UIL Time Framework 2.0</td>
      <td> TJvTFAlarm
      <td>JvCore <sup>4.</sup><br>
      <td>Thread components (for version 6 and newer only)<br>
      <p>TJvMtMonitorSection </p>
      <td>DotNet style components (Do not require the .Net framework to
be installed)<br>
      <td> TJvDotNetCheckListBox
      <p>TJvDotNetDBEdit <sup>5.</sup><br>
      <p>TJvDotNetDBListBox <sup>5.</sup><br>
      <p>TJvDotNetDBMemo <sup>5.</sup><br>
      <p>TJvDotNetDBRichEdit <sup>5.</sup><br>
      <td>Docking components</td>
      <td> TJvDockServer
      <p>TJvDockVSNetStyle </p>
      <td>JvCore <sup>4.</sup></td>
      <td>XP/Office XP style controls (Do not require to run on XP to
display correct look)<br>
      <td> TJvXPStyleManager
1. Not available in C++ Builder 6<br>
2. Not available in C++ Builder 5<br>
3. Limited functionality in Delphi 5<br>
4. If USEJVCL is defined (it is by default). If you change the
definition of USEJVCL, you MUST regenerate the packages using the
PackageGenerator available in $(JVCL)\devtools. The installer will do
that for you.<br>
5. Not available in Standard and Personal versions.<br>
<h4>New components added</h4>
<p>The following new components and libraries has been added since JVCL
  <li>The Globus Library </li>
  <li>Jans Delphi Components </li>
  <li>The UIB Interbase/Firebird Database Components </li>
  <li>Print Preview components </li>
  <li>Validator components </li>
  <li>K Wizard component and RouteMaps</li>
  <li>UIL Time Framework 2.0</li>
  <li>Managed Threads Components</li>
  <li>TJvAppInstances (controls how often an application can be startet</li>
  <li>TJvImageList (can handle resources and external images)</li>
  <li>DockPresident components</li>
  <li>Delphi eXperience Controls II</li>
  <li>Delphi eXperience DotNet Controls II</li>
  <li>TJvLookupAutoComplete (extends edit fields with autocomplete
  <li>TJvDebugHandler (creates log files on exceptions with call stack)</li>
<h4>Components deprecated, renamed, removed or changed </h4>
<p>Below follows a list of components that have been removed, renamed
or are deprecated
since JVCL 2.10 (i.e they will most likely disappear in the near
<h5>Removed Components</h5>
  <p>TJvBreatheSkin, TJvCommandEdit, TJvCoupler, TJvCPUUsage,
TJvHighLighter, TJvMemoryInfos, TJvMousePositionner, TJvNagScreen,
TJvPerforated, TJvPopupMemo, TJvAutoSave, TJvRegAuto, TJvCurrencyEdit,
TJvxCurrencyEdit, TJvFloatEdit, TJvFloatEdit2, TJvButton </p>
<h5>Renamed Components</h5>
  <p>The following units and classes have been renamed in this version:</p>
<h5>Deprecated Components</h5>
  <p>TJvControlPanelButton, TJvStartMenuButton, TJvFavoritesButton,
<h5>Changed Components</h5>
  <p>TJvComputerInfo has been changed from TComponent to TObject. This
change was
done to promote safety since there was a risk that the streaming of
properties could modify important registry values on the end-users
computer. To
continue using TJvComputerInfo, open the form where it is located and
click the
"Ignore All" button when Delphi/BCB reports that TJvComputerInfo
cannot be found. Add a private variable of type TJvComputerInfo (with
the same
name as the former TJvComputerInfo component) to the form and create
the class
dynamically. You should now be able to use the class without any
side-effects. For more details, see the comments at the top of
<h4>Naming convention changed</h4>
<p>To keep JVCL consistent, we have adopted a new naming standard. The
naming&nbsp;standard in JVCL&nbsp;affects both classes, types and unit
names. The following section explains the new naming convention
enforced in JVCL:</p>
<blockquote dir="ltr" style="margin-right: 0px;">
<blockquote dir="ltr" style="margin-right: 0px;">
    <li>All files have a "Jv" prefix (capital "J", lower case "v") and
we use "Camel Casing" for the file name
(JvLikeThisForExample.pas).&nbsp; </li>
    <li>All files have an extension in all lower case letters. </li>
    <li>All units are named using the full name of the contained
component/control without the leading "T". If the unit contains several
classes/components, it is either named after the component that will be
installed, the most "significant" component or uses a name that
describes the components in the unit as well as possible. For example,
a unit
with several database components could be named "JvDBControls.pas"
whereas a unit containing a TJvEditor control would be named
"JvEditor.pas". </li>
    <li>All image file names are in ALL UPPER CASE (TJVALARM.BMP)</li>
    <li>All include file names are in ALL LOWER CASE (</li>
<p><strong>Using the word "Form" in filenames</strong></p>
<blockquote dir="ltr" style="margin-right: 0px;">
  <p>All forms (units with DFM's) are suffixed with the word "Form"
regardless of whether they contain a dialog or a form (i.e
JvDualListForm.pas). The word "Form" can also be used as a prefix if
the component in the unit is acting upon a form without being one
itself (i.e JvFormMagnet.pas) </p>
<p><strong>Using the word "Dialog" in filenames</strong></p>
<blockquote dir="ltr" style="margin-right: 0px;">
  <p>The word "Dialog" in a unit name signifies that the unit contains
a component that has no UI at designtime but shows a form or dialog at
run time (i.e JvObjectPickerDialog.pas). At the moment, "Dlg" and
"Dlgs" are accepted but their use is discouraged. </p>
<p><strong>Using the words "Const" and "Consts" in filenames</strong></p>
<blockquote dir="ltr" style="margin-right: 0px;">
  <p>The words "Const" and "Consts" are only used in units that
contains just type, resourcestring and const declarations and no code
(i.e JvConsts.pas). </p>
<p><strong>Using the words "Util" and "Utils" in filenames</strong></p>
<blockquote dir="ltr" style="margin-right: 0px;">
  <p>The word "Util" and "Utils" are only used in units that contains
support routines and classes of more general use (i.e JvJVCLUtils.pas).
Classes in util type units should never be installable. </p>
<p><strong>Design time editors</strong></p>
  <p>Units containing designtime editors should have the same base name
as the component they are primarily used to edit and an "Editor" or
"Editors" suffix, i.e a property editor unit for the TJvBehaviorLabel
should be called either "JvBehaviorLabelEditor" or
"JvBehaviorLabelEditors". </p>
  <p>&nbsp; </p>
  <p>The base name for the unit is controlled by the name of the
component the editor(s) were meant for: if all editors are for the same
component, we use the same rule as for a single editor (the plural
form), if the unit contains generic editors, we name the unit either
according to the editors "family" ("JvDBEditors" contains design
editors for DB related components) or according to it's general data
type (i.e "JvDateEditors" contains editors used to edit date related
properties). </p>
  <p>&nbsp; </p>
  <p>It doesn't matter (name wise) if a unit contains property,
component or any other types of editor. They are all named the same
way. If a design editor is implemented in the same unit as a form, the
unit is named with a "Form" suffix (see rule above for using the word
"Form" in filenames). The reasoning behind this is simple: if a split
of the unit is to be done in the future (which is likely), it is the
design editor that will be moved to a new unit, not the form. The new
unit for the editor will then get an appropriate name with a "Editor"
suffix but the name of the form will not change. </p>
  <p>&nbsp; </p>
  <p>Adding design editors to form units is discouraged. We try to keep
editors in their own unit, preferably one editor per unit. Editor units
should not contain their own Register procedure. The Register procedure
should only be present in specific "Reg" files for a package (see
below). This minimizes confusion and clutter and maximizes reuse, loose
coupling and simplifies maintenance and future restructuring. </p>
<p><strong>Registration units</strong></p>
<blockquote dir="ltr" style="margin-right: 0px;">
  <p>Each design package have it's own registration unit with a
Register procedure. The unit is named with the same base name as the
package but with a "Reg" suffix (i.e the reg file for the "JvCore"
design package is named "JvCoreReg.pas"). The reg file only contains
registrations for the components and design editors. Design editors and
other support code is not added to the reg file unless absolutely
necessary. </p>
  <p>&nbsp; </p>
  <p>A matching dcr file is also included in the \resources folder. The
dcr file always have the same base name as the reg file but with a dcr
file extension (i.e the palette icons for components registered in
JvCoreReg.pas is in \resources\JvCoreReg.dcr). </p>
<p><strong>Palette images color coding</strong></p>
<blockquote dir="ltr" style="margin-right: 0px;">
  <p>All component icons have a common background and an upper case
yellow "J" in a rectangle in the bottom right corner of the image. The
background color of the&nbsp;rectangle identifies the type of component
the icon represent. Currently, we use the following color codes:</p>
  <p><strong>Blue </strong>- Visual components</p>
  <p><strong>Green</strong> - Non-visual components</p>
  <p><strong>Purple</strong> - Database components (visual and
  <p><strong>Maroon - </strong>data provider components (implements
one or more of the IJvDataProvider interfaces)</p>
  <p><strong>Navy</strong> - data consumers (data provider aware
<h2>Getting involved in JVCL development</h2>
<p>If you want to help out making JVCL better or bigger or just plain
cooler, there are several ways in which you can help out.&nbsp; Here
are some of the things we need your help on:</p>
  <li>Donate components and other source code </li>
  <li>Donate time writing help </li>
  <li>Donate time writing demos </li>
  <li>Donate time fixing bugs</li>
<h4>Donate components and other source code</h4>
<p>JVCL accepts donations from developers as long as the components
fulfill the requirements set up by the JEDI and JVCL teams. To read
more about these requirements, visit the page <a
<h4>Donate time writing help</h4>
<p>You can also donate your time by writing help for the components
already in JVCL. 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. We can provide you with auto-generated templates
with all classes, properties, types etc already inserted. The "only"
thing left to do is fill in the actual help text for the help items. If
you are interested in writing help, contact us. </p>
<h4>Donate time writing demos</h4>
<p>One of the best ways of getting to know a new component is to see
the source code of a demo using it and although we have a lot of demos
in JVCL, we still need more and some of the existing demos needs to be
"beefed up". Many developers create test apps to try out a new
component before putting it to use in their real projects so if you
have such a demo or is interested in making more full blown demos for
JVCL, contact us.</p>
<h4>Donate time fixing bugs</h4>
<p>If you want to help fix bugs in JVCL, go to Mantis and check the bug
reports there. You can post replies as well as fixes directly in the
bug report. One of the JVCL 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 JVCL files directly.</p>
<h2><a name="contact"></a>Getting in touch with JVCL developers and
other users</h2>
<p>You can get in touch with the JVCL team and/or other JVCL users in
one of the following manners:</p>
  <li>Homepage. Our homepage is located at <a
 href=""></a> </li>
  <li dir="ltr">
    <p dir="ltr">Newsgroups. You can access the JVCL newsgroups at <a
news://</a> (preferred). Another way to access
the newsgroups is to use the web gateway <a href=""></a>. Thanks to Marco Cant&uacute;
(author of the "Mastering Delphi" books), you can also
access the newsgroups from the Web at <a
 href=""></a>. </p>
  <li>Mail lists. There are still some mail lists on Yahoo to discuss
JVCL but these are gradually being closed down, so please do not use
these. If you can't access the newsgroups, you can post messages to the
mail lists on sourceforge. Go to <a href=""></a>
and click the "Lists" link to get to the soureforge mail lists
(deprecated). </li>
  <li>Bug reporting. To report bugs, suggest improvement or new
features or donate a component, go to Mantis (our on-line bug tracker)
and post/reply to the reports there. You'll find Mantis at <a
 href=""></a>. Please make sure your
problem hasn't already been reported and fixed before posting a new bug