Re: [dev] Re: documentation for filter flags?

Allen Pulsifer schrieb: NOTINCHOOSER excludes it from the filter dialog, the awful dialog you get when OOo can't find a filter. Hello Markus, Thank you for the hint on how to force the filter chooser dialog to appear. I was able to confirm that the NOTINCHOOSER flag does not work, and entered

Re: [dev] documentation for filter flags?

Allen Pulsifer schrieb: NOTINCHOOSER excludes it from the filter dialog, the awful dialog you get when OOo can't find a filter. Hello Mathias, Thank you, that is helpful. Is there sample file somewhere that causes OOo to bring up the filter dialog? I wanted to test NOTINCHOOSER but I'm unabl

Re: [dev] documentation for filter flags?

Mathias Bauer schrieb: Allen Pulsifer wrote: Just to follow up on this question, what in particular does the NOTINCHOOSER flag do? In testing, and in examining the source code, it appears to do nothing. In contrast, the NOTINFILEDIALOG hides the format in all dialogs, including File | Open, F

Re: [dev] Specification Process Possibilities ... what about a wiki?

Hi Cor, On 10/25/06, Cor Nouws <[EMAIL PROTECTED]> wrote: Hi David, *, David Fraser wrote: [...] > 3) The spec process is apparently working well for those inside Sun, > less well for those outside. If there were an easier route for those > less involved in development to produce specs it coul

[dev] Specification Process Possibilities ...

I would like some advise about when a Specification Document should be written. I have submitted quite a few enhancement requests for Writer most of which are at status=new, some of them have an assigned owner and some are still owner=requirements. I have 22 issues and enhancements submitted, a

Re: [dev] cpu looping in cupsd and soffice.bin

Joost Andrae wrote: > > workaround: > The environment variable SAL_DISABLE_CUPS set to a value (eg. 1) > disables cups use within OpenOffice.org. In that case you can manually > configure your printers using OOo's printer administration tool spadmin > which you can find within the program di

Re: [dev] cpu looping in cupsd and soffice.bin

Hi, I experience exactly the same problem like you with cupsd and OpenOffice in a loop. I have also SuSE (OpenSuSE 10.0) and OpenOffice 2.0 (build 2.0.0.1). Any luck looking for help at SuSE? Randolf Andy Pepperdine wrote: > > On Monday 23 October 2006 14:42, G. Roderick Singleton wrote: > [

Re: [dev] Specification Process Possibilities ... what about a wiki?

Hi David, *, David Fraser wrote: [...] 3) The spec process is apparently working well for those inside Sun, less well for those outside. If there were an easier route for those less involved in development to produce specs it could be run concurrently as an alternate mechanism (possibly with

Re: [dev] Specification Process Possibilities ... what about a wiki?

Hi David, > For issue 12719 I attempted to have a faster and more accessible > specification process > This involved developing the spec collaboratively in the wiki > Unfortunately the spec team did not like this idea and have gone for an > OOo template for designing specifications with > This i

Re: [dev] Quickstarter quirks

Hi Gerry, >>The existing Windows version of the quickstarter is covered by >>http://specs.openoffice.org/appwide/menus/desktop_menu_integration.sxw, >>reachable from http://specs.openoffice.org/. > > So you are saying the *NIX version behaves in exactly the same way? No I don't say so. I didn't

[dev] Where to find source code for X,,,

I would like to find out why my computer refuses to save OOo spreadsheets. It works fine for ordinary diskfiles but fails on my USB stick. I have been plodding through the Developers Guide and the CVS repository but am utterly confused. In the end I want the source code that is executed when c

Re: [dev] Quickstarter quirks

On Wed, 2006-10-25 at 15:52 +0200, Frank Schönheit - Sun Microsystems Germany wrote: > Hi Gerry, > > > Okay. Sounds reasonable. However, this new feature needs to be > > documented so I am looking for confirmation that your guess is so. Can > > someone confirm or direct me to some spec that will e

Re: [dev] Specification Process Possibilities ... what about a wiki?

David Fraser <[EMAIL PROTECTED]> writes: > ...but I think there are still significant cases where using a wiki > is a much faster route for people (particularly outside > contributors) to use to collaboratively produce a specification. > Seconded. A wiki has a low barrier for entry, can cross-link

Re: [dev] Specification Process Possibilities ... what about a wiki?

Hi David, On 10/25/06, David Fraser <[EMAIL PROTECTED]> wrote: This involved developing the spec collaboratively in the wiki Unfortunately the spec team did not like this idea and have gone for an OOo template for designing specifications with Did the spec team discuss with you the reason why

Re: [dev] Quickstarter quirks

Hi Gerry, > Okay. Sounds reasonable. However, this new feature needs to be > documented so I am looking for confirmation that your guess is so. Can > someone confirm or direct me to some spec that will explain whether this > is *NIX specific, WM specific (e.g. Gnome vs. KDE vs. ...) or mimics > Wi

Re: [dev] Specification Process Possibilities ...

Hi Hirano, > I encourage community developers and CJK developers to access the spec > project wiki [1] and the spec template [2]. > > http://specs.openoffice.org/servlets/ReadMsg?list=dev&msgNo=59 > http://specs.openoffice.org/servlets/ReadMsg?list=dev&msgNo=83 > > Can you help fix them? I just

Re: [dev] Specification Process Possibilities ...

On 10/25/06, Nikolai Pretzell <[EMAIL PROTECTED]> wrote: Hi Thorsten, Thorsten Ziehm schrieb: > Hi Michael, > >> them: "We need this burdensome process for Higher Quality !" >> us: "But lets face it quality is still not good" >> them: "Then we need -even-more- burdensome process !

Re: [dev] Specification Process Possibilities ...

Hi Thorsten, Thorsten Ziehm schrieb: Hi Michael, them: "We need this burdensome process for Higher Quality !" us: "But lets face it quality is still not good" them: "Then we need -even-more- burdensome process !" Nobody said, that it is needed to include _burdensome

Re: [dev] Quickstarter quirks

On Wed, 2006-10-25 at 15:08 +0200, Frank Schönheit - Sun Microsystems Germany wrote: > Hi Gerry, > > > A quick question. Why is the quickstarter enabler kept in a config > > directory outside of the user's OOo stuff. > > I suppose that's because this is really about desktop integration: The > des

Re: [dev] Possible exploit potential in openoffice

On Wed, 2006-10-25 at 14:53 +0200, Stephan Bergmann wrote: > Caolan McNamara wrote: > > Also, we really should also add... > > > > .section.note.GNU-stack,"",@progbits > > > > to the end of bridges/source/cpp_uno/gcc3_linux_intel/call.s similiar to > > the line at the end of bridg

Re: [dev] Quickstarter quirks

Hi Gerry, > A quick question. Why is the quickstarter enabler kept in a config > directory outside of the user's OOo stuff. I suppose that's because this is really about desktop integration: The desktop probably checks this location for things to, well, quickstart. Just a guess. Ciao Frank --

Re: [dev] Possible exploit potential in openoffice

Caolan McNamara wrote: On Wed, 2006-10-25 at 13:58 +0200, Stephan Bergmann wrote: After some analysis I just filed . However, that issue is probably specific to OOo as built by Sun (and available for download from the OOo web site). If

Re: [dev] Quickstarter quirks (was: [dev] Specification Process Possibilities ...)

On Wed, 2006-10-25 at 08:45 +0200, Frank Schönheit - Sun Microsystems Germany wrote: > Hi Michael, > [snipped] > Hmm. It's a link pointing to some other CWS' installation (which does > not exist anymore). Removing it (and my user data) gave me the > quickstarter, again, created a new link (to my

Re: [dev] Specification Process Possibilities ... what about a wiki?

Kazunari Hirano wrote: Hi, Frank Schönheit wrote: However, what I really *really* like about this process is the exchange of ideas and arguments. I respect the process. I encourage community developers and CJK developers to access the spec project wiki [1] and the spec template [2]. For issue

Re: [dev] Warning: operator += enforces hidden conversion

Hi Bjoern, Bjoern Milcke schrieb: I came across the following piece of code: String a; xub_StrLen n = 0; n += a.Len(); This breaks on Windows (due to -werror). Because of the warning: warning C4244: '+=' : conversion from 'int' to 'USHORT', possible loss of data (in the last lin

Re: [dev] OpenOffice port using USL C compiler on SCO OpenServer 6

Ronald Joe Record wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, We are porting OpenOffice 2.0.3 to OpenServer 6 using the USL C compiler (UDK on SCO platforms). We're currently stuck in the bridges port and don't see how to run the bridges tests. Are there instructions on how to run

Re: [dev] Possible exploit potential in openoffice

On Wed, 2006-10-25 at 13:58 +0200, Stephan Bergmann wrote: > > After some analysis I just filed > . However, that > issue is probably specific to OOo as built by Sun (and available for > download from the OOo web site). If your OOo at /us

Re: [dev] Possible exploit potential in openoffice

James Courtier-Dutton wrote: scanelf is a tool one can use to find which programs have an executable stack. For security reasons, and executable stack should be avoided if at all possible. scanelf -Rqe /usr/lib/openoffice/* results in a lot of openoffice having an executable stack. e.g. RWX ---

Re: [dev] Specification Process Possibilities ...

Hi, Frank Schönheit wrote: However, what I really *really* like about this process is the exchange of ideas and arguments. I respect the process. I encourage community developers and CJK developers to access the spec project wiki [1] and the spec template [2]. http://specs.openoffice.org/serv

Re: [dev] Specification Process Possibilities ...

Hi Michael, them: "We need this burdensome process for Higher Quality !" us: "But lets face it quality is still not good" them: "Then we need -even-more- burdensome process !" Nobody said, that it is needed to include _burdensome_ processes to get a hig

Re: [dev] Wiki Extension: ParserFunctions

Stefan, Stefan Taxhet wrote: But I didn't take the time to read on and bother about '#'s and '#if's. could you do at least the fix regarding the 'if'? Otherwise it is unusable (and worthless :-( ). Greetings Stefan Thanks Kay --

Re: [dev] Specification Process Possibilities ...

Michael Meeks wrote: [...] Having a formalised process (1 paragraph necessary?) for quickly including code into OO.o that is disabled in all Sun builds, and quickly getting fixes / changes into that etc. would be much appreciated. This is something we have been wanting for some years now;

Re: [dev] Specification Process Possibilities ...

Hi Michael, > Well - it looks like that on the face of it. However - while I > absolutely loathe the process, I can (perhaps) live with it - if it > actually worked :-) Sadly it is totally dysfunctional. If 1 (one) > interaction can take of the order of months to occur, the spec. process > w

Re: [dev] UNO & STL

Eike Rathke wrote: Hi CLAIRE,, On Monday, 2006-10-23 16:16:09 +0100, CLAIRE, Narinder, Group Risk Mgmt wrote: When Building an uno component in C++ with a Makefile taken from one of the examples in SDK, which STL is visible, the native STL or STLport ? STLport. If STLport , then if the uno