in reply to Re: Best way to handle interactive user input?
in thread Best way to handle interactive user input?

Hey! Sorry about being so vague. I hope this makes more sense. So I have used XML::Twig to parse the whole file and it took 70 secs for one file. And I have to parse many such files at one go. So instead I thought I could just display the options to parse and parse only that particular section. But like you said, it may be a good idea to display leaf for each menu and then do step 3 and 4.
  • Comment on Re^2: Best way to handle interactive user input?

Replies are listed 'Best First'.
Re^3: Best way to handle interactive user input?
by Discipulus (Canon) on Nov 26, 2015 at 08:30 UTC
    if you have big big files you can enjoy the ability of XML::Twig to parse on the fly using twig_handler if you are smart enough you can build an handler that does everything you need as grab data and display the menu (the twig knows his father and his silbings and his children too). That said i was no able to navigate interactively an XML when i tried to do so. It would be simpler to put all the data in minimal database (SQLite)

    L*
    There are no rules, there are no thumbs..
    Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.