tkperl vs. tk for GUI to perl script 
Author Message
 tkperl vs. tk for GUI to perl script

I need to write a GUI for an interactive perl script that already exists,
but haven't decided what would be the best choice for this task:

a) write a separate wish script that opens a pipe to the perl script
b) write a separate tkperl script that opens a pipe to the perl script
c) modify the existing perl script, adding tkperl commands

What should I consider in making my choice?  Currently, I'm not that familiar
with tkperl, but would learn it if it is the better choice.

Thanks,

--Dale



Mon, 03 Feb 1997 08:36:06 GMT  
 tkperl vs. tk for GUI to perl script

Dale> I need to write a GUI for an interactive perl script that
Dale> already exists, but haven't decided what would be the best
Dale> choice for this task:

Dale> a) write a separate wish script that opens a pipe to the perl script
Dale> b) write a separate tkperl script that opens a pipe to the perl script
Dale> c) modify the existing perl script, adding tkperl commands

Dale> What should I consider in making my choice?  Currently, I'm not
Dale> that familiar with tkperl, but would learn it if it is the
Dale> better choice.

There are a couple of other questions you need to ask as well before
you decide.

1. is your existing script a "production" script that _has_ to run?
2. to use tkperl5, you need to use perl5 which isn't in Beta test yet,
   and tkperl which is still in Alpha testing.  This means things can
   and probably will change in both.  Is this ok?

For me, if it's a production script, I'd leave it in perl4 for now and
just write a wish script that pipes data back and forth.  In the near
future, I plan on moving over to perl5 exclusivley and use tkperl as
well.   It's just too nice to be able to write X apps in perl.

For you, I'd stick with plan a right now, but possibly start playing
with perl5 and tkperl in your spare time to familiarize yourself with
them.  Then when the time comes, you can ask the same questions again
and have a better idea of your options.

John


 Workstation Specialist - Worcester Polytechnic Institute College Computer Ctr.
                        Kill your television



Mon, 03 Feb 1997 12:03:48 GMT  
 tkperl vs. tk for GUI to perl script
ames/board/44357 <3 comp.lang.perl:31561 comp.lang.tcl:17688

: I need to write a GUI for an interactive perl script that already exists,
: but haven't decided what would be the best choice for this task:
:
: a) write a separate wish script that opens a pipe to the perl script
: b) write a separate tkperl script that opens a pipe to the perl script
: c) modify the existing perl script, adding tkperl commands
:
: What should I consider in making my choice?  Currently, I'm not that familiar
: with tkperl, but would learn it if it is the better choice.

It really depends on what you're optimizing for.  a and b are more modular,
b and c are less bilingual, and c is more efficient.  Plenty of room for
tastes to be disputandum.

And you left out option d, whatever it is.

Larry



Mon, 03 Feb 1997 23:39:26 GMT  
 tkperl vs. tk for GUI to perl script

Quote:
>ames/board/44357 <3 comp.lang.perl:31561 comp.lang.tcl:17688

>: I need to write a GUI for an interactive perl script that already exists,
>: but haven't decided what would be the best choice for this task:
>:
>: a) write a separate wish script that opens a pipe to the perl script
>: b) write a separate tkperl script that opens a pipe to the perl script
>: c) modify the existing perl script, adding tkperl commands
>:
>: What should I consider in making my choice?  Currently, I'm not that familiar
>: with tkperl, but would learn it if it is the better choice.
>It really depends on what you're optimizing for.  a and b are more modular,
>b and c are less bilingual, and c is more efficient.  Plenty of room for
>tastes to be disputandum.
>And you left out option d, whatever it is.

Option d would have to be "Wafe", wouldn't it? Wafe was designed
explicitly to allow non-Tk applications in any language (esp. Perl) to
talk to a GUI front-end via pipes that Wafe sets up. Ok, so the GUI is
not Tk, but tcl+Athena or tcl+Motif.

You also missed out option e: "expect", which takes an existing
interactive application and puts a GUI (Tk) front-end to it.

                        Jan
--
  Jan Newmarch, Information Science and Engineering,
  University of Canberra, PO Box 1, Belconnen, Act 2616
  Australia. Tel: (Aust) 6-2012422. Fax: (Aust) 6-2015041



Fri, 14 Feb 1997 08:10:45 GMT  
 tkperl vs. tk for GUI to perl script
Quote:



>>: I need to write a GUI for an interactive perl script that already exists,
>>: but haven't decided what would be the best choice for this task:
>>:
>>: a) write a separate wish script that opens a pipe to the perl script
>>: b) write a separate tkperl script that opens a pipe to the perl script
>>: c) modify the existing perl script, adding tkperl commands
...
>Option d would have to be "Wafe", wouldn't it? Wafe was designed
...
>You also missed out option e: "expect", which takes an existing

...

Option f) the CGI/HTML+ forms interface.
    Admittedly a limited user interface, but if you are already running
    WWW at your site, it instantly ports your application to most computer
    systems with only one source code / server to maintain.

--Maurice



Sat, 15 Feb 1997 09:54:15 GMT  
 
 [ 5 post ] 

 Relevant Pages 

1. what Tk Tk/perl Tkperl perl/Tk?

2. Win32::GUI vs TK

3. Where is perl debugger GUI (tkperl)??

4. Tcl::Tk and Tcl modules are available to provide Tk GUI to perl

5. tkperl or guiperl - creating binary distribution of tk script

6. Interactive GUI builder for Tkperl?

7. GUI builder for TkPerl

8. Gui Builder for TkPerl

9. price of perl (was Re: GUI vs command line)

10. opinions on tcl/tk vs perl/tk

11. perl/tk vs.tcl/tk

12. Perl/Tk vs. Tcl/Tk

 

 
Powered by phpBB® Forum Software