RE: [PDF Viewer] Utility request
Heh...just give me some time. We might get Java 1.1 compatibility dynamically loaded yet. ;) -Original Message- From: Peter B. West [mailto:[EMAIL PROTECTED]] Sent: Monday, July 29, 2002 7:44 PM To: [EMAIL PROTECTED] Subject: Re: [PDF Viewer] Utility request Victor, The IAC, by this account, only has support for Macintosh and DDE/OLE on WIndows. While some work on support for OLE 2 document formats has been done in the Jakarta POI project, I don't know that this will solve the problem of cross-platform support for the project you have in mind. If it's not x-platform, it violates one of basic assumptions of the Apache XML efforts (although users without access to Java 2 may raise their eyebrows at that.) Peter Victor Mote wrote: Ralph LaChance wrote: -Start- Last time I used the Acrobat SDK (1999) it provided support only building a plug-in to Acrobat Exchange (not free) - ie. adding functionality to Exchange itself -- things like specialized searching, indexing, or retrieving simple objects (including text) from the file, adding work flow, modifying Exchange's menus etc. It provided NO support for rendering per se, and, more importantly, had almost no support for modifying the (free) Reader. Whether one could use a plug-in as a vehicle for tightly bolting acrobat exchange is an interesting concept, but (in my opinion) we'd not have any chance to doing anything useful with the reader. -End- Paragraph 1, Chapter 1 of the Core_API/CoreAPIOverview.pdf document in the Acrobat 5 SDK doc says: -Start- The Acrobat core API is a set of interfaces you can use to write plug-ins that integrate with Acrobat and Acrobat Reader. This chapter introduces the core API, describing its object orientation and organization, and a number of other concepts fundamental to understanding the API. Ways to Integrate With the Acrobat Viewers You can develop software that integrates with Acrobat and Acrobat Reader in two ways: * By creating plug-ins that are dynamically linked to the Acrobat viewer and extend the viewer's functionality * By writing a separate application process that uses interapplication communication (IAC) to control Acrobat functionality. DDE and OLE are supported on Windows and Apple events / AppleScript on the Macintosh. -End- There is a separate InterApplication_Communication folder containing related documents. Again, I haven't done it, so maybe it is all theory that doesn't work for the application at hand. And I don't mean to be argumentative -- it just seems that writing a good PDF viewer would be a big enough task that I would want to exhaust other possibilities before heading down that path. -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest Lord, to whom shall we go? - 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: [PDF Viewer] Utility request
On Mon, 2002-07-29 at 11:40, RamanaJV wrote: Ralph, Your idea of Fixing the awt renderer is the correct one. After a deep thought, I too came to the conclusion that instead of writing a PDF renderer, if we can tune up the AWT renderer, it will be great. The main problem with AWT renderer now is the heavy memory it uses. We need to find the source of memory drain and tune it. Heavy memory use: - holds onto every page in memory - area tree holds onto fo tree - all images are also held in the area tree and image factory - in general far too much memory is used for many structures Solutions: - separate area tree from fo tree - allow pages to be saved to disk to reduce memory - improve image handling The design for this is mostly implemented in HEAD. (One day I will convince someone to help out with HEAD code) We need to come up with the basic plan for this. Also, we have to first look and summarize the current issues with AWT renderer and step accordingly. Ramana. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [PDF Viewer] Utility request
Matthew L. Avizinis wrote: It might also be helpful to recognize that as FOP becomes more popular there are distinctly _two_ groups of users emerging. The first group has been using FOP from the beginning and those are the Java developers who use FOP to create some other end product. Recently I've noticed that there are more people attempting to use FOP who are simply people who want to use FOP as an end product (more of an FO viewer) and want it to fulfill the role of a product like X-Smiles (which unfortunately still falls far short of its goal of being a good FO viewer). I believe AWT previewer someday in the future will become some kind of FO IDE and afaik even nowadays somebody in the team has something to donate. -- Oleg Tkachenko Multiconn International, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [PDF Viewer] Utility request
Yes, it's called Acrobat Reader. What's being requested is something a little more tightly integrated to FOP. BTW, I think it's great that MacOSX creates PDF files when you opt to print to a file. -Original Message- From: Mark Malone [mailto:[EMAIL PROTECTED]] Sent: Fri 7/26/2002 7:43 PM To: [EMAIL PROTECTED] Cc: Subject: Re: [PDF Viewer] Utility request Folks, Excuse my ignorance but is the pdf viewer everyone is talking about provided already by Adobe on a huge number of platforms and called acrobat reader? Or is it something else that is being requested? Also, pdf file reading is built into MacOS X as is pdf generation via native print to file output options. What am I missing? -M On Friday, July 26, 2002, at 05:16 AM, Ralph LaChance wrote: At 05:24 AM 7/26/02, Ramana wrote: But, how much worth is a creator, without a viewer. In 90% of the applications the needs come to launch the viewer to be part of the application. No user prefers the print the PDF outside and again open the Acrobat Reader to see it. This lessens the competitiveness of the product. FOP beautifully caters to the creation of PDF, but a viewer is very much worthy and I'm sure the FOP with a viewer definitely strikes. Excuse me, If I'm more user conscious... Strong statements. I suspect there are at least one or two folks on this list who might consider ~them~selves quite user conscious, too. Perhaps you'd find that toning down the rhetoric might be a tad helpful... ;-) ' Best, -Ralph LaChance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] winmail.dat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [PDF Viewer] Utility request
Rhett Aultman wrote: -Start- Yes, it's called Acrobat Reader. What's being requested is something a little more tightly integrated to FOP. -End- RamanaJV wrote: -Start- Acrobat reader is a outside application. If I launch it through a swing application, it gives the splash screen etc. etc. The idea is to develop a viewer which can be part of the swing application. -End- If it helps any, Adobe has a pretty comprehensive Acrobat SDK. Links to it can be found at http://partners.adobe.com/asn/developer/sdks.html. I haven't had a good excuse to do it myself, but my impression is that if tighter integration is required, it could be done using these tools. There is a viewer component that can be pulled up inside another application. If the splash screen is a big issue, I think it can be turned off in the application settings. I don't have Acrobat Reader installed locally, but (full) Acrobat has (and I think the Reader does also), a setting at the Edit / Preferences / Options screen that controls the splash screen at startup. Victor Mote (mailto:[EMAIL PROTECTED]) Enterprise Outfitters (www.outfitr.com) 2025 Eddington Way Colorado Springs, Colorado 80916 Voice 719-622-0650, Fax 720-293-0044 attachment: winmail.dat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [PDF Viewer] Utility request
Folks, Excuse my ignorance but is the pdf viewer everyone is talking about provided already by Adobe on a huge number of platforms and called acrobat reader? Or is it something else that is being requested? Also, pdf file reading is built into MacOS X as is pdf generation via native print to file output options. What am I missing? -M On Friday, July 26, 2002, at 05:16 AM, Ralph LaChance wrote: At 05:24 AM 7/26/02, Ramana wrote: But, how much worth is a creator, without a viewer. In 90% of the applications the needs come to launch the viewer to be part of the application. No user prefers the print the PDF outside and again open the Acrobat Reader to see it. This lessens the competitiveness of the product. FOP beautifully caters to the creation of PDF, but a viewer is very much worthy and I'm sure the FOP with a viewer definitely strikes. Excuse me, If I'm more user conscious... Strong statements. I suspect there are at least one or two folks on this list who might consider ~them~selves quite user conscious, too. Perhaps you'd find that toning down the rhetoric might be a tad helpful... ;-) ' Best, -Ralph LaChance - 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: [PDF Viewer] Utility request
Ralph LaChance wrote: At 12:46 PM 7/25/02, you wrote: After seeing the OutOfMemoryError, the AWT renderer is causing, why don't thinking of providing a PDF viewer in the FOP itself. I think, this will be useful so much. I don't think people couldn't have ever thought about it, but is it diffucult to do so? I feel, FOP is very much useful with the PDF viewer. What do others say? Seems to me it might be a lot simpler to fix the awt viewer... Also, oddly enough doing a viewer against pdf is rather tricky - Adobe put an un-supported java-bean on their web site, but it is buggy and hasn't been updated in 2 or so years. The only commercial pkg (a toolset; some assembly required) I know of probably would pose a licensing challenge (understatement) Anyone contacted Adobe to see if they wanna opensource it? -- 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]
RE: [PDF Viewer] Utility request
I see FOP's role as being a data transformer first and foremost. We may want to consider packaging a PDF viewer with FOP, but I'd recommend against putting it *IN* FOP. -Original Message- From: RamanaJV [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 25, 2002 12:47 PM To: [EMAIL PROTECTED] Subject: [PDF Viewer] Utility request Dear FOP developers, After seeing the OutOfMemoryError, the AWT renderer is causing, why don't thinking of providing a PDF viewer in the FOP itself. I think, this will be useful so much. I don't think people couldn't have ever thought about it, but is it diffucult to do so? I feel, FOP is very much useful with the PDF viewer. What do others say? Ramana. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
