5.0 ruins existing code lines

Discussions and Tech Support related to automating the iMacros Browser or Internet Explorer from any scripting and programming language, such as VBS (WSH), VBA, VB, Perl, Delphi, C# or C++.
Forum rules
Before asking a question or reporting an issue:
1. Please review the list of FAQ's.
2. Use the search box (at the top of each forum page) to see if a similar problem or question has already been addressed.
3. Try searching the iMacros Wiki - it contains the complete iMacros reference as well as plenty of samples and tutorials.
4. We can respond much faster to your posts if you include the following information: CLICK HERE FOR IMPORTANT INFORMATION TO INCLUDE IN YOUR POST
Post Reply
Posts: 5
Joined: Thu Mar 16, 2006 1:28 am

5.0 ruins existing code lines

Post by JSager » Thu Mar 16, 2006 1:35 am

Hi guys -

I may be a bit late in pointing this out now, but you should hear it nonetheless.

I am a developer who works on a product which includes iMacros.

Recently, due to the Windows security issue with file download boxes, we needed to move from iOpus 4.x to iMacros 5.x

In doing so I discovered that you folks at iOpus have broken one of the cardinal rules of software releases:

NEVER break existing code that depends on yours.

Couldn't you have just left the scripting commands that used to be in there alone and deprecated them like everyone else does? You can always add new commands, but don't EVER take existing ones away!

You completely broke our application and I had to spend three days of developer time and weeks of QA time (can you hear the words FULL REGRESSION TESTING ringing in your head? I can). The fact that you don't intend to fix the security problem in version 4 combined with the fact that it's a complete blocker cost my company many thousands of dollars.

My company's been using your products since the early days of version 3, and your software has gotten a heck of a lot better during that time. Next time you upgrade it, please respect that fact that there's a lot of production level code out in the field that depends on you not whimsically changing your scripting interface commands between versions.

Jeremy Sager
Post Reply