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

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

  -----Original Message-----
  From: vb4...@li...
[mailto:vb4...@li...]On Behalf Of Luke-Jr
  Sent: Monday, November 20, 2000 12:13 AM
  To: vb4...@li...
  Subject: Re: [VB4Linux-Dev] hey I guess so.


  Scott Beasley wrote:
    >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/

  Hmm... Maybe we could ask the author if we could use it and upgrade it to
VB.NET...
     show him the bait??  :))))
    >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?

  Well, that's what I was originally thinking for the CHM stuff, but I guess
we /COULD/ do everything in VB4Linux... Maybe even rewrite the VB2C once
everything's done so we can say we programmed it in itself. ;-P
       we shall keep upgrading VB2C all the time....so as to make sure soon,
our vb2c would be different from the authors....
    >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.

    >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 ;-)

    scott
    _______________________________________________
    VB4Linux-Dev mailing list
    VB4...@li...
    http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev