vb4linux-dev Mailing List for Visual Basic for Linux (Page 4)
Status: Planning
Brought to you by:
luke-jr
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(78) |
Dec
(11) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
|
Feb
|
Mar
(10) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2003 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2004 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
From: <mas...@so...> - 2000-11-17 13:50:28
|
Hi All! On Fri, Nov 17, 2000 at 07:05:55PM -0800, Abhijit Paithankar wrote: > I guess so. > how do we divide the work? [...] > > I think instead of giving 2 options, we could have just a VB2C interpreter. [...] Yacc/Lex? > > there are some tasks on the task-list that can be clubbed together like: > > CHM Reader/Viewer and CHM Compiler Don't know anything about CHM ... :( > Syntax colorer and GUI i.e. GUI and the editor > VB2C interpreter and Syntax checker > Today i've getting started with glade, with gtk+ basics... Yeah! I think it's too difficult to make some kind of GUI with this... > 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 > Mmmm... I'm thinking... Just making a shell, it isn't? A VBshell, that interpretes the vbcommand, directly. The compilations are made by vb2c, but the debug, for me, it so slowly with a reverse-interpreter C->VB ...my english... :(* > there are some doubts too: > > at design-time, we can emulate the Win32 API. should we make use of Wine > here? Wine, recreates all the win32 api? If yes, i think that we can use it... > that shall take care of OCX stuff. > > Also, we can appoint Task-Managers who will be responsible for a particular > (or a group of) task and then they can think about the way to implement > their own module. > > do we need a website admin? > > once we have these things clear, we can start off. > Yes... :)))) I've reinstalled my linuxbox, (crash of course... :)))) ) I'm ready.. :) -- Massimiliano Masi from www.mascanc.org The Old BBs... |
From: Abhijit P. <abh...@ma...> - 2000-11-17 13:36:17
|
I guess so. how do we divide the work? I think instead of giving 2 options, we could have just a VB2C interpreter. there are some tasks on the task-list that can be clubbed together like: CHM Reader/Viewer and CHM Compiler Syntax colorer and GUI i.e. GUI and the editor VB2C interpreter and Syntax checker 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 there are some doubts too: at design-time, we can emulate the Win32 API. should we make use of Wine here? that shall take care of OCX stuff. Also, we can appoint Task-Managers who will be responsible for a particular (or a group of) task and then they can think about the way to implement their own module. do we need a website admin? once we have these things clear, we can start off. ab -----Original Message----- From: vb4...@li... [mailto:vb4...@li...]On Behalf Of Luke-Jr Sent: Friday, November 17, 2000 4:52 AM To: vb4...@li... Subject: Re: [VB4Linux-Dev] hey Dunno... I guess we should start working on the project? Do we have all the plans ready? Abhijit Paithankar wrote: > whatever happened? > why is everyone so silent? > _______________________________________________ > VB4Linux-Dev mailing list > VB4...@li... > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev |
From: Luke-Jr <Mi...@an...> - 2000-11-17 12:52:27
|
Dunno... I guess we should start working on the project? Do we have all the plans ready? Abhijit Paithankar wrote: > whatever happened? > why is everyone so silent? > _______________________________________________ > VB4Linux-Dev mailing list > VB4...@li... > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev |
From: Abhijit P. <abh...@ma...> - 2000-11-17 12:43:45
|
whatever happened? why is everyone so silent? |
From: Luke-Jr <Mi...@an...> - 2000-11-14 13:25:01
|
Well, emulation of Windows seems to cause things to take longer to load... Maybe we can `emulate' everything during compile-time and have 100% Linux-compatible binaries be written which is the result of what emulation would make the code be? The binaries would probably have some wasted data that's not used, but with a little optimization we could probably fix that too... Abhijit Paithankar wrote: > Apart from the OCX problems, I still am confused about implementation of > DLLs and ODBC drivers. > > what we can do is, create a library that would emulate the VB environment > and translate the messages received from the VB applications and translate > them into messages that Linux API can understand. All programs would run > inside this emulated environment. > > As for the compiler, even that could run under the environment so that we > can directly use all the Win controls. > > _______________________________________________ > VB4Linux-Dev mailing list > VB4...@li... > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev |
From: Abhijit P. <abh...@ma...> - 2000-11-14 10:07:45
|
just to get things clear for everyone. this is what we plan to do. 1. We plan to provide an interface such that whatever OCX, ActiveX controls are available or will be available in the future, will just be 'imported' at design-time [we might need to emulate this-->Wine could be of help] and NOT re-written. This shall take care of keeping updating every time new control comes up. 2. A program that would use the same BASIC language as input or rather the same code used by ppl to develop VB apps on M$ platform, interpret the code to C and then just use gcc to compile. This would produce native Linux programs. |
From: Martino S. <ms...@ti...> - 2000-11-13 18:03:38
|
They look similar but aren't the same of vb4linux For Phoenix: "allows developers with Visual Basic experience to start developing for Linux without having to face a steep learning curve: " I think that this application cannot import VB files... KBasic is for the KDE environment and have the same problem of Phoenix. ----- Original Message ----- From: "Abhijit Paithankar" <abh...@ma...> To: "VB4Linux" <vb4...@li...> Sent: Tuesday, November 14, 2000 6:29 AM Subject: [VB4Linux-Dev] check > check these websites. > > These guys have already done exactly what we are planning to do.... > which makes me think...are we re-inventing the wheel? > > http://www.janus-software.com/ > http://www.kbasic.de/ > _______________________________________________ > VB4Linux-Dev mailing list > VB4...@li... > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev |
From: Abhijit P. <abh...@ma...> - 2000-11-13 15:59:14
|
check these websites. These guys have already done exactly what we are planning to do.... which makes me think...are we re-inventing the wheel? http://www.janus-software.com/ http://www.kbasic.de/ |
From: Abhijit P. <abh...@ma...> - 2000-11-12 09:13:51
|
Apart from the OCX problems, I still am confused about implementation of DLLs and ODBC drivers. what we can do is, create a library that would emulate the VB environment and translate the messages received from the VB applications and translate them into messages that Linux API can understand. All programs would run inside this emulated environment. As for the compiler, even that could run under the environment so that we can directly use all the Win controls. |
From: <abh...@ma...> - 2000-11-11 19:25:41
|
I guess I agree with Luke-Jr. compatiblity with current Win 'native' controls and objects would be a major advantage we do not have to worry about newer controls coming up every now and then.. -- Original Message As Follows -- Subject: Re: [VB4Linux-Dev] GUI Development From: Luke-Jr <Mi...@an...> To: vb4...@li... Date: Sat, 11 Nov 2000 09:44:24 -0500 Maybe we could do that also, but I was thinking on the lines of having the Windows OCXes supported by VB4Linux even if emulation is needed... There's alot of Windows OCXes out there, after all... Martino Serri wrote: > I don't think is a good idea to call the OCX at run-time, we need to do this > a reimplementation of OLE and friends. > > We can also do a basic library for the common OCX used on the VB Project and > link it to the project. > > ----- Original Message ----- > From: "Luke-Jr" <Mi...@an...> > To: <vb4...@li...> > Sent: Thursday, November 09, 2000 9:49 PM > Subject: Re: [VB4Linux-Dev] GUI Development > > > Hmm... OCXes /IS/ a problem I didn't think of... Maybe we can use a module > for > > OCX support that has a bit of code from Wine or something... As far as > > compiling OCXes is concerned, I think we'll have to make it write it in > Windows > > format for compatibility... I'm pretty sure Wine must have documentation > of the > > Windows executable format... > > > > Martino Serri wrote: > > > > _______________________________________________ > VB4Linux-Dev mailing list > VB4...@li... > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev Attachment-Disposition: attachment; filename="Mike.vcf" Content-Type: text/x-vcard; charset=us-ascii; name="Mike.vcf" --------------------------------------------------------------- This Message was Powered by Xcel Communications Sign up for your FREE EMAIL account today at http://www.mailroom.com Give your FAX machine an email address http://www.faxroom.com |
From: Luke-Jr <Mi...@an...> - 2000-11-11 14:44:45
|
Maybe we could do that also, but I was thinking on the lines of having the Windows OCXes supported by VB4Linux even if emulation is needed... There's alot of Windows OCXes out there, after all... Martino Serri wrote: > I don't think is a good idea to call the OCX at run-time, we need to do this > a reimplementation of OLE and friends. > > We can also do a basic library for the common OCX used on the VB Project and > link it to the project. > > ----- Original Message ----- > From: "Luke-Jr" <Mi...@an...> > To: <vb4...@li...> > Sent: Thursday, November 09, 2000 9:49 PM > Subject: Re: [VB4Linux-Dev] GUI Development > > > Hmm... OCXes /IS/ a problem I didn't think of... Maybe we can use a module > for > > OCX support that has a bit of code from Wine or something... As far as > > compiling OCXes is concerned, I think we'll have to make it write it in > Windows > > format for compatibility... I'm pretty sure Wine must have documentation > of the > > Windows executable format... > > > > Martino Serri wrote: > > > > _______________________________________________ > VB4Linux-Dev mailing list > VB4...@li... > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev |
From: Martino S. <ms...@ti...> - 2000-11-11 12:51:06
|
I don't think is a good idea to call the OCX at run-time, we need to do this a reimplementation of OLE and friends. We can also do a basic library for the common OCX used on the VB Project and link it to the project. ----- Original Message ----- From: "Luke-Jr" <Mi...@an...> To: <vb4...@li...> Sent: Thursday, November 09, 2000 9:49 PM Subject: Re: [VB4Linux-Dev] GUI Development > Hmm... OCXes /IS/ a problem I didn't think of... Maybe we can use a module for > OCX support that has a bit of code from Wine or something... As far as > compiling OCXes is concerned, I think we'll have to make it write it in Windows > format for compatibility... I'm pretty sure Wine must have documentation of the > Windows executable format... > > Martino Serri wrote: > |
From: Luke-Jr <Mi...@an...> - 2000-11-10 21:05:35
|
CHM are Micro$oft HTML Help files... Massimiliano Masi wrote: > Hi! > > > for the VB *.chm files, if you guys could wait till monday, I could have > > those files up by then. > > Mike, I think I would need the admin rights to do the needful...(or do I?) > > Exactly, what are the *.chm files? > > > > > I found out some more info about the GUI Development: > > > > If you want something that will work on all X-servers, you are better > > off using just Xlib and XT and not using any widget set at all. This > > will ensure that your applicatoin will work on any X-server. However, > > this involoves a lot of programming even for small things like buttons, > > menus, and diaglog boxes, etc. that we generally take for granted when > > we use a widget set. > > > > Yes. The Xlib giveus some simple directive to build widgets. > > Using it, its too long, and too difficult to make widgets more fine than GTK > or QT. > > > If you would like to be able to use your application under all > > distributions under linux, then you should program using GTK, there is a > > tutorial at gtk.org and a book in the market. > > An Oreilly book... GNOME/GTK. > > I've read the tutorial, is not so difficult to learn. > > > Glade is very useful once you understand the code that is required to be > > written in GTK, since you need to add to the code automatically > > generated by Glade. Once you understand basic GTK concepts, Glade makes > > UI development very easy. > > The basic concept of the GTK widgets is simple. All is based on the > gtk_container(); > > Is our application fulluycompatible with vb6or later? > For me I must learn all the file specificatiions (frx, vbp, frm, basmodules) > :)))) > > The MSOffice implementation? We treat it as OCX? > > We can integrate with some LinuxOffice as well SUNSoffice, koffice, ecc... > > Thinking thatGTK Pure is for us. > > And all the gtk portings. > > _______________________________________________ > VB4Linux-Dev mailing list > VB4...@li... > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev |
From: Massimiliano M. <mas...@so...> - 2000-11-10 19:08:36
|
Hi! > for the VB *.chm files, if you guys could wait till monday, I could have > those files up by then. > Mike, I think I would need the admin rights to do the needful...(or do I?) Exactly, what are the *.chm files? > > I found out some more info about the GUI Development: > > If you want something that will work on all X-servers, you are better > off using just Xlib and XT and not using any widget set at all. This > will ensure that your applicatoin will work on any X-server. However, > this involoves a lot of programming even for small things like buttons, > menus, and diaglog boxes, etc. that we generally take for granted when > we use a widget set. > Yes. The Xlib giveus some simple directive to build widgets. Using it, its too long, and too difficult to make widgets more fine than GTK or QT. > If you would like to be able to use your application under all > distributions under linux, then you should program using GTK, there is a > tutorial at gtk.org and a book in the market. An Oreilly book... GNOME/GTK. I've read the tutorial, is not so difficult to learn. > Glade is very useful once you understand the code that is required to be > written in GTK, since you need to add to the code automatically > generated by Glade. Once you understand basic GTK concepts, Glade makes > UI development very easy. The basic concept of the GTK widgets is simple. All is based on the gtk_container(); Is our application fulluycompatible with vb6or later? For me I must learn all the file specificatiions (frx, vbp, frm, basmodules) :)))) The MSOffice implementation? We treat it as OCX? We can integrate with some LinuxOffice as well SUNSoffice, koffice, ecc... Thinking thatGTK Pure is for us. And all the gtk portings. |
From: Luke-Jr <Mi...@an...> - 2000-11-10 18:46:07
|
I was under the impression that any project members could upload to the project groups' directory and modify files set g+w (which the website IS, BTW)... Maybe we could make a builtin implementation of GTK for VB4Linux? Abhijit Paithankar wrote: > > Well, this may be the first version of VB4Linux that we make! Microsoft > > just accepted me as a Visual Studio.NET beta tester! When I get the > > stuff I'll prolly make the help files accessable to the group... > > hey thats great news! > > for the VB *.chm files, if you guys could wait till monday, I could have > those files up by then. > Mike, I think I would need the admin rights to do the needful...(or do I?) > > I found out some more info about the GUI Development: > > If you want something that will work on all X-servers, you are better > off using just Xlib and XT and not using any widget set at all. This > will ensure that your applicatoin will work on any X-server. However, > this involoves a lot of programming even for small things like buttons, > menus, and diaglog boxes, etc. that we generally take for granted when > we use a widget set. > > If you would like to be able to use your application under all > distributions under linux, then you should program using GTK, there is a > tutorial at gtk.org and a book in the market. > Glade is very useful once you understand the code that is required to be > written in GTK, since you need to add to the code automatically > generated by Glade. Once you understand basic GTK concepts, Glade makes > UI development very easy. > > _______________________________________________ > VB4Linux-Dev mailing list > VB4...@li... > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev |
From: Abhijit P. <abh...@ma...> - 2000-11-10 15:47:53
|
> Well, this may be the first version of VB4Linux that we make! Microsoft > just accepted me as a Visual Studio.NET beta tester! When I get the > stuff I'll prolly make the help files accessable to the group... hey thats great news! for the VB *.chm files, if you guys could wait till monday, I could have those files up by then. Mike, I think I would need the admin rights to do the needful...(or do I?) I found out some more info about the GUI Development: If you want something that will work on all X-servers, you are better off using just Xlib and XT and not using any widget set at all. This will ensure that your applicatoin will work on any X-server. However, this involoves a lot of programming even for small things like buttons, menus, and diaglog boxes, etc. that we generally take for granted when we use a widget set. If you would like to be able to use your application under all distributions under linux, then you should program using GTK, there is a tutorial at gtk.org and a book in the market. Glade is very useful once you understand the code that is required to be written in GTK, since you need to add to the code automatically generated by Glade. Once you understand basic GTK concepts, Glade makes UI development very easy. |
From: Massimiliano M. <mas...@so...> - 2000-11-10 11:00:26
|
> Well, this may be the first version of VB4Linux that we make! Microsoft > just accepted me as a Visual Studio.NET beta tester! When I get the > stuff I'll prolly make the help files accessable to the group... > :)))))))))))))) |
From: Abhijit P. <abh...@ma...> - 2000-11-10 03:59:13
|
DAO : Data Access Objects RDO: Remote Data Objects ADO: ActiveX Data Objects for database connectivity. Again, these objects work with ODBC drivers so we need a set of ODBC Drivers too what about COM DCOM support ? Also, the present version; VB6 is NOT Object Oriented. VB7 is expected to be Object Oriented. Do we make VB4Linux Object Oriented? ================================================================== Luke-Jr wrote: > Not sure what DAO or ADO are, but most of those are things I've thought of > already and are on the project's Task list... > > Abhijit Paithankar wrote: > > > > > > > We can do a command line tool called from the VBIDE that reinterprets the > > > BASIC syntax to C, like gjc or similiar. > > > > > > But another problem is in my mind: the OCX support. How we can implement the > > > OCX linkage? > > > I was thinking to an open library like the VCL for Delphi. > > > > > > _______________________________________________ > > > VB4Linux-Dev mailing list > > > VB4...@li... > > > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev > > > > ok, I think we shall go ahead with the "VB2C" model > > > > we need to think about a lot of things > > > > 1. DAO and ADO Support > > 2. OCX Support > > 3. CHM and HLP file creator and reader > > 4. VB Code Editor > > 5. VB2C interpreter [has "something2C" been implemented before in the open > > development community?] > > 6. GUI Development > > 7. Runtime Environment > > 8. Work Distribution > > 9. Project Documentation |
From: Luke-Jr <Mi...@an...> - 2000-11-10 03:48:48
|
Well, this may be the first version of VB4Linux that we make! Microsoft just accepted me as a Visual Studio.NET beta tester! When I get the stuff I'll prolly make the help files accessable to the group... |
From: Luke-Jr <Mi...@an...> - 2000-11-09 22:50:20
|
Wrong. It doesn't SEEM to be very big... It IS very big... ;-P Massimiliano Masi wrote: > > > Since GNOME and KDE can co-exist, GNOME-version and KDE-version would > not > > > be necessary. We would use the basic Gtk+ library. For that matter, > Glade > > > would be fine but, then you have to decide if it provides sufficient > > > degree of control. > > Yes. At this stage, I think that glade does not provide too much control for > the widget. (0.5?) > > > > > > > Also, it would be great if we could separate the back end engine from > the > > > front end GUI again for modularity. > > > we could actually develop the front end and the back end separately. > > > We can then integrate them together. > > > > We can do a command line tool called from the VBIDE that reinterprets the > > BASIC syntax to C, like gjc or similiar. > > GNUBasic (don't know the real name of the package) reinterprets BASIC->C? > we can use it? > > > > > But another problem is in my mind: the OCX support. How we can implement > the > > OCX linkage? > > I was thinking to an open library like the VCL for Delphi. > > (accidenti al mio inglese) > > Think that we must decide some of important question about the win32 > programming ... > > OCX Linking, ADODB, other conterparties vb software, for example. > > This project seems to be very big!!!!!!!!!!!!!!!!!!! > > ;-)))))))))))) > > -- > English for the impatient: Lesson 1: How old are you? Ehm... argh... > > _______________________________________________ > VB4Linux-Dev mailing list > VB4...@li... > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev |
From: Luke-Jr <Mi...@an...> - 2000-11-09 20:50:30
|
Not sure what DAO or ADO are, but most of those are things I've thought of already and are on the project's Task list... Abhijit Paithankar wrote: > > > > We can do a command line tool called from the VBIDE that reinterprets the > > BASIC syntax to C, like gjc or similiar. > > > > But another problem is in my mind: the OCX support. How we can implement the > > OCX linkage? > > I was thinking to an open library like the VCL for Delphi. > > > > _______________________________________________ > > VB4Linux-Dev mailing list > > VB4...@li... > > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev > > ok, I think we shall go ahead with the "VB2C" model > > we need to think about a lot of things > > 1. DAO and ADO Support > 2. OCX Support > 3. CHM and HLP file creator and reader > 4. VB Code Editor > 5. VB2C interpreter [has "something2C" been implemented before in the open > development community?] > 6. GUI Development > 7. Runtime Environment > 8. Work Distribution > 9. Project Documentation |
From: Luke-Jr <Mi...@an...> - 2000-11-09 20:49:24
|
Hmm... OCXes /IS/ a problem I didn't think of... Maybe we can use a module for OCX support that has a bit of code from Wine or something... As far as compiling OCXes is concerned, I think we'll have to make it write it in Windows format for compatibility... I'm pretty sure Wine must have documentation of the Windows executable format... Martino Serri wrote: > ----- Original Message ----- > From: "Abhijit Paithankar" <abh...@ma...> > To: <vb4...@li...> > Sent: Thursday, November 09, 2000 2:07 PM > Subject: Re: [VB4Linux-Dev] GUI Development > > > ok my SF Unix name is: ab_p > > > > hey man...before we start off, we need the requirement specifications > > document for the project it is important. > > Also, we need to clearly define the architecture and figure out the > > modules so that they can be worked upon individually by different > > programmers. > > Since GNOME and KDE can co-exist, GNOME-version and KDE-version would not > > be necessary. We would use the basic Gtk+ library. For that matter, Glade > > would be fine but, then you have to decide if it provides sufficient > > degree of control. > > > > Also, it would be great if we could separate the back end engine from the > > front end GUI again for modularity. > > we could actually develop the front end and the back end separately. > > We can then integrate them together. > > We can do a command line tool called from the VBIDE that reinterprets the > BASIC syntax to C, like gjc or similiar. > > But another problem is in my mind: the OCX support. How we can implement the > OCX linkage? > I was thinking to an open library like the VCL for Delphi. > > _______________________________________________ > VB4Linux-Dev mailing list > VB4...@li... > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev |
From: Massimiliano M. <mas...@so...> - 2000-11-09 17:59:35
|
> > Since GNOME and KDE can co-exist, GNOME-version and KDE-version would not > > be necessary. We would use the basic Gtk+ library. For that matter, Glade > > would be fine but, then you have to decide if it provides sufficient > > degree of control. Yes. At this stage, I think that glade does not provide too much control for the widget. (0.5?) > > > > Also, it would be great if we could separate the back end engine from the > > front end GUI again for modularity. > > we could actually develop the front end and the back end separately. > > We can then integrate them together. > > We can do a command line tool called from the VBIDE that reinterprets the > BASIC syntax to C, like gjc or similiar. GNUBasic (don't know the real name of the package) reinterprets BASIC->C? we can use it? > > But another problem is in my mind: the OCX support. How we can implement the > OCX linkage? > I was thinking to an open library like the VCL for Delphi. (accidenti al mio inglese) Think that we must decide some of important question about the win32 programming ... OCX Linking, ADODB, other conterparties vb software, for example. This project seems to be very big!!!!!!!!!!!!!!!!!!! ;-)))))))))))) -- English for the impatient: Lesson 1: How old are you? Ehm... argh... |
From: Massimiliano M. <mas...@so...> - 2000-11-09 17:50:53
|
----- Original Message ----- From: "Luke-Jr" <Mi...@an...> To: <vb4...@li...> Sent: Wednesday, November 08, 2000 7:01 PM Subject: [VB4Linux-Dev] GUI Development > Before I begin working on the main window for the GUI (seems to be the > obvious place to start...), I'd like opinions of how the windows should > be designed... The GUI must be 100% X11 compatible so that anyone can > use it... For now at least so we don't have to make a "GNOME-version" > and "KDE-version" etc (unless someone knows how to have it do GNOME is > running in GNOME and KDE if in KDE etc...)... Anyway, I was thinking > about using Glade without the GNOME functions for the GUI... Of course, > that's all I know about as far as GUI development anyway (besides doing > raw C)... Any other ideas? > No... ;-) Simply, we can use XLib directly, ;PPPP There was an old example, a GUI from an italian boy, the name was vdk or vdkbuilder ... don't know where...(the uri of the project) Of course, we can use GTK (gtk pure). I've only seen glade, not too much... I think that glade works well...!!!! The first thing that I must do is learn TOO MUCH ENGLISH ... :(((((((((((((((((( Bye Massimiliano |
From: Abhijit P. <abh...@ma...> - 2000-11-09 16:50:02
|
> > We can do a command line tool called from the VBIDE that reinterprets the > BASIC syntax to C, like gjc or similiar. > > But another problem is in my mind: the OCX support. How we can implement the > OCX linkage? > I was thinking to an open library like the VCL for Delphi. > > _______________________________________________ > VB4Linux-Dev mailing list > VB4...@li... > http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev ok, I think we shall go ahead with the "VB2C" model we need to think about a lot of things 1. DAO and ADO Support 2. OCX Support 3. CHM and HLP file creator and reader 4. VB Code Editor 5. VB2C interpreter [has "something2C" been implemented before in the open development community?] 6. GUI Development 7. Runtime Environment 8. Work Distribution 9. Project Documentation |