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

[Luke-Jr <Mi...@an...>]

As this project is meant to be a near-exact port of Visual Basic (besides the
binary result and OS), the debugger should be VB.....

Scott Beasley wrote:

> On Sun, 19 Nov 2000, Luke-Jr wrote:
>
> > Abhijit Paithankar wrote:
> >
> > > pls see message below:
> > >
> > > > Erm... Fix your clock please? It's not the 20th and if you're in
> > > > a different
> > > > timezone, shouldn't it put the -0500 or something in the Date
> > > > header...
> > >
> > > Done sir! :)
> > >
> > > > > > >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....
> > > >
> > > > Yup...
> > > >
> > > > > 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.
> > > >
> > > > Hmm... In that case, I could start on the GUI today... I'm MUCH better at
> > > > VB than C...
> > > > (I'll just have to remember not to use the WinAPI as I doubt VB2C
> > > > will make up
> > > > for that for a while...)
> > >
> > > yes...the earlier the better.
> > > also, we could use the latest version of GTK+...just make sure all of use
> > > the same versions of any libraries/software we use.
> > >
> > > 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 think it best to keep this part of the code as hi-level as
> possible.  And again it does not matter if it is not compiled or
> compilable for awhile, without a good solid core (vb2c) it's useless
> anyway.  The debugger is upfor debate on if it should be in C or
> VB.  Though in the Tcl/Tk and Python world their debuggers are mixed.
>
> scott
>
> _______________________________________________
> VB4Linux-Dev mailing list
> VB4...@li...
> http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev