Just enter this line into the Komodo Help search box
CGI Debugging
I did that yesterday and it seems easy enough but still no joy. My question was more about how to configure OS X to run TTX locally within the Komodo environment.
Based on your following comments, it would seem that I'd need to set it up on a web server in OS X Server same as if I was really going to host it.
I guess I was under the false impression that Komodo would handle all the simulations as long as my OS had Perl installed. I realize now that makes little sense and feel somewhat silly.
It will explain how to configure web server and Komodo for remote debugging (you should use remote debugging even if both Komodo IDE and web server reside on the same server).
I erroneously thought I could do local debugging since Perl is part of OS X and Komodo would simulate the server environment.
I should just install TTX on the Mac Server on my LAN and use Komodo on my Mac desktop computer.
re. tough interface & Mac
Actually the TTX was being developed on Linux, then Windows, then Mac OSX. I still use Windows XP (as VMWare Fusion guest) for SQL Server related testing and IE proof reading. The interface is based on mailbox concept and first hand experience running medium scale customer service center - the help desk is communication tool, rather than a set of fancy bells and whistles. Do not get me wrong, I am not against good bells and nice whistles, but the interface must follow real life workflow.
For my customers,
it's a communication tool- No different than Outlook Express and it must be just as quick & easy for them to use. My New Ticket form is just Name, Email, Subject, & Body, just like an email.
For me,
it's an organizational tool- I must be able to see everything together for each job (Ticket) and see all jobs in one place. Unlike Outlook, where messages could get lost, overlooked, or they have nothing to do with jobs. Not to mention that email messages themselves sometimes do not arrive due to spam, filters, laziness, etc. With any live internet connection, just go to my TTX web site, post a message, and it's guaranteed to be in there regardless of email settings, filters, etc.
I never installed the optional TTX email & piping scripts because I felt that TTX was already simple enough to use. Giving my customers the option of emailing ticket responses seemed like a step backwards towards unreliability... not with TTX but with email in general. I tell them all that if they want prompt service they have to keep all the messages within TTX.
I like the interface, it's simple, makes sense, and flows logically, that's why I called it nice & tight. It's also very easy to customize with a little CSS. And I wouldn't enjoy being moderator here if I didn't enjoy tweaking TTX.
