Steve, My point exactly, and you have just confirmed that you'll continue pushing best practices even if that person doesn't want to know that.
You can either help that person in the current situation or you can't, if you can't hold your views back on best practices because the developers like myself who have been around since Version 1.0 of coldfusion are aware of pitfalls and best practices, but every know and then we come across older code that has to be maintained or added to, and unless the client has the cash to make the changes we are stuck with what we have to maintain, you of all people should be well aware of that, and others who have been contracting or have done contracting would also be very well aware of these things. You didn't listen to what I was saying Steve, the same as you probably didn't listen to the posts about not pushing to upgrade and you'll fix your problems, that should have been enough for people to not be so quick to jump on someone because they are stuck with older code to maintain, and that is the key older code to maintain. My point is that the poster is maybe more than aware of best practices, or upgrading to fixing a problem and in an ideal world we could do that, but we don't live in an ideal world and that poster is not interested to here best practices, they are after a solution to a problem that they have with the current code or technology that is being used. Get off your high horse about saying that mentioning best practices is good for all to know, because that can be pointed out in a separate email, not to the person who is after a solution for their current problem. In my case it is older technology that is tied to a specific platform, I was not interested in best practices for cross browser issues, if I was interested I would ask how to make it cross browser and I didn't so why do you and others point out that best practice is to do it this way, I wasn't asking for best practice, I was asking for a solution to a problem to get that to work. Steve, take a hint and learn that this is not an ideal world we live in and don't push something that that person is maybe more than aware off. Now I'll spell it out for you and others to read, I am interested in a solution to a current problem I am not here to be told that I should have done it this way or its best practice to do it this way, or I need to upgrade to fix this problem. I guess when it comes to most people on this list, you'll all not get jobs in the bigger fortune 500 companies because they are always 5+ years behind in technology due to the costs off keeping up to date with technology, and to support applications that run on these older system is what I am saying, I could upgrade the systems to be more up to date but hey that would cost 100's of millions of dollars to these companies, and I could follow best practices and change the 900,000+ lines of code to make this application be more in line with best practices, but I am only being paid to maintain not upgrade, to you see my point here now Steve. Enough Said.... Regards Andrew Scott Technical Consultant NuSphere Pty Ltd Level 2/33 Bank Street South Melbourne, Victoria, 3205 Phone: 03 9686 0485 - Fax: 03 9699 7976 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Onnis Sent: Thursday, 24 February 2005 12:00 PM To: CFAussie Mailing List Subject: [cfaussie] Re: Javascript Checkbox change Andrew "this forum is designed for people to talk about solutions, problems and technologies to suit the environment they are working in." Exactly and I agree. From your initial post I was not aware that you were trying to fix someonthing someone else may have done or you had particular constraints, so why wouldn't someone offer a different method of doing something. In the end it comes down to either taking on what someone suggests or not. I am sure it was not said to have a go at you, but more of a general comment on how you could be doing something in particular, such as your issue. There are many many ways to do many many things. I mean you could have gone parent.document.forms[0].Test.checked or parent.document.formName.Test.checked or parent.document.forms[0].elements[23].checked All that was is a suggesttion on how to do something, not a direct attack on you Enough said Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andrew Scott Sent: Thursday, February 24, 2005 11:41 AM To: CFAussie Mailing List Subject: [cfaussie] Re: Javascript Checkbox change Steve, The problem is that when someone posts to the list they are looking for a solution or help on their problem, if someone wants to later turn around and say that its best practice to do it this way and not that then that is great. But instead of comments made like: er yeah .all.Test.checked heh 'using .all is MS code, one should access the objects in a W3C manner by using document.getElementById("Test") ' This is not saying it is best practice, that is having a dig at someone for not being able to do best practice due to other reasons. This is what has been driving me a little made when posting on this forum, because you get all the people chime in and its best to do it this way or update to this, but stop and think for a moment there are reasons for everything. And the reason here is that others will also be in the same position, so regardless of whether your comment or other peoples comments are marked as its good to tell others about best practices is a load of crap. There are websites and information that people can search for on best practices, this forum is designed for people to talk about solutions, problems and technologies to suit the environment they are working in. People post here to get a solution to a project that is maybe more ancient than the when best practice was created, and don't have the time to make the necessary changes. I have been a member of this list from the day it was created, and peoples attitude has not changed and we continue to see it on a weekly basis. Like I said the posts about coldfusion 5 was the same, they didn't have a choice and look at the response to that by people who couldn't upgrade and were stuck to use the technology and code that they had to use. This is the same and people out there have to wake up and realise that they might be able to always use best practice, or they might always be able to use the latest and greatest. But this is the real world and this is not practical in every situation, the point here is that before making a post stop and think about the situation this person is in, stop and think about what that person is actually asking. Whether it be best practice or a solution to older technology, then there is a reason for them to do it there way, and that is what best practice doesn't cater for. These posters want to know a solution to that problem, and don't need to here best practice or you should have done this or best to upgrade to fix that. Most of you have been here long enough to know that you could be developing under MX 7.0 today, and next month you will be developing under CF 5.0 and then you'll be the one in the position of dealing with other peoples code, and asking the simple thing of fixing something without wanting to here you should have done it this way. I have rambled on long enough and vented the frustration that others have been feeling for a long time, a lot of left this list because of these reasons. Regards Andrew Scott Technical Consultant NuSphere Pty Ltd Level 2/33 Bank Street South Melbourne, Victoria, 3205 Phone: 03 9686 0485 - Fax: 03 9699 7976 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
