vb4linux-dev

[VB4Linux-Dev] VB4Linux

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

hey mike!
have you made any documentation about how the whole system is going to work
?

things like how OCXs are managed, or how the debugging environment works and
stuff like that...??

pls let me know

Regards,
ab_p

[VB4Linux-Dev] VB4Linux

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

Hi,
I am writing after a long time.

I would like to discuss some issues regarding the VB2C compiler.

First of all, I have been able to have the compiler working at a level that has been achieved by the Naken-VB2C and it does it better, and more features are present.

The problem I am facing now, is, how do I extract the toolbars and the images from the form?

Also, how do we address the problems of various system dependent features of VB?

Is this project really feasible?

Regards,
Abhijit Paithankar

Re: [VB4Linux-Dev] VB4Linux

[Jimmy O'R. <ji...@ir...>]

On Fri, 8 Jun 2001, Abhijit Paithankar wrote:

> Hi,
> I am writing after a long time.
> 
> I would like to discuss some issues regarding the VB2C compiler.
> 
> First of all, I have been able to have the compiler working at a level that has been achieved by the Naken-VB2C and it does it better, and more features are present.
> 
> The problem I am facing now, is, how do I extract the toolbars and the images from the form?

Gnome Basic has support for this stuff. The frx file contains the various
files with a 2 character boundary which seems to be a type descriptor.
> 
> Also, how do we address the problems of various system dependent features of VB?

Use Wine?
> 
> Is this project really feasible?

Yeah. If the backend can be made modular enough, it could be used to
compile normal VB to MSIL, and hence to .Net, which will get a lot of
support from VB programmers who don't want to go checking everything
they've written.
> 
> Regards,
> Abhijit Paithankar
Jimmy O'Regan

[VB4Linux-Dev] Re: VB4Linux

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

Hmm... The images will probably be a problem... I haven't looked at the 
FRX files yet, but there is a slight chance they might simply be a 
resource file...
What system dependent features are you referring to?

Abhijit Paithankar wrote:

>Hi,
>I am writing after a long time.
>
>I would like to discuss some issues regarding the VB2C compiler.
>
>First of all, I have been able to have the compiler working at a level that has been achieved by the Naken-VB2C and it does it better, and more features are present.
>
>The problem I am facing now, is, how do I extract the toolbars and the images from the form?
>
>Also, how do we address the problems of various system dependent features of VB?
>
>Is this project really feasible?
>
>Regards,
>Abhijit Paithankar
>

[VB4Linux-Dev] VB4Linux

[<cls...@ya...>]

Hi everybody, is the project still running? i have
look at the project page, but no releases, no sources
on the CVS, no Home Page, just some discusion on the
Mailing List.

_________________________________________________________
Do You Yahoo!?
La mejor conexión a internet y 25MB extra a tu correo por $100 al mes. http://net.yahoo.com.mx

Re: [VB4Linux-Dev] VB4Linux

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

Well, I think the best way to implement OCX stuff would probably be to
have a seperate OCX2SO converter...
The debugging environment will not use the compiler at all probably...


Abhijit Paithankar wrote:
> 
> hey mike!
> have you made any documentation about how the whole system is going to work
> ?
> 
> things like how OCXs are managed, or how the debugging environment works and
> stuff like that...??
> 
> pls let me know
> 
> Regards,
> ab_p
> 
> _______________________________________________
> VB4Linux-Dev mailing list
> VB4...@li...
> http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev

RE: [VB4Linux-Dev] VB4Linux

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

an OCX2SO converter is possible when you have the OCX source code....but we
want to convert the OCX components that are already compiled....in this
case, the OCX2SO is not possible.
we either have to re-write the OCX files, or emulate them...the first one is
very tedious, but emulation is difficult to implement...then one might say
why not emulate the whole VB environment??

we need solid foundation architecture for this project.

Regards,
ab_p

> -----Original Message-----
> From: vb4...@li...
> [mailto:vb4...@li...]On Behalf Of Luke-Jr
> Sent: Saturday, December 23, 2000 8:31 AM
> To: vb4...@li...
> Subject: Re: [VB4Linux-Dev] VB4Linux
>
>
> Well, I think the best way to implement OCX stuff would probably be to
> have a seperate OCX2SO converter...
> The debugging environment will not use the compiler at all probably...
>
>
> Abhijit Paithankar wrote:
> >
> > hey mike!
> > have you made any documentation about how the whole system is
> going to work
> > ?
> >
> > things like how OCXs are managed, or how the debugging
> environment works and
> > stuff like that...??
> >
> > pls let me know
> >
> > Regards,
> > ab_p
> >
> > _______________________________________________
> > VB4Linux-Dev mailing list
> > VB4...@li...
> > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev
>
> _______________________________________________
> VB4Linux-Dev mailing list
> VB4...@li...
> http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev

Re: [VB4Linux-Dev] VB4Linux

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

Well, I was thinking more of OCX2SO making a pre-emulated SO file... A
bit more complex, but probably the best idea....

Abhijit Paithankar wrote:
> 
> an OCX2SO converter is possible when you have the OCX source code....but we
> want to convert the OCX components that are already compiled....in this
> case, the OCX2SO is not possible.
> we either have to re-write the OCX files, or emulate them...the first one is
> very tedious, but emulation is difficult to implement...then one might say
> why not emulate the whole VB environment??
> 
> we need solid foundation architecture for this project.
> 
> Regards,
> ab_p
> 
> > -----Original Message-----
> > From: vb4...@li...
> > [mailto:vb4...@li...]On Behalf Of Luke-Jr
> > Sent: Saturday, December 23, 2000 8:31 AM
> > To: vb4...@li...
> > Subject: Re: [VB4Linux-Dev] VB4Linux
> >
> >
> > Well, I think the best way to implement OCX stuff would probably be to
> > have a seperate OCX2SO converter...
> > The debugging environment will not use the compiler at all probably...
> >
> >
> > Abhijit Paithankar wrote:
> > >
> > > hey mike!
> > > have you made any documentation about how the whole system is
> > going to work
> > > ?
> > >
> > > things like how OCXs are managed, or how the debugging
> > environment works and
> > > stuff like that...??
> > >
> > > pls let me know
> > >
> > > Regards,
> > > ab_p
> > >
> > > _______________________________________________
> > > VB4Linux-Dev mailing list
> > > VB4...@li...
> > > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev
> >
> > _______________________________________________
> > VB4Linux-Dev mailing list
> > VB4...@li...
> > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev
> 
> _______________________________________________
> VB4Linux-Dev mailing list
> VB4...@li...
> http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev