Phil Ehrens wrote: > Perl and Python are NOT platform independent at the same level. > Have you coded in Perl, Python, and Tcl for Windows, OSX, Linux, > and Solaris? I have. You will spend at LEAST three times as much > time doing this with Perl or Python as you would with Tcl/Tk.
I do this since 12 years with Perl on Solaris, Irix, Linux and Windows. Never did it with Tcl/Tk, because I'am happy how good it works with Perl ;) > It should have no priority at all, but I thought that Transcode > supported Windows. My bad. You really thought transcode supports Windows? I am stunned. > I'm not kidding. I have no idea why you find this so unbelievable. Because _Internet technology_ for video editing / transcoding purposes is just not the best technology you can choose (of course anything is _possible_ ...). I did many HTML/JavaScript/Ajax coding in my life and I never would try to cover a video editing solution with that technology. It's simply not appropriate for that and bloats things up tremendously (if it's not just a simple HTML form, which just generates one simple command line and just spits out transcode's output... but I think that's not the idea of an "offical GUI" we're originally talking about here...). > All the gui needs to be able to do is take user input, build > command lines, and hook output from Transcode, right? That would be the minimum. More than that for example would be realtime previewing which needs some more effort than "just" wrapping command lines. As well it sounds very easy: user input -> build cmdline -> grab transcode output. Building an intuitive GUI which supports the user in his _goals_ (not just enumerating command line options), is much more difficult. This challenge is of course mostly independent from the toolkit used. Regards, Jörn -- Think before you code. And while you're coding it won't hurt either. ;)
pgpBFBM1Usvw9.pgp
Description: PGP signature
