Hello Leif, Thursday, June 30, 2005, 4:27:50 PM, you wrote:
> If you look at it, that's exactly what RITLabs and every developer who > is putting out applications is dealing with. Some new functionality is > needed and you have to figure out how to incorporate it in without > breaking something else. Sometimes it's easy, oftentimes it's not. Leif, I am no programmer but I work in an industry that has to have very resilient products and the thing that is worrying me about TB development is the apparent effort being extended to add new features/functions when there are issues with the existing ones. RL would do themselves a lot of favours if they implemented a feature/function freeze at the present time and picked off all the existing bugs. Get the code base stable before implementing anything else... Once stable implement one feature at a time into the betas so you know what is breaking what... I would dearly love TB to continue and get back on track but I have already started evaluating other options (none of which appear to be as complete as TB) as a fallback position. Come on guys, we *are* behind you on this (we wouldn't be testing otherwise!) we just want some stability to the product before more changes are made... Thanks for reading -- Tony Brookes [EMAIL PROTECTED] http://www.tonybro.com Using The Bat! v3.5.28 on Windows XP Service Pack 2 ________________________________________________________ Current beta is 3.5.35 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
