|
| Winform control import wizard in VCL.NET |
 |
29 Jul 2006 02:24:28 -0700 |
Hi,
I am planning to use the .NET based 3rd party controls such as Xtragrid or
Essential Grid in VCL.NET platform.
The question I have are:
1. Is design-time feature of these controls supported in VCL.NET? As I don't see
the properties in object inspector.
2. Is it possible to code all design-time properties functionality at run-time
in VCL.NET code-behind .NFM pascal file?
3. Is ".NET Databinding model" supported for these controls in VCL.NET
platform?
4. Is .NET 3rd party control (Winform based controls) support for VCL.NET
platform?
regards,
Jitender
|
| Post Reply
|
| Re: Winform control import wizard in VCL.NET |
 |
Sat, 29 Jul 2006 09:38:04 -040 |
On 29 Jul 2006 02:24:28 -0700, Jitender wrote:
> 1. Is design-time feature of these controls supported in VCL.NET?
> As I don't see the properties in object inspector.
You should at least see some properties. Some will be unsupported if
they have types that the VCL framework does not understand.
> 2. Is it possible to code all design-time properties functionality
> at run-time in VCL.NET code-behind .NFM pascal file?
In the Pascal file? Yes it should be.
> 3. Is ".NET Databinding model" supported for these controls in
> VCL.NET platform?
Only if you use .NET datasets and create the bindings in code.
> 4. Is .NET 3rd party control (Winform based controls) support for
> VCL.NET platform?
Only by using the wizard. Also I have found some controls that don't
work.
--
Marc Rohloff [TeamB]
|
| Post Reply
|
| Re: Winform control import wizard in VCL.NET |
 |
31 Jul 2006 06:00:08 -0700 |
Is .NET based 3rd party controls like Xtragrid or Essential Grid tested in
VCL.NET platform?
As I don't find any general issues with these controls in VS.NET (C#) for which
this control was targetted(Developed).
regards,
Jitender
"Marc Rohloff [TeamB]" <"on request"> wrote:
>On 29 Jul 2006 02:24:28 -0700, Jitender wrote:
>
>> 1. Is design-time feature of these controls supported in VCL.NET?
>> As I don't see the properties in object inspector.
>You should at least see some properties. Some will be unsupported if
>they have types that the VCL framework does not understand.
>
>> 2. Is it possible to code all design-time properties functionality
>> at run-time in VCL.NET code-behind .NFM pascal file?
>In the Pascal file? Yes it should be.
>
>> 3. Is ".NET Databinding model" supported for these controls
in
>> VCL.NET platform?
>Only if you use .NET datasets and create the bindings in code.
>
>> 4. Is .NET 3rd party control (Winform based controls) support for
>> VCL.NET platform?
>Only by using the wizard. Also I have found some controls that don't
>work.
>
>--
>Marc Rohloff [TeamB]
>marc rohloff -at- myrealbox -dot- com
|
| Post Reply
|
| Re: 3rd Party .NET Control import in VCL.NET |
 |
1 Aug 2006 07:09:45 -0700 |
Rather than generalities, I will ask very specific's behind the question that I
have raised:
The advantage I thought I will get using Essential Grid/XtraGrid (.NET based
control imported in VCL.NET) is that I will move to .NET (C#) easily at later
stage from the intermediate VCL.NET build.
Question 1:
I don't see any control specific properties of 3rd party .NET controls such as
Xtragrid/EssentialGrid whereas I can able to see only properties that are
usually visible for all the controls in Delphi 2006 say standard/Win32 etc.
delphi controls.
Question 2:
The vendor confirmed that designer (XtraGrid Design-time-Xtragrid designer,
Level Designer and Band and Columns customization design-time) feature are not
implementable in VCL.NET as they have built it specifically for VS.NET platform.
I have asked the vendor to explain why it is not possible in runtime.
EssentialGrid also has design-time feature such as Gridboundcolumn editor to add
columns and configure each column properties individually with StyleInfo. But I
am not able to create the equivalent code of VS.NET (C#) for this functionality
in VCL.NET.
Question 3:
I get an error when I assign Datasource property of Essential grid with a
Datasource (TDatasource- with ADOConnection and ADODataset or ADODB) on Delphi
VCL.NET form(nfm file). The exception message is
"BadDataSourceForComplexBinding".
Whereas for VCL.NET based DBgrid control/data-aware controls the datasource is
working fine.
Question 4:
The controls that I would like to know whether works in VCL.NET are Xtragrid
control and Essential Grid control.
I am sure there are some light weight Winform .NET controls works in VCL.NET
using this wizard.
Basically, both XtraGrid & Essential Grid is targetted for .NET (C#.NET)
development and it is working fine.
Am I still going in right direction which is technically feasible or do you
think I have to use specific Grid for VCL.NET i.e. ExpressQuantumGrid and target
for C# based Grid (Essential Grid/XtraGrid) control at later stage of
development.
regards,
Jitender
"Jitender" <jitender.mahinderkar@ge.com> wrote:
>
>
>Is .NET based 3rd party controls like Xtragrid or Essential Grid tested in
VCL.NET platform?
>
>As I don't find any general issues with these controls in VS.NET (C#) for
which this control was targetted(Developed).
>
>regards,
>Jitender
>
>
>"Marc Rohloff [TeamB]" <"on request"> wrote:
>>On 29 Jul 2006 02:24:28 -0700, Jitender wrote:
>>
>>> 1. Is design-time feature of these controls supported in VCL.NET?
>>> As I don't see the properties in object inspector.
>>You should at least see some properties. Some will be unsupported if
>>they have types that the VCL framework does not understand.
>>
>>> 2. Is it possible to code all design-time properties functionality
>>> at run-time in VCL.NET code-behind .NFM pascal file?
>>In the Pascal file? Yes it should be.
>>
>>> 3. Is ".NET Databinding model" supported for these
controls in
>>> VCL.NET platform?
>>Only if you use .NET datasets and create the bindings in code.
>>
>>> 4. Is .NET 3rd party control (Winform based controls) support for
>>> VCL.NET platform?
>>Only by using the wizard. Also I have found some controls that don't
>>work.
>>
>>--
>>Marc Rohloff [TeamB]
>>marc rohloff -at- myrealbox -dot- com
>
|
| Post Reply
|
|
|
|
|
|
|
|
|
|