GUI lib
-
Hi, I'm planning to give a new fresh look to my application. Which of these libraries would you recomend to me?: Codejock Xtreme toolkit[^] Dundas Ultimate Toolbox[^] BCGControlbar library[^]
I use BCG for Awasu and have been very happy with it. Their support doesn't seem to be the best but to their credit, I've rarely needed to use it. I also tried Dundas - they have better individual controls than BCG.
Lets be honest, isn't it amazing how many truly stupid people you meet during the course of the day. Carry around a pad and pencil, you'll have twenty or thirty names by the end of the day - George Carlin Awasu 1.1.5 [^]: A free RSS reader with support for Code Project.
-
Hi, I'm planning to give a new fresh look to my application. Which of these libraries would you recomend to me?: Codejock Xtreme toolkit[^] Dundas Ultimate Toolbox[^] BCGControlbar library[^]
BCG is excellent. I have used it on several projects with no problems.
-
Hi, I'm planning to give a new fresh look to my application. Which of these libraries would you recomend to me?: Codejock Xtreme toolkit[^] Dundas Ultimate Toolbox[^] BCGControlbar library[^]
I will have to put in my plug for wxWindows[^]. It has about the same types of GUI componetns as MFC, so it's not really in the same category as the ones you mentioned. However it means you can port you app to other OSes, such as Linux and Mac, and probably Palm and CE in the near future, too. Just my two cents. :) No single raindrop believes that it is responsible for the flood.
-
Hi, I'm planning to give a new fresh look to my application. Which of these libraries would you recomend to me?: Codejock Xtreme toolkit[^] Dundas Ultimate Toolbox[^] BCGControlbar library[^]
I just evaluated all three. I was extremely dissapointed in BCG. It seemed extremely buggy and the documentation was absolutely horrible. It was nothing more than the headers fed through a help file maker. We never got around to actually using Dundas in our code base. It was missing several key features we needed and still is. Plus, several years ago, I used Ultimate Grid thought it was rather weak. The company also had a copy of their TCP/IP library which I experimented with and found it to be horrible. One problem with both BCG and Dundas is that they both started out as very disparate libraries and have been kludged together in a single package. (For example, Dundas advertises "JPG Support". Unless they've changed it, this is nothing more than the public JPG libraries repackaged.) To be fair to Dundas, I've heard their support is much better than in the past and in it appears they've actually worked on the product in the last six months. At least enough to do two releases. (In years past, they've gone for long periods without any releases.) As you can tell, I found Codejock to be the best solution. They provide all the features we need in a very well designed package. I liked how it worked so seemlessly with our code. Their technical support was fantastic--and this was only with the demo! The only downside is the help, which is pretty lame. The complete lack of tutorials and how-to articles is as annoying as it is astonishing. Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
-
I just evaluated all three. I was extremely dissapointed in BCG. It seemed extremely buggy and the documentation was absolutely horrible. It was nothing more than the headers fed through a help file maker. We never got around to actually using Dundas in our code base. It was missing several key features we needed and still is. Plus, several years ago, I used Ultimate Grid thought it was rather weak. The company also had a copy of their TCP/IP library which I experimented with and found it to be horrible. One problem with both BCG and Dundas is that they both started out as very disparate libraries and have been kludged together in a single package. (For example, Dundas advertises "JPG Support". Unless they've changed it, this is nothing more than the public JPG libraries repackaged.) To be fair to Dundas, I've heard their support is much better than in the past and in it appears they've actually worked on the product in the last six months. At least enough to do two releases. (In years past, they've gone for long periods without any releases.) As you can tell, I found Codejock to be the best solution. They provide all the features we need in a very well designed package. I liked how it worked so seemlessly with our code. Their technical support was fantastic--and this was only with the demo! The only downside is the help, which is pretty lame. The complete lack of tutorials and how-to articles is as annoying as it is astonishing. Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
Odd you've had such a different experience of BCG to what I have. What bugs did you find? I found it to be reasonably stable although I don't push the envelope very hard. The doco is not terribly good although most of the code is self-explanatory so I don't really need to use it much. I found the app wizards (that generate code skeletons) helpful in figuring out how things are supposed to work. I wanted to eval Codejock as well but they didn't reply to my emails :rolleyes:
Lets be honest, isn't it amazing how many truly stupid people you meet during the course of the day. Carry around a pad and pencil, you'll have twenty or thirty names by the end of the day - George Carlin Awasu 1.1.5 [^]: A free RSS reader with support for Code Project.
-
Odd you've had such a different experience of BCG to what I have. What bugs did you find? I found it to be reasonably stable although I don't push the envelope very hard. The doco is not terribly good although most of the code is self-explanatory so I don't really need to use it much. I found the app wizards (that generate code skeletons) helpful in figuring out how things are supposed to work. I wanted to eval Codejock as well but they didn't reply to my emails :rolleyes:
Lets be honest, isn't it amazing how many truly stupid people you meet during the course of the day. Carry around a pad and pencil, you'll have twenty or thirty names by the end of the day - George Carlin Awasu 1.1.5 [^]: A free RSS reader with support for Code Project.
Taka Muraoka wrote: What bugs did you find? There most immediate concerned toolbar creation. The wizard also created bad code which caused errors. (The wizards for .NET 2003 were horrible.) The worse was that it apparently swallowed a background paint message in an app with multiple views. I was unable to track this one down but didn't care since it was the straw that broke the camel's back. We returned the product a few days later. In the almost three weeks I spent with the code, I encountered at least a dozen errors, each of which took hours for me to resolve. Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
-
I just evaluated all three. I was extremely dissapointed in BCG. It seemed extremely buggy and the documentation was absolutely horrible. It was nothing more than the headers fed through a help file maker. We never got around to actually using Dundas in our code base. It was missing several key features we needed and still is. Plus, several years ago, I used Ultimate Grid thought it was rather weak. The company also had a copy of their TCP/IP library which I experimented with and found it to be horrible. One problem with both BCG and Dundas is that they both started out as very disparate libraries and have been kludged together in a single package. (For example, Dundas advertises "JPG Support". Unless they've changed it, this is nothing more than the public JPG libraries repackaged.) To be fair to Dundas, I've heard their support is much better than in the past and in it appears they've actually worked on the product in the last six months. At least enough to do two releases. (In years past, they've gone for long periods without any releases.) As you can tell, I found Codejock to be the best solution. They provide all the features we need in a very well designed package. I liked how it worked so seemlessly with our code. Their technical support was fantastic--and this was only with the demo! The only downside is the help, which is pretty lame. The complete lack of tutorials and how-to articles is as annoying as it is astonishing. Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
Joe Woodbury wrote: One problem with both BCG and Dundas is that they both started out as very disparate libraries and have been kludged together in a single package. I do not know why you decide to put only BCG and Dundas in this category. We all saw CodeJock grew out of Codeguru. From the very start the BCG library was the library of choice. It is true Dundas is highly a package of existing classes - just download the demo, the yellow popup dialog that will just not go was WDJ article. Tbe BCG Prof, seems to be a more planned work based on the original BCG library. Your point on the BCG documentations is, however, correct. There was a time I wanted to use it for my company here in Japan. All other programmers in my company are Japanese but was told to use the forum - knowing that my co-workers will not be able to, I reconsidered the project. On bugs, yes! I will say there was a typical bug that took them more than half a year to provide an answer. It affected my choice of the library for that same project - it was ActiveX Document Server support. Finally, they managed to solve it. I think they need to spend more responses on the documentations instead of creating more and more controls. In all, BCG leads on many grounds, but CodeJock is also improved greatly with their recent releases, making it difficult to recommend one over the other. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
-
Taka Muraoka wrote: What bugs did you find? There most immediate concerned toolbar creation. The wizard also created bad code which caused errors. (The wizards for .NET 2003 were horrible.) The worse was that it apparently swallowed a background paint message in an app with multiple views. I was unable to track this one down but didn't care since it was the straw that broke the camel's back. We returned the product a few days later. In the almost three weeks I spent with the code, I encountered at least a dozen errors, each of which took hours for me to resolve. Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
Were the problems with the standard or the professional version? Frankly, I still have to purchase a GUI library for a project. I had one version of the Dundas grid, and was not happy with it. I bought it when I read OLE DB source was supported - it turns out to be a big jock. Finally, I was tool to replace it with the ADO source, which was not appreciate for my project then where we could not just make connections to database at will, some of the customers were paying per session for the database access. Which grid library will you recommend then? I will prefer one with sources! Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
-
Hi, I'm planning to give a new fresh look to my application. Which of these libraries would you recomend to me?: Codejock Xtreme toolkit[^] Dundas Ultimate Toolbox[^] BCGControlbar library[^]
I suggest you add Prof-UIS to your list. I'm using it in new product and am impressed with its capabilities. Support is good, but docs aren't. See: http://www.prof-uis.com[^] There is also an article here at CP on it. Neville Franks, Author of ED for Windows. Free Trial at www.getsoft.com
-
I suggest you add Prof-UIS to your list. I'm using it in new product and am impressed with its capabilities. Support is good, but docs aren't. See: http://www.prof-uis.com[^] There is also an article here at CP on it. Neville Franks, Author of ED for Windows. Free Trial at www.getsoft.com
Thanks Neville, it looks a great library :-)
-
Taka Muraoka wrote: What bugs did you find? There most immediate concerned toolbar creation. The wizard also created bad code which caused errors. (The wizards for .NET 2003 were horrible.) The worse was that it apparently swallowed a background paint message in an app with multiple views. I was unable to track this one down but didn't care since it was the straw that broke the camel's back. We returned the product a few days later. In the almost three weeks I spent with the code, I encountered at least a dozen errors, each of which took hours for me to resolve. Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
Joe Woodbury wrote: There most immediate concerned toolbar creation. The wizard also created bad code which caused errors. (The wizards for .NET 2003 were horrible.) I've had a few minor problems with toolbars but nothing I can't live with. I've only used BCG with VC6 so I can't comment on it wrt VC7. I've got no plans to "upgrade" to VC7 any time soon. I use a few third-party libraries and the thought of trying to get them to work on the seething mass of instability that is VC7 is just too horrible to contemplate.
Lets be honest, isn't it amazing how many truly stupid people you meet during the course of the day. Carry around a pad and pencil, you'll have twenty or thirty names by the end of the day - George Carlin Awasu 1.1.5 [^]: A free RSS reader with support for Code Project.
-
Joe Woodbury wrote: There most immediate concerned toolbar creation. The wizard also created bad code which caused errors. (The wizards for .NET 2003 were horrible.) I've had a few minor problems with toolbars but nothing I can't live with. I've only used BCG with VC6 so I can't comment on it wrt VC7. I've got no plans to "upgrade" to VC7 any time soon. I use a few third-party libraries and the thought of trying to get them to work on the seething mass of instability that is VC7 is just too horrible to contemplate.
Lets be honest, isn't it amazing how many truly stupid people you meet during the course of the day. Carry around a pad and pencil, you'll have twenty or thirty names by the end of the day - George Carlin Awasu 1.1.5 [^]: A free RSS reader with support for Code Project.
Well, I had a serious problem with the VC7.0 too. It turns out to be MS bugs causing many leaks in the BCG. MS sent me patches, but I could not them since it was not universal fix. With VS.NET 2003, I think MFC is fixed and the problems I had are gone - will need to give it another try. In such cases, BCGSoft should have provided some "work-round", but they normally wait till MS is fixed the problem (in service packs) - may be one source of the bad image! Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
-
Joe Woodbury wrote: One problem with both BCG and Dundas is that they both started out as very disparate libraries and have been kludged together in a single package. I do not know why you decide to put only BCG and Dundas in this category. We all saw CodeJock grew out of Codeguru. From the very start the BCG library was the library of choice. It is true Dundas is highly a package of existing classes - just download the demo, the yellow popup dialog that will just not go was WDJ article. Tbe BCG Prof, seems to be a more planned work based on the original BCG library. Your point on the BCG documentations is, however, correct. There was a time I wanted to use it for my company here in Japan. All other programmers in my company are Japanese but was told to use the forum - knowing that my co-workers will not be able to, I reconsidered the project. On bugs, yes! I will say there was a typical bug that took them more than half a year to provide an answer. It affected my choice of the library for that same project - it was ActiveX Document Server support. Finally, they managed to solve it. I think they need to spend more responses on the documentations instead of creating more and more controls. In all, BCG leads on many grounds, but CodeJock is also improved greatly with their recent releases, making it difficult to recommend one over the other. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
Paul Selormey wrote: I do not know why you decide to put only BCG and Dundas in this category. Simply because while looking at the code and the API, CodeJock seemed more unified to me. While looking at the code BCG gave me the feeling of heavily evolving code. Perhaps it was actually designed the way it is, in which case I retract that remark. I'll keep it for Dundas since I know it's a collection of at least two major class libraries and several minor ones. Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
-
Were the problems with the standard or the professional version? Frankly, I still have to purchase a GUI library for a project. I had one version of the Dundas grid, and was not happy with it. I bought it when I read OLE DB source was supported - it turns out to be a big jock. Finally, I was tool to replace it with the ADO source, which was not appreciate for my project then where we could not just make connections to database at will, some of the customers were paying per session for the database access. Which grid library will you recommend then? I will prefer one with sources! Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
Paul Selormey wrote: Which grid library will you recommend then? Don't know. As it turns out, I just removed a very old version of Chris Maunder's grid control (from the CodeGuru days) from some code and haven't yet decided what to replace it with. That's one of my tasks this week. Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke