On Monday 09 January 2006 01:42 pm, Mathias Bauer wrote: > Hi Hal, > > Hal Vaughan wrote: > > I just wanted to say thanks for the quick help and replies this past > > week. I have a Java application that was using OOo 1.x and I needed to > > see how much effort it would take to upgrade to 2.x (it was either that > > or use 1.1.5). I thought, when the time came to actually upgrade to 2.x, > > that it would take a few weeks, largely because the API is so confusing > > to me and I had a lot of trouble figuring out just what I needed to call > > to do what. In terms of actual work, it took less than a day to upgrade > > to using OOo 2.x. > > That's nice to hear. That's how it should be. Our goal is to have no > additional coding effort if you switch to a new version (perhaps except > for using the new features or improved APIs of this version). We are > trying to achieve this by keeping our API stable. Of course even if the > API is stable it is always possible that a changed behavior causes some > > trouble. In your case it was the URL stuff: > > I had a problem with file URLs in the first version. I don't remember > > the full story, but for some reason there was a problem with keeping > > track of the slashes after file:. In 1.x, OOo was lax about this and > > allowed file:/C:/My Documents and would require it to be file:///C:/My > > Documents in 2.x. While a change (and the biggest one in the API that I > > had to deal with), if I had not taken advantage of OOo's laxness in the > > first place (something that was undocumented), this would never have been > > a problem. > > That's the reason why "lax" behavior is never good - it can create > problems afterwards. But it's hard to spot. ;-) > > > I loaded a document, printed it, waited on a PrintListener until the OOo > > part of the printing was completed, then closed the document and > > repeated. I remember I asked on this list about the PrintListener, and > > there was some discussion over it. I don't remember where, but I had > > read information somewhere that indicated a PrintListener was not needed. > > That's not true. If I didn't use one, called print, then closed the > > document, it would not print properly. > > > > I've asked, but have received no information on this in 2.x (I don't > > think it's something people pay attention to unless they've had to). It > > would be nice (and speed up my app) if it weren't needed, but I don't > > want to remove it, have it test well on my system because of some timing > > glitch, and cause problems for clients. > > I answered to that meanwhile. I agree that removing the listener will > not give you that much but is always a risk. > > > That is almost impossible. While OOo has, overall, moved ahead, I think > > the Installation has moved backwards. I am still waiting to see if > > someone on the Install list can tell me how to make a response file for > > Windows. While everything else works fine with 2.x, I may have to drop > > back to 1.x simply because I can't find what I need to know how to > > install OOo the way I want on my clients' Windows systems! > > I think you are wrong here. Especially on Windows the new installer is a > big step into the right direction. And AFAIK it *is* possible to create > response files.
I asked about that about a week ago on the install list and am still waiting for an answer. While I admit that is not proof, a lot of Googling turned up nothing. Other than your statement and one other reference, I have yet to find anything to tell me how to do this without using Orca to edit the .msi file. I tried all the command options I could find for the setup program (/r, /saveinf, and a few others I found) and all any options ever did was cause the help window to open -- with no information in it on creating response files. I did find I could at lest specify a parameter to set in the command line, which lets me specify what directory to install to. For now I'm using that. While people have said it is possible to create response files, nobody, even in the install project, has been able to tell me how to do it. I am honestly beginning to think they are more rumor than actual. (Not that I'm trying to argue, just that my experience indicates people have heard of them, but nobody knows how to do it.) Hal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
