In an attempt to make this comment worthy of its own node, I'd like to pose the general question to all monks, whether they have any keen ideas how to let users interact with perl by using systems they're already familiar with. I guess the challenge is making it error-proof, because it's easy to ask someone to submit a tab-separated list, but harder to make sure he or she puts all the necessary tabs and no unnecessary tabs. Forcing users to use OUR choice of interface is great because it makes it error-proof, but it's not so nice for the user.
 
It was very much with this idea in mind that I wrote this code. I played with a few data storage methods for this web site - I decided that MySQL was more than what was needed by this client, DBM didn't really allow for easy update without yet-another-interface, CSV wasn't flexible enough (or more too that I don't really like using DBD::CSV) and while XML provided portability and easy updating, Excel seemed to be an easier option for the client.
 
This data storage method in combination with a web-upload facility, I believe, will allow my client to readily update their web site with minimal fuss and without having to come back to me, as their web developer, to consistently update their site. Autonomy equates to empowerment and in a world where increasingly users are playing 'catch-up' in the IT sector, empowerment can translate (I hope) to higher levels of satisfaction.
 

 
Ooohhh, Rob no beer function well without!

---

---

• 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.