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

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

> -----Original Message-----
> From: vb4...@li...
> [mailto:vb4...@li...]On Behalf Of Scott
> Beasley
> Sent: Sunday, November 19, 2000 7:28 AM
> To: vb4...@li...
> Subject: RE: [VB4Linux-Dev] hey I guess so.
>
>
> >how do we divide the work?
> >FROM: Abhijit PaithankarDATE: 11/17/2000
>
> >I think instead of giving 2 options, we could have just a VB2C
> >interpreter.
> Anyone looked at this: http://www.naken.cc/vb2c/

It looks OK, but we shall have to request him for the source code...atleast
the basic stuff is already present....

> >CHM Reader/Viewer and CHM Compiler
> >Syntax colorer and GUI i.e. GUI and the editor
> >VB2C interpreter and Syntax checker
> What about holding off until a base vb2c is done, then code most of the
> tools in the language itself, or do them in VB now and use them as a test
> for the translator?

Since a lot of work is to be done on the GUI/Editor, like being able to
create a project and work within the project, the toolbars are to be
emulated, and a lot of other stuff needs to be figured out, the GUI/Editor
can be developed independently and then the projectfile shall be passed on
to the VB2C compiler....actually, you could download the vb2c interpreter at
the URL above, and start off on that.

> >other tasks like runtime debugger need to be thought of coz` of
> >interpreting, the debugger shall need to reverse-interpret the C code to
> >VB
> Same as above.

ya....this needs some ground work to be done before starting off

> >at design-time, we can emulate the Win32 API. should we make use of Wine
> >where?
> >that shall take care of OCX stuff.
> I would use the Wine libs.... saves time and money ;-)

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...

ab