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:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 11:10 PM To: [EMAIL PROTECTED] Subject: RE: FOP AWT Window Shuts Down Application -Original Message- From: Christian Geisert [mailto:[EMAIL PROTECTED]] Sent: February 20, 2002 1:28 PM To: [EMAIL PROTECTED] 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-cvsm=101420095016596w=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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] org.zip Description: Zip compressed data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP AWT Window Shuts Down Application
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:[EMAIL PROTECTED]] Gesendet: Donnerstag, 21. Februar 2002 10:27 An: [EMAIL PROTECTED] 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:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 11:10 PM To: [EMAIL PROTECTED] Subject: RE: FOP AWT Window Shuts Down Application -Original Message- From: Christian Geisert [mailto:[EMAIL PROTECTED]] Sent: February 20, 2002 1:28 PM To: [EMAIL PROTECTED] 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-cvsm=101420095016596w=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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP AWT Window Shuts Down Application
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:[EMAIL PROTECTED]] Sent: February 21, 2002 5:51 AM To: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP AWT Window Shuts Down Application
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:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 4:32 AM To: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP AWT Window Shuts Down Application
If it makes you feel better it has already been done. http://marc.theaimsgroup.com/?l=fop-cvsm=101420095016596w=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:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 4:32 AM To: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
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-cvsm=101420095016596w=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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP AWT Window Shuts Down Application
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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP AWT Window Shuts Down Application
-Original Message- From: Christian Geisert [mailto:[EMAIL PROTECTED]] Sent: February 20, 2002 1:28 PM To: [EMAIL PROTECTED] 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-cvsm=101420095016596w=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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
