Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Thank you so much - that is exactly what I am looking for.

I do need it ordered because I'm creating a Perl Tk UI that will read this setup file, allow users to modify it and write it back out...basically, creating a Suite installer outside of InstallShield. I'm thinking of using a NoteBook where the first tab will have a list of Products and Features with CheckBoxes. The other tabs will have the "Property = Value" info in a label Textbox fashion so they can change the values and write out a new setup.ini.

I will also have another script that can be run from the UI and cmdline for users without UI capabilities, that will just read the setup.ini, build the commands to run each install silently and run them...where obviously, order does not matter.

Still have to figure that one out - when running outside the UI, how do I determine what to install. I May have to add a Product="y|n", Feature="y|n" to the setup.ini file.

Thanks a bunch - I knew to use Arrays of Hashes but couldn't conceptualize it visually.

Boy do I have a lot to learn - who'd thunk to use an || in a Hash Key. Great stuff.

If anyone has a better solution...by all means, let me know.


In reply to Re^4: Reading Install type config file into hash by tmurnane
in thread Reading Install type config file into hash by tmurnane

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others wandering the Monastery: (2)
As of 2024-04-19 01:09 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found