[dev] Make component unloading possible again on *NIX

2009-01-08 Thread Thorsten Behrens
Hi,

with the 3.0 Linux baseline being glibc-2.2.3, maybe it's time to
enable dlclose() again in osl_unloadModule()?

From the atexit manpage:
  Since glibc 2.2.3, atexit() (and on_exit(3)) can be used within
   a shared library to establish functions that are called when
   the shared library is unloaded.

Cheers,

-- Thorsten
diff --git sal/osl/unx/module.c sal/osl/unx/module.c
index 874eb52..89d0869 100644
--- sal/osl/unx/module.c
+++ sal/osl/unx/module.c
@@ -150,12 +150,14 @@ void SAL_CALL osl_unloadModule(oslModule hModule)
if (hModule)
{
 #ifndef NO_DL_FUNCTIONS
-#ifndef GCC
-/* gcc (2.9.1 (egcs), 295) registers atexit handlers for
+#ifndef OLD_GLIBC
+/* gcc (starting with 2.9.1 (egcs), 295) registers atexit handlers 
for
  * static destructors which obviously cannot
  * be called after dlclose. A compiler feature. The workaround 
for now
  * is not to dlclose libraries. Since most of them are closed at 
shutdown
- * this does not make that much a difference
+ * this does not make that much a difference.
+ * Since glibc 2.2.3 atexit handlers will be called on
+ * dlclose, when registered from within a shared lib
  */
 int nRet = dlclose(hModule);


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Re: [dev] Make component unloading possible again on *NIX

2009-01-08 Thread Caolán McNamara
On Thu, 2009-01-08 at 10:08 +0100, Thorsten Behrens wrote:
 Hi,
 
 with the 3.0 Linux baseline being glibc-2.2.3, maybe it's time to
 enable dlclose() again in osl_unloadModule()?

This was #i96683#, but needs to be reassigned to someone.

C.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



Re: [dev] Make component unloading possible again on *NIX

2009-01-08 Thread Thorsten Behrens
On Thu, Jan 08, 2009 at 09:14:35AM +, Caolán McNamara wrote:
  with the 3.0 Linux baseline being glibc-2.2.3, maybe it's time to
  enable dlclose() again in osl_unloadModule()?
 
 This was #i96683#, but needs to be reassigned to someone.
 
Ah, so the disabling is doubly irrelevant now?

At any rate, I have unloading canvas libs work beautifully now (after
killing a broken unload implementation in libanimcore), which is a
real bonus during debugging - you don't need to restart OOo anymore.

Cheers,

-- Thorsten

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



[dev] moving psprint into vcl

2009-01-08 Thread Philipp Lohmann

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

2009-01-08 Thread eric b

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

2009-01-08 Thread Philipp Lohmann

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] Make component unloading possible again on *NIX

2009-01-08 Thread Stephan Bergmann

On 01/08/09 10:37, Thorsten Behrens wrote:

On Thu, Jan 08, 2009 at 09:14:35AM +, Caolán McNamara wrote:

with the 3.0 Linux baseline being glibc-2.2.3, maybe it's time to
enable dlclose() again in osl_unloadModule()?

This was #i96683#, but needs to be reassigned to someone.


Ah, so the disabling is doubly irrelevant now?

At any rate, I have unloading canvas libs work beautifully now (after
killing a broken unload implementation in libanimcore), which is a
real bonus during debugging - you don't need to restart OOo anymore.


Thorsten, do you want to take over 
http://qa.openoffice.org/issues/show_bug.cgi?id=96683 (completely 
dropping the #ifndef and GCC 2 comment)?  Otherwise, I could include it 
in one of my OOo 3.1 CWSs.


-Stephan

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



Re: [dev] moving psprint into vcl

2009-01-08 Thread Rüdiger Timm


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

2009-01-08 Thread H Duerr

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

2009-01-08 Thread Philipp Lohmann

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] Software Engineering Students Open Source development

2009-01-08 Thread Eike Rathke
Hi eric.bachard,

On Thursday, 2009-01-08 01:52:11 +0100, eric.bachard wrote:

 Hi Andreas,

 Le 7 janv. 09 à 16:36, A.Meiszner a écrit :
 [...]]


I forwarded your mail to Andreas as he's not subscribed to the mailing
list.

  Eike

-- 
 OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer.
 SunSign   0x87F8D412 : 2F58 5236 DB02 F335 8304  7D6C 65C9 F9B5 87F8 D412
 OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
 Please don't send personal mail to the e...@sun.com account, which I use for
 mailing lists only and don't read from outside Sun. Use er...@sun.com Thanks.


pgpB09ys9ivmF.pgp
Description: PGP signature


Re: [dev] Software Engineering Students Open Source development

2009-01-08 Thread eric.bachard

Hi Eike,

Eike Rathke a écrit :


I forwarded your mail to Andreas as he's not subscribed to the mailing list.


Ooops ... Thank you very much !

And Happy New Year to you :-)

Kind regards,
Eric

--
Education Project: 
http://wiki.services.openoffice.org/wiki/Education_Project

L'association EducOOo : http://www.educoo.org
Blog : http://eric.bachard.free.fr/news


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



Re: [dev] moving psprint into vcl

2009-01-08 Thread Rüdiger Timm



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] Make component unloading possible again on *NIX

2009-01-08 Thread Thorsten Behrens
On Thu, Jan 08, 2009 at 10:53:26AM +0100, Stephan Bergmann wrote:
 Thorsten, do you want to take over  
 http://qa.openoffice.org/issues/show_bug.cgi?id=96683 (completely  
 dropping the #ifndef and GCC 2 comment)?  Otherwise, I could include it  
 in one of my OOo 3.1 CWSs.

Hi Stephan,

I'd prefer the latter, as I currently don't have any 3.1 CWS in
flight.

TIA,

-- Thorsten

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



Re: [dev] moving psprint into vcl

2009-01-08 Thread Philipp Lohmann

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



[dev] @Eric: Software Engineering Students Open Source development

2009-01-08 Thread Andreas Meiszner

Hi Eric

Happy to meet you and interesting stuff you are doing as I see from the 
information and links you provided!!! This seems actually very close to 
the work I am currently engaged at with Aristotle University.


I suggest that the two of us have a short IRC chat / phone conversation 
to check for synergies -- just tell me at which time I can find you at 
the channels you mentioned.


Just to have it mentioned and avoid confusion, I am not actually giving 
this software engineering course, but have worked with Prof. Ioannis 
Stamelos (who gives the course) for the past 3 years in another project 
and now volunteered to help at this pilot course. I am supporting the 
course more from the virtual and organizational side. Volunteered also 
means we do this without funding, like you, so with equally limited 
resources.


It would be great to explore some common actions, such as the live 
events we now consider running. I have been running several IRC sessions 
with some of the students last year, and it was good to get further the 
current work they are doing and to provide assistance. The sessions at 
UStream I thought of would be more of an informative / introductory 
nature. UStream allows the host to videocast meanwhile the audience 
is participating by chat. This should be moderate in terms of required 
bandwith and equipment to participate at such an event. One advantage is 
that the session will be recorded (including the chat log), so it is 
preserved for others / future students. The service is also free, like 
almost all of the things one needs today -- which is a great advancement 
educational wise. Chats certainly are always a plan B. Playing at the 
web on a daily base as part of my research I think that you can do a lot 
of funky things, with very limited sources -- though certainly the HR 
aspect is the crucial one nowadays.


I heard already about Seneca from various sources, so apparently they 
also do some interesting things.


Btw: Glad you forwarded my mail to the educational list -- I now 
subscribed to it too!


Hope hearing from you again!

Best

Andreas

With kind regards,
Mit freundlichen Grüßen
Com os melhores cumprimentos


Andreas  Meiszner
_

Institute of Educational Technology

The Open University
Milton Keynes
MK7 6AA
United Kingdom





eric.bachard wrote: Hi Andreas,

My apologies if ever you receive the mail twice in meantime, but looks 
like the initial one has been filtered :-/


Best regards,
Eric Bachard

Co Lead,
OpenOffice.org Education Project




Subject:
[dev-educ] Re: [dev] Software Engineering Students  Open Source 
development

From:
eric.bachard eric.bach...@free.fr
Date:
Thu, 08 Jan 2009 01:52:11 +0100
To:
d...@education.openoffice.org

To:
d...@education.openoffice.org
CC:
dev@openoffice.org


Hi Andreas,

Le 7 janv. 09 à 16:36, A.Meiszner a écrit :
 A hello to all and I hope this mail made it to the right section!

No doubt, most of the OOo devs will read it :)

If I can, for Education dedicated questions, there is a 
d...@education.openoffice.org mailing list (subscribe is mandatory), 
where I forwarded your mail.


 We are currently piloting an open approach for the course 
Introduction to Software Engineering (ISE) at Aristotle University in 
Greece,



That's a great idea. And I'm sincerily glad to read such news : you have 
all my encouragements !



 aimed at bringing together Aristotle students, students from fellow 
universities, open source practitioners and anyone else interested in SE.


As professor myself, in a french engineer school, I try to do the same 
with my students, and I perfectly understand what your need is.



 To facilitate the students entrance to open source projects we are 
now trying to organize some live events for Jan / Feb
 2008 (chats, video sessions or pod casts at ustream) that would 
introduce the students to some aspects relevant to

 working in open source environments.

If you are interested, I propose to discuss directly about that on IRC 
(see below for the channel/server).



 Therefore I wondered if anyone here might be interested in chairing 
one of those live events and to talk (A) about
 OpenOffice in general, some experiences and challenges, ways to 
contribute to it, etc and (B) about a more generic

 topic relevant for newbies (e.g. understanding the code, etc).

In my free time, as myself developer for OOo since several years (mostly 
Mac OS X port), and involved in mentoring students since several years 
two (twice Google SoC mentor, and some other), and I sincerily think 
OpenOffice.org Education Project can answer such request and organize 
such event successfully.


In fact, we are used to do IRC meeting as ClassRooms. Please notice we 
use IRC, because people attending are from all around the world, and not 
everybody has a good connectivity. So IRC is the less bad compromise. 
Anyway, we