So how about this as the public interface:
package org.apache.fop.apps;
public class AwtManager
{
public AwtManager(InputSource fo)
public AwtManager(InputSource xsl. InputSource xml)
//these are separated so the work of showing the preview can go on a
background thread
public Component getPreviewPanel()
public Component showPreview()
//possible also to set the saved file type in the save method
public void save(Component fileChooserParent)
public void save(File f)
public Action getSaveAction()
public void print()
public Action getPrintAction()
public void zoom(String zoomFactor)
public JCombo getZoomCombo()
public void goToPage(int n)
...etc...
//a short hand for lazy people
public JToolBar getToolbar()
}
Any committer wants to tell me where it'll go in the tree, I'll get onto it
tomorrow: I've done most of it.
Alistair
-----Original Message-----
From: Jim Urban [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2002 2:29 PM
To: [EMAIL PROTECTED]
Subject: RE: AWT Window
While were suggesting enhancements for the AWT window, here is a change I
made to the code Ivan Latysh sent me last week. I needed to process XML:FO
which is dynamically generated and not .xml and .xsl files. So I modified
the run method to take an InputSource object (containing XML:FO) instead of
two File objects. I would like to see this option added if possible. It
makes using the AWT window much easier when the report to be viewed is build
from data retrieved from a database by a server and sent to a client
application or applet for viewing. It also works well with Java Web Start,
where the placing of .xml and .xsl files on the workstation is a hassle due
to the JWS security sandbox.
Thanks,
Jim
> -----Original Message-----
> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 21, 2002 8:07 AM
> To: [EMAIL PROTECTED]
> Subject: Re: AWT Window
>
>
>
> ----- Original Message -----
> From: "IvanLatysh" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, February 21, 2002 2:53 PM
> Subject: AWT Window
>
>
> > Hello, Alistair!
> > You wrote to <[EMAIL PROTECTED]> on Thu, 21 Feb 2002
> 09:26:32 -0000:
> >
> > AH> Now that a few more people are interested in this:
> >
> > AH> I think that it would be more useful if the basic AWT API
> returned a
> > AH> JPanel rather than a JFrame.
> ...
> > From my practice the best way to make this flexible is just give JPanel
> without any controls.
> > Just a report. And implement into this "pane" methods to switch pages,
> zoom, import ....
> > And, If I need preview window I will do preview by myself with
> my buttons
> and my style.
> > I think this is right way to do it.
>
> Better still... give the JPanel like you propose and Actions that (if
> needed) can be easily put in a toolbar.
>
> --
> Nicola Ken Barozzi [EMAIL PROTECTED]
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
