RE: [VB4Linux-Dev] hey I guess so.

[Abhijit P. <abh...@ma...>]

> > For the GUI, I think you should program directly in C on the
> Linux box. I am
> > really doubtful of how powerful vb2c is at present....would it
> be able to
> > interpret all those toolbars, and "File Open" dialog boxes and all that?
>
> Well, nobody said that the GUI had to be compiled until the VB2C
> part of the
> project was done anyway... Besides, a complicated test program
> would probably be a necessity when working on the VB2C...

I see your point..
but then you shall have to wait for a while before the vb2c is strong enough
for it.

again, the programs that have been compiled with vb2c might not be as
optimized/fast as their C counterparts

> > > > Pls check if Wine can emulate the OCX controls...and how do
> we integrate
> > > > them in the code that is to be converted to C...I am still not
> > > sure about
> > > > this stuff...
> > >
> > > Wine can emulate OCX controls... There's 2 possibilities for
> > > including Windows
> > > files:
> > >     1. Link a modified version of Wine in with the program
> and emulate the
> > > OCXes only (if possible)
> > >     2. Pre-emulate the OCX controls into C code and link a
> > > "ported" OCX into
> > > the program...
> >
> > Some team members could do some R&D on this topic. It would be of great
> > help.
>
> R&D??

Research & Development
finding, trying and testing