Hi Laurent, My apologies for the late reply. Have been busy with work.

Thanks for your reply.Regarding your reply,yes true asking users to write config file is easy. but I guess we are again missing the point.

Idea is to come up with some design which allows customization of code and still allows to control basic flow of tasks. Till now the suggestions cover following: 1) vsespb's suggestion, covered use of known customizations. 2) your suggestion, covers control of flow and tasks.

Also I gave it another thought and wondered if providing a template to even an inexperienced user something like following should be kind of easy to understand right? 

<xmlFile>
    <action name="A" execute="true" />
    <action name="B" execute="true" />
</xmlFile>

[download]

I understand its xml file. But normal user simply need to switch true to false to control flow or change order of elements (example: putting B before A) to change flow while experienced user can make use of customization tasks available. The only thing tempting me to use xml is the schema file/validations/child elements/structure offered by it which can help me mix complex and simple tasks at the same place.

Anyway will wait a bit more for inputs before I go with any implementation.

In reply to Re^4: handling tasks and customizing flow of tasks using perl by asham
in thread handling tasks and customizing flow of tasks using perl by asham

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


  • 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! —
  • 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:
    & &amp;
    < &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.