Folks,
I'm all for supporting this product growing as it has tons of potential, but when you come out with a new release, PLEASE provide us a list of depricated or removed functions. As a toolkit developer, one of your highest priorities has to be to ensure backwards compatibility (when possible), especially towards apps built on your products.
I can understand the need to violate backwards compatibility, it does happen, but things like UpdateView() being removed? The project conversion process needs to be improved. If nothing else, providing some documentation as to which object methods and properties have been removed, or at least leaving the old functions in as stubs and marking them as obsolete would be a great help.
I now have 67 errors for properties and/or methods no longer existing, and it's stressful at best to resolve some of these things. Please don't take this as complaining, I just want to see it become a very smooth process like DevExpress and some other controls.
Kind Regards,
Matt
I'm all for supporting this product growing as it has tons of potential, but when you come out with a new release, PLEASE provide us a list of depricated or removed functions. As a toolkit developer, one of your highest priorities has to be to ensure backwards compatibility (when possible), especially towards apps built on your products.
I can understand the need to violate backwards compatibility, it does happen, but things like UpdateView() being removed? The project conversion process needs to be improved. If nothing else, providing some documentation as to which object methods and properties have been removed, or at least leaving the old functions in as stubs and marking them as obsolete would be a great help.
I now have 67 errors for properties and/or methods no longer existing, and it's stressful at best to resolve some of these things. Please don't take this as complaining, I just want to see it become a very smooth process like DevExpress and some other controls.
Kind Regards,
Matt