I had Tango 3 and Filemaker on a Mac PPC 7600 for years very reliably.

I loved Tango so much I convinced my day job (at the time) to purchase Tango 2000, which we ran on a PC, connecting to an Oracle db... also very reliably.

Since then, I had to redevelop my personal website for OS X and the latest Tango. I moved to Mac OS X Tiger Server, on an iMac running Tango 5.5 and OpenBase through JDBC.... I'm still using FileMaker (currently at version 9), though: I collect and serve all my information through Tango->JDBC->OpenBase, but I edit and manipulate data through OpenBase->ODBC->FileMaker.

I'm actually very happy, so far, with this setup with few issues. My biggest issues were in initial setup, and they all had workarounds.

I had to completely redevelop my site because Tango 5.5 is sketchy opening and editing older files, and has no (current) FileMaker support on Mac OS X (this is partly FileMaker's fault by requiring FileMaker Server if you want to use FileMaker as a Server DB). Every time I tried opening and editing one of my older Tango 3 files, Tango Studio would bomb if I tried to change the data source.... In fact, just adding a data source in Tango 5.5 (for any interface) bombs the app...

I think Tango was one of the best development platforms out there for web apps, but sadly, I've just seen support for my platforms of choice go down the tubes.... It's very hard justifying the expense of Tango, anymore. I can't even imagine trying to upgrade my server to an Intel Mac and Leopard!!! Even sadder still, is the near silence from WiTango on their development plans for Intel Macs and Leopard....

If I had the time, my next development platform of choice would be OpenBase and WebObjects... the learning curve for WebObjects, though is very steep -- even with computer language/development experience! Luckily, I don't have to go there in the near term...



On Dec 3, 2007, at 11:15 AM, Kent Swisher wrote:

I had Tango 2000 running reliably for years on 300Mhz G4 with webstar 3 and Filemaker 4. Performance was never an issue for our internal applications. G4 hardware is easy to come by for cheap. Only recently converted all to PC. Still using filemaker for Witango apps, but we may yet convert to mysql.

-> Kent

On 12/2/2007 11:54 AM, Bob Parks wrote:
A belated thank you for the replies to my question about running Witango
on Mac Leopard last week.
I guess the quick summary is that I dont want to go there.  I do not
need to run on Leopard.
So I guess my real question is what is the best Mac setup to run Witango?
Basically, I have a truly archaic Tango setup working now.  (Tango 2
running on WebStar 4 on OS 9, talking to a Butler database server
running on OS 8).  It is all on prehistoric hardware, that has been
running forever.  But its tolerable performance, and its been working
but the hardware is starting to die. I was going to do the upgrade to Tango 3 when it came out, but the early releases were pretty buggy, so I put it off.. and off.. ;-) I again
started to work on upgrading it about 5 years ago, but hit some major
changes in business, and the old Tango stuff was working, so it fell to
the bottom of the priority list.
I need to get it moved to something more modern. I dont need to change the functionality, I just want to be able to run it on new hardware that can keep it all working for a while longer. Maybe when the new hardware becomes unsupportable, there will be other options for keeping it going
or the time and priority to rewrite it.
I still don't have a huge amount of time right now to throw at this, so the goal is a simple and reliable solution. I do have some end of year
money if I can buy something to make it easier.
I REALLY want to stick with Mac hardware and OS on this if at all possible.
Thus, 3 issues.. database, server, and studio.
Database.. seems like lots of options.  mySQL seems easy and widely
used. I have already gotten all the data exported out of Butler and done trial imports into mySQL and that seems to work fine. If some other DB worked better, and was not too expensive, that would be fine, but I dont
want to get caught in the proprietary and out of business trap again,
like I did with Butler (Butler was a good option at the time). For Witango, I have collected various versions along the way, so I have
copies of Pervasive 3.5 and 2000, as well as Witango 5.0, and can buy
5.5 if needed.   I already tried porting the old .qry files and I can
use 3.5 to convert the old 2.x files to a .taf and then 5.5 demo version was able to read the 3.5 files. I can run any of the above software, and I can do OS 10.3 or 10.4, PPC
or Intel.  JDBC or ODBC.  And no problem to buy drivers if needed.
The critical part of this is for internal use only and sits behind a
good firewall, so security issues with old OS versions are not a major
problem.
Any suggestions?
Thanks in advance.
Bob
********************************************************************* **** Bob Parks [EMAIL PROTECTED] [EMAIL PROTECTED] www.kidsource.com " We call it theory when we know much about something but nothing works,
        and practice when everything works but nobody knows why."
 - Albert Einstein
********************************************************************* **** _____________________________________________________________________ ___
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

Reply via email to