You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Jim Urban <ji...@netsteps.net> on 2002/02/19 18:52:03 UTC
FOP AWT Window Shuts Down Application
I am using the FOP AWT viewer (PreviewDialog) to display and print reports
within my application. The problem is, whenever I close the FOP viewer, my
application shuts down. How can I keep this from happening?
Thanks,
Jim Urban
Product Manager
Netsteps Inc.
Suite 505E
1 Pierce Pl.
Itasca, IL 60143
Voice: (630) 250-3045 x2164
Fax: (630) 250-3046
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: SSH'ing
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
Hi, Keiron
I definitely expected the second approach to work. If I can SSH into A
(cvs.apache.org, or icarus), and I can SSH into B (xml.apache.org, among
others, or daedalus), and I can scp to both, then I ought to be able to scp
between A and B from my machine. But it aborted every time I tried it.
My problem with the first approach is that SSH uses passwords also, but as a
convenience I have the password set to nothing so I don't have to enter it
every time. What happened was icarus asked me for a password and I had none
to give. So that failed.
Further investigation is required. :-)
Arved
-----Original Message-----
From: Keiron Liddle [mailto:keiron@aftexsw.com]
Sent: February 22, 2002 4:23 AM
To: fop-dev@xml.apache.org
Subject: SSH'ing
Hi Arved,
I ssh'ed into A (thats cvs.apache.org right?) and did an scp to B. As I
use password access only then I had to enter a password. It sounds like
you are using key access, in which case wouldn't you need you key for B
setup in A?
From you machine you should still be able to do
scp a:/home/... b:/www/...
and I think it will use the keys from you machine which are apparently
working.
On 2002.02.21 23:52 Arved Sandstrom wrote:
> Thank you. Just out of curiosity, what did you do that worked? Because if
> we
> call 'icarus' A and 'daedalus' B, I SSH'd into both A and B, and then
> from
> the session on B I attempted to scp from A (where the distros were) to B.
> That failed because scp asked for a password. I also tried doing the scp
> with both A and B being remote specifications; every time I tried that it
> hung for 30 or 60 seconds and then aborted without any explanation.
>
> I can SSH into both, and scp to both; it's the scp between the two that
> is
> the problem.
>
> But now that I think about it I could have done 4 transfers...
>
> Arved
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
SSH'ing
Posted by Keiron Liddle <ke...@aftexsw.com>.
Hi Arved,
I ssh'ed into A (thats cvs.apache.org right?) and did an scp to B. As I
use password access only then I had to enter a password. It sounds like
you are using key access, in which case wouldn't you need you key for B
setup in A?
From you machine you should still be able to do
scp a:/home/... b:/www/...
and I think it will use the keys from you machine which are apparently
working.
On 2002.02.21 23:52 Arved Sandstrom wrote:
> Thank you. Just out of curiosity, what did you do that worked? Because if
> we
> call 'icarus' A and 'daedalus' B, I SSH'd into both A and B, and then
> from
> the session on B I attempted to scp from A (where the distros were) to B.
> That failed because scp asked for a password. I also tried doing the scp
> with both A and B being remote specifications; every time I tried that it
> hung for 30 or 60 seconds and then aborted without any explanation.
>
> I can SSH into both, and scp to both; it's the scp between the two that
> is
> the problem.
>
> But now that I think about it I could have done 4 transfers...
>
> Arved
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: FOP AWT Window Shuts Down Application
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
Thank you. Just out of curiosity, what did you do that worked? Because if we
call 'icarus' A and 'daedalus' B, I SSH'd into both A and B, and then from
the session on B I attempted to scp from A (where the distros were) to B.
That failed because scp asked for a password. I also tried doing the scp
with both A and B being remote specifications; every time I tried that it
hung for 30 or 60 seconds and then aborted without any explanation.
I can SSH into both, and scp to both; it's the scp between the two that is
the problem.
But now that I think about it I could have done 4 transfers...
Arved
-----Original Message-----
From: Keiron Liddle [mailto:keiron@aftexsw.com]
Sent: February 21, 2002 5:51 AM
To: fop-dev@xml.apache.org
Subject: Re: FOP AWT Window Shuts Down Application
I have put the files across. So they are now publicly available.
On 2002.02.21 00:10 Arved Sandstrom wrote:
> Or now that Arved tried and could not (SSH permissions problems, even
> though
> I can ssh and scp to both icarus and daedalus), we are going to have to
> get
> Christian properly set up on both machines.
>
> Someone else (a committer) want to give it a shot? It might just be some
> kind of configuration thing for me. Right now the FOP distros are on
> icarus
> under /x1/home/chrisg. They need to go to daedalus.
>
> Arved
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: FOP AWT Window Shuts Down Application
Posted by Keiron Liddle <ke...@aftexsw.com>.
I have put the files across. So they are now publicly available.
On 2002.02.21 00:10 Arved Sandstrom wrote:
> Or now that Arved tried and could not (SSH permissions problems, even
> though
> I can ssh and scp to both icarus and daedalus), we are going to have to
> get
> Christian properly set up on both machines.
>
> Someone else (a committer) want to give it a shot? It might just be some
> kind of configuration thing for me. Right now the FOP distros are on
> icarus
> under /x1/home/chrisg. They need to go to daedalus.
>
> Arved
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: FOP AWT Window Shuts Down Application
Posted by "Peter B. West" <pb...@powerup.com.au>.
Christian Geisert wrote:
>
> Ok, I'll do it .. but it's to late for 0.20.3rc2 (which is already
> on icarus, waiting for Arved to move it to daedalus)
>
Oops! I hope icarus is not on Solaris. It will go down any time now.
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: AWT Window
Posted by IvanLatysh <iv...@yourmail.com>.
Hello, Nicola!
You wrote to <fo...@xml.apache.org> on Thu, 21 Feb 2002 15:06:44 +0100:
NKB> Better still... give the JPanel like you propose and Actions that
NKB> (if needed) can be easily put in a toolbar.
Yes, exactly.
It better because most of developers use their fill and look.
They use custom buttons and other stuff.
And one more about I concern it is size of FOP.
All my application with all drivers and everything what I need :
(ivLib.jar, library.jar, manager.jar, mm.mysql-2.0.4-bin.jar) = 861,347 bytes
And FOP:
(avalon-framework-4.0.jar, batik.jar, fop.jar, jimi-1.0.jar, logkit-1.0b4.jar,
xalan-2.2.D14.jar, xerces-1.4.4.jar) = 7,245,957 bytes
At least you should repack all libraryes and take only classes which you actually need.
Because from this point it hard to use application thru JavaWebStart.
---
Yours sincerely, Ivan Latysh.
Ivan@yourmail.com
http://ivan.yourmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: AWT Window
Posted by IvanLatysh <iv...@yourmail.com>.
Hello, Jim!
You wrote to <fo...@xml.apache.org> "Nicola Ken Barozzi" <ba...@nicolaken.com> on Thu, 21
Feb 2002 08:19:22 -0600:
JU> Sounds good to me. Just one thing, get rid of that System.exit() in
JU> the dispose method! Let the implementer decide what to do when the
JU> window containing the panel is closed.
You know.
I did mail to FOP community a long, long time ago.
And no one bother about this.
Here is my message from December 12, 2001 11:46 AM
>Hi All.
>I am playing around to get my application run.
>And I have met some funny piece of code.
>Like this:
>package org.apache.fop.viewer;
>...
>public class PreviewDialog extends JFrame implements ProgressListener,
> MessageListener {
>...
>And when I get look at method dispose I was surprised:
> public void dispose() {
> System.exit(0);
> }
>It's really cool - 100% of free resources :-)
---
Yours sincerely, Ivan Latysh.
Ivan@yourmail.com
http://ivan.yourmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: AWT Window
Posted by Jim Urban <ji...@netsteps.net>.
Sounds good to me. Just one thing, get rid of that System.exit() in the
dispose method! Let the implementer decide what to do when the window
containing the panel is closed.
Jim
> -----Original Message-----
> From: Nicola Ken Barozzi [mailto:barozzi@nicolaken.com]
> Sent: Thursday, February 21, 2002 8:07 AM
> To: fop-dev@xml.apache.org
> Subject: Re: AWT Window
>
>
>
> ----- Original Message -----
> From: "IvanLatysh" <iv...@yourmail.com>
> To: <fo...@xml.apache.org>
> Sent: Thursday, February 21, 2002 2:53 PM
> Subject: AWT Window
>
>
> > Hello, Alistair!
> > You wrote to <fo...@xml.apache.org> 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 krysalis.org@nicolaken.com
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> For additional commands, email: fop-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: AWT Window
Posted by IvanLatysh <iv...@yourmail.com>.
Hello, Jim!
You wrote to <fo...@xml.apache.org> on Thu, 21 Feb 2002 08:29:09 -0600:
JU> While were suggesting enhancements for the AWT window, here is a
JU> change I made to the code Ivan Latysh sent me last week. I needed
JU> to process XML:FO which is dynamically generated and not .xml and
JU> .xsl files. So I modified the run method to take an InputSource
JU> object (containing XML:FO) instead of two File objects. I would
JU> like to see this option added if possible. It makes using the AWT
JU> window much easier when the report to be viewed is build from data
JU> retrieved from a database by a server and sent to a client
JU> application or applet for viewing. It also works well with Java Web
JU> Start, where the placing of .xml and .xsl files on the workstation
JU> is a hassle due to the JWS security sandbox.
I also did tiny class that retrieve data from your database using XML file with your SQL querys
(not only one) .
And return XML file with same structure as supplied SQL.
All this stuff with small demo = 25,181 bytes. And using only SUN JDK.
If you interesting of this - just mail me.
This is targeting for FOP. In case you are working with relational database and you need to
build an report.
---
Yours sincerely, Ivan Latysh.
Ivan@yourmail.com
http://ivan.yourmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: AWT Window
Posted by Alistair Hopkins <al...@berthengron.co.uk>.
The information re CurrentPage, etc., is available from the AWTRenderer: it
may make more sense to expose that for advanced users.
The getToolbar() proposal is a shorthand to call all the getAction, getCombo
methods: if you don't want to use it, you can do it the long way using the
actions
I think the interface should be kept as simple as possible, but allowing
people to dig further into the FOP API if they need to: it's pretty hard
work learning all this stuff if all you want is a nice, clean and simple
print preview functionality in your swing app.
Given that the best VB can do is the dreaded Crystal Reports, and Adobe seem
to be backing off the java Acrobat viewer (jvm 1.1.8 latest!) which makes
iText a fairly poor solution, then there seems to be an opening in the
'market' for Fop here. All my users want everything on paper.
What do C++ developers do for quality custom printing? I have no idea.
Al
-----Original Message-----
From: IvanLatysh [mailto:ivan@yourmail.com]
Sent: Thursday, February 21, 2002 5:02 PM
To: fop-dev@xml.apache.org
Subject: Re: AWT Window
Hello, Alistair!
You wrote to <fo...@xml.apache.org> "Nicola Ken Barozzi"
<ba...@nicolaken.com> on Thu, 21
Feb 2002 15:28:59 -0000:
AH> More?
>> public void print()
>> public Action getPrintAction()
>> public void zoom(String zoomFactor)
>> public JCombo getZoomCombo()
>> public void goToPage(int n)
>> ...etc...
Some stuff like
public int getCurrentPage() // get currently displayed page
public int getPageCount() // get the number of pages
public int getZoom() // get current zoom
To simplify custom preview dialog.
And I think
public JToolBar getToolbar()
Should be removed. Instead of this better to provide in samples simple
preview window.
As example I am do not using JToolBar and why I need it into my imports.
---
Yours sincerely, Ivan Latysh.
Ivan@yourmail.com
http://ivan.yourmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: AWT Window
Posted by IvanLatysh <iv...@yourmail.com>.
Hello, Alistair!
You wrote to <fo...@xml.apache.org> "Nicola Ken Barozzi" <ba...@nicolaken.com> on Thu, 21
Feb 2002 15:28:59 -0000:
AH> More?
>> public void print()
>> public Action getPrintAction()
>> public void zoom(String zoomFactor)
>> public JCombo getZoomCombo()
>> public void goToPage(int n)
>> ...etc...
Some stuff like
public int getCurrentPage() // get currently displayed page
public int getPageCount() // get the number of pages
public int getZoom() // get current zoom
To simplify custom preview dialog.
And I think
public JToolBar getToolbar()
Should be removed. Instead of this better to provide in samples simple preview window.
As example I am do not using JToolBar and why I need it into my imports.
---
Yours sincerely, Ivan Latysh.
Ivan@yourmail.com
http://ivan.yourmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: AWT Window
Posted by Alistair Hopkins <al...@berthengron.co.uk>.
Action[] getActions +1
save(OutputStream) +1
but I like some internal (protected?) means whereby the implementer has to
do no explicit coding atall to get preview/print/save functionality: hence
the getSaveAction Action which brings up a JFileChooser: but as the API also
allows itself to be used for direct printing without previewing, I can't
assume that the preview panel is up so I need to ask for a JFileChooser
parent component to enable it to be sensible & modal.
More?
-----Original Message-----
From: Nicola Ken Barozzi [mailto:barozzi@nicolaken.com]
Sent: Thursday, February 21, 2002 3:11 PM
To: fop-dev@xml.apache.org
Subject: Re: AWT Window
From: "Alistair Hopkins" <al...@berthengron.co.uk>
> 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)
-0
> public void save(File f)
+-0
> public Action getSaveAction()
save(OutputStream out)
> 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()
> }
Action[] getActions()
--
Nicola Ken Barozzi krysalis.org@nicolaken.com
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: AWT Window
Posted by Nicola Ken Barozzi <ba...@nicolaken.com>.
From: "Alistair Hopkins" <al...@berthengron.co.uk>
> 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)
-0
> public void save(File f)
+-0
> public Action getSaveAction()
save(OutputStream out)
> 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()
> }
Action[] getActions()
--
Nicola Ken Barozzi krysalis.org@nicolaken.com
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: AWT Window
Posted by Jim Urban <ji...@netsteps.net>.
I like it! For what its worth, you have my vote.
Jim
> -----Original Message-----
> From: Alistair Hopkins [mailto:alistair@berthengron.co.uk]
> Sent: Thursday, February 21, 2002 8:59 AM
> To: fop-dev@xml.apache.org
> Subject: RE: AWT Window
>
>
> 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:jim.urban@netsteps.net]
> Sent: Thursday, February 21, 2002 2:29 PM
> To: fop-dev@xml.apache.org
> 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:barozzi@nicolaken.com]
> > Sent: Thursday, February 21, 2002 8:07 AM
> > To: fop-dev@xml.apache.org
> > Subject: Re: AWT Window
> >
> >
> >
> > ----- Original Message -----
> > From: "IvanLatysh" <iv...@yourmail.com>
> > To: <fo...@xml.apache.org>
> > Sent: Thursday, February 21, 2002 2:53 PM
> > Subject: AWT Window
> >
> >
> > > Hello, Alistair!
> > > You wrote to <fo...@xml.apache.org> 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 krysalis.org@nicolaken.com
> > - verba volant, scripta manent -
> > (discussions get forgotten, just code remains)
> > ---------------------------------------------------------------------
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> > For additional commands, email: fop-dev-help@xml.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> For additional commands, email: fop-dev-help@xml.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> For additional commands, email: fop-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: AWT Window
Posted by Alistair Hopkins <al...@berthengron.co.uk>.
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:jim.urban@netsteps.net]
Sent: Thursday, February 21, 2002 2:29 PM
To: fop-dev@xml.apache.org
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:barozzi@nicolaken.com]
> Sent: Thursday, February 21, 2002 8:07 AM
> To: fop-dev@xml.apache.org
> Subject: Re: AWT Window
>
>
>
> ----- Original Message -----
> From: "IvanLatysh" <iv...@yourmail.com>
> To: <fo...@xml.apache.org>
> Sent: Thursday, February 21, 2002 2:53 PM
> Subject: AWT Window
>
>
> > Hello, Alistair!
> > You wrote to <fo...@xml.apache.org> 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 krysalis.org@nicolaken.com
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> For additional commands, email: fop-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: AWT Window
Posted by Jim Urban <ji...@netsteps.net>.
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:barozzi@nicolaken.com]
> Sent: Thursday, February 21, 2002 8:07 AM
> To: fop-dev@xml.apache.org
> Subject: Re: AWT Window
>
>
>
> ----- Original Message -----
> From: "IvanLatysh" <iv...@yourmail.com>
> To: <fo...@xml.apache.org>
> Sent: Thursday, February 21, 2002 2:53 PM
> Subject: AWT Window
>
>
> > Hello, Alistair!
> > You wrote to <fo...@xml.apache.org> 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 krysalis.org@nicolaken.com
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> For additional commands, email: fop-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: AWT Window
Posted by Nicola Ken Barozzi <ba...@nicolaken.com>.
----- Original Message -----
From: "IvanLatysh" <iv...@yourmail.com>
To: <fo...@xml.apache.org>
Sent: Thursday, February 21, 2002 2:53 PM
Subject: AWT Window
> Hello, Alistair!
> You wrote to <fo...@xml.apache.org> 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 krysalis.org@nicolaken.com
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
AWT Window
Posted by IvanLatysh <iv...@yourmail.com>.
Hello, Alistair!
You wrote to <fo...@xml.apache.org> 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. I want to use it in a JInternalFrame
AH> rather than a
AH> JFrame to mimic standard Windoze print preview behaviour. Somebody
AH> else wants to use an applet. It's also nice to be able to offer a
AH> .save(File f)
AH> option from the API/viewer so that viewers can save the report as
AH> well as view and print it.
>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.
---
Yours sincerely, Ivan Latysh.
Ivan@yourmail.com
http://ivan.yourmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: FOP AWT Window Shuts Down Application
Posted by Henrik Holle <he...@megatel.de>.
After closing this Preview-Panel the memory is not released.
I can`t found any references on object and don`t know why the GC doesn`t
collect
The objects?
I need some help, previewing of large documents consume about 20mb
memory, and after 2 or 3
Previews i get a OutOfMemoryException.
-----Ursprüngliche Nachricht-----
Von: Alistair Hopkins [mailto:alistair@berthengron.co.uk]
Gesendet: Donnerstag, 21. Februar 2002 10:27
An: fop-dev@xml.apache.org
Betreff: RE: FOP AWT Window Shuts Down Application
Now that a few more people are interested in this:
I think that it would be more useful if the basic AWT API returned a
JPanel rather than a JFrame. I want to use it in a JInternalFrame
rather than a JFrame to mimic standard Windoze print preview behaviour.
Somebody else wants to use an applet. It's also nice to be able to
offer a .save(File f) option from the API/viewer so that viewers can
save the report as well as view and print it.
The AWTStarter class can then extremely simply be modified to use this
API.
If any committer is interested, I'll clean up the attached further and
return it to them for inclusion. Running it in parallel with FOP is
proving to be a bit boring and I'd be delighted to see it rolled back
in.
Hope this helps,
Alistair
-----Original Message-----
From: Arved Sandstrom [mailto:Arved_37@chebucto.ns.ca]
Sent: Wednesday, February 20, 2002 11:10 PM
To: fop-dev@xml.apache.org
Subject: RE: FOP AWT Window Shuts Down Application
-----Original Message-----
From: Christian Geisert [mailto:christian.geisert@isu-gmbh.de]
Sent: February 20, 2002 1:28 PM
To: fop-dev@xml.apache.org
Subject: Re: FOP AWT Window Shuts Down Application
Keiron Liddle wrote:
>
> If it makes you feel better it has already been done.
> http://marc.theaimsgroup.com/?l=fop-cvs&m=101420095016596&w=2
>
> Someone might even commit this to the maintanence branch.
Ok, I'll do it .. but it's to late for 0.20.3rc2 (which is already on
icarus, waiting for Arved to move it to daedalus)
Christian
******************************
Or now that Arved tried and could not (SSH permissions problems, even
though I can ssh and scp to both icarus and daedalus), we are going to
have to get Christian properly set up on both machines.
Someone else (a committer) want to give it a shot? It might just be some
kind of configuration thing for me. Right now the FOP distros are on
icarus under /x1/home/chrisg. They need to go to daedalus.
Arved
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: FOP AWT Window Shuts Down Application
Posted by Alistair Hopkins <al...@berthengron.co.uk>.
Now that a few more people are interested in this:
I think that it would be more useful if the basic AWT API returned a JPanel
rather than a JFrame. I want to use it in a JInternalFrame rather than a
JFrame to mimic standard Windoze print preview behaviour. Somebody else
wants to use an applet. It's also nice to be able to offer a .save(File f)
option from the API/viewer so that viewers can save the report as well as
view and print it.
The AWTStarter class can then extremely simply be modified to use this API.
If any committer is interested, I'll clean up the attached further and
return it to them for inclusion. Running it in parallel with FOP is proving
to be a bit boring and I'd be delighted to see it rolled back in.
Hope this helps,
Alistair
-----Original Message-----
From: Arved Sandstrom [mailto:Arved_37@chebucto.ns.ca]
Sent: Wednesday, February 20, 2002 11:10 PM
To: fop-dev@xml.apache.org
Subject: RE: FOP AWT Window Shuts Down Application
-----Original Message-----
From: Christian Geisert [mailto:christian.geisert@isu-gmbh.de]
Sent: February 20, 2002 1:28 PM
To: fop-dev@xml.apache.org
Subject: Re: FOP AWT Window Shuts Down Application
Keiron Liddle wrote:
>
> If it makes you feel better it has already been done.
> http://marc.theaimsgroup.com/?l=fop-cvs&m=101420095016596&w=2
>
> Someone might even commit this to the maintanence branch.
Ok, I'll do it .. but it's to late for 0.20.3rc2 (which is already
on icarus, waiting for Arved to move it to daedalus)
Christian
******************************
Or now that Arved tried and could not (SSH permissions problems, even though
I can ssh and scp to both icarus and daedalus), we are going to have to get
Christian properly set up on both machines.
Someone else (a committer) want to give it a shot? It might just be some
kind of configuration thing for me. Right now the FOP distros are on icarus
under /x1/home/chrisg. They need to go to daedalus.
Arved
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: FOP AWT Window Shuts Down Application
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
-----Original Message-----
From: Christian Geisert [mailto:christian.geisert@isu-gmbh.de]
Sent: February 20, 2002 1:28 PM
To: fop-dev@xml.apache.org
Subject: Re: FOP AWT Window Shuts Down Application
Keiron Liddle wrote:
>
> If it makes you feel better it has already been done.
> http://marc.theaimsgroup.com/?l=fop-cvs&m=101420095016596&w=2
>
> Someone might even commit this to the maintanence branch.
Ok, I'll do it .. but it's to late for 0.20.3rc2 (which is already
on icarus, waiting for Arved to move it to daedalus)
Christian
******************************
Or now that Arved tried and could not (SSH permissions problems, even though
I can ssh and scp to both icarus and daedalus), we are going to have to get
Christian properly set up on both machines.
Someone else (a committer) want to give it a shot? It might just be some
kind of configuration thing for me. Right now the FOP distros are on icarus
under /x1/home/chrisg. They need to go to daedalus.
Arved
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: FOP AWT Window Shuts Down Application
Posted by Christian Geisert <ch...@isu-gmbh.de>.
Keiron Liddle wrote:
>
> If it makes you feel better it has already been done.
> http://marc.theaimsgroup.com/?l=fop-cvs&m=101420095016596&w=2
>
> Someone might even commit this to the maintanence branch.
Ok, I'll do it .. but it's to late for 0.20.3rc2 (which is already
on icarus, waiting for Arved to move it to daedalus)
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: FOP AWT Window Shuts Down Application
Posted by Keiron Liddle <ke...@aftexsw.com>.
If it makes you feel better it has already been done.
http://marc.theaimsgroup.com/?l=fop-cvs&m=101420095016596&w=2
Someone might even commit this to the maintanence branch.
On 2002.02.20 14:22 Jim Urban wrote:
> I thought about that, but then we would have a custom version of FOP.
> This
> would mean that every time we upgrade to a new version of FOP someone
> would
> have to know to go into the source and make this change and rebuild FOP.
> I
> would rather see a more permanent solution implemented such as adding a
> function to PreviewDialog "void setExitOnClose(boolean shouldExit)" which
> would set a flag which would be checked to see if System.exit should be
> called. I would do this, but I am not an authorized FOP developer and do
> not have access to CVS either. If someone would offer to check out
> PreviewDialog.java from CVS and email it to me I will gladly make the
> change
> and email back to them to review and check back in to CVS.
>
> Jim
>
> > -----Original Message-----
> > From: Keiron Liddle [mailto:keiron@aftexsw.com]
> > Sent: Wednesday, February 20, 2002 4:32 AM
> > To: fop-dev@xml.apache.org
> > Subject: Re: FOP AWT Window Shuts Down Application
> >
> >
> >
> > You could comment out the System.exit call in PreviewDialog.java.
> >
> > On 2002.02.19 18:52 Jim Urban wrote:
> > > I am using the FOP AWT viewer (PreviewDialog) to display and print
> > > reports
> > > within my application. The problem is, whenever I close the FOP
> viewer,
> > > my
> > > application shuts down. How can I keep this from happening?
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Escape sequence characters
Posted by Henrik Holle <he...@megatel.de>.
Hi,
Is it possible to put the characters '<' and '>' in my Fo-document?
I does not know how to escape them correctly!
It this possible and how?
Thx
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: FOP AWT Window Shuts Down Application
Posted by Jim Urban <ji...@netsteps.net>.
I thought about that, but then we would have a custom version of FOP. This
would mean that every time we upgrade to a new version of FOP someone would
have to know to go into the source and make this change and rebuild FOP. I
would rather see a more permanent solution implemented such as adding a
function to PreviewDialog "void setExitOnClose(boolean shouldExit)" which
would set a flag which would be checked to see if System.exit should be
called. I would do this, but I am not an authorized FOP developer and do
not have access to CVS either. If someone would offer to check out
PreviewDialog.java from CVS and email it to me I will gladly make the change
and email back to them to review and check back in to CVS.
Jim
> -----Original Message-----
> From: Keiron Liddle [mailto:keiron@aftexsw.com]
> Sent: Wednesday, February 20, 2002 4:32 AM
> To: fop-dev@xml.apache.org
> Subject: Re: FOP AWT Window Shuts Down Application
>
>
>
> You could comment out the System.exit call in PreviewDialog.java.
>
> On 2002.02.19 18:52 Jim Urban wrote:
> > I am using the FOP AWT viewer (PreviewDialog) to display and print
> > reports
> > within my application. The problem is, whenever I close the FOP viewer,
> > my
> > application shuts down. How can I keep this from happening?
> >
> > Thanks,
> >
> > Jim Urban
> > Product Manager
> > Netsteps Inc.
> > Suite 505E
> > 1 Pierce Pl.
> > Itasca, IL 60143
> > Voice: (630) 250-3045 x2164
> > Fax: (630) 250-3046
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> For additional commands, email: fop-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: FOP AWT Window Shuts Down Application
Posted by Keiron Liddle <ke...@aftexsw.com>.
You could comment out the System.exit call in PreviewDialog.java.
On 2002.02.19 18:52 Jim Urban wrote:
> I am using the FOP AWT viewer (PreviewDialog) to display and print
> reports
> within my application. The problem is, whenever I close the FOP viewer,
> my
> application shuts down. How can I keep this from happening?
>
> Thanks,
>
> Jim Urban
> Product Manager
> Netsteps Inc.
> Suite 505E
> 1 Pierce Pl.
> Itasca, IL 60143
> Voice: (630) 250-3045 x2164
> Fax: (630) 250-3046
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org