Re: [sc-dev] Need UI name for new FDIST function
Hi Regina, I would suggest DISTF(). It adds the benefit that all distribution functions could be grouped at some point under a DIST...() name. DISTGAMMA() DISTPOISSON() DISTGAUSS() (reluctantly DISTNORM) There could be a shorthand form: DISTF DISTG DISTP DISTN (it is for this that I would accept DISTNORM() ) Sincerely, Leonard Original-Nachricht > Datum: Tue, 07 Apr 2009 22:48:43 +0200 > Von: Regina Henschel > An: ux discuss > CC: Calc dev > Betreff: [sc-dev] Need UI name for new FDIST function > Hi all, > (CC dev@sc.openoffice.org) > > with OpenFormula v1.2 we will get a new FDIST function. The current > FDIST function calculates the _right_ tail cumulative distribution > function of the F-distribution. The new function will calculate the > _left_ tail cumulative distribution function and the density function in > addition and will have an optional parameter to distinguish between > cumulative and density. > > The old function is called LEGACY.FDIST and the new one is called FDIST > internally. > > I'm going to implement the new function and need an UI-name for the new > function. I think, it would be very confusing to use the internal names > in the UI too, because than we would have different meanings of FDIST in > OOo3.1 and OOo3.2. > > I suggest to use FDISTLEFT. But perhaps there is a spreadsheet > application that has got this left tailed version already? > EXCEL 2007 and Gnumeric 1.6.3 do not know this function. > > Any suggestions? > > kind regards > Regina > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@sc.openoffice.org > For additional commands, e-mail: dev-h...@sc.openoffice.org -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 - To unsubscribe, e-mail: dev-unsubscr...@sc.openoffice.org For additional commands, e-mail: dev-h...@sc.openoffice.org
[sc-dev] Need UI name for new FDIST function
Hi all, (CC dev@sc.openoffice.org) with OpenFormula v1.2 we will get a new FDIST function. The current FDIST function calculates the _right_ tail cumulative distribution function of the F-distribution. The new function will calculate the _left_ tail cumulative distribution function and the density function in addition and will have an optional parameter to distinguish between cumulative and density. The old function is called LEGACY.FDIST and the new one is called FDIST internally. I'm going to implement the new function and need an UI-name for the new function. I think, it would be very confusing to use the internal names in the UI too, because than we would have different meanings of FDIST in OOo3.1 and OOo3.2. I suggest to use FDISTLEFT. But perhaps there is a spreadsheet application that has got this left tailed version already? EXCEL 2007 and Gnumeric 1.6.3 do not know this function. Any suggestions? kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@sc.openoffice.org For additional commands, e-mail: dev-h...@sc.openoffice.org
Re: [sc-dev] Re: MS Excel file encryption feature contribution to OO.o
Hi Daniel, On Tue, 2009-04-07 at 20:50 +0200, Daniel Rentz wrote: > Hello, > > Kohei Yoshida schrieb: > > > > Great! BTW, the new security framework would probably affect the > > password input UI part, but should not affect anything else IMO. > > Btw, I am interested in the pw input UI stuff to add it to the ooxml > filter. Do you have a pointer for me? Sure. I think there are two parts to the password input UI that I should mention. First, to enable password entry in the file picker dialog, currently we hard-code the filter name in struct CheckPasswordCapability in sfx2 (in sfx2/source/dialog/filedlghelper.cxx). But if the number of filter that supports export encryption grows, it will probably make sense to create a per-filter flag for this so that the password capability can be controlled in the configuration files in the filter module. I believe Mikhail shares this opinion as well (as we talked about this previously). Secondly, the actual password input UI is what has changed recently (since m38?). Since Excel's encryption password has a limitation of 0 to 15 character in length, we need to add that restriction somehow in the new security framework. I asked about this on the d...@framework.ooo list and here is the whole thread we had back then: http://framework.openoffice.org/servlets/BrowseList?list=dev&by=thread&from=2170560 In the old implementation, it was covered by SfxPasswordDialog, and it was quite easy to modify that class to add the aforementioned restriction. But in the new framework, that part is encapsulated into its own module via UNO API, so a new strategy is needed. Unfortunately I don't know any more than what we discussed on this thread since I sort of procrastinated on this. ;-) I hope this pointer is useful for you. Kohei -- Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc. - To unsubscribe, e-mail: dev-unsubscr...@sc.openoffice.org For additional commands, e-mail: dev-h...@sc.openoffice.org
[sc-dev] DataPilot: styles and localization
Hi all, I would like to bring some attention on this issue about Style in Datapilot and localization : http://www.openoffice.org/issues/show_bug.cgi?id=89493 It's very confusing because you would lost the formatting and do not know which styles to use, the foreign or the localized one. Datapilot is a strong feature in OOo vs MS one. Thanks in advance Kind regards Sophie - To unsubscribe, e-mail: dev-unsubscr...@sc.openoffice.org For additional commands, e-mail: dev-h...@sc.openoffice.org
Re: [sc-dev] Re: MS Excel file encryption feature contribution to OO.o
Hello, Kohei Yoshida schrieb: Great! BTW, the new security framework would probably affect the password input UI part, but should not affect anything else IMO. Btw, I am interested in the pw input UI stuff to add it to the ooxml filter. Do you have a pointer for me? Regards Daniel - To unsubscribe, e-mail: dev-unsubscr...@sc.openoffice.org For additional commands, e-mail: dev-h...@sc.openoffice.org
Re: [sc-dev] Re: MS Excel file encryption feature contribution to OO.o
On Tue, 2009-04-07 at 23:09 +0800, Ming Fei Jia wrote: > Kohei, > > Kohei Yoshida wrote on 04/07/2009 11:35:37 AM: > > > > The encryption work is already done. The CWS is blocking for the other > > feature, the sheet protection options, mostly on the ODF TC file format > > change approval. Once the file change is approved the missing piece of > > ODF load/save can be implemented quite easily for that sheet protection > > options feature. > > > > Here is the proposal: > > http://wiki.oasis-open.org/office/Spreadsheet_Table_Protection_Options > > > > (Actually any help pushing my proposal on the ODF TC would be great, > > since you guys are pretty active on the TC...) > I take a look at the proposal again. The proposal mainly includes 2 parts > of contents: (1)add table protection options;(2)add double-hash algorithm. > The proposal makes sense for me although I still need to think about the > implementation details. Of course, let us discuss the proposal on the TC > list, not appropriate here:)> Sure. That's fine. The main sticking point was what URI to use to represent the legacy xls hashing, but let's move the discussion to the TC. > > > > > Do you > > > need our support and cooperation? -:) > > > > Thanks for your offer, but since the core encryption work is 99% > > complete I don't think I need any more help on the core part of the > > implementation. > > > > Having said that, we are still lacking some UI fine-tuning since the UI > > for security, which includes file encryption, has undergone major change > > recently in the framework project. So, some work has to be done to hook > > the xls encryption bits to that new framework, which I haven't done yet. > > So, help in that area would be great. I've been talking with Mikhail > > Voitenko and Mathias Bauer about the new security framework on the > > framework list. > I do not know the framework change at all before now. I need to first > subscribe the framework list and take a look at what happened. Moreover, > besides Excel file encryption, Symphony also implements Word file > encryption, the 2 components should have common part at the framework > layer. If Excel file encryption modified the framework layer(I think > so),the Word file encryption should reuse the same modification. So my > colleague, Steve Yin (in the cc list) and I will investigate how the > framework layer change impacts the sc/sw file encryption. Great! BTW, the new security framework would probably affect the password input UI part, but should not affect anything else IMO. In terms of common part between Word and Excel encryption, my current Excel encryption code is already partitioned to leave the common part at framework level. The cipher code is all implemented in sal, and the front-end class for that is in svx. The code in sc is very minimal in terms of performing the actual encryption since the most heavy lifting is done by that shared front-end class in svx. That front-end class in svx was already there before I began my work, for the import decryption feature. So, I think it's fair to say that the amount of extra work I did for xls export encryption is pretty small. With this in mind, I don't think any other major refactoring is needed to share common code between Word and Excel encryptions. > BTW, before we > discuss issues on framework list, a question first, the framework change > you said has already been put into latest dev repository, or still at some > CWS? so that we can easily get the change code to take a look. thanks. The new security framework I believe was first integrated in m38. So the latest milestone should have that. HTH, Kohei - To unsubscribe, e-mail: dev-unsubscr...@sc.openoffice.org For additional commands, e-mail: dev-h...@sc.openoffice.org
Re: [sc-dev] Re: MS Excel file encryption feature contribution to OO.o
Kohei, Kohei Yoshida wrote on 04/07/2009 11:35:37 AM: > > The encryption work is already done. The CWS is blocking for the other > feature, the sheet protection options, mostly on the ODF TC file format > change approval. Once the file change is approved the missing piece of > ODF load/save can be implemented quite easily for that sheet protection > options feature. > > Here is the proposal: > http://wiki.oasis-open.org/office/Spreadsheet_Table_Protection_Options > > (Actually any help pushing my proposal on the ODF TC would be great, > since you guys are pretty active on the TC...) I take a look at the proposal again. The proposal mainly includes 2 parts of contents: (1)add table protection options;(2)add double-hash algorithm. The proposal makes sense for me although I still need to think about the implementation details. Of course, let us discuss the proposal on the TC list, not appropriate here:)> > > > Do you > > need our support and cooperation? -:) > > Thanks for your offer, but since the core encryption work is 99% > complete I don't think I need any more help on the core part of the > implementation. > > Having said that, we are still lacking some UI fine-tuning since the UI > for security, which includes file encryption, has undergone major change > recently in the framework project. So, some work has to be done to hook > the xls encryption bits to that new framework, which I haven't done yet. > So, help in that area would be great. I've been talking with Mikhail > Voitenko and Mathias Bauer about the new security framework on the > framework list. I do not know the framework change at all before now. I need to first subscribe the framework list and take a look at what happened. Moreover, besides Excel file encryption, Symphony also implements Word file encryption, the 2 components should have common part at the framework layer. If Excel file encryption modified the framework layer(I think so),the Word file encryption should reuse the same modification. So my colleague, Steve Yin (in the cc list) and I will investigate how the framework layer change impacts the sc/sw file encryption. BTW, before we discuss issues on framework list, a question first, the framework change you said has already been put into latest dev repository, or still at some CWS? so that we can easily get the change code to take a look. thanks. > > In terms of timeline, 3.2 integration is realistic. Actually, I already > tried to integrate the CWS for 3.1 (without the UI bits, that is), but > couldn't because of new strings that it introduces (and it was after the > translation deadline). So, 3.2 probably, unless we hit some unexpected > roadblocks. Good, looking forward to seeing your deliverables in 3.2! > > So, that's the gist of it. > > Best, > > Kohei > > > > thanks. > >
RE: Re: [sc-dev] Re: MS Excel file encryption feature contribution toOO.o (#6127-130352576-3019)
This report relates to a message you sent with the following header fields: Message - ID: 135142126 From: kyosh...@novell.com Subject: Re: [sc-dev] Re: MS Excel file encryption feature contribution toOO.o Your message cannot be delivered to the following recipients: Recipient Address: james.helmstet...@sun.com Reason: This address is no longer available -Original Message- From: Kohei Yoshida (kyosh...@novell.com) Sent: Apr 6, 2009 11:36:49 PM Subject: Re: [sc-dev] Re: MS Excel file encryption feature contribution toOO.o Hello Ming, looks like our paths have finally crossed. :-) On Tue, 2009-04-07 at 10:49 +0800, Ming Fei Jia wrote: > Thanks Eike, > > Now I have been added into sc and sw dev list. Since sw and sc are 2 > different projects. Here I only send to sc list. For Word file encryption > issue, I'll discuss it in sw list. > > The CWS that is in implementation of Excel file encryption should be > scsheetprotection02 > (http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=6645&OpenOnly=false&Section=Overview), > right? > > I see the owner of that CWS is Kohei. Hello Kohei, IBM Symphony also > implemented the feature of Excel file encryption, which is the similar with > your work under the above CWS. How about the progress of that CWS now and > the timeline of that CWS will be contributed to OO.o main stream? The encryption work is already done. The CWS is blocking for the other feature, the sheet protection options, mostly on the ODF TC file format change approval. Once the file change is approved the missing piece of ODF load/save can be implemented quite easily for that sheet protection options feature. Here is the proposal: http://wiki.oasis-open.org/office/Spreadsheet_Table_Protection_Options (Actually any help pushing my proposal on the ODF TC would be great, since you guys are pretty active on the TC...) > Do you > need our support and cooperation? -:) Thanks for your offer, but since the core encryption work is 99% complete I don't think I need any more help on the core part of the implementation. Having said that, we are still lacking some UI fine-tuning since the UI for security, which includes file encryption, has undergone major change recently in the framework project. So, some work has to be done to hook the xls encryption bits to that new framework, which I haven't done yet. So, help in that area would be great. I've been talking with Mikhail Voitenko and Mathias Bauer about the new security framework on the framework list. In terms of timeline, 3.2 integration is realistic. Actually, I already tried to integrate the CWS for 3.1 (without the UI bits, that is), but couldn't because of new strings that it introduces (and it was after the translation deadline). So, 3.2 probably, unless we hit some unexpected roadblocks. So, that's the gist of it. Best, Kohei > thanks. > > > Eike Rathke wrote on 04/06/2009 09:03:58 PM: > > > > 04/06/2009 09:11 PM > > > > Subject: > > > > Re: MS Word/Excel file encryption feature contribution to OO.o> > > > > Hi Ming, > > > > On Wednesday, 2009-04-01 15:50:02 +0800, Ming Fei Jia wrote: > > > > > I (call me Ming Fei) am from IBM Lotus Symphony team, seems I ever met > Eike > > > at OASIS ODF TC:). > > > > Yep :-) > > > > > Symphony have implemented the feature about MS Word/Excel file > encryption > > > with the default algorithm Office97/2000 compatible. That means in > > > OpenOffice.org editor, user can save the document to MS Word/Excel > binary > > > format with setting a password. Symphony team plan to contribute this > > > feature to OO.o community. Now our team is doing the code merge from > > > Symphony code base to OO.o code base, as well as going through some IBM > > > internal process. In parallel, we would like to hear any comments and > > > feedback from OO.o community about this feature and how we go next. > Thanks. > > > > For Calc the Excel binary file encryption is already in implementation > > progress in a CWS, the code is not active yet and lacks UI. For > > discussion of details please join the Calc developers d...@sc mailing > > list, to subscribe mailto:dev-subscr...@sc.openoffice.org > > > > Thanks > > Eike > > > > -- > > SunSign 0x87F8D412 : 2F58 5236 DB02 F335 8304 7D6C 65C9 F9B5 87F8 > D412 > > OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS > > -- Necessary legal stuff according to German laws: > > Sun Microsystems GmbH > > Nagelsweg 55, D-20097 Hamburg > > Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten > > Amtsgericht München: HRB 161028 > > Geschäftsführer: Thomas Schröder, Wolfgang Engels, Dr. Roland Bömer > > Vorsitzender des Aufsichtsrates: Martin Häring > > [attachment "attz75m6.dat" deleted by Ming Fei Jia/China/IBM] - To unsubscribe, e-mail: dev-unsubscr...@sc.openoffice.org For additional commands, e-mail: dev-h...@sc.openoffice.org -
