That is a great compilation and an incredible amount of documentation.
Posts like that need to be in a sticky on a web forum, instead of lost
to time on this list.
I don't remember much issues from 3.x to 2000, but I do remember
issues with 5. I don't remember, unfortunately what the issues were
with 5.0, but I remember the whole 5.0-5.5 encoding issues problem.
There was a change in the default encoding of all tags in 5.5, and it
required text searching and replacing of all tafs, and if you had a
lot, and complex tafs, there could be a lot of manual checking and
changing there. So I would add that to the 5.0-5.5 part, but I don't
remember the 5.0 issues.
--
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 Feb 11, 2008, at 11:03 PM, Anthony M. Humphreys wrote:
Michael,
Here's what I know and remember from my tech support days and
training days at Everyware.
2.x to 3.x conversion did have some small issues. this is where the
biggest changes occurred. I can't remember them all now. I'm sorry,
but I longer have my 2.x editor to be able to re-create any of the
issues encountered. But I still have TeMail, the dll for being able
to send RFC 821/822 format emails from Tango Server 2.x on which the
current e-mail action was based. And I also have the documents I
wrote to design and support TeMail, as well as my proposals for the
T3 email action.
3.x to 4.x (Tango 2000) is _very_ straight forward. The big change
was that the TAF files are now in XML rather than in binary format.
4.x merely added objects (TCF Files) and new actions (presentation,
Create Object, Call Method, Object loop) abilities and source code
control integration (check in/check out).
I still have a copy of an internal tool we used to use to view the
internals of 3.x taf files (t3viewer.exe), and the tool we gave out
to change datasources in 3.x files (t3DS.exe). But I don't have my
box numbers for Tango 3.x anymore, even though I still have a copy
of the installers.
If it's still available from Witango for Tango 2000 users, the
Witango 4.5 (windows) editor works much better than the Tango 2000
(4.0) editor ever did.
Witango 3 server and later cannot run 2.x qry files, they must be
converted by an editor/studio.
Tango 2000 (4.x) and 5.0 and 5.5 servers can run Tango 3.x without
conversion, but the editor will force conversion.
Tango 3.x, Tango 2000 (4.x), and Witango 4.5 editors can convert 2.x
qry files. I don't know about Witango 5.0 or 5.5 editors/studios.
Tango 2.x did not have variable scope, all variables were "User"
scoped. Because of this, in part, the default scope for Tango 3 and
4 was "User".
The default variable scope for 5.5 is "Request" (formerly "local"
scope), but that can be changed at the server level for
compatibility, if needed.
So if you are running 3.x or 4.x Tafs, the move to 5.5 will
currently be seamless with one minor change to the server, namely
the default variable scope from "Request" to "User".
If you still have 2.x qrys, your upgrade may be a bit more difficult
as you'll have to convert these to TAFs first, and then test and
debug the conversion before deploying.
If you have more questions, or need more help, feel free to contact
me off list.
Anthony -
----- Original Message -----
From: "Michael Heth" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, February 11, 2008 18:33
Subject: Witango-Talk: Witango Version 6? | 2.3->3.6->4.0->5.5->6.0?
I have sat on the sidelines for quite a while now but assuming that
6.0 works as advertised I may get motivated to bring some old apps up
to snuff.
But I have lost track of the steps that will work to port old apps to
the newer versions.
The old 2.3 to 3.0+ upgrader did not works as smooth as it was
supposed to. I had to fix a lot of snags and that put me off
upgrading a series of admin apps for my CMS.
I remember that you were supposed to be able to open 3.0+ apps in 4.0
and save them and be okay.
Then there was all the talk on the list about the 5.0 or 5.5 studio
introducing a bunch of bugs that had to be fixed on a per app basis.
So does anyone have a walkthrough of what you can do to bring very
old Tafs up to the latest?
Thanks for any help/info.
M./
Michael Heth
[EMAIL PROTECTED]
________________________________________________________________________
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
