Andu wrote: > > I have an even better one; after having convinced people to go with > Metacard for various reasons the next question that needs to be answered > (and a good one too) is what happens if you, the Metacard programmer, > get hit by a car tomorrow (knock on wood), is there a viable replacement > in sight? > >> >> And debugging is a pain in the butt. :) > > Yes, we should get at least a line/word number in an error message but > since the number of Metacard/CGI users is 4 so far, I don't expect we > can dare ask for features.
Good points. MetaTalk is soooo much easier to learn than Perl, so it's unfortunate that more folks aren't into it. I've been in love with Darwin mc since I ran the first echo.mt test. As far as the debugger is concerned, I usually end up copying my whole script and pasting it into a button script in MetaCard for OS X, and then hitting the enter key and seeing where I've made a syntax error. Crude, but helpful. Darwin mc is the coolest thing I've used in a long, long time. Between OS X Server and Darwin mc, I've got the ability to schedule and automate just about anything I want on our network. The more work the computer does, the better. :) Richard MacLemale Instructional Technology Specialist James W. Mitchell High School http://mitchellonline.pasco.k12.fl.us _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
