Hi Jay, I have read your thread here with great interest. You may have read my response to the "Easypano Promotion Announcement" thread further down in the topics list. I would suggest you post a reply in that thread and bring it to the top of the topic list so more readers may respond. You will find some of the bug issues posted there.
Now for a response to your thoughts here. Unless your are in a hurry I would wait on your decision to purchase the TW application. Gather all the information that time will allow so you can make an informed decision.As I stated elsewhere I think TW 1.30 is a cool piece of software but I have to reiteriate that there are some serious issues with its' code. A few weeks back, during one week I wasted 3.5 hours doing work arounds in TW.
"Let me digress here for a monement. I have sent out many resumes in my time and every head hunter I've talked to has emphasized that there should not be so much as a comma out of place on a resume. After all if a job seeker can't take the time to submit an error free resume what kind of work are they going to do for a prospective employer." Well I think the same can be said about software development. If an application developer wants people ( clients, buyers) to take them seriously then they have to show some effort to the public that they are producing a product to the best of their ability.
A few points for you to ponder. Just take a look at the small panorama that runs on the home page of this website. How's that speed?...easy to view for you?...How would you like your clients to have to put up with that? Well EasyPano seems to think it's OK! That is one of the major (my words) bugs in this software. It's not as if this flaw is hidden in the depths of the code but it's the very first thing a viewer will see when a Pano is published. I ask! How could this be overlooked? How could the developers not see this as a problem and not come up with a fix for it.
Another item...my personal research into the EasyPano resume! The EasyPano home page loads very slow for me... so I ran a test on the HTML code at the W3C Markup Validation Service http://validator.w3.org/ and it found
Failed validation, 122 errors
In fact I tested every first page link for the buttons on th