Re: Will the QuickForm API always be a moving target?

<culley@fastmail.fm> wrote : > I just upgraded from Quickform 3.0 to 3.1 on my development machine and > I am finding that Quickform 3.1 is throwing E_USER_ERROR level errors > for depreciated methods. I read here: > > ›™ÒGz»ëa > ‡-'YÁÀhttp://marc.theaimsgroup.com/?l=pear-general&m=105890947805091&w=2 > > that at least one depreciated method is to be removed. Will other > methods also be depreciated? It would be helpful to see a list. The fact that it throws a PEAR error should help you find where in your code you are using a deprecated method. Use a function to handle your PEAR errors and check if the error code is equal to QUICKFORM_DEPRECATED. Deprecated methods are easy to find in QuickForm.php source as they have been marked as such along with an explanation on how to get rid of them. > I have been using QuickForm extensively since version 2.2. Thanks to > everyone who has worked on it-- what a great component! Because I have > been using Quickform for so long it is a little concerning to grep > through my source tree and see how often I have used methods which are > now depreciated. I have been trying my best to always use the most > recent version but I am finding that upgrading QuickForm is like playing > with fire. Every upgrade since 2.9 has broken my code. I'd really love > to see the api freeze up a bit-- production environments need this kind > of stability. The api also seems to be getting increasingly complex. > As the source gets heavier and heavier QuickForm might be in darger of > no longer being so quick ;) 3.0 has frozen up the API, but as we keep on developing QuickForm, there might always be new changes if we feel they improve the code and class behavior. > I personally do not use the renderer stuff at all-- 2.10 had all the > features I need. I suppose I could maintain a personal version of 2.10 > but I would prefer to stay in line with the main trunk. > > I hope this is not taken in the wrong way. I really do appreciate all > the work put into Quickform. I can understand your point of view as I have the same problems with my own code... That's why I have added these QUICKFORM_DEPRECATED errors, so that it's easier to find where deprecated methods are being used and fix my code.. Personally, I log all the errors in a text file and correct them when they appear. 3.1 should be used as a transitional version. Bertrand Mansion Mamasam