LPEX
3.6.6

com.ibm.lpex.samples
Class HtmlSource

java.lang.Object
  extended by com.ibm.lpex.samples.HtmlSource
All Implemented Interfaces:
LpexCommand

public class HtmlSource
extends Object
implements LpexCommand

Sample windowless use of the LPEX widget / command html - generate HTML listing. This utility generates the HTML listing of a file. See also the saveAsHtml editor command.

Here is the HtmlSource source code (listing created with HtmlSource itself).

To run this sample:

   java com.ibm.lpex.samples.HtmlSource inputFile [outputFile]
The class implements LpexCommand, so it can also be run from the command line:

See Also:
All the samples

Constructor Summary
HtmlSource()
           
 
Method Summary
 boolean doCommand(LpexView lpexView, String parameters)
          Entry point when running this utility as an editor command.
static void main(String[] args)
          Entry point when running this utility from the system prompt.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

HtmlSource

public HtmlSource()
Method Detail

main

public static void main(String[] args)
Entry point when running this utility from the system prompt.

Parameters:
args - the input, and optionally output, file names

doCommand

public boolean doCommand(LpexView lpexView,
                         String parameters)
Entry point when running this utility as an editor command.

Specified by:
doCommand in interface LpexCommand
Parameters:
lpexView - the document view in which the command was issued
parameters - the input, and optionally output, file names

LPEX
3.6.6

Copyright © 2012 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.