Re: [dev] no suitable windowing system found, exiting.
Hi, you can delete libvclplug_dummy680ls.so; this is not installed by the install set and used only during the build. I guess you copied that one directly. However that is unlikely to solve your problem. The most likely solution as kendy said is that libvclplug_gen680ls.so is missing symbols due to missing system libraries. Just my 2 cents, pl Jim Watson wrote: Jan Holesovsky wrote: To see what exactly is wrong, do ldd libvclplug_* in the non-working environment and see what library is missing/wrong. These files exist in my build, which uses default configurations Should there be a plug_kde too? [EMAIL PROTECTED]:/opt/o208/program$ ls -la libvcl* | grep _ -rwxr-xr-x 1 jim jim34174 Apr 24 07:56 libvclplug_dummy680ls.so -rwxr-xr-x 1 jim jim 2357729 Apr 24 07:56 libvclplug_gen680ls.so -r--r--r-- 1 jim jim 605608 Apr 18 06:18 libvclplug_gen680ls.so.1.1 -rwxr-xr-x 1 jim jim 1365982 Apr 24 07:56 libvclplug_gtk680ls.so -r--r--r-- 1 jim jim 414536 Apr 18 06:18 libvclplug_gtk680ls.so.1.1 -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] no suitable windowing system found, exiting.
Jim Watson wrote: Meanwhile, its seems for those of us who build outside the structured environment of the distribution packagers, we should build on the oldest possible linux installation. Is that what Sun does? Basically yes. Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] pdf Export: text only?
Laurent Denoue wrote: Can I tell the pdf export filter to only output text, not the images, or vector graphics, or background images (of an Impress for example)? Sorry, currently that is not possible. Laurent. Note: I'm interested in text only because I can already export the actual drawpages of a document as PNG, but I also need the bounding boxes of text, which is available in PDF using pdf2html. Isn't there a more direct way using the OOo API to ask a document's view about its contents ? Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] VCL performance , feature improvements for Sommer of Code?
Clemens Eisserer wrote: What do you think about writing out a summer-of-code slot this year for enhancing VCL. VCL itself is a great toolkit and I guess because of not-existing-manpower it will be used for another couple of years, but I think it lacks some features of modern toolkits. Ah, a diplomat :-) Some areas which could be improved: - Performance. Sometimes slow, sometimes bad feeling. E.g. menus in OpenOffice, Support for doublebuffering Both valid. The menu thing may extend to framework, though. - Layout Managers. Implement Layout-Managers (already existing?) and adopt important dialogs to use them. A long term wish of mine. There even were two attempts at writing Layouting code, one by mmeeks, one by cmc. Both had already progressed to a demo dialog. However there was no resolution about which way to go finally. - I am not a VCL experts but maybe there are additional things to be done? Doing the above things could easily fill a summer :-) As pavel mentioned we should continue any discussion about this in [EMAIL PROTECTED] Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Unicode---Give us all of it!
Niklas Nebel wrote: Stephan Bergmann wrote: In a first step, I will try to identify and gather as many places in OOo that need to be adapted, but I need your help for that: IF YOU KNOW OF ANY PLACE IN OOo THAT NEEDS TO BE ADAPTED, PLEASE LET ME KNOW. Wouldn't that be more or less any occurence of sal_Unicode? There's hundreds of them in Calc alone. That depends probably on the details. If for example you are searching for ansi1252 code characters in a unicode string (e.g. '/' for URL or filename parsing springs to mind), then you need not change that code since those codes do not coincide with the possible surrogate values. I guess many instances may fall into that category where searching for a known constant unicode is concerned. However if we were to change the underlying format of OUString, then also these cases would possibly have to be adjusted; e.g. UTF-8 leaves only true ascii (128) values as a single encoded character (one byte in that case). However if i'm not mistaken, changing OUString from 2 byte values will not be possible since it would change UNO protocol incompatibly, yes ? Just some thoughts, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Quickstarter on Linux
Bjoern Milcke wrote: Hi, since when do we have a quick-starter for Linux? I thought this was not Since michael and kendy deemed one necessary and CWS gtkquickstart got integrated in m187. necessary, as the libraries are kept in memory after the first start anyway, except if a lot of other programs are started meanwhile. So, is it for the first start only? You can also launch new documents from the quickstarter. When I install OOo (even the archive version without system integration) on a Linux machine using the Display on a Solaris server, I get the quick-starter icon in the system bar of my Solaris JDS workspace. (Maybe this vanishes after quitting the linux session window) The checkmark Start quick starter on system launch (or the like) is checked. How does this work as a simple (non-root) user? The same way as on windows: on first start you select the icon once to siwtch the quickstarter off and a second time to end it. Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] State of Valgrind tasks
A query for issues with keyword valgrind turns up exactly one task (17280). So how does one find the valgrind tasks ? Curious, pl Nikolai Pretzell wrote: Hi, this summer we have tried out to run the Office under Valgrind with the automatic GUI test scripts provided by QA. (http://wiki.services.openoffice.org/wiki/ValgrindTasks) These tasks are all pointing to memory violation, so have a high potential to cause GPFs. Therefore I'd like to give an overview how those tasks have been handled until now. In detail, these are the states of the tasks posted to IssueZilla from the test run from August 10 2006: 142 tasks found. From those were: 23 unusable 119 in progress. From the 23 unusable ones: 2 - could not yet be reproduced, however neither is there proof, they are false positives 21 - are duplicate From the 119 ones in progress: 92 - have not yet been touched 4 - are started 12 - are fixed or verified, but still open 11 - are fixed and closed. It would be good to have the majority of the remaining 92 fixed until the 2.1 release. Nikolai - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Learning VCL
Hi, Alan Yaniger wrote: Hi list-members, I deal mostly with RTL issues in OOo, and not surprisingly, I often end up looking at the VCL code. Is there a document which systematically describes this code? If not, does anyone have recommendations about how to go about learning this code in an efficient way? There is basically no documentation on vcl (one of our many entry barriers). For the time being i can only suggest having a look at the sample programs svtools/workben/svdem.cxx and vcl/workben/svdem.cxx. The vcl svdem is a simple hello world while the svtools svdem contains a set of controls and uses dialogs. To use them go to the respective workben directory, dmake and copy svdem and applicat.rdb (they will be produced by dmake) from the bin output directory to an existing office installation. You can start them from there. Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Seeking for guide
Mathias Bauer wrote: Xu, Shenshen wrote: Hello Everybody, Could anybody tell me what is the meaning of the return value of IMPL_LINK, I found some of the codes return 0L and few of the codes return 1L, I wonder what the difference is ? The meaning is that returning 0 means that the link wasn't executed successfully while returning any other value means success. nitpick Actually the return value is a matter of negotiation between caller and callee - an implementation detail so to speak. In some case you might find more values than 0 or 1. Think of a Link as an early version of boost::bind, a safe function pointer. /nitpick As in most cases nobody cared for the return value on the calling side it's possible that also meanwhile nobody cares for it anymore on the called side. :-) Yes, that too :-) Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Pitfall using VCL focus handler and virtual methods GetFocus/LoseFocus
Mathias Bauer wrote: Philipp Lohmann - Sun Germany wrote: That is as correct as useless. :-) Ok, you win. Excuse my being alive. ;-) If anybody has a better idea that can prevent the occurence of our bug by fixing something in VCL please let us know. This would save us the investigation and fixing of all the other cases shown by Carsten. Please consider that Carsten only showed us the places where the link is used, we still have to look for cases where the overwriting of GetFocus() is used, something that will be time consuming. It would be nice to save all this time for other tasks. Calling Hide() on the dialog before destroying might also be used to force the focus out of the window (this should move the focus to the nex overlapping window, in this case i assume this should be the document). However this is obviously also something we cannot do in vcl. Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Pitfall using VCL focus handler and virtual methods GetFocus/LoseFocus
Frank Schönheit - Sun Microsystems Germany wrote: There is even a event listener mechanism for dying windows. Which also doesn't help, since it's also triggered from Window::~Window only - which is too late, since a lot of destruction already happens before this in the derived class. Bullshit. The object dying notifies you that it gets destroyed and you still cannot refrain from using it ? Maybe that's just me, but i would call THAT a destructive attitude ;-) Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Pitfall using VCL focus handler and virtual methods GetFocus/LoseFocus
Mathias Bauer wrote: Philipp Lohmann - Sun Germany wrote: You overlook an important detail: the problem happens before any such notification could have been sent and Frank obvisouly tried to explain that. The case Carsten mentioned was a control implementing :GetFocus and in there manipulating a sibling control via its parent window - which was already destroyed. That sibling would obviously already have gotten its dying notification. The other case you mention has nothing to do with derivatives of Window at all; of course you have to be careful that a member does not access the already partially destroyed parent. But this basically has nothing to do with Window focus handling, except that focus handling is one example for this. Just my 2 cents, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Pitfall using VCL focus handler and virtual methods GetFocus/LoseFocus
Frank Schönheit - Sun Microsystems Germany wrote: No. The MyTabPage implemented a handler for the GetFocus event of one of its children. Please examine the original example more carefully ;) Point taken. The other case you mention has nothing to do with derivatives of Window at all; of course you have to be careful that a member does not access the already partially destroyed parent. That's the point: VCL does this. When a window is destroyed, it's child windows (held as members) are destroyed, too. Now if one of those members has the focus, VCL moves the focus to another suitable control - either the being-destroyed window itself, or to a sibling of the member window. In both cases, VCL calls into a partially destroyed instance. I just tried to say that this has nothing to do with focus handling in particular. You always have to handle such cases, this can happen as soon as you implement a virtual method (or a callback for that matter). Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] New kind of issues: Valgrind
Nikolai Pretzell wrote: So I'd suggest: - Summary looks like: Valgrind ID: ID, ErrorText - The issues get the keyword valgrind. I think that's a good idea. Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] New kind of issues: Valgrind
Frank Schönheit - Sun Microsystems Germany wrote: Hi Nikolai, in a few weeks and beyond, there may occur a kind of IssueZilla issues whose summary starts with Valgrind . There's a keyword valgrind (http://www.openoffice.org/issues/describekeywords.cgi), which already captures this information - IMO duplicating this information in the summary is prone to errors, and should be avoided. Since leaving Valgrind out of the summary would leave titles like ID:23 i strongly oppose simply leaving it. Since Stacktrace ID:x seems to work well for stacktraces, why not stay with Valgrind ID:x for the valgrind bugs ? What naming scheme would you propose instead ? Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] New kind of issues: Valgrind
Frank Schönheit - Sun Microsystems Germany wrote: Hi Philipp, There's a keyword valgrind (http://www.openoffice.org/issues/describekeywords.cgi), which already captures this information - IMO duplicating this information in the summary is prone to errors, and should be avoided. Since leaving Valgrind out of the summary would leave titles like ID:23 i strongly oppose simply leaving it. The complete naming scheme isn't explained in the Wiki, so I didn't now it's a mere ID then. My objection is against using the summary to classify issues (and to me it sounded / still sounds as if this is the main use of the Valgrind in the summary), since this is error-prone. There are other means for classifying issues, namely keywords. Since Stacktrace ID:x seems to work well for stacktraces, Bad example, since stack traces are not submitted in IssueZilla, but in the Sun-internal bug tracking system (to respect user privacy), and this system doesn't know other means for issue classification. Not so bad example, since the current version of Valgrind tasks is handled the same way. I guess this whole issue only crept up since Nikolai wants to move this to IssueZilla tasks as there are no privacy issues involved in tasks created by an automated tool. Still i want to be able to see from the title what an issue is generally about. A tool can never know that, so at least the valgrind title tells me what class of issues this belongs to. why not stay with Valgrind ID:x for the valgrind bugs ? What naming scheme would you propose instead ? Do Valgrind bugs really have an ID? (I mean, except the issue ID)? Aren't they defined by a test case, not by an ID? Die normative Kraft des Faktischen ist da am Werk. Already existing tasks tell us that currently they have an ID. Since the valgrind tasks are mostly related to a set of test cases of unknown size, this is also not a good criterium for the title. I suggest having the Error type or Error text (which according to the Wiki are in the issue description) as summary, since this better describes what's going on than Valgrind ID:x. We could enhance this with the file name where the error occurs, or things like this. Everything allows you to grasp an idea of the issue just from reading the summary. This would be what ? There is no direct relation between any test case basic line and the valgrind output AFAIK, what would be the Error text in your opinion ? Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] OpenOffice and PPD's
Hi, Lesley Northam wrote: OpenOffice 1 (that ships with RedHat 9) cannot see these paper sizes in the printing menu. As a result, I cannot print from OpenOffice 1 (formatting issues). It probably can, but OOo 1 did not support CUPS. You would have to copy your PPD to office/share/psprint/drivers and then create a printer that uses that PPD by using the spadmin tool. OpenOffice 2.0.2 can see these sizes, and is even so kind as to adjust my document accordingly. However, for some sizes it confuses width and height, so my papersize is landscape instead of portrait orientation. The width/height is described correctly in the PPD file. I have some questions: How does the printing system work (in regards to printer-specific options) in OpenOffice 1 and OpenOffice 2? Is it possible to see my printers PPD options in OpenOffice 1? See above. Why is OpenOffice 2.0.2 mucking up the width/height values for some sizes? Because users do so many strange things; like e.g. giving a user paper format in Format-Page and then not adjusting the Landscape/Portrait property so OOo tries to cope with that; which is probably not so good for your specific use case. However there also may be some bugs in paper handling in the layers below the applications. Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Fontconfig support status?
Jan Uhlir wrote: Hello everyone, I have a curious question about status of support of system fontconfig/freetype in recent OpenOffice.org 2.0.x Similar question was left unaswered on user forum so I'm trying my luck here.. I use build options --with-system-freetype --enable-fontconfig. Does it mean that OOo will now obey a system fontconfig settings (/etc/fonts.conf) I have a precise per font settings fonts.conf - size and font tailored hinting, autohinting and antialiasing – and I naturally want OOo to follow them. What is the exact relation between OOo and system fontconfig/freetype if OOo is build with --with-system-freetype --enable-fontconfig? OOo uses fontconfig to discover available fonts and what their names are. Also fontconfig is used to discover which UI font to use if you happen to run the gtk plugin for OOo (usually the case if you run OOo on Gnome). The more detailed settings you mentioned are not supported as of now; that would be an enhancement yet to be implemented. Kind regards, pl -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] warnings01: reftotemp
Stephan Bergmann wrote: So, if there are no objections, I would switch off the reftotemp warning globally for all unxsol platforms. +1 -- If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. -- Author unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] OSL_VERIFY and other diagnostics
Frank Schönheit - Sun Microsystems Germany wrote: Hi Kay, Sorry for the (may be stupid) question, but why not just change OSL_VERIFY to emit nothing, in case OSL_DEBUG_LEVEL == 0? I would expect that only weird code would relay on the evaluation in case of a zero debug level. Why weird? The alternative is something like #if OSL_DEBUG_LEVEL 0 bool result = #endif callSomeFooWhichSignalsSuccess( bar ); OSL_ENSURE( result, this was expected to succeed! ); I definately think that OSL_VERIFY( callSomeFooWhichSignalsSuccess( bar ) ); is the better (non-weird) alternative here. That case is weird, because you choose to ignore the return value. In that you create a possibly not easy to find error. Ignoring return values is just bad code. Now there certainly are case in which the return value can be ignored safely, but then an OSL_VERIFY wouldn't be necessary either. Actually i think we should remove OSL_VERIFY for good. Just my 2 cents, pl -- Never be afraid to try something new. Remember: amateurs built the ark; professionals built the Titanic. -- Autor unbekannt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] OSL_VERIFY and other diagnostics
Kay Ramme - Sun Germany - Hamburg wrote: Philipp Lohmann - Sun Germany wrote: Can I interpretate this in a way, you to be willing to join our diagnose and debug macro consolidation meeting?! So, watch out for an event notification for sometime next week :-) Very good, that will test the vacation mail feature of our mail server then :-) -- Never be afraid to try something new. Remember: amateurs built the ark; professionals built the Titanic. -- Autor unbekannt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Save as PDF?
Hi, what exactly would you want to know ? I could point at the vcl project to vcl/inc/pdfwriter.hxx and vcl/source/gdi/pdfwriter_impl.[hc]xx which contain that parts of OOo's PDF export that actually handle creating a PDF. But that is of course code working inside OOo, one would have to adapt that heavily to work in Mozilla. Plus the code is mostly undocumented :-( . Kind regards, pl Ryan Singer wrote: There is some interest in making a save as pdf feature in future versions of Mozilla on the PC and on linux, and one of my friends at the mozilla foundation was wondering if he could talk to a OOo developer about where to start with that. Any of you interested in helping? Just reply to me off-list and I'll forward you along. -- Never be afraid to try something new. Remember: amateurs built the ark; professionals built the Titanic. -- Autor unbekannt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] portaudio sndfile: why SO only?
eric.bachard wrote: Hi Rene, Rene Engelhard a écrit : Hi, why is portaudio / sndfile SO only in 680? It was implemented in SRX645 whith OOo in mind, too. What is the reason? That the envvar needed isn't set? The reason is very simple: the child workspace vclppbugs8 that contains the change for 645 is not integrated yet. I suppose it will be integrated for 1.1.5. Regards, pl -- Never be afraid to try something new. Remember: amateurs built the ark; professionals built the Titanic. -- Autor unbekannt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] portaudio sndfile: why SO only?
Philipp Lohmann - Sun Germany wrote: Rene Engelhard wrote: Huh ? it's not SO only; it's a configure option, configured with environment variable ENABLE_PASF. Regards, pl Sorry, i looked at the wrong place ... which i'd have noticed had i looked at your patch first, stupid me. I didn't see the wrong build dependency. Of course you're right. Regards, pl -- Never be afraid to try something new. Remember: amateurs built the ark; professionals built the Titanic. -- Autor unbekannt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
