I don't think that helps at all. This bug is horrendous, and well
known. Yet where is the acknowledgement, or knowledgebase, or techdoc
about how to work around or avoid? You have provided none of that.
Heck, how about a small addon to the studio or utility, that just
WARNED you of the presence of bad !CSTs on a save since it is so easy
to detect?
Witango inc has ignored it, and other issues, and left the community
to flounder.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Apr 12, 2007, at 7:53 PM, Phil Wade wrote:
Ben,
You are making the assumption that bug is in code we have access to
or control over. If we could fix the bug we would have.
The issue lies in a portion of an external library that was
licensed by pervasive from a 3rd Party (and subsequently us) which
gave them the ability to do a lot of cross platform functions.
With the introduction of OS X and the carbon lib a few of these
functions do not work as they used to and with subsequent releases
of OS X the issue became worse. Try as we may we were not able to
convince the developer to update or maintain their library or
secure the source code we needed. Removing the framework to fix
the issue meant we had to rewrite a major portion of the Dev Studio.
With the Tango 2000 and Witango 5.x Dev Studios based on number of
now obsolete libraries, frameworks and APIs on both platforms we
had no choice but to redevelop the Dev Studio from the ground up
which we have been doing for the last 2 years to ensure we can
continue to support it.
These issues do not affect the server. The 5.5 server is based on
code we have written and open source libraries that will ensure it
can be upgraded and maintained well into the future.
Keep an eye out for the first public beta of the 6.0 Dev Studio
next week for all operating systems with a JRE 6.0. There are
still a few glitches we are working on but we are pretty sure it is
fully backward compatible with Witango Server 5.5.
Regards
Phil
On 13/04/2007, at 11:01 AM, Ben Johansen wrote:
It is unconscionable for a vendor to have such a blatant bug in
software and not deal with it.
this is going on 2 years, of knowing it has this issue and not
fixing it.
and selling it as if there is not a problem.
I really appreciate getting pressure and being accused of wasting
time, just to find out that it was this bug that should have been
fixed.
No this is not just a Mac issue. It happens, though not as much in
Windows version of Dev Studio
I caution anyone that is working on a high profile site and using
this product. you better check each and every file after every
save because the dev studio can't be trusted
Ben
_____________________________________________________________________
___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
