Re: [dev] moving psprint into vcl
Hi all, since DEV300m42 is out (which conveniently contains the last changes to psprint), the move of psprint into vcl takes place now. Kind regards, pl -- Those who can, do; those who can't, teach. And those who can't teach, go into administration. -- attributed to Lois McMaster Bujold - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] moving psprint into vcl
Hi Philipp, I think you can remove X11 stuff. From my impression, now no one uses MacOSX with X11. Best, From: Philipp Lohmann philipp.lohm...@sun.com Subject: [dev] moving psprint into vcl Date: Thu, 08 Jan 2009 10:47:51 +0100 Hi all, for various reasons we (hdu and me in this case) would like to move the code now residing in psprint into vcl. reasons to do so: - font subsetting code is in psprint and on many platforms linked statically into vcl anyway. - future CUPS versions will migrate from PostScript to PDF as their primary spool file format. moving psprint to vcl will make it easier to do this migration in OOo, too. - vcl is psprint's only customer anyway. - there is code duplication between psprint and vcl currently that can be removed after this changed. However this will mean there will be a CWS that will make this migration and changes to psprint in other CWS will be moot (see the discussion about svn not warning about committing to moved files). So consider yourself warned that we will announce a time at which no changes to psprint should be made until a certain CWS is integrated (not that there are that many people doing that anyway :-) ) At the same time we could do a little cleanup and first thing coming to mind is the MACOSX specific code which could be removed. That would however mean that the old MacOSX X11 port would not really work anymore (at least WRT to printing). So I want to ask: do we really continue to have the X11 Mac port in the 3.0 line ? Are there any compelling arguments for this ? Kind regards, pl -- Someone told me: Smile and be happy, it could be worse And I smiled and was happy and things became worse. -- Author unknown - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] moving psprint into vcl
Hi, Philipp Lohmann wrote: for various reasons we (hdu and me in this case) would like to move the code now residing in psprint into vcl. [...] What about psprint_config and the non-free PPDs lying around there? (http://qa.openoffice.org/issues/show_bug.cgi?id=72327) Regards, Rene - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] moving psprint into vcl
Rene Engelhard wrote: What about psprint_config and the non-free PPDs lying around there? (http://qa.openoffice.org/issues/show_bug.cgi?id=72327) That is independent of this move. The PPD files (and their copyright (non)issues) are in the same state as ever. Until someone finds a solution to that this probably won't change. Kind regards, pl -- Someone told me: Smile and be happy, it could be worse And I smiled and was happy and things became worse. -- Author unknown - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] moving psprint into vcl
Hi all, for various reasons we (hdu and me in this case) would like to move the code now residing in psprint into vcl. reasons to do so: - font subsetting code is in psprint and on many platforms linked statically into vcl anyway. - future CUPS versions will migrate from PostScript to PDF as their primary spool file format. moving psprint to vcl will make it easier to do this migration in OOo, too. - vcl is psprint's only customer anyway. - there is code duplication between psprint and vcl currently that can be removed after this changed. However this will mean there will be a CWS that will make this migration and changes to psprint in other CWS will be moot (see the discussion about svn not warning about committing to moved files). So consider yourself warned that we will announce a time at which no changes to psprint should be made until a certain CWS is integrated (not that there are that many people doing that anyway :-) ) At the same time we could do a little cleanup and first thing coming to mind is the MACOSX specific code which could be removed. That would however mean that the old MacOSX X11 port would not really work anymore (at least WRT to printing). So I want to ask: do we really continue to have the X11 Mac port in the 3.0 line ? Are there any compelling arguments for this ? Kind regards, pl -- Someone told me: Smile and be happy, it could be worse And I smiled and was happy and things became worse. -- Author unknown - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] moving psprint into vcl
Hi Philipp, Le 8 janv. 09 à 10:47, Philipp Lohmann a écrit : Hi all, for various reasons we (hdu and me in this case) would like to move the code now residing in psprint into vcl. That's a good idea. reasons to do so: - font subsetting code is in psprint and on many platforms linked statically into vcl anyway. - future CUPS versions will migrate from PostScript to PDF as their primary spool file format. moving psprint to vcl will make it easier to do this migration in OOo, too. - vcl is psprint's only customer anyway. - there is code duplication between psprint and vcl currently that can be removed after this changed. All are good reasons, and simplify cannot be bad. However this will mean there will be a CWS that will make this migration and changes to psprint in other CWS will be moot (see the discussion about svn not warning about committing to moved files). So consider yourself warned that we will announce a time at which no changes to psprint should be made until a certain CWS is integrated (not that there are that many people doing that anyway :-) ) Noticed :) At the same time we could do a little cleanup and first thing coming to mind is the MACOSX specific code which could be removed. That would however mean that the old MacOSX X11 port would not really work anymore (at least WRT to printing). So I want to ask: do we really continue to have the X11 Mac port in the 3.0 line ? Are there any compelling arguments for this ? AFAIK, nobody works on maintain X11 (not only printing) version on Mac, and nobody will complain. And to be honest, I think 2.4.3 (I still continue to believe maxleofix4x11 will be integrated a day) is the very last version to have X11 working, and I agree to no longer support it in 3.x line. So : +1 from me for your proposal Kind regards, Eric P.S. : any news for an ATSUI replacement ? IMHO, Apple should provide something soon, no ? -- qɔᴉɹə
Re: [dev] moving psprint into vcl
eric b wrote: P.S. : any news for an ATSUI replacement ? IMHO, Apple should provide something soon, no ? That replacement is CoreText. Unfortunately that does not exist in Tiger, even if ATSUI is already deprecated in Leopard. Herbert has some ideas about that migration. Kind regards, pl -- Someone told me: Smile and be happy, it could be worse And I smiled and was happy and things became worse. -- Author unknown - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] moving psprint into vcl
Philipp Lohmann wrote: Hi all, for various reasons we (hdu and me in this case) would like to move the code now residing in psprint into vcl. reasons to do so: - font subsetting code is in psprint and on many platforms linked statically into vcl anyway. - future CUPS versions will migrate from PostScript to PDF as their primary spool file format. moving psprint to vcl will make it easier to do this migration in OOo, too. - vcl is psprint's only customer anyway. - there is code duplication between psprint and vcl currently that can be removed after this changed. However this will mean there will be a CWS that will make this migration and changes to psprint in other CWS will be moot (see the discussion about svn not warning about committing to moved files). So consider yourself warned that we will announce a time at which no changes to psprint should be made until a certain CWS is integrated (not that there are that many people doing that anyway :-) ) At the same time we could do a little cleanup and first thing coming to mind is the MACOSX specific code which could be removed. That would however mean that the old MacOSX X11 port would not really work anymore (at least WRT to printing). So I want to ask: do we really continue to have the X11 Mac port in the 3.0 line ? Are there any compelling arguments for this ? Kind regards, pl Hi Philipp, I'm all in favour of this change. My only question would be about the time line. We are going to split off a separate OOo 3.1 code line soon. Only 3.1 tasks will be accepted there. Having psprint code inside vcl on TRUNK and in a separate module on 3.1 branch for several months sounds like a maintenance nightmare. Rüdiger - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] moving psprint into vcl
Philipp Lohmann wrote: eric b wrote: P.S. : any news for an ATSUI replacement ? IMHO, Apple should provide something soon, no ? That replacement is CoreText. Unfortunately that does not exist in Tiger, even if ATSUI is already deprecated in Leopard. Herbert has some ideas about that migration. Please see issue 97829 (http://www.openoffice.org/issues/show_bug.cgi?id=97829) to track this. The idea to support the different APIs is simple: - on OSX 10.4 to 10.x use ATSUI - from OSX 10.(x+1) use CoreText There is just the problem that this is time-consuming SMOP (simple matter of programming), which needs to be coded and tested thoroughly. Layout incompatibilities with documents done with an ATSUI code base should be avoided. And there is the minor problem that we currently build for a 10.4 baseline. I just created the issue to track it. That task has currently a relatively low priority. -- Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] moving psprint into vcl
Rüdiger Timm wrote: I'm all in favour of this change. My only question would be about the time line. We are going to split off a separate OOo 3.1 code line soon. Only 3.1 tasks will be accepted there. Having psprint code inside vcl on TRUNK and in a separate module on 3.1 branch for several months sounds like a maintenance nightmare. Aside from the need for development to handle possible changes in two separate CWS, will there be additional maintanence problems ? I don't really expect psprint changes for 3.1 anymore (knock on wood), so I am willing to risk that. However if there are problems for releng as well, we could wait a little more until the 3.1 tree has stabilized a bit. Kind regards, pl -- Someone told me: Smile and be happy, it could be worse And I smiled and was happy and things became worse. -- Author unknown - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] moving psprint into vcl
Philipp Lohmann wrote: Rüdiger Timm wrote: I'm all in favour of this change. My only question would be about the time line. We are going to split off a separate OOo 3.1 code line soon. Only 3.1 tasks will be accepted there. Having psprint code inside vcl on TRUNK and in a separate module on 3.1 branch for several months sounds like a maintenance nightmare. Aside from the need for development to handle possible changes in two separate CWS, will there be additional maintanence problems ? I don't really expect psprint changes for 3.1 anymore (knock on wood), so I am willing to risk that. However if there are problems for releng as well, we could wait a little more until the 3.1 tree has stabilized a bit. Kind regards, pl No other problems. Just that childworkspaces for 3.1 / 3.1.1 containing psprint (and certain parts of vcl?) can't get cloned for 3.2 any more. Rüdiger - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] moving psprint into vcl
Rüdiger Timm wrote: No other problems. Just that childworkspaces for 3.1 / 3.1.1 containing psprint (and certain parts of vcl?) can't get cloned for 3.2 any more. Ok, but that will be our problem. We would have that at any time. I agree that some proper care has to be taken, but at least you will know whom to kick when things go southward ;-) Kind regards, pl -- Someone told me: Smile and be happy, it could be worse And I smiled and was happy and things became worse. -- Author unknown - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
