Steve,

Last year after you released the Dev-Express wrapper Trent stated the you guys were using Dev-Express in your medical system. This statement weighed quite a bit on my decision to use Dev-Express as I figured if you are using it in your medical system chances are that you guys will run into issues etc and be familiar with that set of controls.

Now Trent say's

The point I am trying to make is that the decision to purchase and use a 3rd party UI control set should not be based on what you guys are using rather on which control set you believe has the best features etc. You guys do an excellent job of providing the wrappers as well as the interfaces and the selection of a 3rd party UI control shouldnt matter.

Paul 

Paul,

I agree you should use whatever controls that provide the features you want and are comfortable using.  The SF source code provides a plethora of samples on how to plumb a new or third party control.  Paul, I do not agree with your characterization of SF moving from one control base to another.  I may remind you it was our desire to use Ingragistics initially but we could not obtain the necessary legal release to include a wrapper in our code.  It was only at the insistence of Larry Caylor that Infragistics caved-in. 

We included Dev-Express and Infragistics because they are the most commonly used.  Beyond these two products trying to create a wrapper for all third party controls is beyond any benefit we would receive.

Hi Paul;



Sometime one vendor may have nicer components, but then in another release, another vendor can jump over them. Previously, DevExpress has been very good, I even own them (but have not used their .Net stuff yet), but now, IG seems like has taken larger steps. At this point, I'm just concerned that all the AJAX stuff in IG components work properly through BO.

..ßen

Trent,

Ben is correct on that last year you were all fired up about Dev Express and Infragistics was not in the picture. I ended up dropping Infragistics and using Dev-Express as DevEx seemed to be the direction the SF was going for enhanced UI controls and figured I would rather use something that you guys were supposed to be using yourselves. Now you are saying Infragistics is where it is.   

Ben,

Don't make the mistake I did. Choose the UI control's  you want to use because you like them I liked Infragistics alot better than I like Dev-Express

Thanks Trent; Yes I had followed that,



and I even went back to last year's threads where back in Sept or Oct, you mentioned you had evaluated DevExpress and IG, and for Editor, you selected DevExpress. But the recent thread, shows that you had switched to IG for better performance.





I do have the full DevExpress system, however I spent a lots of time yesterday looking at IG components for ASP.Net, and they are much better and smoother. Their new AppStylist gives you a nice control over the Look&Feel of your app.



So, Trent as long as I use "IBusinessBinding" interface, I'm free to use IG databound components? Even the ones that use AJAX to get/set data via client?



As I was watching some of the videos, the guy was saying how AJAX controls use database gateways to communicate with the database server and that alarmed me about using BO on the server side.



Can you elaborate how the AJAX component will work through BO?



Thanks!

..ßen

I have already given my opinion on another thread: http://forum.strataframe.net/FindPost8373.aspx .  As I mentioned, we use the SF controls with a few Infragistics editor controls within our medical software.  We have no wrapper for any 3rd party web controls and do not have any plans at the moment to create any.  You can use the IBusinessBindable interface to integrate native StrataFrame data-binding for any 3rd party control, so the choice is yours in this area. 

The second part to this question is, will I be able to use any of the IG ASP.Net components with SF? I'd like to know if there are known problems before investing in IG NetAdvantage.



Any comment or input, is much appreciated!

..ßen

Hi All;



I'm trying to finalize my tools before starting the app. The App. will be partly Windows and partly ASP.Net sharing data.



I like to get some thoughts and experiences from SF team and those how have chosen one v.s. the other and why?



a) SF comes with a limited number of Windows components that are nicely tied with SF framework and also takes advantage of SF theme system. This helps building a uniform application, but the components are limited, especially when it comes to the ASP.Net part (I mean for grid and new Web gadgets that IG offer).



b) Infragistics (IG), offer a very nice and complete components, with a powerful "Application Stylist" design for Windows and web. This gives you a wide range of designs, BUT you loose the SF themes (like the navigation tool bar, application header and etc.) and also we loose some of the SF integrations that are already in SF components.



Due to my lack of experience (being new to SF and IG), I really would like from those who have gone through this road to share their suggestions.



Thank you in advance!

..ßen