Hi,
What about a schema like this.
if a user wanted to export
1) only the XML: -xml {path}
2) only the HTML with default XSL: -html {path} **here we might
generate a XML and delete it after the execution.
**XSL should be in the directory where the tool invoked from.
3) XML and HTML with default XSL: -xml {path} -html {path} **XSL
should be in the directory where the tool invoked from.
4) only the HTML with user specified XSL: -xsl {path} -html {path}
**here we might generate a XML and delete it after the execution.
5) XML and HTML with user specified XSL: -xml {path} -xsl {path} -html {path}
Suggestions are highly appreciated.
Thanks.
On Fri, Jul 16, 2010 at 8:09 PM, Nirmal Fernando <[email protected]> wrote:
> Hi Bryan,
> Please see my comments in line.
>
>> I wonder if perhaps the PlanExporter could make some of these
>> behaviors conditional?
>>
>> Some users might want to export only the XML, some might want
>> to export only the HTML. Some might want to export both. Some
>> might want to export the HTML, but might want to use a different
>> XSL stylesheet than the one included with PlanExporter. etc.
>>
> Yeah, these behaviors can be achieved, but perhaps it's a good
> idea to generate/export the XML in each behavior, since we need it
> to achieve all those behaviors.
>
>> Do you think it would be helpful to have command-line arguments
>> that let the user indicate what particular combination of outputs
>> is desired?
>
> Yeah, that would be really helpful.
> I think we should come to a conclusion (at least for now) on
> what behaviors we should allow and what command line arguments
> to be used for each behavior.
>
> Thanks.
> --
> Best Regards,
> Nirmal
>
> C.S.Nirmal J. Fernando
> Department of Computer Science & Engineering,
> Faculty of Engineering,
> University of Moratuwa,
> Sri Lanka.
>
--
Best Regards,
Nirmal
C.S.Nirmal J. Fernando
Department of Computer Science & Engineering,
Faculty of Engineering,
University of Moratuwa,
Sri Lanka.
