I'd like to be part of this AWESOME project. Not sure if I'm supposed to be sending this message here on the forum, or to a person in particular but here it is none the less.
I'm already a member of the Class Builder Discussion List under the alias MystifyingShadows.
About me, Well to make a long story short, I've been learning to program since I was 8 years old, I'm now 33 (you do the math :-). I've also ported 2 applications from Windows to Unix/Linux. and since your current issue is the porting of ClassBuilder to Unix, thought it might be a good idea to see where you're at in this.
Hoping to hear from you soon
Stephane Richard
Software Developer
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You got my vote also, If you are on the list, you know the issues: Wine/MFC or wxWindows, documentation generation with roundtrip capabilities etc. It seems you have experience with porting apps to linux, perhaps you have ideas about which route to take.
Jimmy Venema
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well I think we need to stick to RTF for the documentation generation. before I make suggestion there would be two things to do, which I'll start when I get home from work.
1. open windows classbuilder generated RTF in my unix box. (current windows RTF specification is 1.6) and I'd like to see if Linux supports the same 1.6 revision of the RTF standard as well.
2. the way you insert your graphics in the code, this code you said you just input in the document and everything seems to fit in. I'd like to know if that's an RTF feature, or an MFC rtf library feature. If that' in the specifications and isn't really MFC dependant or not totally, maybe the port of that part would be easier than expected.
As far as GUI is concerned, it depends on the background of the developers, by that I mean if we all know C/C++ wxWindows is probably the quickest way to go because it is a somwhat hybrid version of MFC it's all class wrappers and object oriented libraries (also known as a Thick binding to Windows Services as well as Linux and Mac). This means that you can actually develop a standard (when you port your windows) that others can use with minimal conversions in Linux and the Mac. I dont know about the others maybe they are the same, GTK is bad n this manner as it seems to have devided in 4 standards. Console, Windows, UNIX and Mac as they seemed to have "technically" tried to reproduce the libraries as per OS specifications. If we get a Mac programmer he'd probably be pretty fast where a Windows programmer would be slower to convert to Mac. So I would recommend wxwindows strongly.
I'd need to learn more about the other GUI libraries mentionned on the list to recommend them or not.
Stephane Richard
Software Developer
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Rtf thing is not MFC specific, but something of the windows API. You can draw into an metafile
device context and get at the end a bag of bytes
representing the metafile. Although MFC is used, the same functionality can be used without MFC.
The bytes are converted to hex nibbles in ASCII and thats it. Search for ::WriteRtf or more speficicly ::WriteRtfDiagram to get to the Rtf generation code.
As for GUI libraries I think theer are two candidates one is wxWindows as already mentioned the other big force is Qt the trolls from norway with the KDE environment. With Qt 3.0 there seems also good IDE development support for their environment.
Jimmy Venema
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Qt is strong, no doubt, and indeed it has been out there for a good while. however true that they have an excellent development in the name of KDEvelop, it's main flaw is that it's not open source for windows (at least not as of now, maybe in a few years :-). if it wasn't for that I would have chosed it but since this is an open source project I simply thought that maybe everything we use should indeed be open source as well. if KDE developers want your tool, they can always get wxWindows :-). The other way around might pose a flaw on this project's part instead of on the KDE developers part. Qt is strong, no doubt. But I'm a bit doubtful about paying for a commercial library or product to develop an open source project. :-).
Stephane Richard
Software Developer
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i' m frank "gulliver" landgraf. My Background is 3 year mfc-programming(database apps and cad) and about 3 years java (web front end for document management, swing-gui & network programming, actually working on eos).
wxWindows is a big monster, but probably it would be the best choice at this time.
Regards
Frank
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-03-14
HI,
my name is Martin Ltke.I use Classbuilder and monitor its development for about 2 years or so...
It was exciting news when i received word its open source now. A wish came true.
Id like to join in.
I do C++ for about 7 years now mainly in the gaming sector. Im working for Silverstyle Entertainment a gamestudio located in Berlin, Germany as a Junior Programmer.
I could see that the most important tasks like parsing source code into existing CBDs are already in pursue. But i think some convenience tasks in the GUI can still be done.
Regards Martin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-05-21
Me too! I started at age 9, and now I'm 33. My backgound is UNIX systems and application programming, C++/RDBMS. Some X11 and some Qt (for fun, just to learn it). On Windows I mostly use Delphi (Borland VCL) and VC++ MFC/ATL/WTL.
I'm really excited to see that Class Builder is now Open Source! I'm happy to help wherever I can. For starters, I should aquaint myself with the source code first!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello everyone,
I'd like to be part of this AWESOME project. Not sure if I'm supposed to be sending this message here on the forum, or to a person in particular but here it is none the less.
I'm already a member of the Class Builder Discussion List under the alias MystifyingShadows.
About me, Well to make a long story short, I've been learning to program since I was 8 years old, I'm now 33 (you do the math :-). I've also ported 2 applications from Windows to Unix/Linux. and since your current issue is the porting of ClassBuilder to Unix, thought it might be a good idea to see where you're at in this.
Hoping to hear from you soon
Stephane Richard
Software Developer
You got my vote!
I passed it onto Jimmy.
Craig Gunhouse (gunner)
You got my vote also, If you are on the list, you know the issues: Wine/MFC or wxWindows, documentation generation with roundtrip capabilities etc. It seems you have experience with porting apps to linux, perhaps you have ideas about which route to take.
Jimmy Venema
Well I think we need to stick to RTF for the documentation generation. before I make suggestion there would be two things to do, which I'll start when I get home from work.
1. open windows classbuilder generated RTF in my unix box. (current windows RTF specification is 1.6) and I'd like to see if Linux supports the same 1.6 revision of the RTF standard as well.
2. the way you insert your graphics in the code, this code you said you just input in the document and everything seems to fit in. I'd like to know if that's an RTF feature, or an MFC rtf library feature. If that' in the specifications and isn't really MFC dependant or not totally, maybe the port of that part would be easier than expected.
As far as GUI is concerned, it depends on the background of the developers, by that I mean if we all know C/C++ wxWindows is probably the quickest way to go because it is a somwhat hybrid version of MFC it's all class wrappers and object oriented libraries (also known as a Thick binding to Windows Services as well as Linux and Mac). This means that you can actually develop a standard (when you port your windows) that others can use with minimal conversions in Linux and the Mac. I dont know about the others maybe they are the same, GTK is bad n this manner as it seems to have devided in 4 standards. Console, Windows, UNIX and Mac as they seemed to have "technically" tried to reproduce the libraries as per OS specifications. If we get a Mac programmer he'd probably be pretty fast where a Windows programmer would be slower to convert to Mac. So I would recommend wxwindows strongly.
I'd need to learn more about the other GUI libraries mentionned on the list to recommend them or not.
Stephane Richard
Software Developer
The Rtf thing is not MFC specific, but something of the windows API. You can draw into an metafile
device context and get at the end a bag of bytes
representing the metafile. Although MFC is used, the same functionality can be used without MFC.
The bytes are converted to hex nibbles in ASCII and thats it. Search for ::WriteRtf or more speficicly ::WriteRtfDiagram to get to the Rtf generation code.
As for GUI libraries I think theer are two candidates one is wxWindows as already mentioned the other big force is Qt the trolls from norway with the KDE environment. With Qt 3.0 there seems also good IDE development support for their environment.
Jimmy Venema
Qt is strong, no doubt, and indeed it has been out there for a good while. however true that they have an excellent development in the name of KDEvelop, it's main flaw is that it's not open source for windows (at least not as of now, maybe in a few years :-). if it wasn't for that I would have chosed it but since this is an open source project I simply thought that maybe everything we use should indeed be open source as well. if KDE developers want your tool, they can always get wxWindows :-). The other way around might pose a flaw on this project's part instead of on the KDE developers part. Qt is strong, no doubt. But I'm a bit doubtful about paying for a commercial library or product to develop an open source project. :-).
Stephane Richard
Software Developer
Hi,
i' m frank "gulliver" landgraf. My Background is 3 year mfc-programming(database apps and cad) and about 3 years java (web front end for document management, swing-gui & network programming, actually working on eos).
wxWindows is a big monster, but probably it would be the best choice at this time.
Regards
Frank
HI,
my name is Martin Ltke.I use Classbuilder and monitor its development for about 2 years or so...
It was exciting news when i received word its open source now. A wish came true.
Id like to join in.
I do C++ for about 7 years now mainly in the gaming sector. Im working for Silverstyle Entertainment a gamestudio located in Berlin, Germany as a Junior Programmer.
I could see that the most important tasks like parsing source code into existing CBDs are already in pursue. But i think some convenience tasks in the GUI can still be done.
Regards Martin
Me too! I started at age 9, and now I'm 33. My backgound is UNIX systems and application programming, C++/RDBMS. Some X11 and some Qt (for fun, just to learn it). On Windows I mostly use Delphi (Borland VCL) and VC++ MFC/ATL/WTL.
I'm really excited to see that Class Builder is now Open Source! I'm happy to help wherever I can. For starters, I should aquaint myself with the source code first!