Existing users, 
Advanced Search
 DTerm - 3.2Instrumentation libraries that can be left in shipping code |
|
||||||||||||||||
|
|||||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
We consider e-mail… - Version: 3.0.2, 1/5/2003 12:44AM PST
Austin-Soft.com (Austin-Soft.com)
a very critical communications tool, so we answer all e-mail. We've been investigating setting up an e-mail list, but have yet to find an acceptable solution. We have not considered using a webboard because of the confidentiality of some of the communications.
I agree VERY… - Version: 3.0.2, 12/21/2002 11:26AM PST
jwiede
strongly with harleyb's comment: Devs giving themselves self-serving (e.g. star-inclusive) reviews is CLEARLY against the VT ToS, and Austin-Soft.com should replace that review with one using "n/a" instead. It's not up to the dev to decide what star reviews are "valid", the whole point of the VT system is to allow folks to give _dev unmoderated_ reviews and ratings. As opposed to dev sites where they typically only allow "good" reviews. Gotta take the bad with the good, and if you feel heynnema's review is undeserved, convince them to change it by showing them what they're looking for in your product.
I believe what… - Version: 3.0.2, 12/21/2002 11:25AM PST
jwiede
heynnema is looking for as a support site is a support "board" instead of just an email address. Reasonable request for a commercial product, in my book, as it's quite easy for a company to ignore email (not saying AustinSoft does, just that other companies do). Having a support board gives customers obvious indication of how quickly and well a dev responds to support requests. Given the vast array of free "webboard" offerings, it's something AustinSoft ought to consider for a developer-targeted product of this nature (since it will intrinsically generate more, and more complex, support requests than, say, a simple user-targeted app).
