I second the use of Wx::SingleChoiceDialog or
Wx::MultiChoiceDialog like jmlynesjr sugested.
Parsing XML like you do is not a good choice, use a dedicated module, something like this:
use strict;
use warnings;
use XML::Simple;
use Data::Printer;
my $data = do { local $/; <DATA> }; # slurp DATA
my $ref = XMLin(
$data,
#KeyAttr => { Question => 'questionId' }, # unordered data
ForceArray => ['item'],
ContentKey => '-content'
);
p $ref;
__DATA__
<Questions>
<Question>
<questionId>TNHSCS010001</questionId>
<question>Jenkins is primiary used of ...</question>
<Answers correct="no">Nightly Builds</Answers>
<Answers correct="yes">CI Builds</Answers>
<Answers correct="no">Report Generation</Answers>
<Answers correct="no">All the above</Answers>
</Question>
<Question>
<questionId>TNHSCS010002</questionId>
<question>CI builds are setup to ...</question>
<Answers correct="yes">Catch potentail build errors</Answers>
<Answers correct="no">Find bugs</Answers>
<Answers correct="no">Reduce build time</Answers>
<Answers correct="no">None of the above</Answers>
</Question>
</Questions>
Notice that a valid XML must have a root tag. I also changed a little the structure...
Regards, Stefan
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|