Whew! Where to begin? It is a kinda neat idea -- specify the layout of of the GUI on the command line; or, really nice: save it in a simple text file. Very appealing. I took out the one bad line that caused the syntax error, and it worked. But as for the implementation...

• The thing is totally unproductive (i.e. no use) if the command line does not include an "OK" somewhere -- you should just put this at the bottom of the window if the user forgets to supply it.
• Why only accept/print a single set of entries and then quit? Allow for a distinction between "Print" and "Exit", in case the user wants to go through a bunch of record entries in a single run (but then you have to worry about making sure the output is parsable -- most likely it will be redirected to a file or downstream process, and you might want something like XML to delimit the records). Maybe include a "Quit" case, too, to allow for skipping the output.
• There appears to be a lot of "cut and paste" style programming here -- you make something work for one case, then just copy it and tweak it for every other case. And you don't notice the things that all these cases have in common, which should be done just once for all cases.
• Did you every think about using an array or a hash to store widget handles and data? You can do that, and it would really help to cut down on the bulk, befuddlement and brittleness of your code. For every "eval ..." you have like these:

         eval "\$answer$count=0;";
         eval "\$textframe$fcount->Checkbutton(...);";
  [download]

  you could have something like the following, which will be much safer, saner, and easier to grasp and maintain:

         $answer[$count] = 0;
         $textframe[$fcount]->Checkbutton(...);
  [download]

  Once you start to organize your widgets and related data as parts of an overall data structure, the code will be a lot more compact and a lot easier to enhance.

I won't spend the time to try to prove this, but I suspect the same functionality could be achieved with about half as much code, or more likely, a third.

update: Forgot to mention -- Please fix your indenting style. Try this command-line, putting the file name of your script as indicated:

perl -MO=Deparse your_script.pl
[download]

Doesn't that seem easier to read than what you posted? It does make a difference. (The output will differ in more than just the spacing, but the main point is to note the overall approach and layout.) Actually having tried it myself just now, it seems you have lots of unnecessary white space within your eval strings -- once you get rid of all those evals, it'll all be nicer in many respects.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.