Apache OpenOffice Wiki - User contributions [en]

Calc/ODFF Implementation/Examine functions

2013-02-06T18:26:25Z

ErAck: /* Examine Changes in Functions for ODFv1.2 */ implemented/integrated in LibO 4.0

== Examine Changes in Functions for ODFv1.2 ==

This is a collection of the differences I found and what I know is already done or in progress. I also note, when I found problems in the draft spec itself. You are invited to add your observations. [[User:Regina|Regina]] 19:40, 10 October 2008 (CEST)

=== Statistical Functions ===

{| class="wikitable"
|-
! Function !! ODFv1.2 !! CALC !! Action !! Progress ||
|-
! AVERAGEIF
| || implemented || implementation by Marina (makkica) ||{{bug|101466}} integrated in LibO 4.0 ||
|-
! AVERAGEIFS
| || implemented || implementation by Marina (makkica) ||{{bug|101466}} integrated in LibO 4.0 ||
|-
! BETADIST
| Draft Spec misses faktor 1/(b-a) in densitiy case || not yet implemented || Inform [[User:ErAck|Eike Rathke]] ||correct in draft 22a of ODFF ||
|-
| ||Has density case and optional parameter, to choose between density and cumulative || not yet implemented || expand function to density case and additional parameter,tracked in {{Bug|91547}} || integrated in OOo3.2||
|-
! BINOMDIST
| Parameter C is integer with constraint to 0 and 1. It should be Logical as in other distributions || C=0 is density, all other values of C are treated as cumulative || || ||
|-
! LEGACY.CHIDIST
| Returns 1 for x <0 || x < 0 returns Err:502 || expand domain to x < 0 internal,patch in {{Bug|94555}} ||integrated in OOo3.2 ||
|-
! CHISQDIST
| density function and cumulative left tail of chi-square distribution || not yet implemented || prepare Implementation, patch in {{Bug|94555}} || integrated in OOo3.2 ||
|-
! CHISQINV
| inverse of CHISQDIST(...TRUE()) || not yet implemented || prepare Implementation, patch in {{Bug|94555}} || integrated in OOo3.2 ||
|-
! EXPONDIST
| Parameter ''Cumulative'' has type Logical and is optional. || Last Parameter C has type Number and is not optional. C=0 returns denisity, other values for C return cumulative function. || || ||
|-
! FDIST
| density function and cumulative left tail of F-distribution || not yet implemented|| prepare for implementation || first draft, depends on BETADIST {{Bug|91547}} ||
|-
| || || Name conflicts with actual FDIST, which calculates right tail. OOo2.4 does not handle namespace correctly and takes new FDIST as old one || get new UI-name || have brought problem to dev@sc ||
|-
! FINV
| inverse of new FDIST || not yet implemented || || ||
|-
| || || Name conflicts with actual FINV, which calculates inverse for right tail. || get new UI-name || ||
|-
! GAMMA
| Parameter is constraint to >= 0 || Gamma is definied for all real numbers, but non-positive integers || Inform [[User:ErAck|Eike Rathke]] || ||
|-
| || ||not yet implemented || prepare implementation using full domain. Add UI texts. patch in {{Bug|94555}} || integrated in OOo3.2||
|-
| ||is in subgroup Mathematical functions || will go to subgroup Statistical functions || ||Mail to OASIS [http://lists.oasis-open.org/archives/office-comment/] ||
|-
! GAMMALN
| is in subgroup Mathematical Functions || is in subgroup Statistical Functions || || ||
|-
! GAMMADIST
| Last Parameter has type Logical || Last Parameter has type Number || Change type internal to bool. Change UI texts. patch in {{Bug|94555}} || integrated in OOo3.2 ||
|-
| ||Domain for Parameter x includes x < 0 || x < 0 returns Err:502 in OOo2.* || Change implementation || integrated in OOo3.0 ||
|-
! GROWTH
| Last parameter has type Logical (in Excel too) || Last parameter has type Number || || ||
|-
| ||is in subgroup Statistical Functions (in Excel too) || is in subgroup Array Functions || || ||
|-
! HYPGEOMDIST
| Optional, logical parameter to calculate "exact" or "at most" || no parameter, calculates always "exact" || || ||
|-
! INTERCEPT
| Current, "Calculates the point at which a line will intersect the y-values by using known x-values and y-values." (BTW: That is literally from Excel help.) Problems:1. It calculates no point but a single value. 2. The line does not intersect the y-values but the y-axis. 3. It does not say, that the line is the linear regression of the known values.|| || ||Mail to OASIS [http://lists.oasis-open.org/archives/office-comment/] ||
|-
! NORMDIST
| Last Parameter has type Logical and is optional || Last Parameter has type Number and is required ||Change implementation, {{Bug|100119}}|| integrated in OOo3.2||
|-
| || ||Accuracy is insufficient for x<−2 because cancellation.||New implementation with ERFC.{{Bug|69069}}, {{Bug|97091}} ||integrated in OOo3.2||
|-
! LEGACY.NORMSDIST
| "This is exactly NORMDIST(x)." Should be "This is exactly NORMDIST(x;0;1)." because mean parameter and standard deviation parameter are not optional.|| || ||correct in draft 22a of ODFF ||
|-
| || ||Accuracy is insufficient for x<−2 because cancellation.||New implementation with ERFC. {{Bug|69069}}, {{Bug|97091}}|| integrated in OOo3.2||
|-
! LOGNORMDIST
| Four parameters, all but first parameter are optional ||Three parameters, all required||Change implementation {{Bug|100119}}|| integrated in OOo3.2 ||
|-
! PERCENTRANK
| It has an optional parameter ''Significance''||not yet implemented|| || ||
|-
! PHI
| Description is unclear. PHI(x)=NORMDIST(x;0;1;FALSE()). It is the density function of the standard normal distribution || || ||correct in draft 22a of ODFF ||
|-
! POISSON
| Parameter ''Cumulative'' has type Logical and is optional.|| Parameter 'C' is required. 'C'=0 is density function, all others are cumulative||change in calc {{Bug|96837}}|| integrated in OOo3.1||
|-
! QUARTILE
| Example calculates with ''Quart=1.5'' although there is a constraint INT(Quart)=Quart|| || ||Mail to OASIS [http://lists.oasis-open.org/archives/office-comment/]||
|-
! RANK
| Description "If not 0, Data is ranked in descending order." has to be "If not 0, Data is ranked in ascending order."|| || ||correct in draft 22a of ODFF ||
|-
! SKEWP
| || not yet implemented|| || ||
|-
! STDEVA
| The text "cells with text are converted to 0;" conflicts with "The handling of strings is implementation defined."|| || ||Mail to OASIS [http://lists.oasis-open.org/archives/office-comment/] ||
|-
! TDIST
| In Draft 26 it was corrected to show the cumulative function. In addition it was renamed to LEGACY.TDIST to be consistent with other right tailed distributions. || Calc (and Excel) evaluates the cumulative function. ||Implementation has to be adapted.|| not started ||
|-
! TREND
| The optional parameters ''knownX'' and ''newX'' may be empty, denoted as ;;|| ''knownX'' and ''knownY'' cannot be empty|| || ||
|-
| ||Parameter ''AllowOffset'' is Logical|| Parameter is 0 or ''not 0''|| || ||
|-
! TRIMMEAN
| The limits in the definition formula are wrong. Either count i from 0, then sum from i=cutOff to n−1−cutOff, or count i from 1, then sum from i=cutOff+1 to n−cutOff || || ||correct in draft 22a of ODFF ||
|-
! TTEST
| (1) All formulas miss the degrees of freedom. It is necessary for TDIST. In case unequal variance there must be defined, whether the degrees of freedom are made integer by FLOOR or whether they remain real. (2) case paired: <math>\scriptstyle \sqrt {n-1}</math> is wrong because it is already contained in <math> s_{X_1 - X_2}</math>. (3) case equal variance: definition of s² is missing. (4) case unequal variance: definition does not meet usual definitions. In fact it is the definition for the equal variance case, with pooled variance.(5) As TDIST actually returns the values of the CDF, this formulas has to be revised together with TDIST.|| ||Corrent implementation fits to draft, no action needed. ||draft 22a of ODFF has got correct definition for type 2 and 3, type 1 has got an error, which will be corrected soon. ||
|-
! WEIBULL
| Parameter ''Cumulative'' is logical.||Parameter is 0 or ''not 0''|| || ||
|-
| ||Alpha and Beta are exchanged in the formula, compared with the current implementation in OOo, Excel and Gnumeric.|| || ||Draft 22a of ODFF has got a better description. ||
|-
! ZTEST
| || Calc calculates z-value wrong. Read discussion in {{Bug|90759}} || Correct sigma-bug|| integrated in OOo3.2||
|-
| || || Uses instable algorithm for standard deviation.||Change to stable version or use STDEV directly.|| ||
|-
| || Calculates <math>\scriptstyle 1-P( -|z| \le Z \le |z|)</math>|| Beside the sigma-bug OOo calculates <math>\scriptstyle 1-P( Z \le z)</math> for z>0 and <math>\scriptstyle P( Z \le |z|)</math> for z<0|| || Mail to OASIS [http://lists.oasis-open.org/archives/office-comment/] ||
|-
! Functionname
| ODF || Calc || Action || Progress ||
|}

=== Other Functions ===

{| class="wikitable"
|-
! Function !! ODFv1.2 !! CALC !! Action !! Progress ||
|-
! CEILING
| Already second parameter (significance) is optional. || Only third parameter (mode) is optional. || Change in Calc and write additional parameter to file for backwards compatibility (not that easy because the actual value depends on the first parameter). Until then let at least the interpreter handle it as optional. || - ||
|-
! FLOOR
| Already second parameter (significance) is optional. || Only third parameter (mode) is optional. || Change in Calc and write additional parameter to file for backwards compatibility (not that easy because the actual value depends on the first parameter). Until then let at least the interpreter handle it as optional. || - ||
|-
! GCD
| "Return the largest value that can be evenly divided (no remainder) into the given numbers." Should be "Return the largest value that can divide the given numbers evenly (no remainder)."|| - || - || Text is correct since OpenFormula draft 22.||
|-
! LOG
| Base (third parameter) is optional with default 10.||All parameters are required.||Change in Calc||Done (Lvyue) {{Bug|96835}}, integrated to OOo3.1||
|-
! ISOWEEKNUM
| || not implemented yet || || ||
|-
! DATEDIF
| || not implemented yet || implementation by Winfried Donkers and Eike Rathke || implemented in LibO 3.6.0 ||
|-
! PDURATION
| || not implemented yet || || ||
|-
! COUNTIFS
| || implemented || implementation by Marina (makkica) ||{{bug|90269}} integrated in LibO 4.0 ||
|-
! NUMBERVALUE
| || not implemented yet || || ||
|-
! XOR
| || implemented || implementation by Marina (makkica) || implemented in LibO 4.0 by Winfried Donkers ||
|-
! IFERROR
| || not implemented yet || implementation by Winfried Donkers and Eike Rathke ||{{bug|92677}} implemented in LibO 4.0 ||
|-
! IFNA
| || not implemented yet || implementation by Winfried Donkers and Eike Rathke ||{{bug|92677}} implemented in LibO 4.0 ||
|-
! CSC
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111413}} integrated in LibO 3.5.0 ||
|-
! CSCH
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111413}} integrated in LibO 3.5.0 ||
|-
! SEC
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111413}} integrated in LibO 3.5.0 ||
|-
! SECH
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111413}} integrated in LibO 3.5.0 ||
|-
! SUMIFS
| || implemented || implementation by Marina (makkica) ||{{bug|95144}} integrated in LibO 4.0 ||
|-
! BITAND
| || not implemented yet || implementation by Wolfgang (wope)||{{bug|111519}} implemented in LibO 3.5.0 ||
|-
! BITLSHIFT
| || not implemented yet || implementation by Wolfgang (wope)||{{bug|111519}} implemented in LibO 3.5.0 ||
|-
! BITOR
| || not implemented yet || implementation by Wolfgang (wope)||{{bug|111519}} implemented in LibO 3.5.0 ||
|-
! BITRSHIFT
| || not implemented yet || implementatin by Wolfgang (wope)||{{bug|111519}} implemented in LibO 3.5.0 ||
|-
! BITXOR
| || not implemented yet || implementation by Wolfgang (wope)||{{bug|111519}} implemented in LibO 3.5.0 ||
|-
! FINDB
| || not implemented yet || || ||
|-
! LEFTB
| || not implemented yet || || ||
|-
! LENB
| || not implemented yet || || ||
|-
! MIDB
| || not implemented yet || || ||
|-
! REPLACEB
| || not implemented yet || || ||
|-
! RIGHTB
| || not implemented yet || || ||
|-
! SEARCHB
| || not implemented yet || || ||
|-
! IMCSCH
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||
|-
! IMSEC
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||
|-
! IMSECH
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||
|-
! IMSINH
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||
|-
! IMCOSH
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||
|-
! IMTAN
| || not implemented yet ||Implementation by [[User:Regina|Regina]]||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||
|-
! IMCOT
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||
|-
! IMCSC
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||
|-
! Functionname
| ODF || Calc || Action || Progress ||
|}

----

[[Category:Calc]]

[[Category:To-Do]]

Calc/ODFF Implementation/Examine functions

2012-08-26T14:56:19Z

ErAck: /* Other Functions */ implemented/integrated in LibO 3.5.0/3.6.0

== Examine Changes in Functions for ODFv1.2 ==
This is a collection of the differences I found and what I know is already done or in progress. I also note, when I found problems in the draft spec itself. You are invited to add your observations. [[User:Regina|Regina]] 19:40, 10 October 2008 (CEST)

=== Statistical Functions ===

{| class="wikitable"
|-
! Function !! ODFv1.2 !! CALC !! Action !! Progress ||

|-
! AVERAGEIF
| || implemented || implementation by Marina (makkica) ||{{bug|101466}} ||

|-
! AVERAGEIFS
| || not implemented yet || implementation by Marina (makkica) ||{{bug|101466}} ||

|-
! BETADIST
| Draft Spec misses faktor 1/(b-a) in densitiy case || not yet implemented || Inform [[User:ErAck|Eike Rathke]] ||correct in draft 22a of ODFF ||
|-
| ||Has density case and optional parameter, to choose between density and cumulative || not yet implemented || expand function to density case and additional parameter,tracked in {{Bug|91547}} || integrated in OOo3.2||

|-
! BINOMDIST
| Parameter C is integer with constraint to 0 and 1. It should be Logical as in other distributions || C=0 is density, all other values of C are treated as cumulative || || ||

|-
! LEGACY.CHIDIST
| Returns 1 for x <0 || x < 0 returns Err:502 || expand domain to x < 0 internal,patch in {{Bug|94555}} ||integrated in OOo3.2 ||

|-
! CHISQDIST
| density function and cumulative left tail of chi-square distribution || not yet implemented || prepare Implementation, patch in {{Bug|94555}} || integrated in OOo3.2 ||

|-
! CHISQINV
| inverse of CHISQDIST(...TRUE()) || not yet implemented || prepare Implementation, patch in {{Bug|94555}} || integrated in OOo3.2 ||

|-
! EXPONDIST
| Parameter ''Cumulative'' has type Logical and is optional. || Last Parameter C has type Number and is not optional. C=0 returns denisity, other values for C return cumulative function. || || ||

|-
! FDIST
| density function and cumulative left tail of F-distribution || not yet implemented|| prepare for implementation || first draft, depends on BETADIST {{Bug|91547}} ||
|-
| || || Name conflicts with actual FDIST, which calculates right tail. OOo2.4 does not handle namespace correctly and takes new FDIST as old one || get new UI-name || have brought problem to dev@sc ||

|-
! FINV
| inverse of new FDIST || not yet implemented || || ||
|-
| || || Name conflicts with actual FINV, which calculates inverse for right tail. || get new UI-name || ||

|-
! GAMMA
| Parameter is constraint to >= 0 || Gamma is definied for all real numbers, but non-positive integers || Inform [[User:ErAck|Eike Rathke]] || ||
|-
| || ||not yet implemented || prepare implementation using full domain. Add UI texts. patch in {{Bug|94555}} || integrated in OOo3.2||
|-
| ||is in subgroup Mathematical functions || will go to subgroup Statistical functions || ||Mail to OASIS [http://lists.oasis-open.org/archives/office-comment/] ||

|-
! GAMMALN
| is in subgroup Mathematical Functions || is in subgroup Statistical Functions || || ||

|-
! GAMMADIST
| Last Parameter has type Logical || Last Parameter has type Number || Change type internal to bool. Change UI texts. patch in {{Bug|94555}} || integrated in OOo3.2 ||
|-
| ||Domain for Parameter x includes x < 0 || x < 0 returns Err:502 in OOo2.* || Change implementation || integrated in OOo3.0 ||

|-
! GROWTH
| Last parameter has type Logical (in Excel too) || Last parameter has type Number || || ||
|-
| ||is in subgroup Statistical Functions (in Excel too) || is in subgroup Array Functions || || ||

|-
! HYPGEOMDIST
| Optional, logical parameter to calculate "exact" or "at most" || no parameter, calculates always "exact" || || ||

|-
! INTERCEPT
| Current, "Calculates the point at which a line will intersect the y-values by using known x-values and y-values." (BTW: That is literally from Excel help.) Problems:1. It calculates no point but a single value. 2. The line does not intersect the y-values but the y-axis. 3. It does not say, that the line is the linear regression of the known values.|| || ||Mail to OASIS [http://lists.oasis-open.org/archives/office-comment/] ||

|-
! NORMDIST
| Last Parameter has type Logical and is optional || Last Parameter has type Number and is required ||Change implementation, {{Bug|100119}}|| integrated in OOo3.2||
|-
| || ||Accuracy is insufficient for x<−2 because cancellation.||New implementation with ERFC.{{Bug|69069}}, {{Bug|97091}} ||integrated in OOo3.2||

|-
! LEGACY.NORMSDIST
| "This is exactly NORMDIST(x)." Should be "This is exactly NORMDIST(x;0;1)." because mean parameter and standard deviation parameter are not optional.|| || ||correct in draft 22a of ODFF ||
|-
| || ||Accuracy is insufficient for x<−2 because cancellation.||New implementation with ERFC. {{Bug|69069}}, {{Bug|97091}}|| integrated in OOo3.2||

|-
! LOGNORMDIST
| Four parameters, all but first parameter are optional ||Three parameters, all required||Change implementation {{Bug|100119}}|| integrated in OOo3.2 ||

|-
! PERCENTRANK
| It has an optional parameter ''Significance''||not yet implemented|| || ||

|-
! PHI
| Description is unclear. PHI(x)=NORMDIST(x;0;1;FALSE()). It is the density function of the standard normal distribution || || ||correct in draft 22a of ODFF ||

|-
! POISSON
| Parameter ''Cumulative'' has type Logical and is optional.|| Parameter 'C' is required. 'C'=0 is density function, all others are cumulative||change in calc {{Bug|96837}}|| integrated in OOo3.1||

|-
! QUARTILE
| Example calculates with ''Quart=1.5'' although there is a constraint INT(Quart)=Quart|| || ||Mail to OASIS [http://lists.oasis-open.org/archives/office-comment/]||

|-
! RANK
| Description "If not 0, Data is ranked in descending order." has to be "If not 0, Data is ranked in ascending order."|| || ||correct in draft 22a of ODFF ||

|-
! SKEWP
| || not yet implemented|| || ||

|-
! STDEVA
| The text "cells with text are converted to 0;" conflicts with "The handling of strings is implementation defined."|| || ||Mail to OASIS [http://lists.oasis-open.org/archives/office-comment/] ||

|-
! TDIST
| In Draft 26 it was corrected to show the cumulative function. In addition it was renamed to LEGACY.TDIST to be consistent with other right tailed distributions. || Calc (and Excel) evaluates the cumulative function. ||Implementation has to be adapted.|| not started ||

|-
! TREND
| The optional parameters ''knownX'' and ''newX'' may be empty, denoted as ;;|| ''knownX'' and ''knownY'' cannot be empty|| || ||
|-
| ||Parameter ''AllowOffset'' is Logical|| Parameter is 0 or ''not 0''|| || ||

|-
! TRIMMEAN
| The limits in the definition formula are wrong. Either count i from 0, then sum from i=cutOff to n−1−cutOff, or count i from 1, then sum from i=cutOff+1 to n−cutOff || || ||correct in draft 22a of ODFF ||

|-
! TTEST
| (1) All formulas miss the degrees of freedom. It is necessary for TDIST. In case unequal variance there must be defined, whether the degrees of freedom are made integer by FLOOR or whether they remain real. (2) case paired: <math>\scriptstyle \sqrt {n-1}</math> is wrong because it is already contained in <math> s_{X_1 - X_2}</math>. (3) case equal variance: definition of s² is missing. (4) case unequal variance: definition does not meet usual definitions. In fact it is the definition for the equal variance case, with pooled variance.(5) As TDIST actually returns the values of the CDF, this formulas has to be revised together with TDIST.|| ||Corrent implementation fits to draft, no action needed. ||draft 22a of ODFF has got correct definition for type 2 and 3, type 1 has got an error, which will be corrected soon. ||

|-
! WEIBULL
| Parameter ''Cumulative'' is logical.||Parameter is 0 or ''not 0''|| || ||
|-
| ||Alpha and Beta are exchanged in the formula, compared with the current implementation in OOo, Excel and Gnumeric.|| || ||Draft 22a of ODFF has got a better description. ||

|-
! ZTEST
| || Calc calculates z-value wrong. Read discussion in {{Bug|90759}} || Correct sigma-bug|| integrated in OOo3.2||
|-
| || || Uses instable algorithm for standard deviation.||Change to stable version or use STDEV directly.|| ||
|-
| || Calculates <math>\scriptstyle 1-P( -|z| \le Z \le |z|)</math>|| Beside the sigma-bug OOo calculates <math>\scriptstyle 1-P( Z \le z)</math> for z>0 and <math>\scriptstyle P( Z \le |z|)</math> for z<0|| || Mail to OASIS [http://lists.oasis-open.org/archives/office-comment/] ||

|-
! Functionname
| ODF || Calc || Action || Progress ||
|}

=== Other Functions ===

{| class="wikitable"

|-
! Function !! ODFv1.2 !! CALC !! Action !! Progress ||

|-
! CEILING
| Already second parameter (significance) is optional. || Only third parameter (mode) is optional. || Change in Calc and write additional parameter to file for backwards compatibility (not that easy because the actual value depends on the first parameter). Until then let at least the interpreter handle it as optional. || - ||

|-
! FLOOR
| Already second parameter (significance) is optional. || Only third parameter (mode) is optional. || Change in Calc and write additional parameter to file for backwards compatibility (not that easy because the actual value depends on the first parameter). Until then let at least the interpreter handle it as optional. || - ||

|-
! GCD
| "Return the largest value that can be evenly divided (no remainder) into the given numbers." Should be "Return the largest value that can divide the given numbers evenly (no remainder)."|| - || - || Text is correct since OpenFormula draft 22.||

|-
! LOG
| Base (third parameter) is optional with default 10.||All parameters are required.||Change in Calc||Done (Lvyue) {{Bug|96835}}, integrated to OOo3.1||

|-
! ISOWEEKNUM
| || not implemented yet || || ||

|-
! DATEDIF
| || not implemented yet || implementation by Winfried Donkers and Eike Rathke || implemented in LibO 3.6.0 ||

|-
! PDURATION
| || not implemented yet || || ||

|-
! COUNTIFS
| || not implemented yet || implementation by Marina (makkica) ||{{bug|90269}}||

|-
! NUMBERVALUE
| || not implemented yet || || ||

|-
! XOR
| || implemented || implementation by Marina (makkica) || ||

|-
! IFERROR
| || not implemented yet || implementation by Marina (makkica) ||{{bug|92677}} ||

|-
! IFNA
| || not implemented yet || implementation by Marina (makkica) ||{{bug|92677}} ||

|-
! CSC
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111413}} integrated in LibO 3.5.0 ||

|-
! CSCH
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111413}} integrated in LibO 3.5.0 ||

|-
! SEC
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111413}} integrated in LibO 3.5.0 ||

|-
! SECH
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111413}} integrated in LibO 3.5.0 ||

|-
! SUMIFS
| || not implemented yet || implementation by Marina (makkica) ||{{bug|95144}} ||

|-
! BITAND
| || not implemented yet || implementation by Wolfgang (wope)||{{bug|111519}} implemented in LibO 3.5.0 ||

|-
! BITLSHIFT
| || not implemented yet || implementation by Wolfgang (wope)||{{bug|111519}} implemented in LibO 3.5.0 ||

|-
! BITOR
| || not implemented yet || implementation by Wolfgang (wope)||{{bug|111519}} implemented in LibO 3.5.0 ||

|-
! BITRSHIFT
| || not implemented yet || implementatin by Wolfgang (wope)||{{bug|111519}} implemented in LibO 3.5.0 ||

|-
! BITXOR
| || not implemented yet || implementation by Wolfgang (wope)||{{bug|111519}} implemented in LibO 3.5.0 ||

|-
! FINDB
| || not implemented yet || || ||

|-
! LEFTB
| || not implemented yet || || ||

|-
! LENB
| || not implemented yet || || ||

|-
! MIDB
| || not implemented yet || || ||

|-
! REPLACEB
| || not implemented yet || || ||

|-
! RIGHTB
| || not implemented yet || || ||

|-
! SEARCHB
| || not implemented yet || || ||

|-
! IMCSCH
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||

|-
! IMSEC
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||

|-
! IMSECH
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||

|-
! IMSINH
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||

|-
! IMCOSH
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||

|-
! IMTAN
| || not implemented yet ||Implementation by [[User:Regina|Regina]]||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||

|-
! IMCOT
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||

|-
! IMCSC
| || not implemented yet ||Implementation by [[User:Regina|Regina]] ||Patch in {{bug|111609}} integrated in LibO 3.6.0 ||

|-
! Functionname
| ODF || Calc || Action || Progress ||
|}

----
[[Category:Calc]]
[[Category:To-Do]]

User:ErAck

2011-11-02T02:23:05Z

ErAck: reality check

{| align="right"
| [[Image:ErAck_128x128.png‎]]
|}
* Name: Eike Rathke
* Nick: erAck
* OOo: er, erack
* Areas of expertise:
** [[Calc]] spreadsheet application compiler, interpreter, engine
** number formatter
** [[I18npool|internationalization (i18n)]] and locale data, '''not''' localization (l10n)
*** .signature: number formatter stricken i18n transpositionizer
* IRC: irc://irc.freenode.net/#dev.openoffice.org
* Private URL: http://www.erack.de/
* μBlog: http://identi.ca/erack
* Blog: http://jroller.com/erAck
* Location: Hamburg, Germany
* Timezone: UTC+1 with DST rule TZ=CET-1CEST-2,M3.5.0/2,M10.5.0/3

== lately worked on ==

* [http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula OASIS OpenDocument file format formula specification], ODFF aka OpenFormula.
* mentorship for implementors, review of patches and integration.
* Bits of formula compiler and interpreter changes.


== Work flow ==

My personal [[/WorkFlow| work flow and environment]] when working on code.

== Wiki stuff ==

Edit help: [[:Category:Help]]

=== Code syntax highlighting ===

Code syntax highlighting is possible with
<pre>
<source lang="$LANGUAGE">
...
</source>
</pre>

where ''$LANGUAGE'' is one of this list that was dynamically generated using <code><nowiki><source lang="invalid"></source></nowiki></code>

<source lang="invalid"></source>

'''NOTE:''' the old SwinBrain CodeSyntaxHighlight does not work anymore since the wiki upgrade on 2008-02-14
<pre>
<code>[language]
...
</code>
</pre>
produces rubbish now!

=== Templates ===

<code><nowiki>{{Documentation/Caution| Do or don't.}}</nowiki></code>
{{Documentation/Caution| Do or don't.}}

<code><nowiki>{{Documentation/Note| Note that.}}</nowiki></code>
{{Documentation/Note| Note that.}}

<code><nowiki>{{Template:Documentation/Tip| Tip.}}</nowiki></code>
{{Template:Documentation/Tip| Tip.}}

{{LinkBanner}}

For many more see
* [[Documentation/Dashboard/Wiki_Editing_Policy#List_of_Existing_Documentation_Templates]]
* [[:Category:Wiki_Templates]], especially
** [[:Category:Formatting_templates]]
** [[:Category:Wiki_Templates_Expressing_Quality]]
* [[Special:Mostlinkedtemplates]]

=== Pretty Sortable Table ===

<pre>
{| class="prettytable sortable"
|-
! Column 1 Header || Column 2 Header
|-
| some data column 1 || and some data column 2
|-
| more data column 1 || even more data column 2
|}
</pre>

{| class="prettytable sortable"
|-
! Column 1 Header || Column 2 Header
|-
| some data column 1 || and some data column 2
|-
| more data column 1 || even more data column 2
|}

=== new topic ===
<nowiki>Insert non-formatted text here</nowiki>

User:ErAck

2011-07-30T18:39:37Z

ErAck:

{| align="right"
| [[Image:ErAck_128x128.png‎]]
|}
* Name: Eike Rathke
* Nick: erAck
* OOo: er, erack
* Working on:
** [[Calc]] spreadsheet application compiler, interpreter, engine
** number formatter
** [[I18npool|internationalization (i18n)]] and locale data, '''not''' localization (l10n)
*** .signature: number formatter stricken i18n transpositionizer
* IRC: irc://irc.freenode.net/#dev.openoffice.org
* Email Calc developers: [mailto:dev@sc.openoffice.org dev@sc.openoffice.org] mailing list
* Email personal: [mailto:erack@openoffice.org erack@openoffice.org]
* Private URL: http://www.erack.de/
* μBlog: http://identi.ca/erack
* Blog: http://jroller.com/erAck
* Location: Hamburg, Germany
* Timezone: UTC+1 with DST rule TZ=CET-1CEST-2,M3.5.0/2,M10.5.0/3

== currently working on ==

* [http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula OASIS OpenDocument file format formula specification], ODFF aka OpenFormula.
* mentorship for implementors, review of patches and integration.
* Bits of formula compiler and interpreter changes.


== Work flow ==

My personal [[/WorkFlow| work flow and environment]] when working on code.

== Wiki stuff ==

Edit help: [[:Category:Help]]

=== Code syntax highlighting ===

Code syntax highlighting is possible with
<pre>
<source lang="$LANGUAGE">
...
</source>
</pre>

where ''$LANGUAGE'' is one of this list that was dynamically generated using <code><nowiki><source lang="invalid"></source></nowiki></code>

<source lang="invalid"></source>

'''NOTE:''' the old SwinBrain CodeSyntaxHighlight does not work anymore since the wiki upgrade on 2008-02-14
<pre>
<code>[language]
...
</code>
</pre>
produces rubbish now!

=== Templates ===

<code><nowiki>{{Documentation/Caution| Do or don't.}}</nowiki></code>
{{Documentation/Caution| Do or don't.}}

<code><nowiki>{{Documentation/Note| Note that.}}</nowiki></code>
{{Documentation/Note| Note that.}}

<code><nowiki>{{Template:Documentation/Tip| Tip.}}</nowiki></code>
{{Template:Documentation/Tip| Tip.}}

{{LinkBanner}}

For many more see
* [[Documentation/Dashboard/Wiki_Editing_Policy#List_of_Existing_Documentation_Templates]]
* [[:Category:Wiki_Templates]], especially
** [[:Category:Formatting_templates]]
** [[:Category:Wiki_Templates_Expressing_Quality]]
* [[Special:Mostlinkedtemplates]]

=== Pretty Sortable Table ===

<pre>
{| class="prettytable sortable"
|-
! Column 1 Header || Column 2 Header
|-
| some data column 1 || and some data column 2
|-
| more data column 1 || even more data column 2
|}
</pre>

{| class="prettytable sortable"
|-
! Column 1 Header || Column 2 Header
|-
| some data column 1 || and some data column 2
|-
| more data column 1 || even more data column 2
|}

=== new topic ===
<nowiki>Insert non-formatted text here</nowiki>

User:ErAck

2011-07-30T18:38:55Z

ErAck: update to reality

{| align="right"
| [[Image:ErAck_128x128.png‎]]
|}
* Name: Eike Rathke
* Nick: erAck
* OOo: er
* Working on:
** [[Calc]] spreadsheet application compiler, interpreter, engine
** number formatter
** [[I18npool|internationalization (i18n)]] and locale data, '''not''' localization (l10n)
*** .signature: number formatter stricken i18n transpositionizer
* IRC: irc://irc.freenode.net/#dev.openoffice.org
* Email Calc developers: [mailto:dev@sc.openoffice.org dev@sc.openoffice.org] mailing list
* Email personal: [mailto:erack@openoffice.org erack@openoffice.org]
* Private URL: http://www.erack.de/
* μBlog: http://identi.ca/erack
* Blog: http://jroller.com/erAck
* Location: Hamburg, Germany
* Timezone: UTC+1 with DST rule TZ=CET-1CEST-2,M3.5.0/2,M10.5.0/3

== currently working on ==

* [http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula OASIS OpenDocument file format formula specification], ODFF aka OpenFormula.
* mentorship for implementors, review of patches and integration.
* Bits of formula compiler and interpreter changes.


== Work flow ==

My personal [[/WorkFlow| work flow and environment]] when working on code.

== Wiki stuff ==

Edit help: [[:Category:Help]]

=== Code syntax highlighting ===

Code syntax highlighting is possible with
<pre>
<source lang="$LANGUAGE">
...
</source>
</pre>

where ''$LANGUAGE'' is one of this list that was dynamically generated using <code><nowiki><source lang="invalid"></source></nowiki></code>

<source lang="invalid"></source>

'''NOTE:''' the old SwinBrain CodeSyntaxHighlight does not work anymore since the wiki upgrade on 2008-02-14
<pre>
<code>[language]
...
</code>
</pre>
produces rubbish now!

=== Templates ===

<code><nowiki>{{Documentation/Caution| Do or don't.}}</nowiki></code>
{{Documentation/Caution| Do or don't.}}

<code><nowiki>{{Documentation/Note| Note that.}}</nowiki></code>
{{Documentation/Note| Note that.}}

<code><nowiki>{{Template:Documentation/Tip| Tip.}}</nowiki></code>
{{Template:Documentation/Tip| Tip.}}

{{LinkBanner}}

For many more see
* [[Documentation/Dashboard/Wiki_Editing_Policy#List_of_Existing_Documentation_Templates]]
* [[:Category:Wiki_Templates]], especially
** [[:Category:Formatting_templates]]
** [[:Category:Wiki_Templates_Expressing_Quality]]
* [[Special:Mostlinkedtemplates]]

=== Pretty Sortable Table ===

<pre>
{| class="prettytable sortable"
|-
! Column 1 Header || Column 2 Header
|-
| some data column 1 || and some data column 2
|-
| more data column 1 || even more data column 2
|}
</pre>

{| class="prettytable sortable"
|-
! Column 1 Header || Column 2 Header
|-
| some data column 1 || and some data column 2
|-
| more data column 1 || even more data column 2
|}

=== new topic ===
<nowiki>Insert non-formatted text here</nowiki>

ICU/bugs and patches

2011-07-20T11:38:57Z

ErAck: updated version 4.0.1 for OOo 3.2

List of patches applied to OOo's [[ICU]] module (currently ICU v4.0.1 for OOo >= 3.2) and bugs and patches submitted to [http://bugs.icu-project.org/trac/ ICU trac], the ICU bug tracking system.

If you really ''have'' to apply a patch to ICU to make things work, '''please''' submit that patch to ''ICU trac'', so the next version of ICU will include the changes, and list your patch with ICU trac ID here. We strive for being able to build against an unpatched ICU, so that configure --with-system-icu will be possible without loosing functionality.

__TOC__

== reverted upstream changeset for tracker ticket 6249 ==

An upstream change (for ICU's [http://bugs.icu-project.org/trac/ticket/6249 tracker ticket 6249]) introduced a regression ([http://www.openoffice.org/issues/show_bug.cgi?id=99241 OOo issue 99241]). Reverting that upstream change (ICU's [http://bugs.icu-project.org/trac/changeset/24081 changeset 24041]) solves the problem. Updated ICU ticket 6249 accordingly.

== add RPATH for URE ==

The patch changes RPATH from <code>$ORIGIN</code> to <code>$ORIGIN:$ORIGIN/../ure-link/lib</code> because libicu*.so are linked against libstdc++.so.6 and libgcc_s.so.1 that are distributed with the new layered [[Uno/Runtime_Environment | UNO Runtime Environment (URE)]]. This to ensure that the libraries are found there in case they are not already loaded.

However, one could argue that the libraries are already loaded when ICU is pulled in, which almost certainly is the case for libstdc++, and probably also for the libgcc_s GCC support library, but that for some machine models may contain some rarely used symbols such that it wasn't loaded but ICU needs it. This is very unlikely though, but you never know..

Anyway, the patch certainly is nothing to upstream, hence no ICU trac ID.

We'll keep thinking about another solution.

OOo developer: Stephan Bergmann <sb>

== MinGW platform ==

Patch to be able to build ICU on the Minimalist GNU for Windows platform. 
See [http://www.openoffice.org/nonav/issues/showattachment.cgi/57880/icu_4_0_icu_mingw.patch icu_4_0_icu_mingw.patch] attached to {{Bug|96100}}. 
Introduced with {{CWS|mingwport16}} for OOo3.1

OOo port maintainer: Takashi Ono <tono>

Filed with ICU as http://bugs.icu-project.org/trac/ticket/6638
[[Category:I18n]]
small text

Adding a new language or locale

2011-04-15T21:07:39Z

ErAck: adapted bugzilla URL to new system

If you plan a new localization of OOo and want to have '''a new language or locale'''
added, some very basic assignments and mappings have to be done to make it
known to the code and the build system.

* The numeric Microsoft® locale identifier (LCID), here informally usually referred as ''MS-LangID'', for attribution used by the core code and also needed for import and export of MS-Office document file formats.
* The ISO 639 language code and ISO 3166 country code for [[:Category:I18n|internationalization]], [[API]] and [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office OpenDocument Format (ODF)] file storage.
* A mapping between those two.
* A language list box entry.
* Whether the language uses complex text layout (CTL).
* Whether the language is written from right to left (RTL).
* An entry for the build system to build the UI localization.

If your language/locale is already present in one of the language list boxes
of the font attribution dialog (Format → Character → Font), probably
nothing needs to be done, except maybe an entry to the build system needs to
be added. If in doubt, just ask on the ''dev@l10n'' mailing list.

To have a LangID assigned and the necessary mappings and entries added, please
first login to the OOo website and then submit an issue of type Enhancement to
Component ''l10n'' and Subcomponent ''i18npool'' by using
[http://openoffice.org/bugzilla/enter_bug.cgi?product=l10n&component=i18npool&cf_bug_type=ENHANCEMENT&rep_platform=All&op_sys=All&version=current&assigned_to=er@openoffice.org this URL].

Your requested language usually will be added for the next minor release of OOo.

Just state that you want Language (Country) [xxx-YY] added, and if it is CTL
or RTL please say so. The xxx here is the ISO 639-1 (two characters codes,
preferred if one exists for the language) or 639-2/639-3 (three characters
codes) language code and YY the ISO 3166 country code. If you don't know them
don't mind, the responsible i18n developer (assigned issue owner) will look
them up anyway. The best source is [http://www.sil.org/iso639-3/codes.asp SIL ISO 639-3].

If you happen to know that MS already defined a language identifier for your
language/locale you may state that as well. URLs pointing to relevant
information can be found at
[http://www.erack.de/bookmarks/D.html#GIL_MS erAck's link collection], try to
pick the ''NLS information page'' first. Unfortunately MS published several
resources with only partial information instead of consolidating all on just
one single page. They also change their URLs from time to time, which is why
this page here doesn't directly link to them. Again, it doesn't matter if you
don't include the ID, the i18n developer will look it up anyway and assign an
ID unique within OOo if it doesn't already exist.

Adding a language to the language list box makes it available for character
attribution and spell-checking. Availability of spell checker, hyphenation and
thesaurus of course depends on the installed dictionaries. To be able to fully
support it as a locale, including number formats and calendar data, and having
it selectable as default document language we would need a locale data file.
Please see [[How to submit new Locale Data]] for details.

[[Category:Localization]]
[[Category:I18n]]

How to submit new Locale Data

2011-04-15T21:05:18Z

ErAck: /* General Information */

== General Information ==

To be able to fully support a [[Adding_a_new_language_or_locale|new language or locale]]
or an already existing but not yet fully supported language/country
combination as a locale, including number formats and calendar data, and
having it selectable as default document language, OOo needs a locale data
file.

Locale data files can quite easily be generated with the generator
available at http://www.it46.se/localegen/

For technical details and semantics of elements please see the
[http://www.it46.se/localegen/docs/index.php generator's documentation]
and the comments in the
[http://hg.services.openoffice.org/DEV300/file/tip/i18npool/source/localedata/data/locale.dtd locale data DTD file]
and as a sample locale data file for example the
[http://hg.services.openoffice.org/DEV300/file/tip/i18npool/source/localedata/data/en_US.xml en_US locale]

Note that several locale data elements may be inherited from another locale's
data by means of the ''ref="..."'' attribute if they share identical data,
which may come handy if locales are to be created for the same language but
different countries that differ only in a few elements such as currency
symbols. This would have to be done manually though. Doing so also reduces the
memory footprint needed during runtime when the data libraries are loaded.

If you want to create and contribute a locale data file for your locale, you
can either

* Create the locale data file using the generator, login to the OOo website and then submit a new issue using [http://openoffice.org/bugzilla/enter_bug.cgi?product=l10n&component=localedata&cf_bug_type=ENHANCEMENT&rep_platform=All&op_sys=All&version=current&assigned_to=er@openoffice.org this URL], where you say that it is available. We would then contact Alberto, whom you granted the right to contribute your data, see http://www.it46.se/localegen/copyright.php

* Or create the locale data file, login to the OOo website and then submit a new issue using [http://openoffice.org/bugzilla/enter_bug.cgi?product=l10n&component=localedata&cf_bug_type=PATCH&rep_platform=All&op_sys=All&version=current&assigned_to=er@openoffice.org this URL], and attach the generated file to that issue. Please note that to integrate code or data contributed we need a signed [[Oracle Contributor Agreement]] form (OCA) filled-out. This would be the preferred way if you plan to do other contributions that would need a signed OCA as well. 

If you came to this page because an already existing issue pointed you here to
submit new locale data, you don't have to create a new issue using one of the
above URLs of course, attach the locale data file to the already existing
issue instead.

== Pitfalls ==

There are a few pitfalls or things to think about when generating locale data:

=== Index Keys and Scripts ===

==== Character Range ====

In section ''H. Enumeration and Scripts'', the default ''H1. Character range for indexes''
entry is '''A-Z'''. If your language uses other characters, e.g. additionally
accented characters, or completely different characters, you probably want to
add them at the proper position. See the generator's documentation and/or the
documentation in the DTD file mentioned above for the ''LC_INDEX'' section.

==== Unicode Script ====

The preselected '''BasicLatin''' and '''Latin1Supplement''' scripts usually are
sufficient for Western European languages. If your language uses other or
completely different characters please select the appropriate Unicode
script(s). For the distribution of characters in different Unicode scripts see
[http://www.unicode.org/charts/ The Unicode Character Code Charts By Script].

=== Currency Formats ===

The generator in step 3 section ''I. Currency'' offers two list boxes,
''I6. Currency format for positive values'' and ''I7. Currency format for negative values''.
While the format for positive values defaulted to '''$1''' (currency symbol
immediately preceding the amount) may be correct, the default format for negative values
'''($1)''' (parentheses around symbol and amount, but no minus sign) almost
certainly is not for countries other than US. Please take the time and choose
the correct entries of both list boxes.

[[Category:Localization]]
[[Category:I18n]]

How to submit new Locale Data

2011-04-15T21:03:17Z

ErAck: /* General Information */ adapted bugzilla URL to new system

== General Information ==

To be able to fully support a [[Adding_a_new_language_or_locale|new language or locale]]
or an already existing but not yet fully supported language/country
combination as a locale, including number formats and calendar data, and
having it selectable as default document language, OOo needs a locale data
file.

Locale data files can quite easily be generated with the generator
available at http://www.it46.se/localegen/

For technical details and semantics of elements please see the
[http://www.it46.se/localegen/docs/index.php generator's documentation]
and the comments in the
[http://hg.services.openoffice.org/DEV300/file/tip/i18npool/source/localedata/data/locale.dtd locale data DTD file]
and as a sample locale data file for example the
[http://hg.services.openoffice.org/DEV300/file/tip/i18npool/source/localedata/data/en_US.xml en_US locale]

Note that several locale data elements may be inherited from another locale's
data by means of the ''ref="..."'' attribute if they share identical data,
which may come handy if locales are to be created for the same language but
different countries that differ only in a few elements such as currency
symbols. This would have to be done manually though. Doing so also reduces the
memory footprint needed during runtime when the data libraries are loaded.

If you want to create and contribute a locale data file for your locale, you
can either

* Create the locale data file using the generator, login to the OOo website and then submit a new issue using [http://openoffice.org/bugzilla/enter_bug.cgi?product=l10n&component=localedata&cf_bug_type=ENHANCEMENT&rep_platform=All&op_sys=All&version=current&assigned_to=er@openoffice.org this URL], where you say that it is available. We would then contact Alberto, whom you granted the right to contribute your data, see http://www.it46.se/localegen/copyright.php

* Or create the locale data file, login to the OOo website and then submit a new issue using [http://openoffice.org/bugzilla/enter_bug.cgi?product=l10n&component=localedata&cf_bug_type=ENHANCEMENT&rep_platform=All&op_sys=All&version=current&assigned_to=er@openoffice.org this URL], and attach the generated file to that issue. Please note that to integrate code or data contributed we need a signed [[Oracle Contributor Agreement]] form (OCA) filled-out. This would be the preferred way if you plan to do other contributions that would need a signed OCA as well. 

If you came to this page because an already existing issue pointed you here to
submit new locale data, you don't have to create a new issue using one of the
above URLs of course, attach the locale data file to the already existing
issue instead.

== Pitfalls ==

There are a few pitfalls or things to think about when generating locale data:

=== Index Keys and Scripts ===

==== Character Range ====

In section ''H. Enumeration and Scripts'', the default ''H1. Character range for indexes''
entry is '''A-Z'''. If your language uses other characters, e.g. additionally
accented characters, or completely different characters, you probably want to
add them at the proper position. See the generator's documentation and/or the
documentation in the DTD file mentioned above for the ''LC_INDEX'' section.

==== Unicode Script ====

The preselected '''BasicLatin''' and '''Latin1Supplement''' scripts usually are
sufficient for Western European languages. If your language uses other or
completely different characters please select the appropriate Unicode
script(s). For the distribution of characters in different Unicode scripts see
[http://www.unicode.org/charts/ The Unicode Character Code Charts By Script].

=== Currency Formats ===

The generator in step 3 section ''I. Currency'' offers two list boxes,
''I6. Currency format for positive values'' and ''I7. Currency format for negative values''.
While the format for positive values defaulted to '''$1''' (currency symbol
immediately preceding the amount) may be correct, the default format for negative values
'''($1)''' (parentheses around symbol and amount, but no minus sign) almost
certainly is not for countries other than US. Please take the time and choose
the correct entries of both list boxes.

[[Category:Localization]]
[[Category:I18n]]

Cpp Coding Standards/SECURITY/IntOver

2011-03-24T15:10:17Z

ErAck: update external URL

Be aware that integers have limited range – not properly checking valid input ranges before doing integer arithmetic, or assigning to other integer types of insufficient range, will lead to overflows. Often, integer overflows can be used as an attack vector to launch a subsequent buffer overflow, with the fatal consequences outlined in [[../../SECURITY#BuffOver|Security:BuffOver]].

Hints:
*Read and understand [http://www.phrack.org/archives/60/p60_0x0a_Basic%20Integer%20Overflows_by_blexim.txt this background article] on integer overflows.

*Generally, use sal_Size for buffer sizes and counts. There is usually no reason to use a signed value here (but watch out for assignments and comparisons with signed types).

*If you perform integer arithmetic, and the result is used to index arrays, calculate sizes, or as a parameter to array-new, make sure the operands fall into a safe, and well-understood range (check ''before'' you perform the calculation). Be even more careful if the input for this aritmetics is coming from an untrusted source like values read from a document by a document parsing code.

*Be extremely careful not to pass signed integers to memory allocation functions (new, alloca, rtl_allocateMemory), as they are interpreted as unsigned integers.

*Triple-check any integer-related compiler warnings, and any cast operations that silence them.

*Be aware of the [http://blogs.msdn.com/oldnewthing/archive/2004/01/29/64389.aspx implicit buffer overflows] in new[] operator (see [http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#624 C++ DR 624]).

See also [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncode/html/secure04102003.asp Reviewing Code for Integer Manipulation Vulnerabilities] (broken URL, update, anyone?).
[[Category:Coding Standards]]

How to submit new Locale Data

2011-03-14T14:33:56Z

ErAck: adapt URLs

== General Information ==

To be able to fully support a [[Adding_a_new_language_or_locale|new language or locale]]
or an already existing but not yet fully supported language/country
combination as a locale, including number formats and calendar data, and
having it selectable as default document language, OOo needs a locale data
file.

Locale data files can quite easily be generated with the generator
available at http://www.it46.se/localegen/

For technical details and semantics of elements please see the
[http://www.it46.se/localegen/docs/index.php generator's documentation]
and the comments in the
[http://hg.services.openoffice.org/DEV300/file/tip/i18npool/source/localedata/data/locale.dtd locale data DTD file]
and as a sample locale data file for example the
[http://hg.services.openoffice.org/DEV300/file/tip/i18npool/source/localedata/data/en_US.xml en_US locale]

Note that several locale data elements may be inherited from another locale's
data by means of the ''ref="..."'' attribute if they share identical data,
which may come handy if locales are to be created for the same language but
different countries that differ only in a few elements such as currency
symbols. This would have to be done manually though. Doing so also reduces the
memory footprint needed during runtime when the data libraries are loaded.

If you want to create and contribute a locale data file for your locale, you
can either

* Create the locale data file using the generator, login to the OOo website and then submit a new issue using [http://openoffice.org/bugzilla/enter_bug.cgi?version=current&component=l10n&subcomponent=localedata&issue_type=ENHANCEMENT&assigned_to=er this URL], where you say that it is available. We would then contact Alberto, whom you granted the right to contribute your data, see http://www.it46.se/localegen/copyright.php

* Or create the locale data file, login to the OOo website and then submit a new issue using [http://openoffice.org/bugzilla/enter_bug.cgi?version=current&component=l10n&subcomponent=localedata&issue_type=PATCH&assigned_to=er this URL], and attach the generated file to that issue. Please note that to integrate code or data contributed we need a signed [[Oracle Contributor Agreement]] form (OCA) filled-out. This would be the preferred way if you plan to do other contributions that would need a signed OCA as well. 

If you came to this page because an already existing issue pointed you here to
submit new locale data, you don't have to create a new issue using one of the
above URLs of course, attach the locale data file to the already existing
issue instead.

== Pitfalls ==

There are a few pitfalls or things to think about when generating locale data:

=== Index Keys and Scripts ===

==== Character Range ====

In section ''H. Enumeration and Scripts'', the default ''H1. Character range for indexes''
entry is '''A-Z'''. If your language uses other characters, e.g. additionally
accented characters, or completely different characters, you probably want to
add them at the proper position. See the generator's documentation and/or the
documentation in the DTD file mentioned above for the ''LC_INDEX'' section.

==== Unicode Script ====

The preselected '''BasicLatin''' and '''Latin1Supplement''' scripts usually are
sufficient for Western European languages. If your language uses other or
completely different characters please select the appropriate Unicode
script(s). For the distribution of characters in different Unicode scripts see
[http://www.unicode.org/charts/ The Unicode Character Code Charts By Script].

=== Currency Formats ===

The generator in step 3 section ''I. Currency'' offers two list boxes,
''I6. Currency format for positive values'' and ''I7. Currency format for negative values''.
While the format for positive values defaulted to '''$1''' (currency symbol
immediately preceding the amount) may be correct, the default format for negative values
'''($1)''' (parentheses around symbol and amount, but no minus sign) almost
certainly is not for countries other than US. Please take the time and choose
the correct entries of both list boxes.

[[Category:Localization]]
[[Category:I18n]]

Adding a new language or locale

2011-03-14T14:26:33Z

ErAck: adapt URL

If you plan a new localization of OOo and want to have '''a new language or locale'''
added, some very basic assignments and mappings have to be done to make it
known to the code and the build system.

* The numeric Microsoft® locale identifier (LCID), here informally usually referred as ''MS-LangID'', for attribution used by the core code and also needed for import and export of MS-Office document file formats.
* The ISO 639 language code and ISO 3166 country code for [[:Category:I18n|internationalization]], [[API]] and [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office OpenDocument Format (ODF)] file storage.
* A mapping between those two.
* A language list box entry.
* Whether the language uses complex text layout (CTL).
* Whether the language is written from right to left (RTL).
* An entry for the build system to build the UI localization.

If your language/locale is already present in one of the language list boxes
of the font attribution dialog (Format → Character → Font), probably
nothing needs to be done, except maybe an entry to the build system needs to
be added. If in doubt, just ask on the ''dev@l10n'' mailing list.

To have a LangID assigned and the necessary mappings and entries added, please
first login to the OOo website and then submit an issue of type Enhancement to
Component ''l10n'' and Subcomponent ''i18npool'' by using
[http://openoffice.org/bugzilla/enter_bug.cgi?version=current&component=l10n&subcomponent=i18npool&issue_type=ENHANCEMENT&assigned_to=er this URL].

Your requested language usually will be added for the next minor release of OOo.

Just state that you want Language (Country) [xxx-YY] added, and if it is CTL
or RTL please say so. The xxx here is the ISO 639-1 (two characters codes,
preferred if one exists for the language) or 639-2/639-3 (three characters
codes) language code and YY the ISO 3166 country code. If you don't know them
don't mind, the responsible i18n developer (assigned issue owner) will look
them up anyway. The best source is [http://www.sil.org/iso639-3/codes.asp SIL ISO 639-3].

If you happen to know that MS already defined a language identifier for your
language/locale you may state that as well. URLs pointing to relevant
information can be found at
[http://www.erack.de/bookmarks/D.html#GIL_MS erAck's link collection], try to
pick the ''NLS information page'' first. Unfortunately MS published several
resources with only partial information instead of consolidating all on just
one single page. They also change their URLs from time to time, which is why
this page here doesn't directly link to them. Again, it doesn't matter if you
don't include the ID, the i18n developer will look it up anyway and assign an
ID unique within OOo if it doesn't already exist.

Adding a language to the language list box makes it available for character
attribution and spell-checking. Availability of spell checker, hyphenation and
thesaurus of course depends on the installed dictionaries. To be able to fully
support it as a locale, including number formats and calendar data, and having
it selectable as default document language we would need a locale data file.
Please see [[How to submit new Locale Data]] for details.

[[Category:Localization]]
[[Category:I18n]]

Editor Vim

2011-01-04T17:44:14Z

ErAck: /* Resolve HG conflicts */

There exist only two real editors in the programmer's world ;-) One is Vim,
and the other is the ''eier-legende-woll-milch-sau'' (sorry for that German
phrase being a modified translation of
''allrounder - all-in-one device suitable for every purpose'',
couldn't resist ;-) (X)Emacs. So here we go for Vim.

== General Vim settings ==

In ''.vimrc'' have the following settings. For the tabstops=4 setting it may
not be desired to have this globally effective, you may want to restrict it to
an OOo/SO environment by evaluating the $SOLARENV environment variable,
<code>if $SOLARENV != ""</code>

<pre>
set ts=4 " tabstops are 4 (for all code)
set sw=4 " shiftwidth is 4
set expandtab " expand tabs to spaces
set showmatch " briefly jump to matching brackets
set showmode " the mode we're in
if version >= 600
filetype on " enable file type detection
filetype plugin on " enable file type plugins
filetype indent on " enable file type indents
endif

" previous and next compiler error (quickfix)
map <C-P> :cp<CR>
map <C-N> :cn<CR>

" Only do this part when compiled with support for autocommands.
if has("autocmd")

" In text files, always limit the width of text to 78 characters, tabs are 8
autocmd BufRead *.txt,*.doc,*.dok setlocal tw=78 ts=8 sw=8 fo+=rn1

" Treat resource files and headers like C files
autocmd BufRead *.hrc,*.src setlocal ft=c

" Treat generated UNO header files like C++ files
autocmd BufRead *.hdl setlocal ft=cpp

" mail bodies have a textwidth of 72 characters, activate numbering
" formatting, reset comments to default, no indenting
autocmd FileType mail setlocal tw=72 fo+=rn1 comments& nocindent

" AutoDoc comments in C/C++ files without '*' middle part
autocmd FileType c,cpp setlocal comments^=s:/**,mb:\ ,e:*/

" AutoDoc comments in IDL files have a textwidth of 72 characters
autocmd FileType idl setlocal comments^=s:/**,mb:\ ,e:*/ tw=72

" OOo .xcu configuration files and the like
autocmd FileType xml setlocal sw=2

" HTML files
autocmd FileType html,css setlocal sw=2

endif

" setting up for :make
set makeprg=$SOLARENV/bin/build.pl\ \-P4\ \-\-\ \-P4

" broken whitespace
:au Syntax * syn match Error /\s\+$/ | syn match Error /^\s* \t\s*/
</pre>

== Vim and the GNU ID-utils ==

As mentioned in [[Little_Helpers#GNU_ID-utils | Little Helpers' GNU Id-utils]], the ''eid'' command makes use of some
environment variables when invoking the editor:

<pre>
setenv VISUAL vim
setenv EIDARG '+/%s/'
setenv EIDLDEL '\<'
setenv EIDRDEL '\>'
</pre>

To be able to invoke the ''lid'' utility from within Vim we need a key mapping
and function call, you may place this section into your ''.vimrc'' file:

<pre>
" GNU id-utils, taken from :h ident-search
" Generate the ID file in the current directory or in .. or ../.. or ../../..
" To use it, place the cursor on a word, type "_u" and vim will load the file
" that contains the word. Search for the next occurrence of the word in the
" same file with "n". Go to the next file with "_n".
map _u :call ID_search()<Bar>execute "/\\<" . g:word . "\\>"<CR>
map _n :n<Bar>execute "/\\<" . g:word . "\\>"<CR>
function ID_search()
let g:word = expand("<cword>")
let x = system("lid --key=none ". g:word)
let x = substitute(x, "\n", " ", "g")
execute "next " . x
endfun
</pre>

=== lid.vim plugin ===

[http://vim.sourceforge.net/scripts/script.php?script_id=251 lid.vim] is
a plugin to integrate GNU id-utils with Vim, providing a ''lid -g'' output in
the ''quickfix'' window that can be travelled using the '':cnext'' and
'':cprev'' commands respectively their keyboard mappings.

== Vim and Ctags ==

That's easy, as vim has builtin support for ctags, see '':h tagsrch.txt'', in
''.vimrc'' just tell it where to search for the ''tags'' files:

<pre>
" Tags files are searched first relative to the current file, then relative to
" the current working directory, and last in the $HOME directory.
set tags=./tags,./../tags,./../../tags,./../../../tags,./../../../../tags,./../../../../../tags,tags,../tags,../../tags,../../../tags,../../../../tags,../../../../../tags,~/tags
</pre>

For general ''Exuberant Ctags'' information and a script how to create the ''tags'' database see the [[Little_Helpers#Exuberant_Ctags | Little Helpers' Exuberant Ctags]] section.

== Vim and Cscope ==

For general ''Cscope'' information and a script how to create a cscope
database for an OOo project see the
[[Little_Helpers#Cscope | Little Helpers' Cscope]]
section.

=== Builtin Cscope support ===

Vim has builtin (well, if compiled in) support for cscope, see '':h cscope''.
In ''.vimrc'' you may want to setup some things, but this is also a matter of
work habits. Consider the following an example and consult the fine manual.

<pre>
" Cscope settings
if has("cscope")
" quickfix window usage
set cscopequickfix=s-,c-,d-,i-,t-,e-
" :tag and the like use :cstag
set cscopetag
" first search cscope, than tags file
set cscopetagorder=0
set nocsverb
" add any database in current directory
if filereadable("cscope.out")
cs add cscope.out
" else add database pointed to by environment
elseif $CSCOPE_DB != ""
cs add $CSCOPE_DB
endif
set csverb
endif
</pre>

=== More comfortable plugin script cecscope.vim ===

The
[http://www.vim.org/scripts/script.php?script_id=1453 command and menu driven cscope interface]
eases things a bit. It requires vim7.0aa snapshot #188 or later, the Vim7.1
release does fine.

== Include file searches in Vim ==

Set the ''path'' variable in ''.vimrc'':

<pre>
" Where to look for files in gf and ^Wf and similar commands,
" and for include files for i_^X^I and i_^X^D commands.
" To use VIM_INC in OOo/SO environment define
" alias solvim 'if ( ! $?UPDMINOREXT ) setenv UPDMINOREXT "" ; setenv VIM_INC ./${INPATH}/inc,../${INPATH}/inc,../../${INPATH}/inc,../../../${INPATH}/inc,`echo $SOLARINC|sed -e "s/^-I//" -e "s/ *-I/,/g"`,${SOLARVERSION}/${INPATH}/inc${UPDMINOREXT}/offuh'
" Note the two space characters in the second substitute, and execute the alias after a setsolar.
" Under 4NT you need some rubbish like (note this isn't updated since ages)
" alias solvim=set _uq_%0=%@unique[%tmp%] && echos VIM_INC=>>_uq_%0 && echo %SOLARINC|sed -e "s/^-I//" -e "s/ \+-I/,/g">>_uq_%0 && set /r _uq_%0 && del /q _uq_%0
set path=.,./inc,./../inc,./../../inc,./../../../inc,./../../../../inc,$VIM_INC,,/usr/local/include,/usr/include
</pre>

In case you missed it in the comments above: you need to invoke a shell alias
after having sourced the environment:

<pre>
tcsh
alias solvim 'if ( ! $?UPDMINOREXT ) setenv UPDMINOREXT "" ; setenv VIM_INC ./${INPATH}/inc,../${INPATH}/inc,../../${INPATH}/inc,../../../${INPATH}/inc,`echo $SOLARINC|sed -e "s/^-I//" -e "s/ *-I/,/g"`,${SOLARVERSION}/${INPATH}/inc${UPDMINOREXT}/offuh'
source LinuxX86Env.Set
solvim
</pre>

See also: in Vim '':h include-search''

== Compiling a source from within Vim ==

Compiling the source from within the editor is of course desired, as warnings
and errors generated by the compiler let you directly jump to the line in
question. There are some quirks to be solved for the OOo/SO environment, but no
real problem, just examine the working ''.vimrc'' sections below. Pressing
Ctrl+K changes the current window's directory locally to the one of the file
loaded, if there is a makfile.mk in that directory, sets the ''makeprg''
variable to the command needed to dmake just the current file, and executes it.

For the quickfix window to pull its content from the compiler output we need to
have a valid error file setting, and as there's always the hassle with DOS
based systems, we also need to take care of that:

<pre>
" This uses the TMP environment variable, be sure to have it set!
if $COMSPEC =~ "\\"
" seems like we're having any DOS
set makeef=$TMP\\vim##.err " :make errorfile
else
set makeef=$TMP/vim##.err " :make errorfile
endif
if $TMP =~ "\\" && ($COMSPEC =~ "4" || $SHELL =~ "4")
" seems like we're having some DOS assumed to be 4DOS compatible
set shellpipe=\|&\ tee
endif
</pre>

Now the ''makeprg'' setting:

<pre>
" Call appropriate makeprg with Ctrl+K
map <C-K> :call Make()<CR>

if $SOLARENV == ""
" Normal makeprg, not in OpenOffice.org/StarOffice environment
function Make()
make
endfun
else
" Special dmake, only in OpenOffice.org/StarOffice environment
set makeprg=dmake
function SetMakeprg()
" For a detached gvim we need to source the environment, assuming
" the current working directory being source/core/tool/ or
" similar, and having a copy of the setsolar -file environment
" file as module/../ENV.$INPATH or in $SRC_ROOT set a
" ln -s LinuxX86Env.Set ENV.$INPATH
" For terminal vim re-sourcing the environment isn't necessary.
if has("gui_running")
if filereadable( "./prj/d.lst" )
set makeprg=source\ ../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ./$INPATH/slo/%:t:r.obj
elseif filereadable( "../prj/d.lst" )
set makeprg=source\ ../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../prj/d.lst" )
set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../prj/d.lst" )
set makeprg=source\ ../../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../../prj/d.lst" )
set makeprg=source\ ../../../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../../../$INPATH/slo/%:t:r.obj
else
set makeprg=source\ ./ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t
endif
else
if filereadable( "./prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ./$INPATH/slo/%:t:r.obj
elseif filereadable( "../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../../../$INPATH/slo/%:t:r.obj
else
set makeprg=dmake\ wall=t\ debug=t
endif
endif
" Just some copy&paste versions:
" Entire module, edit ENV.... and set BUILD_COMMAND to content of build alias
"set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ $BUILD_COMMAND
"set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ dmake\ ../../../$INPATH/slo/%:t:r.obj
"set makeprg=dmake\ product=full
" temporary override, no wall, no debug
"if filereadable( "./prj/d.lst" )
" set makeprg=dmake\ ./$INPATH/slo/%:t:r.obj
"elseif filereadable( "../prj/d.lst" )
" set makeprg=dmake\ ../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../prj/d.lst" )
" set makeprg=dmake\ ../../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../../prj/d.lst" )
" set makeprg=dmake\ ../../../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../../../prj/d.lst" )
" set makeprg=dmake\ ../../../../$INPATH/slo/%:t:r.obj
"else
" set makeprg=dmake
"endif
endfun
function Make()
let my_local_path = expand("%:h")
if (my_local_path == "")
let my_local_path = "."
endif
if filereadable( my_local_path . "/makefile.mk" )
exec 'lcd ' . my_local_path
call SetMakeprg()
make
else
echo "No makefile.mk in " . my_local_path
endif
endfun
endif
</pre>

== CVS/SVN/HG integration ==

=== CVS/SVN/HG commands ===

[http://vim.sourceforge.net/scripts/script.php?script_id=90 vcscommand.vim - CVS/SVN integration plugin]

A nice plugin to handle CVS, SVN and HG actions from within Vim. Most useful being
the VCSAnnotate and VCSVimDiff commands, IMHO.

=== Resolve CVS conflicts ===

[http://www.vim.org/scripts/script.php?script_id=1370 CVSconflict - CVS conflict resolution using vimdiff]

A plugin that converts a source file containing CVS merge conflicts into two
VimDiff buffers that then can be easily edited.

This also should work with inline [[Mercurial]] merge conflicts (no separate files created).

=== Resolve HG conflicts ===

See Mercurial wiki [http://mercurial.selenic.com/wiki/MergingWithVim merging with vim] and [http://mercurial.selenic.com/wiki/TipsAndTricks#Using_Vim_as_the_filemerge_program using Vim as the filemerge program] for gvim diff.

== Other useful plugins and resources ==

* [http://www.vim.org/scripts/script.php?script_id=1520 OmniCppComplete - C++ completion omnifunc with a ctags database]
* [http://www.vim.org/scripts/script.php?script_id=1997 undo_tags - small utility that lets you tag undo branches]
* [http://www.erack.de/bookmarks/D.html#VIM erAck's ''VIM and related'' bookmarks]

== A note for developers on WIN\DOS ==

Please don't complicate life for developers on other platforms by interspersing
sources with CarriageReturn characters before linefeeds, which especially is
extremely nasty in patches contributed. As you probably can't patch your
kernel's IO to simply not automatically write CrLf instead of Lf in text files,
when using Vim use this setting:

<pre>
"set fileformats=dos,unix " Vim's default on DOS/WIN/OS2
set fileformats=unix,dos " Vim's default on UNX, also use it on DOS
</pre>

[[Category:Developer Tools]]

Editor Vim

2011-01-04T15:26:11Z

ErAck: /* Resolve HG conflicts */

There exist only two real editors in the programmer's world ;-) One is Vim,
and the other is the ''eier-legende-woll-milch-sau'' (sorry for that German
phrase being a modified translation of
''allrounder - all-in-one device suitable for every purpose'',
couldn't resist ;-) (X)Emacs. So here we go for Vim.

== General Vim settings ==

In ''.vimrc'' have the following settings. For the tabstops=4 setting it may
not be desired to have this globally effective, you may want to restrict it to
an OOo/SO environment by evaluating the $SOLARENV environment variable,
<code>if $SOLARENV != ""</code>

<pre>
set ts=4 " tabstops are 4 (for all code)
set sw=4 " shiftwidth is 4
set expandtab " expand tabs to spaces
set showmatch " briefly jump to matching brackets
set showmode " the mode we're in
if version >= 600
filetype on " enable file type detection
filetype plugin on " enable file type plugins
filetype indent on " enable file type indents
endif

" previous and next compiler error (quickfix)
map <C-P> :cp<CR>
map <C-N> :cn<CR>

" Only do this part when compiled with support for autocommands.
if has("autocmd")

" In text files, always limit the width of text to 78 characters, tabs are 8
autocmd BufRead *.txt,*.doc,*.dok setlocal tw=78 ts=8 sw=8 fo+=rn1

" Treat resource files and headers like C files
autocmd BufRead *.hrc,*.src setlocal ft=c

" Treat generated UNO header files like C++ files
autocmd BufRead *.hdl setlocal ft=cpp

" mail bodies have a textwidth of 72 characters, activate numbering
" formatting, reset comments to default, no indenting
autocmd FileType mail setlocal tw=72 fo+=rn1 comments& nocindent

" AutoDoc comments in C/C++ files without '*' middle part
autocmd FileType c,cpp setlocal comments^=s:/**,mb:\ ,e:*/

" AutoDoc comments in IDL files have a textwidth of 72 characters
autocmd FileType idl setlocal comments^=s:/**,mb:\ ,e:*/ tw=72

" OOo .xcu configuration files and the like
autocmd FileType xml setlocal sw=2

" HTML files
autocmd FileType html,css setlocal sw=2

endif

" setting up for :make
set makeprg=$SOLARENV/bin/build.pl\ \-P4\ \-\-\ \-P4

" broken whitespace
:au Syntax * syn match Error /\s\+$/ | syn match Error /^\s* \t\s*/
</pre>

== Vim and the GNU ID-utils ==

As mentioned in [[Little_Helpers#GNU_ID-utils | Little Helpers' GNU Id-utils]], the ''eid'' command makes use of some
environment variables when invoking the editor:

<pre>
setenv VISUAL vim
setenv EIDARG '+/%s/'
setenv EIDLDEL '\<'
setenv EIDRDEL '\>'
</pre>

To be able to invoke the ''lid'' utility from within Vim we need a key mapping
and function call, you may place this section into your ''.vimrc'' file:

<pre>
" GNU id-utils, taken from :h ident-search
" Generate the ID file in the current directory or in .. or ../.. or ../../..
" To use it, place the cursor on a word, type "_u" and vim will load the file
" that contains the word. Search for the next occurrence of the word in the
" same file with "n". Go to the next file with "_n".
map _u :call ID_search()<Bar>execute "/\\<" . g:word . "\\>"<CR>
map _n :n<Bar>execute "/\\<" . g:word . "\\>"<CR>
function ID_search()
let g:word = expand("<cword>")
let x = system("lid --key=none ". g:word)
let x = substitute(x, "\n", " ", "g")
execute "next " . x
endfun
</pre>

=== lid.vim plugin ===

[http://vim.sourceforge.net/scripts/script.php?script_id=251 lid.vim] is
a plugin to integrate GNU id-utils with Vim, providing a ''lid -g'' output in
the ''quickfix'' window that can be travelled using the '':cnext'' and
'':cprev'' commands respectively their keyboard mappings.

== Vim and Ctags ==

That's easy, as vim has builtin support for ctags, see '':h tagsrch.txt'', in
''.vimrc'' just tell it where to search for the ''tags'' files:

<pre>
" Tags files are searched first relative to the current file, then relative to
" the current working directory, and last in the $HOME directory.
set tags=./tags,./../tags,./../../tags,./../../../tags,./../../../../tags,./../../../../../tags,tags,../tags,../../tags,../../../tags,../../../../tags,../../../../../tags,~/tags
</pre>

For general ''Exuberant Ctags'' information and a script how to create the ''tags'' database see the [[Little_Helpers#Exuberant_Ctags | Little Helpers' Exuberant Ctags]] section.

== Vim and Cscope ==

For general ''Cscope'' information and a script how to create a cscope
database for an OOo project see the
[[Little_Helpers#Cscope | Little Helpers' Cscope]]
section.

=== Builtin Cscope support ===

Vim has builtin (well, if compiled in) support for cscope, see '':h cscope''.
In ''.vimrc'' you may want to setup some things, but this is also a matter of
work habits. Consider the following an example and consult the fine manual.

<pre>
" Cscope settings
if has("cscope")
" quickfix window usage
set cscopequickfix=s-,c-,d-,i-,t-,e-
" :tag and the like use :cstag
set cscopetag
" first search cscope, than tags file
set cscopetagorder=0
set nocsverb
" add any database in current directory
if filereadable("cscope.out")
cs add cscope.out
" else add database pointed to by environment
elseif $CSCOPE_DB != ""
cs add $CSCOPE_DB
endif
set csverb
endif
</pre>

=== More comfortable plugin script cecscope.vim ===

The
[http://www.vim.org/scripts/script.php?script_id=1453 command and menu driven cscope interface]
eases things a bit. It requires vim7.0aa snapshot #188 or later, the Vim7.1
release does fine.

== Include file searches in Vim ==

Set the ''path'' variable in ''.vimrc'':

<pre>
" Where to look for files in gf and ^Wf and similar commands,
" and for include files for i_^X^I and i_^X^D commands.
" To use VIM_INC in OOo/SO environment define
" alias solvim 'if ( ! $?UPDMINOREXT ) setenv UPDMINOREXT "" ; setenv VIM_INC ./${INPATH}/inc,../${INPATH}/inc,../../${INPATH}/inc,../../../${INPATH}/inc,`echo $SOLARINC|sed -e "s/^-I//" -e "s/ *-I/,/g"`,${SOLARVERSION}/${INPATH}/inc${UPDMINOREXT}/offuh'
" Note the two space characters in the second substitute, and execute the alias after a setsolar.
" Under 4NT you need some rubbish like (note this isn't updated since ages)
" alias solvim=set _uq_%0=%@unique[%tmp%] && echos VIM_INC=>>_uq_%0 && echo %SOLARINC|sed -e "s/^-I//" -e "s/ \+-I/,/g">>_uq_%0 && set /r _uq_%0 && del /q _uq_%0
set path=.,./inc,./../inc,./../../inc,./../../../inc,./../../../../inc,$VIM_INC,,/usr/local/include,/usr/include
</pre>

In case you missed it in the comments above: you need to invoke a shell alias
after having sourced the environment:

<pre>
tcsh
alias solvim 'if ( ! $?UPDMINOREXT ) setenv UPDMINOREXT "" ; setenv VIM_INC ./${INPATH}/inc,../${INPATH}/inc,../../${INPATH}/inc,../../../${INPATH}/inc,`echo $SOLARINC|sed -e "s/^-I//" -e "s/ *-I/,/g"`,${SOLARVERSION}/${INPATH}/inc${UPDMINOREXT}/offuh'
source LinuxX86Env.Set
solvim
</pre>

See also: in Vim '':h include-search''

== Compiling a source from within Vim ==

Compiling the source from within the editor is of course desired, as warnings
and errors generated by the compiler let you directly jump to the line in
question. There are some quirks to be solved for the OOo/SO environment, but no
real problem, just examine the working ''.vimrc'' sections below. Pressing
Ctrl+K changes the current window's directory locally to the one of the file
loaded, if there is a makfile.mk in that directory, sets the ''makeprg''
variable to the command needed to dmake just the current file, and executes it.

For the quickfix window to pull its content from the compiler output we need to
have a valid error file setting, and as there's always the hassle with DOS
based systems, we also need to take care of that:

<pre>
" This uses the TMP environment variable, be sure to have it set!
if $COMSPEC =~ "\\"
" seems like we're having any DOS
set makeef=$TMP\\vim##.err " :make errorfile
else
set makeef=$TMP/vim##.err " :make errorfile
endif
if $TMP =~ "\\" && ($COMSPEC =~ "4" || $SHELL =~ "4")
" seems like we're having some DOS assumed to be 4DOS compatible
set shellpipe=\|&\ tee
endif
</pre>

Now the ''makeprg'' setting:

<pre>
" Call appropriate makeprg with Ctrl+K
map <C-K> :call Make()<CR>

if $SOLARENV == ""
" Normal makeprg, not in OpenOffice.org/StarOffice environment
function Make()
make
endfun
else
" Special dmake, only in OpenOffice.org/StarOffice environment
set makeprg=dmake
function SetMakeprg()
" For a detached gvim we need to source the environment, assuming
" the current working directory being source/core/tool/ or
" similar, and having a copy of the setsolar -file environment
" file as module/../ENV.$INPATH or in $SRC_ROOT set a
" ln -s LinuxX86Env.Set ENV.$INPATH
" For terminal vim re-sourcing the environment isn't necessary.
if has("gui_running")
if filereadable( "./prj/d.lst" )
set makeprg=source\ ../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ./$INPATH/slo/%:t:r.obj
elseif filereadable( "../prj/d.lst" )
set makeprg=source\ ../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../prj/d.lst" )
set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../prj/d.lst" )
set makeprg=source\ ../../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../../prj/d.lst" )
set makeprg=source\ ../../../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../../../$INPATH/slo/%:t:r.obj
else
set makeprg=source\ ./ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t
endif
else
if filereadable( "./prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ./$INPATH/slo/%:t:r.obj
elseif filereadable( "../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../../../$INPATH/slo/%:t:r.obj
else
set makeprg=dmake\ wall=t\ debug=t
endif
endif
" Just some copy&paste versions:
" Entire module, edit ENV.... and set BUILD_COMMAND to content of build alias
"set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ $BUILD_COMMAND
"set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ dmake\ ../../../$INPATH/slo/%:t:r.obj
"set makeprg=dmake\ product=full
" temporary override, no wall, no debug
"if filereadable( "./prj/d.lst" )
" set makeprg=dmake\ ./$INPATH/slo/%:t:r.obj
"elseif filereadable( "../prj/d.lst" )
" set makeprg=dmake\ ../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../prj/d.lst" )
" set makeprg=dmake\ ../../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../../prj/d.lst" )
" set makeprg=dmake\ ../../../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../../../prj/d.lst" )
" set makeprg=dmake\ ../../../../$INPATH/slo/%:t:r.obj
"else
" set makeprg=dmake
"endif
endfun
function Make()
let my_local_path = expand("%:h")
if (my_local_path == "")
let my_local_path = "."
endif
if filereadable( my_local_path . "/makefile.mk" )
exec 'lcd ' . my_local_path
call SetMakeprg()
make
else
echo "No makefile.mk in " . my_local_path
endif
endfun
endif
</pre>

== CVS/SVN/HG integration ==

=== CVS/SVN/HG commands ===

[http://vim.sourceforge.net/scripts/script.php?script_id=90 vcscommand.vim - CVS/SVN integration plugin]

A nice plugin to handle CVS, SVN and HG actions from within Vim. Most useful being
the VCSAnnotate and VCSVimDiff commands, IMHO.

=== Resolve CVS conflicts ===

[http://www.vim.org/scripts/script.php?script_id=1370 CVSconflict - CVS conflict resolution using vimdiff]

A plugin that converts a source file containing CVS merge conflicts into two
VimDiff buffers that then can be easily edited.

This also should work with inline [[Mercurial]] merge conflicts (no separate files created).

=== Resolve HG conflicts ===

See [http://mercurial.selenic.com/wiki/TipsAndTricks#Using_Vim_as_the_filemerge_program Mercurial wiki, using Vim as the filemerge program] for gvim diff.

== Other useful plugins and resources ==

* [http://www.vim.org/scripts/script.php?script_id=1520 OmniCppComplete - C++ completion omnifunc with a ctags database]
* [http://www.vim.org/scripts/script.php?script_id=1997 undo_tags - small utility that lets you tag undo branches]
* [http://www.erack.de/bookmarks/D.html#VIM erAck's ''VIM and related'' bookmarks]

== A note for developers on WIN\DOS ==

Please don't complicate life for developers on other platforms by interspersing
sources with CarriageReturn characters before linefeeds, which especially is
extremely nasty in patches contributed. As you probably can't patch your
kernel's IO to simply not automatically write CrLf instead of Lf in text files,
when using Vim use this setting:

<pre>
"set fileformats=dos,unix " Vim's default on DOS/WIN/OS2
set fileformats=unix,dos " Vim's default on UNX, also use it on DOS
</pre>

[[Category:Developer Tools]]

Editor Vim

2011-01-04T15:18:07Z

ErAck: /* CVS/SVN/HG integration */ gvim diff to resolve HG conflicts

There exist only two real editors in the programmer's world ;-) One is Vim,
and the other is the ''eier-legende-woll-milch-sau'' (sorry for that German
phrase being a modified translation of
''allrounder - all-in-one device suitable for every purpose'',
couldn't resist ;-) (X)Emacs. So here we go for Vim.

== General Vim settings ==

In ''.vimrc'' have the following settings. For the tabstops=4 setting it may
not be desired to have this globally effective, you may want to restrict it to
an OOo/SO environment by evaluating the $SOLARENV environment variable,
<code>if $SOLARENV != ""</code>

<pre>
set ts=4 " tabstops are 4 (for all code)
set sw=4 " shiftwidth is 4
set expandtab " expand tabs to spaces
set showmatch " briefly jump to matching brackets
set showmode " the mode we're in
if version >= 600
filetype on " enable file type detection
filetype plugin on " enable file type plugins
filetype indent on " enable file type indents
endif

" previous and next compiler error (quickfix)
map <C-P> :cp<CR>
map <C-N> :cn<CR>

" Only do this part when compiled with support for autocommands.
if has("autocmd")

" In text files, always limit the width of text to 78 characters, tabs are 8
autocmd BufRead *.txt,*.doc,*.dok setlocal tw=78 ts=8 sw=8 fo+=rn1

" Treat resource files and headers like C files
autocmd BufRead *.hrc,*.src setlocal ft=c

" Treat generated UNO header files like C++ files
autocmd BufRead *.hdl setlocal ft=cpp

" mail bodies have a textwidth of 72 characters, activate numbering
" formatting, reset comments to default, no indenting
autocmd FileType mail setlocal tw=72 fo+=rn1 comments& nocindent

" AutoDoc comments in C/C++ files without '*' middle part
autocmd FileType c,cpp setlocal comments^=s:/**,mb:\ ,e:*/

" AutoDoc comments in IDL files have a textwidth of 72 characters
autocmd FileType idl setlocal comments^=s:/**,mb:\ ,e:*/ tw=72

" OOo .xcu configuration files and the like
autocmd FileType xml setlocal sw=2

" HTML files
autocmd FileType html,css setlocal sw=2

endif

" setting up for :make
set makeprg=$SOLARENV/bin/build.pl\ \-P4\ \-\-\ \-P4

" broken whitespace
:au Syntax * syn match Error /\s\+$/ | syn match Error /^\s* \t\s*/
</pre>

== Vim and the GNU ID-utils ==

As mentioned in [[Little_Helpers#GNU_ID-utils | Little Helpers' GNU Id-utils]], the ''eid'' command makes use of some
environment variables when invoking the editor:

<pre>
setenv VISUAL vim
setenv EIDARG '+/%s/'
setenv EIDLDEL '\<'
setenv EIDRDEL '\>'
</pre>

To be able to invoke the ''lid'' utility from within Vim we need a key mapping
and function call, you may place this section into your ''.vimrc'' file:

<pre>
" GNU id-utils, taken from :h ident-search
" Generate the ID file in the current directory or in .. or ../.. or ../../..
" To use it, place the cursor on a word, type "_u" and vim will load the file
" that contains the word. Search for the next occurrence of the word in the
" same file with "n". Go to the next file with "_n".
map _u :call ID_search()<Bar>execute "/\\<" . g:word . "\\>"<CR>
map _n :n<Bar>execute "/\\<" . g:word . "\\>"<CR>
function ID_search()
let g:word = expand("<cword>")
let x = system("lid --key=none ". g:word)
let x = substitute(x, "\n", " ", "g")
execute "next " . x
endfun
</pre>

=== lid.vim plugin ===

[http://vim.sourceforge.net/scripts/script.php?script_id=251 lid.vim] is
a plugin to integrate GNU id-utils with Vim, providing a ''lid -g'' output in
the ''quickfix'' window that can be travelled using the '':cnext'' and
'':cprev'' commands respectively their keyboard mappings.

== Vim and Ctags ==

That's easy, as vim has builtin support for ctags, see '':h tagsrch.txt'', in
''.vimrc'' just tell it where to search for the ''tags'' files:

<pre>
" Tags files are searched first relative to the current file, then relative to
" the current working directory, and last in the $HOME directory.
set tags=./tags,./../tags,./../../tags,./../../../tags,./../../../../tags,./../../../../../tags,tags,../tags,../../tags,../../../tags,../../../../tags,../../../../../tags,~/tags
</pre>

For general ''Exuberant Ctags'' information and a script how to create the ''tags'' database see the [[Little_Helpers#Exuberant_Ctags | Little Helpers' Exuberant Ctags]] section.

== Vim and Cscope ==

For general ''Cscope'' information and a script how to create a cscope
database for an OOo project see the
[[Little_Helpers#Cscope | Little Helpers' Cscope]]
section.

=== Builtin Cscope support ===

Vim has builtin (well, if compiled in) support for cscope, see '':h cscope''.
In ''.vimrc'' you may want to setup some things, but this is also a matter of
work habits. Consider the following an example and consult the fine manual.

<pre>
" Cscope settings
if has("cscope")
" quickfix window usage
set cscopequickfix=s-,c-,d-,i-,t-,e-
" :tag and the like use :cstag
set cscopetag
" first search cscope, than tags file
set cscopetagorder=0
set nocsverb
" add any database in current directory
if filereadable("cscope.out")
cs add cscope.out
" else add database pointed to by environment
elseif $CSCOPE_DB != ""
cs add $CSCOPE_DB
endif
set csverb
endif
</pre>

=== More comfortable plugin script cecscope.vim ===

The
[http://www.vim.org/scripts/script.php?script_id=1453 command and menu driven cscope interface]
eases things a bit. It requires vim7.0aa snapshot #188 or later, the Vim7.1
release does fine.

== Include file searches in Vim ==

Set the ''path'' variable in ''.vimrc'':

<pre>
" Where to look for files in gf and ^Wf and similar commands,
" and for include files for i_^X^I and i_^X^D commands.
" To use VIM_INC in OOo/SO environment define
" alias solvim 'if ( ! $?UPDMINOREXT ) setenv UPDMINOREXT "" ; setenv VIM_INC ./${INPATH}/inc,../${INPATH}/inc,../../${INPATH}/inc,../../../${INPATH}/inc,`echo $SOLARINC|sed -e "s/^-I//" -e "s/ *-I/,/g"`,${SOLARVERSION}/${INPATH}/inc${UPDMINOREXT}/offuh'
" Note the two space characters in the second substitute, and execute the alias after a setsolar.
" Under 4NT you need some rubbish like (note this isn't updated since ages)
" alias solvim=set _uq_%0=%@unique[%tmp%] && echos VIM_INC=>>_uq_%0 && echo %SOLARINC|sed -e "s/^-I//" -e "s/ \+-I/,/g">>_uq_%0 && set /r _uq_%0 && del /q _uq_%0
set path=.,./inc,./../inc,./../../inc,./../../../inc,./../../../../inc,$VIM_INC,,/usr/local/include,/usr/include
</pre>

In case you missed it in the comments above: you need to invoke a shell alias
after having sourced the environment:

<pre>
tcsh
alias solvim 'if ( ! $?UPDMINOREXT ) setenv UPDMINOREXT "" ; setenv VIM_INC ./${INPATH}/inc,../${INPATH}/inc,../../${INPATH}/inc,../../../${INPATH}/inc,`echo $SOLARINC|sed -e "s/^-I//" -e "s/ *-I/,/g"`,${SOLARVERSION}/${INPATH}/inc${UPDMINOREXT}/offuh'
source LinuxX86Env.Set
solvim
</pre>

See also: in Vim '':h include-search''

== Compiling a source from within Vim ==

Compiling the source from within the editor is of course desired, as warnings
and errors generated by the compiler let you directly jump to the line in
question. There are some quirks to be solved for the OOo/SO environment, but no
real problem, just examine the working ''.vimrc'' sections below. Pressing
Ctrl+K changes the current window's directory locally to the one of the file
loaded, if there is a makfile.mk in that directory, sets the ''makeprg''
variable to the command needed to dmake just the current file, and executes it.

For the quickfix window to pull its content from the compiler output we need to
have a valid error file setting, and as there's always the hassle with DOS
based systems, we also need to take care of that:

<pre>
" This uses the TMP environment variable, be sure to have it set!
if $COMSPEC =~ "\\"
" seems like we're having any DOS
set makeef=$TMP\\vim##.err " :make errorfile
else
set makeef=$TMP/vim##.err " :make errorfile
endif
if $TMP =~ "\\" && ($COMSPEC =~ "4" || $SHELL =~ "4")
" seems like we're having some DOS assumed to be 4DOS compatible
set shellpipe=\|&\ tee
endif
</pre>

Now the ''makeprg'' setting:

<pre>
" Call appropriate makeprg with Ctrl+K
map <C-K> :call Make()<CR>

if $SOLARENV == ""
" Normal makeprg, not in OpenOffice.org/StarOffice environment
function Make()
make
endfun
else
" Special dmake, only in OpenOffice.org/StarOffice environment
set makeprg=dmake
function SetMakeprg()
" For a detached gvim we need to source the environment, assuming
" the current working directory being source/core/tool/ or
" similar, and having a copy of the setsolar -file environment
" file as module/../ENV.$INPATH or in $SRC_ROOT set a
" ln -s LinuxX86Env.Set ENV.$INPATH
" For terminal vim re-sourcing the environment isn't necessary.
if has("gui_running")
if filereadable( "./prj/d.lst" )
set makeprg=source\ ../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ./$INPATH/slo/%:t:r.obj
elseif filereadable( "../prj/d.lst" )
set makeprg=source\ ../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../prj/d.lst" )
set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../prj/d.lst" )
set makeprg=source\ ../../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../../prj/d.lst" )
set makeprg=source\ ../../../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../../../$INPATH/slo/%:t:r.obj
else
set makeprg=source\ ./ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t
endif
else
if filereadable( "./prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ./$INPATH/slo/%:t:r.obj
elseif filereadable( "../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../../../$INPATH/slo/%:t:r.obj
else
set makeprg=dmake\ wall=t\ debug=t
endif
endif
" Just some copy&paste versions:
" Entire module, edit ENV.... and set BUILD_COMMAND to content of build alias
"set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ $BUILD_COMMAND
"set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ dmake\ ../../../$INPATH/slo/%:t:r.obj
"set makeprg=dmake\ product=full
" temporary override, no wall, no debug
"if filereadable( "./prj/d.lst" )
" set makeprg=dmake\ ./$INPATH/slo/%:t:r.obj
"elseif filereadable( "../prj/d.lst" )
" set makeprg=dmake\ ../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../prj/d.lst" )
" set makeprg=dmake\ ../../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../../prj/d.lst" )
" set makeprg=dmake\ ../../../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../../../prj/d.lst" )
" set makeprg=dmake\ ../../../../$INPATH/slo/%:t:r.obj
"else
" set makeprg=dmake
"endif
endfun
function Make()
let my_local_path = expand("%:h")
if (my_local_path == "")
let my_local_path = "."
endif
if filereadable( my_local_path . "/makefile.mk" )
exec 'lcd ' . my_local_path
call SetMakeprg()
make
else
echo "No makefile.mk in " . my_local_path
endif
endfun
endif
</pre>

== CVS/SVN/HG integration ==

=== CVS/SVN/HG commands ===

[http://vim.sourceforge.net/scripts/script.php?script_id=90 vcscommand.vim - CVS/SVN integration plugin]

A nice plugin to handle CVS, SVN and HG actions from within Vim. Most useful being
the VCSAnnotate and VCSVimDiff commands, IMHO.

=== Resolve CVS conflicts ===

[http://www.vim.org/scripts/script.php?script_id=1370 CVSconflict - CVS conflict resolution using vimdiff]

A plugin that converts a source file containing CVS merge conflicts into two
VimDiff buffers that then can be easily edited.

This also should work with inline [[Mercurial]] merge conflicts (no separate files created).

=== Resolve HG conflicts ===

See [http://mercurial.selenic.com/wiki/TipsAndTricks#Using_Vim_as_the_filemerge_program| Mercurial wiki, using Vim as the filemerge program] for gvim diff.

== Other useful plugins and resources ==

* [http://www.vim.org/scripts/script.php?script_id=1520 OmniCppComplete - C++ completion omnifunc with a ctags database]
* [http://www.vim.org/scripts/script.php?script_id=1997 undo_tags - small utility that lets you tag undo branches]
* [http://www.erack.de/bookmarks/D.html#VIM erAck's ''VIM and related'' bookmarks]

== A note for developers on WIN\DOS ==

Please don't complicate life for developers on other platforms by interspersing
sources with CarriageReturn characters before linefeeds, which especially is
extremely nasty in patches contributed. As you probably can't patch your
kernel's IO to simply not automatically write CrLf instead of Lf in text files,
when using Vim use this setting:

<pre>
"set fileformats=dos,unix " Vim's default on DOS/WIN/OS2
set fileformats=unix,dos " Vim's default on UNX, also use it on DOS
</pre>

[[Category:Developer Tools]]

Editor Vim

2011-01-04T15:12:09Z

ErAck: /* Resolve CVS conflicts */ should also work with inline HG conflicts

There exist only two real editors in the programmer's world ;-) One is Vim,
and the other is the ''eier-legende-woll-milch-sau'' (sorry for that German
phrase being a modified translation of
''allrounder - all-in-one device suitable for every purpose'',
couldn't resist ;-) (X)Emacs. So here we go for Vim.

== General Vim settings ==

In ''.vimrc'' have the following settings. For the tabstops=4 setting it may
not be desired to have this globally effective, you may want to restrict it to
an OOo/SO environment by evaluating the $SOLARENV environment variable,
<code>if $SOLARENV != ""</code>

<pre>
set ts=4 " tabstops are 4 (for all code)
set sw=4 " shiftwidth is 4
set expandtab " expand tabs to spaces
set showmatch " briefly jump to matching brackets
set showmode " the mode we're in
if version >= 600
filetype on " enable file type detection
filetype plugin on " enable file type plugins
filetype indent on " enable file type indents
endif

" previous and next compiler error (quickfix)
map <C-P> :cp<CR>
map <C-N> :cn<CR>

" Only do this part when compiled with support for autocommands.
if has("autocmd")

" In text files, always limit the width of text to 78 characters, tabs are 8
autocmd BufRead *.txt,*.doc,*.dok setlocal tw=78 ts=8 sw=8 fo+=rn1

" Treat resource files and headers like C files
autocmd BufRead *.hrc,*.src setlocal ft=c

" Treat generated UNO header files like C++ files
autocmd BufRead *.hdl setlocal ft=cpp

" mail bodies have a textwidth of 72 characters, activate numbering
" formatting, reset comments to default, no indenting
autocmd FileType mail setlocal tw=72 fo+=rn1 comments& nocindent

" AutoDoc comments in C/C++ files without '*' middle part
autocmd FileType c,cpp setlocal comments^=s:/**,mb:\ ,e:*/

" AutoDoc comments in IDL files have a textwidth of 72 characters
autocmd FileType idl setlocal comments^=s:/**,mb:\ ,e:*/ tw=72

" OOo .xcu configuration files and the like
autocmd FileType xml setlocal sw=2

" HTML files
autocmd FileType html,css setlocal sw=2

endif

" setting up for :make
set makeprg=$SOLARENV/bin/build.pl\ \-P4\ \-\-\ \-P4

" broken whitespace
:au Syntax * syn match Error /\s\+$/ | syn match Error /^\s* \t\s*/
</pre>

== Vim and the GNU ID-utils ==

As mentioned in [[Little_Helpers#GNU_ID-utils | Little Helpers' GNU Id-utils]], the ''eid'' command makes use of some
environment variables when invoking the editor:

<pre>
setenv VISUAL vim
setenv EIDARG '+/%s/'
setenv EIDLDEL '\<'
setenv EIDRDEL '\>'
</pre>

To be able to invoke the ''lid'' utility from within Vim we need a key mapping
and function call, you may place this section into your ''.vimrc'' file:

<pre>
" GNU id-utils, taken from :h ident-search
" Generate the ID file in the current directory or in .. or ../.. or ../../..
" To use it, place the cursor on a word, type "_u" and vim will load the file
" that contains the word. Search for the next occurrence of the word in the
" same file with "n". Go to the next file with "_n".
map _u :call ID_search()<Bar>execute "/\\<" . g:word . "\\>"<CR>
map _n :n<Bar>execute "/\\<" . g:word . "\\>"<CR>
function ID_search()
let g:word = expand("<cword>")
let x = system("lid --key=none ". g:word)
let x = substitute(x, "\n", " ", "g")
execute "next " . x
endfun
</pre>

=== lid.vim plugin ===

[http://vim.sourceforge.net/scripts/script.php?script_id=251 lid.vim] is
a plugin to integrate GNU id-utils with Vim, providing a ''lid -g'' output in
the ''quickfix'' window that can be travelled using the '':cnext'' and
'':cprev'' commands respectively their keyboard mappings.

== Vim and Ctags ==

That's easy, as vim has builtin support for ctags, see '':h tagsrch.txt'', in
''.vimrc'' just tell it where to search for the ''tags'' files:

<pre>
" Tags files are searched first relative to the current file, then relative to
" the current working directory, and last in the $HOME directory.
set tags=./tags,./../tags,./../../tags,./../../../tags,./../../../../tags,./../../../../../tags,tags,../tags,../../tags,../../../tags,../../../../tags,../../../../../tags,~/tags
</pre>

For general ''Exuberant Ctags'' information and a script how to create the ''tags'' database see the [[Little_Helpers#Exuberant_Ctags | Little Helpers' Exuberant Ctags]] section.

== Vim and Cscope ==

For general ''Cscope'' information and a script how to create a cscope
database for an OOo project see the
[[Little_Helpers#Cscope | Little Helpers' Cscope]]
section.

=== Builtin Cscope support ===

Vim has builtin (well, if compiled in) support for cscope, see '':h cscope''.
In ''.vimrc'' you may want to setup some things, but this is also a matter of
work habits. Consider the following an example and consult the fine manual.

<pre>
" Cscope settings
if has("cscope")
" quickfix window usage
set cscopequickfix=s-,c-,d-,i-,t-,e-
" :tag and the like use :cstag
set cscopetag
" first search cscope, than tags file
set cscopetagorder=0
set nocsverb
" add any database in current directory
if filereadable("cscope.out")
cs add cscope.out
" else add database pointed to by environment
elseif $CSCOPE_DB != ""
cs add $CSCOPE_DB
endif
set csverb
endif
</pre>

=== More comfortable plugin script cecscope.vim ===

The
[http://www.vim.org/scripts/script.php?script_id=1453 command and menu driven cscope interface]
eases things a bit. It requires vim7.0aa snapshot #188 or later, the Vim7.1
release does fine.

== Include file searches in Vim ==

Set the ''path'' variable in ''.vimrc'':

<pre>
" Where to look for files in gf and ^Wf and similar commands,
" and for include files for i_^X^I and i_^X^D commands.
" To use VIM_INC in OOo/SO environment define
" alias solvim 'if ( ! $?UPDMINOREXT ) setenv UPDMINOREXT "" ; setenv VIM_INC ./${INPATH}/inc,../${INPATH}/inc,../../${INPATH}/inc,../../../${INPATH}/inc,`echo $SOLARINC|sed -e "s/^-I//" -e "s/ *-I/,/g"`,${SOLARVERSION}/${INPATH}/inc${UPDMINOREXT}/offuh'
" Note the two space characters in the second substitute, and execute the alias after a setsolar.
" Under 4NT you need some rubbish like (note this isn't updated since ages)
" alias solvim=set _uq_%0=%@unique[%tmp%] && echos VIM_INC=>>_uq_%0 && echo %SOLARINC|sed -e "s/^-I//" -e "s/ \+-I/,/g">>_uq_%0 && set /r _uq_%0 && del /q _uq_%0
set path=.,./inc,./../inc,./../../inc,./../../../inc,./../../../../inc,$VIM_INC,,/usr/local/include,/usr/include
</pre>

In case you missed it in the comments above: you need to invoke a shell alias
after having sourced the environment:

<pre>
tcsh
alias solvim 'if ( ! $?UPDMINOREXT ) setenv UPDMINOREXT "" ; setenv VIM_INC ./${INPATH}/inc,../${INPATH}/inc,../../${INPATH}/inc,../../../${INPATH}/inc,`echo $SOLARINC|sed -e "s/^-I//" -e "s/ *-I/,/g"`,${SOLARVERSION}/${INPATH}/inc${UPDMINOREXT}/offuh'
source LinuxX86Env.Set
solvim
</pre>

See also: in Vim '':h include-search''

== Compiling a source from within Vim ==

Compiling the source from within the editor is of course desired, as warnings
and errors generated by the compiler let you directly jump to the line in
question. There are some quirks to be solved for the OOo/SO environment, but no
real problem, just examine the working ''.vimrc'' sections below. Pressing
Ctrl+K changes the current window's directory locally to the one of the file
loaded, if there is a makfile.mk in that directory, sets the ''makeprg''
variable to the command needed to dmake just the current file, and executes it.

For the quickfix window to pull its content from the compiler output we need to
have a valid error file setting, and as there's always the hassle with DOS
based systems, we also need to take care of that:

<pre>
" This uses the TMP environment variable, be sure to have it set!
if $COMSPEC =~ "\\"
" seems like we're having any DOS
set makeef=$TMP\\vim##.err " :make errorfile
else
set makeef=$TMP/vim##.err " :make errorfile
endif
if $TMP =~ "\\" && ($COMSPEC =~ "4" || $SHELL =~ "4")
" seems like we're having some DOS assumed to be 4DOS compatible
set shellpipe=\|&\ tee
endif
</pre>

Now the ''makeprg'' setting:

<pre>
" Call appropriate makeprg with Ctrl+K
map <C-K> :call Make()<CR>

if $SOLARENV == ""
" Normal makeprg, not in OpenOffice.org/StarOffice environment
function Make()
make
endfun
else
" Special dmake, only in OpenOffice.org/StarOffice environment
set makeprg=dmake
function SetMakeprg()
" For a detached gvim we need to source the environment, assuming
" the current working directory being source/core/tool/ or
" similar, and having a copy of the setsolar -file environment
" file as module/../ENV.$INPATH or in $SRC_ROOT set a
" ln -s LinuxX86Env.Set ENV.$INPATH
" For terminal vim re-sourcing the environment isn't necessary.
if has("gui_running")
if filereadable( "./prj/d.lst" )
set makeprg=source\ ../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ./$INPATH/slo/%:t:r.obj
elseif filereadable( "../prj/d.lst" )
set makeprg=source\ ../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../prj/d.lst" )
set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../prj/d.lst" )
set makeprg=source\ ../../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../../prj/d.lst" )
set makeprg=source\ ../../../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../../../$INPATH/slo/%:t:r.obj
else
set makeprg=source\ ./ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t
endif
else
if filereadable( "./prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ./$INPATH/slo/%:t:r.obj
elseif filereadable( "../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../../../$INPATH/slo/%:t:r.obj
else
set makeprg=dmake\ wall=t\ debug=t
endif
endif
" Just some copy&paste versions:
" Entire module, edit ENV.... and set BUILD_COMMAND to content of build alias
"set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ $BUILD_COMMAND
"set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ dmake\ ../../../$INPATH/slo/%:t:r.obj
"set makeprg=dmake\ product=full
" temporary override, no wall, no debug
"if filereadable( "./prj/d.lst" )
" set makeprg=dmake\ ./$INPATH/slo/%:t:r.obj
"elseif filereadable( "../prj/d.lst" )
" set makeprg=dmake\ ../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../prj/d.lst" )
" set makeprg=dmake\ ../../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../../prj/d.lst" )
" set makeprg=dmake\ ../../../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../../../prj/d.lst" )
" set makeprg=dmake\ ../../../../$INPATH/slo/%:t:r.obj
"else
" set makeprg=dmake
"endif
endfun
function Make()
let my_local_path = expand("%:h")
if (my_local_path == "")
let my_local_path = "."
endif
if filereadable( my_local_path . "/makefile.mk" )
exec 'lcd ' . my_local_path
call SetMakeprg()
make
else
echo "No makefile.mk in " . my_local_path
endif
endfun
endif
</pre>

== CVS/SVN/HG integration ==

=== CVS/SVN/HG commands ===

[http://vim.sourceforge.net/scripts/script.php?script_id=90 vcscommand.vim - CVS/SVN integration plugin]

A nice plugin to handle CVS, SVN and HG actions from within Vim. Most useful being
the VCSAnnotate and VCSVimDiff commands, IMHO.

=== Resolve CVS conflicts ===

[http://www.vim.org/scripts/script.php?script_id=1370 CVSconflict - CVS conflict resolution using vimdiff]

A plugin that converts a source file containing CVS merge conflicts into two
VimDiff buffers that then can be easily edited.

This also should work with inline [[Mercurial]] merge conflicts (no separate files created).

== Other useful plugins and resources ==

* [http://www.vim.org/scripts/script.php?script_id=1520 OmniCppComplete - C++ completion omnifunc with a ctags database]
* [http://www.vim.org/scripts/script.php?script_id=1997 undo_tags - small utility that lets you tag undo branches]
* [http://www.erack.de/bookmarks/D.html#VIM erAck's ''VIM and related'' bookmarks]

== A note for developers on WIN\DOS ==

Please don't complicate life for developers on other platforms by interspersing
sources with CarriageReturn characters before linefeeds, which especially is
extremely nasty in patches contributed. As you probably can't patch your
kernel's IO to simply not automatically write CrLf instead of Lf in text files,
when using Vim use this setting:

<pre>
"set fileformats=dos,unix " Vim's default on DOS/WIN/OS2
set fileformats=unix,dos " Vim's default on UNX, also use it on DOS
</pre>

[[Category:Developer Tools]]

Community Council/Agenda

2010-11-25T20:23:27Z

ErAck: now the right position...

{{Community_Council}}
== Upcoming Meeting ==

Date: 2010-11-04 (Derived from the [[Community Council/Calendar|Community Council Meeting Calendar]])

Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=04&month=11&year=2010&hour=19&min=30&sec=0&p1=0 19.30 UTC] (click on the link to show world clock times)

Location: IRC

== Agenda and Work Status ==

The following table represents the agenda of the upcoming meeting and the current work status of topics / action items. Working with this table is described in the [[Community Council/Meeting Guidelines|Community Council Meeting Guidelines]].

{| class="prettytable sortable"
|-
! scope="col" | ID 
! scope="col" | Topic 
! scope="col" | Status 
! scope="col" | Responsible 
! scope="col" | Last Update 
! scope="col" | Details 
|-
| 0 
| List of Action Items of previous meeting for approval 
| ''none'' 
| all 
| 2010-10-14 
|
*Meeting minutes of previous meeting at [[Community Council/Minutes#2010-10-14|Minutes#2010-10-14]] 
*Result: (to be confirmed)

|-
| 2010-10-14#1 
| Where do we stand 
| new 
| all 
| 2010-10-14 
|
*Now that many members of the community council support the Document Foundation: how do find the best way to go on?
*Discussion: A summary seems hard to provide, so please consider to read the [[Community Council Log 20101014#IRC_Log_2010-10-14|IRC Log]].
*Result: Cor and Martin will have a talk and discuss the topic. Additionally, some community council members request to resolve the issue by next Tuesday (2010-10-19).

|-
| bgcolor="#ffffcc" colspan="6" | Note: Because of running out of time, the meeting has been. So no further Action Items (below) have been discussed.
|-
| 2010-03-04#2 
| Refresh Incubator and NLC Project processes 
| Accepted 
| Louis 
| 2010-03-18 
|
*The NLC homepage (http://native-lang.openoffice.org/) has the language in the policy I wrote many years ago, and I'll be using a version of that plus the earlier drafts submitted to resolve this. The hangup has been what to do with mothballed projects, what to do with the data. We will create an effective category, with very limited permissions, called something like, "Inactive Projects" and the data will remain there, unto perpetuity or the closes thing to it. Expect new update by next CC meeting. 

|-
| 2010-03-04#6 
| Talk to Education Project Leads about structure and remit 
| Stalled 
| louis 
| 2010-03-18 
|
*Louis to take this on and report by next CC meeting of discussions held with the responsible persons. 
|-
| 2010-04-01#1 
| Community situation 
| Accepted 
| All 
| 2010-09-23 
|
*What do we see, where are we, what are we going to do about it. 
*Activities:
**All CC members are asked to think about it and Cor will prepare a proposal for an detailed agenda. 
**Leif already collected some issues (e.g. rare communication via blogs) and will send that to Cor. 
*Next Steps: Proposal that the CC will work on that at the OOoCon in Budapest.
**Cor send a mail on 2010-08-12 with some items for the agenda. 
*2010-09-03/09-21: Page with draft plan [[Community Council/collaboration in the OOo-community|improvement community collaboration]]

|-
| 2010-04-29#2 
|
Missing OOo desktop presence

| Accepted 
| Christoph, Stefan
| 2010-09-21 
|
*Request by a community member to discuss / decide the following question: "''Why should OpenOffice.org give away it's presence on the user's desktop - the main place to be recognized by the people - only to support the "application independency" of ODF?'' A Sun employee stated "The idea of supporting ODF as a application independent open standard is the priority." This leads / will lead to changes with regard to the document and application icon design. The current ODF "only" icons seem to be undesired by the community. Original request to the CC on ooo-discuss: [http://www.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=65958 initial mail (2010-04-14)], [http://www.openoffice.org/servlets/BrowseList?listName=discuss&from=2361081&to=2361081&count=28&by=thread&first=1&windowSize=1000 full mail thread]
*Discussion:
**2010-04-29: Some members stated that the request should be "more actionable" and "better framed" to be decided by the community. Proposal has been made to forward the request to council-discuss to propose how to proceed.
**2010-05-02: Christoph forwarded the [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2564 request to the CC mailing list]. A first discussion took place.
**2010-05-20: Intensive discussion about the request and how to address it. Stefan and Christoph agreed to work out a request to the ODF Icons team to iterate on the design and/or processes. Maybe a "refreshed" team which may provide an agreed-upon proposal. Stefan stated that there shouldn't be any dependency to the next/other releases.
**2010-06-08: Some opinions have been requested from people who initially worked in the branding initiative. Either there isn't feedback yet, or the people aren't currently available to support the i-Team. Ongoing ...
**2010-06-30: Still ongoing ...
**2010-07-22: Andreas provided some insight what currently happens within Oracle. The topic "icons" is currently addressed ...
***A discussion took place with Michael Bemmer and other people at Oracle.
***Outcome: Oracle marketing made a decision that is supposed to be communicated shortly. --> Icons will be redesigned, for the long run, with constraints.
***Motivation: The current design fails with regard to usability aspects. --> Redesign is intended with focus on usability.
***Constraints: The activity will be run open with all necessary involvements.
***Question to Andreas/Martin to discuss whether the official statement may be discussed with the community before it is going to be published "officially".
***Decision to keep this CC Action Item open until there is more visible activity.
**2010-08-12: Marketing contact is in vacation, and information also depends on others at Oracle. More information defitively to come at the OOoCon, presentation "[http://www.ooocon.org/index.php/ooocon/2010/paper/view/215 Brand Refresh and new Brand Initiative]". 
**2010-09-21: Request for update sent to Oracle, nothing new yet.
*Next steps: Waiting for the reaction by Oracle, either getting in touch with the community or an official announcement. 
*Cornouws: discussed during OOoCon; looks as if we were able to bring accros the importancy, however, other tasks ask attention first from Oracle people. 
|-
| 2010-11-25#1 
| Update OOo Internship Project 2010 
| New 
| JSC 
| 2010-11-25 
|
* the project ended official on November 14th 
* 5 of 6 project finished successful. One project is put on hold by a request of the student because the lack of time. We offered to finish this project later after the exam when the student has more time again. 
* all projects had a good outcome which will result in a future office release or where we can at least use it as more than a good start point for further work on this topic/feature. 
* overall a good experience and a good project which we should definitely repeat 
|}

 

== Minutes of Previous Meetings ==

To be found [[Community Council/Minutes|here]].

[[Category:Community_Council]]

Community Council/Agenda

2010-11-25T20:20:17Z

ErAck: repair

{{Community_Council}}
== Upcoming Meeting ==

Date: 2010-11-04 (Derived from the [[Community Council/Calendar|Community Council Meeting Calendar]])

Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=04&month=11&year=2010&hour=19&min=30&sec=0&p1=0 19.30 UTC] (click on the link to show world clock times)

Location: IRC

== Agenda and Work Status ==

The following table represents the agenda of the upcoming meeting and the current work status of topics / action items. Working with this table is described in the [[Community Council/Meeting Guidelines|Community Council Meeting Guidelines]].

{| class="prettytable sortable"
|-
! scope="col" | ID 
! scope="col" | Topic 
! scope="col" | Status 
! scope="col" | Responsible 
! scope="col" | Last Update 
! scope="col" | Details 
|-
| 0 
| List of Action Items of previous meeting for approval 
| ''none'' 
| all 
| 2010-10-14 
|
*Meeting minutes of previous meeting at [[Community Council/Minutes#2010-10-14|Minutes#2010-10-14]] 
*Result: (to be confirmed)

|-
| 2010-10-14#1 
| Where do we stand 
| new 
| all 
| 2010-10-14 
|
*Now that many members of the community council support the Document Foundation: how do find the best way to go on?
*Discussion: A summary seems hard to provide, so please consider to read the [[Community Council Log 20101014#IRC_Log_2010-10-14|IRC Log]].
*Result: Cor and Martin will have a talk and discuss the topic. Additionally, some community council members request to resolve the issue by next Tuesday (2010-10-19).

|-
| bgcolor="#ffffcc" colspan="6" | Note: Because of running out of time, the meeting has been. So no further Action Items (below) have been discussed.
|-
| 2010-03-04#2 
| Refresh Incubator and NLC Project processes 
| Accepted 
| Louis 
| 2010-03-18 
|
*The NLC homepage (http://native-lang.openoffice.org/) has the language in the policy I wrote many years ago, and I'll be using a version of that plus the earlier drafts submitted to resolve this. The hangup has been what to do with mothballed projects, what to do with the data. We will create an effective category, with very limited permissions, called something like, "Inactive Projects" and the data will remain there, unto perpetuity or the closes thing to it. Expect new update by next CC meeting. 

|-
| 2010-03-04#6 
| Talk to Education Project Leads about structure and remit 
| Stalled 
| louis 
| 2010-03-18 
|
|-
| 2010-04-01#1 
*Louis to take this on and report by next CC meeting of discussions held with the responsible persons. 
| Community situation 
| Accepted 
| All 
| 2010-09-23 
|
*What do we see, where are we, what are we going to do about it. 
*Activities:
**All CC members are asked to think about it and Cor will prepare a proposal for an detailed agenda. 
**Leif already collected some issues (e.g. rare communication via blogs) and will send that to Cor. 
*Next Steps: Proposal that the CC will work on that at the OOoCon in Budapest.
**Cor send a mail on 2010-08-12 with some items for the agenda. 
*2010-09-03/09-21: Page with draft plan [[Community Council/collaboration in the OOo-community|improvement community collaboration]]

|-
| 2010-04-29#2 
|
Missing OOo desktop presence

| Accepted 
| Christoph, Stefan
| 2010-09-21 
|
*Request by a community member to discuss / decide the following question: "''Why should OpenOffice.org give away it's presence on the user's desktop - the main place to be recognized by the people - only to support the "application independency" of ODF?'' A Sun employee stated "The idea of supporting ODF as a application independent open standard is the priority." This leads / will lead to changes with regard to the document and application icon design. The current ODF "only" icons seem to be undesired by the community. Original request to the CC on ooo-discuss: [http://www.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=65958 initial mail (2010-04-14)], [http://www.openoffice.org/servlets/BrowseList?listName=discuss&from=2361081&to=2361081&count=28&by=thread&first=1&windowSize=1000 full mail thread]
*Discussion:
**2010-04-29: Some members stated that the request should be "more actionable" and "better framed" to be decided by the community. Proposal has been made to forward the request to council-discuss to propose how to proceed.
**2010-05-02: Christoph forwarded the [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=2564 request to the CC mailing list]. A first discussion took place.
**2010-05-20: Intensive discussion about the request and how to address it. Stefan and Christoph agreed to work out a request to the ODF Icons team to iterate on the design and/or processes. Maybe a "refreshed" team which may provide an agreed-upon proposal. Stefan stated that there shouldn't be any dependency to the next/other releases.
**2010-06-08: Some opinions have been requested from people who initially worked in the branding initiative. Either there isn't feedback yet, or the people aren't currently available to support the i-Team. Ongoing ...
**2010-06-30: Still ongoing ...
**2010-07-22: Andreas provided some insight what currently happens within Oracle. The topic "icons" is currently addressed ...
***A discussion took place with Michael Bemmer and other people at Oracle.
***Outcome: Oracle marketing made a decision that is supposed to be communicated shortly. --> Icons will be redesigned, for the long run, with constraints.
***Motivation: The current design fails with regard to usability aspects. --> Redesign is intended with focus on usability.
***Constraints: The activity will be run open with all necessary involvements.
***Question to Andreas/Martin to discuss whether the official statement may be discussed with the community before it is going to be published "officially".
***Decision to keep this CC Action Item open until there is more visible activity.
**2010-08-12: Marketing contact is in vacation, and information also depends on others at Oracle. More information defitively to come at the OOoCon, presentation "[http://www.ooocon.org/index.php/ooocon/2010/paper/view/215 Brand Refresh and new Brand Initiative]". 
**2010-09-21: Request for update sent to Oracle, nothing new yet.
*Next steps: Waiting for the reaction by Oracle, either getting in touch with the community or an official announcement. 
*Cornouws: discussed during OOoCon; looks as if we were able to bring accros the importancy, however, other tasks ask attention first from Oracle people. 
|-
| 2010-11-25#1 
| Update OOo Internship Project 2010 
| New 
| JSC 
| 2010-11-25 
|
* the project ended official on November 14th 
* 5 of 6 project finished successful. One project is put on hold by a request of the student because the lack of time. We offered to finish this project later after the exam when the student has more time again. 
* all projects had a good outcome which will result in a future office release or where we can at least use it as more than a good start point for further work on this topic/feature. 
* overall a good experience and a good project which we should definitely repeat 
|}

 

== Minutes of Previous Meetings ==

To be found [[Community Council/Minutes|here]].

[[Category:Community_Council]]

Talk:Editor Vim

2010-11-22T13:24:00Z

ErAck: /* VIM CVS and SSH configuration */

== VIM CVS and SSH configuration ==

Would be nice to have a tutorial to use the CVS/SSH from OOo configured with the VCSCOMMAND plugin. This will make it easy to just use our keys with VIM directly on the CVS tree.

: No special handling needed. With the SSH tunnel opened all CVS commands are handled transparently, also from VCScommand. --[[User:ErAck|erAck]] 13:24, 22 November 2010 (UTC)

User talk:ErAck

2010-11-22T12:37:23Z

ErAck: /* VCSCOMMAND */

== VCSCOMMAND ==

Hi you ever used the vcscommand? Wonder if there is a way to get the file up and running with the OOo's CVS/Mercurial trees through ssh.
: I assume you refer the Vim http://www.vim.org/scripts/script.php?script_id=90 plugin. I use that, but never the VCSCommit command as I much prefer to commit a changeset containing all related files at once. I wonder though what you mean by <q>the OOo's CVS/Mercurial trees through ssh</q>, as the VCScommands always work against the local Mercurial repository. Not with CSV, but CSV is dead except for the web pages. With CSV you setup a tunnel anyway, so that should be transparent to VCScommand. AFAIR (years ago) there were no problems using that with CSV.

Editor Vim

2010-11-22T12:25:41Z

ErAck: /* CVS/SVN integration */ HG

There exist only two real editors in the programmer's world ;-) One is Vim,
and the other is the ''eier-legende-woll-milch-sau'' (sorry for that German
phrase being a modified translation of
''allrounder - all-in-one device suitable for every purpose'',
couldn't resist ;-) (X)Emacs. So here we go for Vim.

== General Vim settings ==

In ''.vimrc'' have the following settings. For the tabstops=4 setting it may
not be desired to have this globally effective, you may want to restrict it to
an OOo/SO environment by evaluating the $SOLARENV environment variable,
<code>if $SOLARENV != ""</code>

<pre>
set ts=4 " tabstops are 4 (for all code)
set sw=4 " shiftwidth is 4
set expandtab " expand tabs to spaces
set showmatch " briefly jump to matching brackets
set showmode " the mode we're in
if version >= 600
filetype on " enable file type detection
filetype plugin on " enable file type plugins
filetype indent on " enable file type indents
endif

" previous and next compiler error (quickfix)
map <C-P> :cp<CR>
map <C-N> :cn<CR>

" Only do this part when compiled with support for autocommands.
if has("autocmd")

" In text files, always limit the width of text to 78 characters, tabs are 8
autocmd BufRead *.txt,*.doc,*.dok setlocal tw=78 ts=8 sw=8 fo+=rn1

" Treat resource files and headers like C files
autocmd BufRead *.hrc,*.src setlocal ft=c

" Treat generated UNO header files like C++ files
autocmd BufRead *.hdl setlocal ft=cpp

" mail bodies have a textwidth of 72 characters, activate numbering
" formatting, reset comments to default, no indenting
autocmd FileType mail setlocal tw=72 fo+=rn1 comments& nocindent

" AutoDoc comments in C/C++ files without '*' middle part
autocmd FileType c,cpp setlocal comments^=s:/**,mb:\ ,e:*/

" AutoDoc comments in IDL files have a textwidth of 72 characters
autocmd FileType idl setlocal comments^=s:/**,mb:\ ,e:*/ tw=72

" OOo .xcu configuration files and the like
autocmd FileType xml setlocal sw=2

" HTML files
autocmd FileType html,css setlocal sw=2

endif

" setting up for :make
set makeprg=$SOLARENV/bin/build.pl\ \-P4\ \-\-\ \-P4

" broken whitespace
:au Syntax * syn match Error /\s\+$/ | syn match Error /^\s* \t\s*/
</pre>

== Vim and the GNU ID-utils ==

As mentioned in [[Little_Helpers#GNU_ID-utils | Little Helpers' GNU Id-utils]], the ''eid'' command makes use of some
environment variables when invoking the editor:

<pre>
setenv VISUAL vim
setenv EIDARG '+/%s/'
setenv EIDLDEL '\<'
setenv EIDRDEL '\>'
</pre>

To be able to invoke the ''lid'' utility from within Vim we need a key mapping
and function call, you may place this section into your ''.vimrc'' file:

<pre>
" GNU id-utils, taken from :h ident-search
" Generate the ID file in the current directory or in .. or ../.. or ../../..
" To use it, place the cursor on a word, type "_u" and vim will load the file
" that contains the word. Search for the next occurrence of the word in the
" same file with "n". Go to the next file with "_n".
map _u :call ID_search()<Bar>execute "/\\<" . g:word . "\\>"<CR>
map _n :n<Bar>execute "/\\<" . g:word . "\\>"<CR>
function ID_search()
let g:word = expand("<cword>")
let x = system("lid --key=none ". g:word)
let x = substitute(x, "\n", " ", "g")
execute "next " . x
endfun
</pre>

=== lid.vim plugin ===

[http://vim.sourceforge.net/scripts/script.php?script_id=251 lid.vim] is
a plugin to integrate GNU id-utils with Vim, providing a ''lid -g'' output in
the ''quickfix'' window that can be travelled using the '':cnext'' and
'':cprev'' commands respectively their keyboard mappings.

== Vim and Ctags ==

That's easy, as vim has builtin support for ctags, see '':h tagsrch.txt'', in
''.vimrc'' just tell it where to search for the ''tags'' files:

<pre>
" Tags files are searched first relative to the current file, then relative to
" the current working directory, and last in the $HOME directory.
set tags=./tags,./../tags,./../../tags,./../../../tags,./../../../../tags,./../../../../../tags,tags,../tags,../../tags,../../../tags,../../../../tags,../../../../../tags,~/tags
</pre>

For general ''Exuberant Ctags'' information and a script how to create the ''tags'' database see the [[Little_Helpers#Exuberant_Ctags | Little Helpers' Exuberant Ctags]] section.

== Vim and Cscope ==

For general ''Cscope'' information and a script how to create a cscope
database for an OOo project see the
[[Little_Helpers#Cscope | Little Helpers' Cscope]]
section.

=== Builtin Cscope support ===

Vim has builtin (well, if compiled in) support for cscope, see '':h cscope''.
In ''.vimrc'' you may want to setup some things, but this is also a matter of
work habits. Consider the following an example and consult the fine manual.

<pre>
" Cscope settings
if has("cscope")
" quickfix window usage
set cscopequickfix=s-,c-,d-,i-,t-,e-
" :tag and the like use :cstag
set cscopetag
" first search cscope, than tags file
set cscopetagorder=0
set nocsverb
" add any database in current directory
if filereadable("cscope.out")
cs add cscope.out
" else add database pointed to by environment
elseif $CSCOPE_DB != ""
cs add $CSCOPE_DB
endif
set csverb
endif
</pre>

=== More comfortable plugin script cecscope.vim ===

The
[http://www.vim.org/scripts/script.php?script_id=1453 command and menu driven cscope interface]
eases things a bit. It requires vim7.0aa snapshot #188 or later, the Vim7.1
release does fine.

== Include file searches in Vim ==

Set the ''path'' variable in ''.vimrc'':

<pre>
" Where to look for files in gf and ^Wf and similar commands,
" and for include files for i_^X^I and i_^X^D commands.
" To use VIM_INC in OOo/SO environment define
" alias solvim 'if ( ! $?UPDMINOREXT ) setenv UPDMINOREXT "" ; setenv VIM_INC ./${INPATH}/inc,../${INPATH}/inc,../../${INPATH}/inc,../../../${INPATH}/inc,`echo $SOLARINC|sed -e "s/^-I//" -e "s/ *-I/,/g"`,${SOLARVERSION}/${INPATH}/inc${UPDMINOREXT}/offuh'
" Note the two space characters in the second substitute, and execute the alias after a setsolar.
" Under 4NT you need some rubbish like (note this isn't updated since ages)
" alias solvim=set _uq_%0=%@unique[%tmp%] && echos VIM_INC=>>_uq_%0 && echo %SOLARINC|sed -e "s/^-I//" -e "s/ \+-I/,/g">>_uq_%0 && set /r _uq_%0 && del /q _uq_%0
set path=.,./inc,./../inc,./../../inc,./../../../inc,./../../../../inc,$VIM_INC,,/usr/local/include,/usr/include
</pre>

In case you missed it in the comments above: you need to invoke a shell alias
after having sourced the environment:

<pre>
tcsh
alias solvim 'if ( ! $?UPDMINOREXT ) setenv UPDMINOREXT "" ; setenv VIM_INC ./${INPATH}/inc,../${INPATH}/inc,../../${INPATH}/inc,../../../${INPATH}/inc,`echo $SOLARINC|sed -e "s/^-I//" -e "s/ *-I/,/g"`,${SOLARVERSION}/${INPATH}/inc${UPDMINOREXT}/offuh'
source LinuxX86Env.Set
solvim
</pre>

See also: in Vim '':h include-search''

== Compiling a source from within Vim ==

Compiling the source from within the editor is of course desired, as warnings
and errors generated by the compiler let you directly jump to the line in
question. There are some quirks to be solved for the OOo/SO environment, but no
real problem, just examine the working ''.vimrc'' sections below. Pressing
Ctrl+K changes the current window's directory locally to the one of the file
loaded, if there is a makfile.mk in that directory, sets the ''makeprg''
variable to the command needed to dmake just the current file, and executes it.

For the quickfix window to pull its content from the compiler output we need to
have a valid error file setting, and as there's always the hassle with DOS
based systems, we also need to take care of that:

<pre>
" This uses the TMP environment variable, be sure to have it set!
if $COMSPEC =~ "\\"
" seems like we're having any DOS
set makeef=$TMP\\vim##.err " :make errorfile
else
set makeef=$TMP/vim##.err " :make errorfile
endif
if $TMP =~ "\\" && ($COMSPEC =~ "4" || $SHELL =~ "4")
" seems like we're having some DOS assumed to be 4DOS compatible
set shellpipe=\|&\ tee
endif
</pre>

Now the ''makeprg'' setting:

<pre>
" Call appropriate makeprg with Ctrl+K
map <C-K> :call Make()<CR>

if $SOLARENV == ""
" Normal makeprg, not in OpenOffice.org/StarOffice environment
function Make()
make
endfun
else
" Special dmake, only in OpenOffice.org/StarOffice environment
set makeprg=dmake
function SetMakeprg()
" For a detached gvim we need to source the environment, assuming
" the current working directory being source/core/tool/ or
" similar, and having a copy of the setsolar -file environment
" file as module/../ENV.$INPATH or in $SRC_ROOT set a
" ln -s LinuxX86Env.Set ENV.$INPATH
" For terminal vim re-sourcing the environment isn't necessary.
if has("gui_running")
if filereadable( "./prj/d.lst" )
set makeprg=source\ ../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ./$INPATH/slo/%:t:r.obj
elseif filereadable( "../prj/d.lst" )
set makeprg=source\ ../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../prj/d.lst" )
set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../prj/d.lst" )
set makeprg=source\ ../../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../../prj/d.lst" )
set makeprg=source\ ../../../../../ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t\ ../../../../$INPATH/slo/%:t:r.obj
else
set makeprg=source\ ./ENV.$INPATH\ \&\&\ dmake\ wall=t\ debug=t
endif
else
if filereadable( "./prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ./$INPATH/slo/%:t:r.obj
elseif filereadable( "../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../../$INPATH/slo/%:t:r.obj
elseif filereadable( "../../../../prj/d.lst" )
set makeprg=dmake\ wall=t\ debug=t\ ../../../../$INPATH/slo/%:t:r.obj
else
set makeprg=dmake\ wall=t\ debug=t
endif
endif
" Just some copy&paste versions:
" Entire module, edit ENV.... and set BUILD_COMMAND to content of build alias
"set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ $BUILD_COMMAND
"set makeprg=source\ ../../../ENV.$INPATH\ \&\&\ dmake\ ../../../$INPATH/slo/%:t:r.obj
"set makeprg=dmake\ product=full
" temporary override, no wall, no debug
"if filereadable( "./prj/d.lst" )
" set makeprg=dmake\ ./$INPATH/slo/%:t:r.obj
"elseif filereadable( "../prj/d.lst" )
" set makeprg=dmake\ ../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../prj/d.lst" )
" set makeprg=dmake\ ../../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../../prj/d.lst" )
" set makeprg=dmake\ ../../../$INPATH/slo/%:t:r.obj
"elseif filereadable( "../../../../prj/d.lst" )
" set makeprg=dmake\ ../../../../$INPATH/slo/%:t:r.obj
"else
" set makeprg=dmake
"endif
endfun
function Make()
let my_local_path = expand("%:h")
if (my_local_path == "")
let my_local_path = "."
endif
if filereadable( my_local_path . "/makefile.mk" )
exec 'lcd ' . my_local_path
call SetMakeprg()
make
else
echo "No makefile.mk in " . my_local_path
endif
endfun
endif
</pre>

== CVS/SVN/HG integration ==

=== CVS/SVN/HG commands ===

[http://vim.sourceforge.net/scripts/script.php?script_id=90 vcscommand.vim - CVS/SVN integration plugin]

A nice plugin to handle CVS, SVN and HG actions from within Vim. Most useful being
the VCSAnnotate and VCSVimDiff commands, IMHO.

=== Resolve CVS conflicts ===

[http://www.vim.org/scripts/script.php?script_id=1370 CVSconflict - CVS conflict resolution using vimdiff]

A plugin that converts a source file containing CVS merge conflicts into two
VimDiff buffers that then can be easily edited:

== Other useful plugins and resources ==

* [http://www.vim.org/scripts/script.php?script_id=1520 OmniCppComplete - C++ completion omnifunc with a ctags database]
* [http://www.vim.org/scripts/script.php?script_id=1997 undo_tags - small utility that lets you tag undo branches]
* [http://www.erack.de/bookmarks/D.html#VIM erAck's ''VIM and related'' bookmarks]

== A note for developers on WIN\DOS ==

Please don't complicate life for developers on other platforms by interspersing
sources with CarriageReturn characters before linefeeds, which especially is
extremely nasty in patches contributed. As you probably can't patch your
kernel's IO to simply not automatically write CrLf instead of Lf in text files,
when using Vim use this setting:

<pre>
"set fileformats=dos,unix " Vim's default on DOS/WIN/OS2
set fileformats=unix,dos " Vim's default on UNX, also use it on DOS
</pre>

[[Category:Developer Tools]]

Hackfest2010

2010-11-02T00:52:15Z

ErAck: /* Announcement */ preliminary times

{{DISPLAYTITLE:OpenOffice.org HackFest 2010}}
__TOC__

== Announcement ==

[[Hackfest2010/de|Für die deutsche Version dieser Seite klickt bitte hier.]]

 

Dear OOo hackers,

the OOoCon just ended, and we realize how little time we can spend together face2face each year. To properly fix that problem, we hereby announce the next event around OpenOffice.org - a HackFest in Hamburg, specifically targeted to developers, to give all of us more face time & collectively work on the code.

'''The OpenOffice.org HackFest will take place on the weekend of November 6./7. 2010 in the [http://wiki.attraktor.org/index.php/Mex Attraktor in Hamburg]''', and a tentative program could look like this:

*Friday night - beer & fun, warming up, starting 19:00 in the ''Schachcafé'', see below under [[#How_to_get_there]]
*Saturday morning from 11:00 on - Intro talks, Hands-on sessions
*Saturday afternoon/night - collective hacking, bug fixing
*Sunday morning from 11:00 on - wrap-up, review, document

For those who are in need for a bursary, we have a limited travel funding budget available. For sleeping, couchsurfing at the organizers is available. Be aware that would be in an unheated loft, so bringing a sleeping mat and a good sleeping bag would be essential. For more comfortable reasonably priced acommodations see [[Sleeping in Hamburg|the wiki page]]. 

We look forward to meet you there, stay tuned for further announcements around programme and sponsoring! To register yourself, just drop a short note to [mailto:hackfest@openoffice.org hackfest@openoffice.org] and we'll follow up with further information soon. 

Faithfully, your HackFest organizers

Eike, Florian & Thorsten [mailto:hackfest@openoffice.org hackfest@openoffice.org]

== Topics ==

Ideas and topics that could be worked on are collected at [[Hackfest2010/Topics]].

== Location ==

Location at OpenStreetMap: [http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M] Location at Google Maps: [http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18 http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18] 

=== How to get there ===

From Central Station (Hauptbahnhof):
* Take the city train ''S1'' or ''S11'' direction ''Ohlsdorf'' or direction ''Airport/Poppenbüttel'' ([http://www.hvv.de/en/timetables-lines-routes/plans-line-route-networks/usar/ green line]).
* Get off at '''Rübenkamp (City Nord)''', which is 8 stations from central station, the ride will take 17 minutes.
* Take the exit ''City Nord, Fachhochschule, Hebebrandstraße'' in the direction of travel, North.
* The restaurant ''[http://www.schachcafe-hamburg.de/ Schachcafé]'' where we meet for the social on Friday evening starting from 19:00 is located directly at the exit.
* To get to the ''Attraktor e.V.'' location, either
** take the bus ''26'' direction ''S Hamburg Airport'' or ''U Alsterdorf'' and get off at the second stop '''Dakarweg''', take the stairs on the right before the bridge, or
** walk about 1200m to the West along ''Hebebrandstraße'', ''Überseering'', take the stairs on the right before the bridge
* then on the upper level walk straight into ''Attraktor e.V.'', see [http://www.openstreetmap.org/?lat=53.602862&lon=10.024229&zoom=18&layers=M map].

'''Note:''' The entire building complex is on two levels, the Attraktor e.V. is located on the upper level.

If you know the way or dare to find your way ;-) you may walk from ''S Rübenkamp'' exit South all the ''Dakarweg'', cross the bridge and stay on the upper level. A nicer walk but may get tricky, see [http://www.openstreetmap.org/?lat=53.60327&lon=10.02789&zoom=17&layers=M map]. Not recommendable at night, at least not for the first time..

=== How to get away ===

The last bus ''26'' direction ''Bf Rahlstedt'' to get to ''S Rübenkamp'' goes at 22:52.

At ''Rübenkamp'' the ''S1'' direction ''Blankenese'' to get to the Central Station runs every 20 minutes all night, on *:02 *:22 and *:42.

=== Public transport tips ===

If you stay all 3 days it pays to buy a 3-day ticket (''3-Tage-Karte'') for 15.90€. Staying less than 3 days if you plan more than 2 rides a day buy a 9 o'clock day ticket (''9-Uhr-Tageskarte'') after 9:00 for the Greater Hamburg Area (''Großbereich'') for 5.90€, valid until 6:00 in the morning of the following day. A single ticket (''Einzelkarte'') is 2.75€, round or return trips are not permitted.

Subway and city trains run every 20 minutes the entire night during weekends.

See [http://www.hvv.de/ HVV German] or [http://www.hvv.de/en/ HVV English] for details.

[[Category:Conferences]]
{{CCBY}}

Hackfest2010

2010-11-02T00:49:00Z

ErAck: /* Announcement */

{{DISPLAYTITLE:OpenOffice.org HackFest 2010}}
__TOC__

== Announcement ==

[[Hackfest2010/de|Für die deutsche Version dieser Seite klickt bitte hier.]]

 

Dear OOo hackers,

the OOoCon just ended, and we realize how little time we can spend together face2face each year. To properly fix that problem, we hereby announce the next event around OpenOffice.org - a HackFest in Hamburg, specifically targeted to developers, to give all of us more face time & collectively work on the code.

'''The OpenOffice.org HackFest will take place on the weekend of November 6./7. 2010 in the [http://wiki.attraktor.org/index.php/Mex Attraktor in Hamburg]''', and a tentative program could look like this:

*Friday night - beer & fun, warming up, starting 19:00 in the ''Schachcafé'', see below under [[#How_to_get_there]]
*Saturday morning - Intro talks, Hands-on sessions
*Saturday afternoon/night - collective hacking, bug fixing
*Sunday morning - wrap-up, review, document

For those who are in need for a bursary, we have a limited travel funding budget available. For sleeping, couchsurfing at the organizers is available. Be aware that would be in an unheated loft, so bringing a sleeping mat and a good sleeping bag would be essential. For more comfortable reasonably priced acommodations see [[Sleeping in Hamburg|the wiki page]]. 

We look forward to meet you there, stay tuned for further announcements around programme and sponsoring! To register yourself, just drop a short note to [mailto:hackfest@openoffice.org hackfest@openoffice.org] and we'll follow up with further information soon. 

Faithfully, your HackFest organizers

Eike, Florian & Thorsten [mailto:hackfest@openoffice.org hackfest@openoffice.org]

== Topics ==

Ideas and topics that could be worked on are collected at [[Hackfest2010/Topics]].

== Location ==

Location at OpenStreetMap: [http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M] Location at Google Maps: [http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18 http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18] 

=== How to get there ===

From Central Station (Hauptbahnhof):
* Take the city train ''S1'' or ''S11'' direction ''Ohlsdorf'' or direction ''Airport/Poppenbüttel'' ([http://www.hvv.de/en/timetables-lines-routes/plans-line-route-networks/usar/ green line]).
* Get off at '''Rübenkamp (City Nord)''', which is 8 stations from central station, the ride will take 17 minutes.
* Take the exit ''City Nord, Fachhochschule, Hebebrandstraße'' in the direction of travel, North.
* The restaurant ''[http://www.schachcafe-hamburg.de/ Schachcafé]'' where we meet for the social on Friday evening starting from 19:00 is located directly at the exit.
* To get to the ''Attraktor e.V.'' location, either
** take the bus ''26'' direction ''S Hamburg Airport'' or ''U Alsterdorf'' and get off at the second stop '''Dakarweg''', take the stairs on the right before the bridge, or
** walk about 1200m to the West along ''Hebebrandstraße'', ''Überseering'', take the stairs on the right before the bridge
* then on the upper level walk straight into ''Attraktor e.V.'', see [http://www.openstreetmap.org/?lat=53.602862&lon=10.024229&zoom=18&layers=M map].

'''Note:''' The entire building complex is on two levels, the Attraktor e.V. is located on the upper level.

If you know the way or dare to find your way ;-) you may walk from ''S Rübenkamp'' exit South all the ''Dakarweg'', cross the bridge and stay on the upper level. A nicer walk but may get tricky, see [http://www.openstreetmap.org/?lat=53.60327&lon=10.02789&zoom=17&layers=M map]. Not recommendable at night, at least not for the first time..

=== How to get away ===

The last bus ''26'' direction ''Bf Rahlstedt'' to get to ''S Rübenkamp'' goes at 22:52.

At ''Rübenkamp'' the ''S1'' direction ''Blankenese'' to get to the Central Station runs every 20 minutes all night, on *:02 *:22 and *:42.

=== Public transport tips ===

If you stay all 3 days it pays to buy a 3-day ticket (''3-Tage-Karte'') for 15.90€. Staying less than 3 days if you plan more than 2 rides a day buy a 9 o'clock day ticket (''9-Uhr-Tageskarte'') after 9:00 for the Greater Hamburg Area (''Großbereich'') for 5.90€, valid until 6:00 in the morning of the following day. A single ticket (''Einzelkarte'') is 2.75€, round or return trips are not permitted.

Subway and city trains run every 20 minutes the entire night during weekends.

See [http://www.hvv.de/ HVV German] or [http://www.hvv.de/en/ HVV English] for details.

[[Category:Conferences]]
{{CCBY}}

Hackfest2010

2010-11-02T00:44:10Z

ErAck:

{{DISPLAYTITLE:OpenOffice.org HackFest 2010}}
__TOC__

== Announcement ==

[[Hackfest2010/de|Für die deutsche Version dieser Seite klickt bitte hier.]]

 

Dear OOo hackers,

the OOoCon just ended, and we realize how little time we can spend together face2face each year. To properly fix that problem, we hereby announce the next event around OpenOffice.org - a HackFest in Hamburg, specifically targeted to developers, to give all of us more face time & collectively work on the code.

'''The OpenOffice.org HackFest will take place on the weekend of November 6./7. 2010 in the [http://wiki.attraktor.org/index.php/Mex Attraktor in Hamburg]''', and a tentative program could look like this:

*Friday night - beer & fun, warming up
*Saturday morning - Intro talks, Hands-on sessions
*Saturday afternoon/night - collective hacking, bug fixing
*Sunday morning - wrap-up, review, document

For those who are in need for a bursary, we have a limited travel funding budget available. For sleeping, couchsurfing at the organizers is available. Be aware that would be in an unheated loft, so bringing a sleeping mat and a good sleeping bag would be essential. For more comfortable reasonably priced acommodations see [[Sleeping in Hamburg|the wiki page]]. 

We look forward to meet you there, stay tuned for further announcements around programme and sponsoring! To register yourself, just drop a short note to [mailto:hackfest@openoffice.org hackfest@openoffice.org] and we'll follow up with further information soon. 

Faithfully, your HackFest organizers

Eike, Florian & Thorsten [mailto:hackfest@openoffice.org hackfest@openoffice.org]

== Topics ==

Ideas and topics that could be worked on are collected at [[Hackfest2010/Topics]].

== Location ==

Location at OpenStreetMap: [http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M] Location at Google Maps: [http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18 http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18] 

=== How to get there ===

From Central Station (Hauptbahnhof):
* Take the city train ''S1'' or ''S11'' direction ''Ohlsdorf'' or direction ''Airport/Poppenbüttel'' ([http://www.hvv.de/en/timetables-lines-routes/plans-line-route-networks/usar/ green line]).
* Get off at '''Rübenkamp (City Nord)''', which is 8 stations from central station, the ride will take 17 minutes.
* Take the exit ''City Nord, Fachhochschule, Hebebrandstraße'' in the direction of travel, North.
* The restaurant ''[http://www.schachcafe-hamburg.de/ Schachcafé]'' where we meet for the social on Friday evening starting from 19:00 is located directly at the exit.
* To get to the ''Attraktor e.V.'' location, either
** take the bus ''26'' direction ''S Hamburg Airport'' or ''U Alsterdorf'' and get off at the second stop '''Dakarweg''', take the stairs on the right before the bridge, or
** walk about 1200m to the West along ''Hebebrandstraße'', ''Überseering'', take the stairs on the right before the bridge
* then on the upper level walk straight into ''Attraktor e.V.'', see [http://www.openstreetmap.org/?lat=53.602862&lon=10.024229&zoom=18&layers=M map].

'''Note:''' The entire building complex is on two levels, the Attraktor e.V. is located on the upper level.

If you know the way or dare to find your way ;-) you may walk from ''S Rübenkamp'' exit South all the ''Dakarweg'', cross the bridge and stay on the upper level. A nicer walk but may get tricky, see [http://www.openstreetmap.org/?lat=53.60327&lon=10.02789&zoom=17&layers=M map]. Not recommendable at night, at least not for the first time..

=== How to get away ===

The last bus ''26'' direction ''Bf Rahlstedt'' to get to ''S Rübenkamp'' goes at 22:52.

At ''Rübenkamp'' the ''S1'' direction ''Blankenese'' to get to the Central Station runs every 20 minutes all night, on *:02 *:22 and *:42.

=== Public transport tips ===

If you stay all 3 days it pays to buy a 3-day ticket (''3-Tage-Karte'') for 15.90€. Staying less than 3 days if you plan more than 2 rides a day buy a 9 o'clock day ticket (''9-Uhr-Tageskarte'') after 9:00 for the Greater Hamburg Area (''Großbereich'') for 5.90€, valid until 6:00 in the morning of the following day. A single ticket (''Einzelkarte'') is 2.75€, round or return trips are not permitted.

Subway and city trains run every 20 minutes the entire night during weekends.

See [http://www.hvv.de/ HVV German] or [http://www.hvv.de/en/ HVV English] for details.

[[Category:Conferences]]
{{CCBY}}

Hackfest2010

2010-11-02T00:42:33Z

ErAck: /* Location */ more public transport

{{DISPLAYTITLE:OpenOffice.org HackFest 2010}}
__TOC__

== Announcement ==

[[Hackfest2010/de|Für die deutsche Version dieser Seite klickt bitte hier.]]

 

Dear OOo hackers,

the OOoCon just ended, and we realize how little time we can spend together face2face each year. To properly fix that problem, we hereby announce the next event around OpenOffice.org - a HackFest in Hamburg, specifically targeted to developers, to give all of us more face time & collectively work on the code.

'''The OpenOffice.org HackFest will take place on the weekend of November 6./7. 2010 in the [http://wiki.attraktor.org/index.php/Mex Attraktor in Hamburg]''', and a tentative program could look like this:

*Friday night - beer & fun, warming up
*Saturday morning - Intro talks, Hands-on sessions
*Saturday afternoon/night - collective hacking, bug fixing
*Sunday morning - wrap-up, review, document

For those who are in need for a bursary, we have a limited travel funding budget available. For sleeping, couchsurfing at the organizers is available. Be aware that would be in an unheated loft, so bringing a sleeping mat and a good sleeping bag would be essential. For more comfortable reasonably priced acommodations see [[Sleeping in Hamburg|the wiki page]]. 

We look forward to meet you there, stay tuned for further announcements around programme and sponsoring! To register yourself, just drop a short note to [mailto:hackfest@openoffice.org hackfest@openoffice.org] and we'll follow up with further information soon. 

Faithfully, your HackFest organizers

Eike, Florian & Thorsten [mailto:hackfest@openoffice.org hackfest@openoffice.org]

== Location ==

Location at OpenStreetMap: [http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M] Location at Google Maps: [http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18 http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18] 

=== How to get there ===

From Central Station (Hauptbahnhof):
* Take the city train ''S1'' or ''S11'' direction ''Ohlsdorf'' or direction ''Airport/Poppenbüttel'' ([http://www.hvv.de/en/timetables-lines-routes/plans-line-route-networks/usar/ green line]).
* Get off at '''Rübenkamp (City Nord)''', which is 8 stations from central station, the ride will take 17 minutes.
* Take the exit ''City Nord, Fachhochschule, Hebebrandstraße'' in the direction of travel, North.
* The restaurant ''[http://www.schachcafe-hamburg.de/ Schachcafé]'' where we meet for the social on Friday evening starting from 19:00 is located directly at the exit.
* To get to the ''Attraktor e.V.'' location, either
** take the bus ''26'' direction ''S Hamburg Airport'' or ''U Alsterdorf'' and get off at the second stop '''Dakarweg''', take the stairs on the right before the bridge, or
** walk about 1200m to the West along ''Hebebrandstraße'', ''Überseering'', take the stairs on the right before the bridge
* then on the upper level walk straight into ''Attraktor e.V.'', see [http://www.openstreetmap.org/?lat=53.602862&lon=10.024229&zoom=18&layers=M map].

'''Note:''' The entire building complex is on two levels, the Attraktor e.V. is located on the upper level.

If you know the way or dare to find your way ;-) you may walk from ''S Rübenkamp'' exit South all the ''Dakarweg'', cross the bridge and stay on the upper level. A nicer walk but may get tricky, see [http://www.openstreetmap.org/?lat=53.60327&lon=10.02789&zoom=17&layers=M map]. Not recommendable at night, at least not for the first time..

=== How to get away ===

The last bus ''26'' direction ''Bf Rahlstedt'' to get to ''S Rübenkamp'' goes at 22:52.

At ''Rübenkamp'' the ''S1'' direction ''Blankenese'' to get to the Central Station runs every 20 minutes all night, on *:02 *:22 and *:42.

=== Public transport tips ===

If you stay all 3 days it pays to buy a 3-day ticket (''3-Tage-Karte'') for 15.90€. Staying less than 3 days if you plan more than 2 rides a day buy a 9 o'clock day ticket (''9-Uhr-Tageskarte'') after 9:00 for the Greater Hamburg Area (''Großbereich'') for 5.90€, valid until 6:00 in the morning of the following day. A single ticket (''Einzelkarte'') is 2.75€, round or return trips are not permitted.

Subway and city trains run every 20 minutes the entire night during weekends.

See [http://www.hvv.de/ HVV German] or [http://www.hvv.de/en/ HVV English] for details.

== Topics ==

Ideas and topics that could be worked on are collected at [[Hackfest2010/Topics]].

[[Category:Conferences]]
{{CCBY}}

Hackfest2010

2010-11-02T00:15:37Z

ErAck: /* Location */ How to get there

{{DISPLAYTITLE:OpenOffice.org HackFest 2010}}
__TOC__

== Announcement ==

[[Hackfest2010/de|Für die deutsche Version dieser Seite klickt bitte hier.]]

 

Dear OOo hackers,

the OOoCon just ended, and we realize how little time we can spend together face2face each year. To properly fix that problem, we hereby announce the next event around OpenOffice.org - a HackFest in Hamburg, specifically targeted to developers, to give all of us more face time & collectively work on the code.

'''The OpenOffice.org HackFest will take place on the weekend of November 6./7. 2010 in the [http://wiki.attraktor.org/index.php/Mex Attraktor in Hamburg]''', and a tentative program could look like this:

*Friday night - beer & fun, warming up
*Saturday morning - Intro talks, Hands-on sessions
*Saturday afternoon/night - collective hacking, bug fixing
*Sunday morning - wrap-up, review, document

For those who are in need for a bursary, we have a limited travel funding budget available. For sleeping, couchsurfing at the organizers is available. Be aware that would be in an unheated loft, so bringing a sleeping mat and a good sleeping bag would be essential. For more comfortable reasonably priced acommodations see [[Sleeping in Hamburg|the wiki page]]. 

We look forward to meet you there, stay tuned for further announcements around programme and sponsoring! To register yourself, just drop a short note to [mailto:hackfest@openoffice.org hackfest@openoffice.org] and we'll follow up with further information soon. 

Faithfully, your HackFest organizers

Eike, Florian & Thorsten [mailto:hackfest@openoffice.org hackfest@openoffice.org]

== Location ==

Location at OpenStreetMap: [http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M] Location at Google Maps: [http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18 http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18] 

=== How to get there ===

From Central Station (Hauptbahnhof):
* Take the city train ''S1'' or ''S11'' direction ''Ohlsdorf'' or direction ''Airport/Poppenbüttel'' ([http://www.hvv.de/en/timetables-lines-routes/plans-line-route-networks/usar/ green line]).
* Get off at '''Rübenkamp (City Nord)''', which is 8 stations from central station, the ride will take 17 minutes.
* Take the exit ''City Nord, Fachhochschule, Hebebrandstraße'' in the direction of travel, North.
* The restaurant ''[http://www.schachcafe-hamburg.de/ Schachcafé]'' where we meet for the social on Friday evening starting from 19:00 is located directly at the exit.
* To get to the ''Attraktor e.V.'' location, either
** take the bus ''26'' direction ''S Hamburg Airport'' or ''U Alsterdorf'' and get off at the second stop '''Dakarweg''', take the stairs on the right before the bridge, or
** walk about 1200m to the West along ''Hebebrandstraße'', ''Überseering'', take the stairs on the right before the bridge
* then on the upper level walk straight into ''Attraktor e.V.'', see [http://www.openstreetmap.org/?lat=53.602862&lon=10.024229&zoom=18&layers=M map].

'''Note:''' The entire building complex is on two levels, the Attraktor e.V. is located on the upper level.

If you know the way or dare to find your way ;-) you may walk from ''S Rübenkamp'' exit South all the ''Dakarweg'', cross the bridge and stay on the upper level. A nicer walk but may get tricky, see [http://www.openstreetmap.org/?lat=53.60327&lon=10.02789&zoom=17&layers=M map]. Not recommendable at night, at least not for the first time..

== Topics ==

Ideas and topics that could be worked on are collected at [[Hackfest2010/Topics]].

[[Category:Conferences]]
{{CCBY}}

Hackfest2010/Topics

2010-10-18T22:15:28Z

ErAck: /* Concrete Hacks */

{{DISPLAYTITLE:OpenOffice.org HackFest 2010 Topics}}

==Concrete Hacks==

Please add your ideas and topics you'd like to work on or mentor during the hackfest. Issues and/or features to be worked on should either be doable within two days, or at least could be given enough spin to be completed within a reasonable time and amount of effort after the hackfest. If available add links to the corresponding issue and possibly UX or other feature specifications.

Note that this is not an agenda and does not involve any schedule, we're "planning" more in an [http://www.unconference.net/ unConference] style, so about anything may go once the hackfest started. However, getting prepared for some tasks isn't bad either..

{| class="prettytable sortable"
|-
! Module || Topic || Remarks || Issue # || Mentor || Participants Interested
|-
| Calc || Fill operations should not touch filtered rows || A long outstanding issue that if solved would ease many people's itches.. A sketch of possible behavior is available at [[Calc/Drafts/Issue_33851#Fill_cells]] and [[Calc/Drafts/Issue_33851#Fill_series]] || {{Bug|89232}} || Eike Rathke [er] || Nehemiya MAMAN KAKALE Wolfgang Pechlaner {and you} ;-)
|-
| Writer || Unittests || How one creates unittests in the rather tightly coupled writer. || - || Bjoern Michaelsen [b_michaelsen] || Nehemiya MAMAN KAKALE {and you} {and you} ;-)
|-
| solenv || gbuild || The new GNU make based build system by the [[Build Environment Effort]]. || - || Bjoern Michaelsen [b_michaelsen] || {you} {and you} {and you} ;-)
|-
| Chart || implement manually resizing legend || A long outstanding feature request with up to now 116 votes. I have looked in ODF spec in the mean time. It seems that there is no attribute width or height for a legend. So let the user choose the size can only be saved to file format using workarounds. Is that right? If yes, it would not be suitable for our weekend. iha: It is right that those attributes are not available so far in ODF, but this issue is really a pain for the users. ||{{Bug|28670}}|| Ingrid Halama [iha] || Regina {and you} ;-)
|-
| Framework || Implement brackets for negative numbers so, that it is in the given list.|| This is one of the number formatting issues. Perhaps it can be used to get a start to understand number formatting. || {{Bug|15756}} || Eike Rathke [er] || Regina
|-| || || || || ||
|}

==Mentors around==

This is a list of hackers around, that are able to cover/mentor certain subject areas in the code base - if you have specific ideas/plans, poke them if they can help you with that.

{| class="prettytable sortable"
|-
! Modules || Mentor(OOo user name) || Participants Interested
|-
| Calc/I18N || Eike Rathke [er] || Nehemiya MAMAN KAKALE Wolfgang Pechlaner {and you} ;-)
|-
| Draw/Impress/VCL || Thorsten Behrens [thb] || Nehemiya MAMAN KAKALE {and you} {and you} ;-)
|-
| Draw/Impress/Drawinglayer || Armin Le Grand [aw] || Nehemiya MAMAN KAKALE {and you} {and you} ;-)
|-
| Writer || Cédric Bosdonnat [cedricbosdo]|| Nehemiya MAMAN KAKALE {and you} {and you} ;-)
|-
| Writer/New Build System || Bjoern Michaelsen [b_michaelsen] || Nehemiya MAMAN KAKALE {and you} {and you} ;-)
|-
| Calc || Niklas Nebel [nn] || {you} {and you} {and you} ;-)
|-
| gsl || Philipp Lohmann [pl] || {you} {and you} {and you} ;-)
|-
| Chart || Ingrid Halama [iha] || Regina {and you} {and you} ;-)
|-
| Writer || Michael Stahl [mst]|| {you} {and you} {and you} ;-)
|-
|}

[[Category:Conferences]]

Hackfest2010

2010-10-17T14:43:34Z

ErAck: TOC

Hackfest2010/Topics

2010-10-12T13:17:17Z

ErAck: /* Mentors around */

Hackfest2010/Topics

2010-10-10T21:44:16Z

ErAck: "planning" an unConference...

{{DISPLAYTITLE:OpenOffice.org HackFest 2010 Topics}}

Please add your ideas and topics you'd like to work on or mentor during the hackfest. Issues and/or features to be worked on should either be doable within two days, or at least could be given enough spin to be completed within a reasonable time and amount of effort after the hackfest. If available add links to the corresponding issue and possibly UX or other feature specifications.

Note that this is not an agenda and does not involve any schedule, we're "planning" more in an [http://www.unconference.net/ unConference] style, so about anything may go once the hackfest started. However, getting prepared for some tasks isn't bad either..

{| class="prettytable sortable"
|-
! Module || Topic || Remarks || Issue # || Mentor || Participants Interested
|-
| Calc || Fill operations should not touch filtered rows || A long outstanding issue that if solved would ease many people's itches.. A sketch of possible behavior is available at [[Calc/Drafts/Issue_33851#Fill_cells]] and [[Calc/Drafts/Issue_33851#Fill_series]] || {{Bug|89232}} || Eike Rathke [er] || {you} {and you} {and you} ;-)
|-
| || || || || ||
|}

[[Category:Conferences]]

Hackfest2010

2010-10-10T20:55:53Z

ErAck: add Hackfest2010/Topics

{{DISPLAYTITLE:OpenOffice.org HackFest 2010}}

== Announcement ==

[[Hackfest2010/de|Für die deutsche Version dieser Seite klickt bitte hier.]]

 

Dear OOo hackers,

the OOoCon just ended, and we realize how little time we can spend together face2face each year. To properly fix that problem, we hereby announce the next event around OpenOffice.org - a HackFest in Hamburg, specifically targeted to developers, to give all of us more face time & collectively work on the code.

'''The OpenOffice.org HackFest will take place on the weekend of November 6./7. 2010 in the [http://wiki.attraktor.org/index.php/Mex Attraktor in Hamburg]''', and a tentative program could look like this:

*Friday night - beer & fun, warming up
*Saturday morning - Intro talks, Hands-on sessions
*Saturday afternoon/night - collective hacking, bug fixing
*Sunday morning - wrap-up, review, document

For those who are in need for a bursary, we have a limited travel funding budget available. For sleeping, couchsurfing at the organizers is available. Be aware that would be in an unheated loft, so bringing a sleeping mat and a good sleeping bag would be essential. For more comfortable reasonably priced acommodations see [[Sleeping in Hamburg|the wiki page]]. 

We look forward to meet you there, stay tuned for further announcements around programme and sponsoring! To register yourself, just drop a short note to [mailto:hackfest@openoffice.org hackfest@openoffice.org] and we'll follow up with further information soon. 

Faithfully, your HackFest organizers

Eike, Florian & Thorsten [mailto:hackfest@openoffice.org hackfest@openoffice.org]

== Location ==

Location at OpenStreetMap: [http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M] Location at Google Maps: [http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18 http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18] 

== Topics ==

Ideas and topics that could be worked on are collected at [[Hackfest2010/Topics]].

[[Category:Conferences]]
{{CCBY}}

Hackfest2010/Topics

2010-10-10T20:37:59Z

ErAck: hackfest topics

{{DISPLAYTITLE:OpenOffice.org HackFest 2010 Topics}}

Please add your ideas and topics you'd like to work on or mentor during the hackfest. Issues and/or features to be worked on should either be doable within two days, or at least could be given enough spin to be completed within a reasonable time and amount of effort after the hackfest. If available add links to the corresponding issue and possibly UX or other feature specifications.

{| class="prettytable sortable"
|-
! Module || Topic || Remarks || Issue # || Mentor || Participants Interested
|-
| Calc || Fill operations should not touch filtered rows || A long outstanding issue that if solved would ease many people's itches.. A sketch of possible behavior is available at [[Calc/Drafts/Issue_33851#Fill_cells]] and [[Calc/Drafts/Issue_33851#Fill_series]] || {{Bug|89232}} || Eike Rathke [er] || {you} {and you} {and you} ;-)
|-
| || || || || ||
|}

[[Category:Conferences]]

User:ErAck

2010-10-10T20:07:25Z

ErAck: /* Pretty Sortable Table */

{| align="right"
| [[Image:ErAck_128x128.png‎]]
|}
* Name: Eike Rathke
* Nick: erAck
* OOo: er
* Working on:
** [[Calc]] spreadsheet application compiler, interpreter, engine
** number formatter
** [[I18npool|internationalization (i18n)]] and locale data, '''not''' localization (l10n)
*** .signature: number formatter stricken i18n transpositionizer
* IRC: irc://irc.freenode.net/#dev.openoffice.org
* Email Calc developers: [mailto:dev@sc.openoffice.org dev@sc.openoffice.org] mailing list
* Email personal: [mailto:er@openoffice.org er@openoffice.org], [mailto:eike.rathke@oracle.com eike.rathke@oracle.com]
* Private URL: http://www.erack.de/
* μBlog: http://identi.ca/erack
* Blog: http://jroller.com/erAck
* GullFOSS: http://blogs.sun.com/GullFOSS
* Company Name: Oracle Deutschland B.V. & Co. KG
* Company URL: http://oracle.com/office
* Location: Hamburg, Germany
* Timezone: UTC+1 with DST rule TZ=CET-1CEST-2,M3.5.0/2,M10.5.0/3

== currently working on ==

* [http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula OASIS OpenDocument file format formula specification], ODFF aka OpenFormula.
* mentorship for implementors, review of patches and integration.
* Bits of formula compiler and interpreter changes.


== Work flow ==

My personal [[/WorkFlow| work flow and environment]] when working on code.

== Wiki stuff ==

Edit help: [[:Category:Help]]

=== Code syntax highlighting ===

Code syntax highlighting is possible with
<pre>
<source lang="$LANGUAGE">
...
</source>
</pre>

where ''$LANGUAGE'' is one of this list that was dynamically generated using <code><nowiki><source lang="invalid"></source></nowiki></code>

<source lang="invalid"></source>

'''NOTE:''' the old SwinBrain CodeSyntaxHighlight does not work anymore since the wiki upgrade on 2008-02-14
<pre>
<code>[language]
...
</code>
</pre>
produces rubbish now!

=== Templates ===

<code><nowiki>{{Documentation/Caution| Do or don't.}}</nowiki></code>
{{Documentation/Caution| Do or don't.}}

<code><nowiki>{{Documentation/Note| Note that.}}</nowiki></code>
{{Documentation/Note| Note that.}}

<code><nowiki>{{Template:Documentation/Tip| Tip.}}</nowiki></code>
{{Template:Documentation/Tip| Tip.}}

{{LinkBanner}}

For many more see
* [[Documentation/Dashboard/Wiki_Editing_Policy#List_of_Existing_Documentation_Templates]]
* [[:Category:Wiki_Templates]], especially
** [[:Category:Formatting_templates]]
** [[:Category:Wiki_Templates_Expressing_Quality]]
* [[Special:Mostlinkedtemplates]]

=== Pretty Sortable Table ===

<pre>
{| class="prettytable sortable"
|-
! Column 1 Header || Column 2 Header
|-
| some data column 1 || and some data column 2
|-
| more data column 1 || even more data column 2
|}
</pre>

{| class="prettytable sortable"
|-
! Column 1 Header || Column 2 Header
|-
| some data column 1 || and some data column 2
|-
| more data column 1 || even more data column 2
|}

=== new topic ===
<nowiki>Insert non-formatted text here</nowiki>

User:ErAck

2010-10-07T19:13:36Z

ErAck: /* Templates */

{| align="right"
| [[Image:ErAck_128x128.png‎]]
|}
* Name: Eike Rathke
* Nick: erAck
* OOo: er
* Working on:
** [[Calc]] spreadsheet application compiler, interpreter, engine
** number formatter
** [[I18npool|internationalization (i18n)]] and locale data, '''not''' localization (l10n)
*** .signature: number formatter stricken i18n transpositionizer
* IRC: irc://irc.freenode.net/#dev.openoffice.org
* Email Calc developers: [mailto:dev@sc.openoffice.org dev@sc.openoffice.org] mailing list
* Email personal: [mailto:er@openoffice.org er@openoffice.org], [mailto:eike.rathke@oracle.com eike.rathke@oracle.com]
* Private URL: http://www.erack.de/
* μBlog: http://identi.ca/erack
* Blog: http://jroller.com/erAck
* GullFOSS: http://blogs.sun.com/GullFOSS
* Company Name: Oracle Deutschland B.V. & Co. KG
* Company URL: http://oracle.com/office
* Location: Hamburg, Germany
* Timezone: UTC+1 with DST rule TZ=CET-1CEST-2,M3.5.0/2,M10.5.0/3

== currently working on ==

* [http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula OASIS OpenDocument file format formula specification], ODFF aka OpenFormula.
* mentorship for implementors, review of patches and integration.
* Bits of formula compiler and interpreter changes.


== Work flow ==

My personal [[/WorkFlow| work flow and environment]] when working on code.

== Wiki stuff ==

Edit help: [[:Category:Help]]

=== Code syntax highlighting ===

Code syntax highlighting is possible with
<pre>
<source lang="$LANGUAGE">
...
</source>
</pre>

where ''$LANGUAGE'' is one of this list that was dynamically generated using <code><nowiki><source lang="invalid"></source></nowiki></code>

<source lang="invalid"></source>

'''NOTE:''' the old SwinBrain CodeSyntaxHighlight does not work anymore since the wiki upgrade on 2008-02-14
<pre>
<code>[language]
...
</code>
</pre>
produces rubbish now!

=== Templates ===

<code><nowiki>{{Documentation/Caution| Do or don't.}}</nowiki></code>
{{Documentation/Caution| Do or don't.}}

<code><nowiki>{{Documentation/Note| Note that.}}</nowiki></code>
{{Documentation/Note| Note that.}}

<code><nowiki>{{Template:Documentation/Tip| Tip.}}</nowiki></code>
{{Template:Documentation/Tip| Tip.}}

{{LinkBanner}}

For many more see
* [[Documentation/Dashboard/Wiki_Editing_Policy#List_of_Existing_Documentation_Templates]]
* [[:Category:Wiki_Templates]], especially
** [[:Category:Formatting_templates]]
** [[:Category:Wiki_Templates_Expressing_Quality]]
* [[Special:Mostlinkedtemplates]]

=== new topic ===
<nowiki>Insert non-formatted text here</nowiki>

User:ErAck

2010-10-07T19:06:44Z

ErAck: /* Templates */

{| align="right"
| [[Image:ErAck_128x128.png‎]]
|}
* Name: Eike Rathke
* Nick: erAck
* OOo: er
* Working on:
** [[Calc]] spreadsheet application compiler, interpreter, engine
** number formatter
** [[I18npool|internationalization (i18n)]] and locale data, '''not''' localization (l10n)
*** .signature: number formatter stricken i18n transpositionizer
* IRC: irc://irc.freenode.net/#dev.openoffice.org
* Email Calc developers: [mailto:dev@sc.openoffice.org dev@sc.openoffice.org] mailing list
* Email personal: [mailto:er@openoffice.org er@openoffice.org], [mailto:eike.rathke@oracle.com eike.rathke@oracle.com]
* Private URL: http://www.erack.de/
* μBlog: http://identi.ca/erack
* Blog: http://jroller.com/erAck
* GullFOSS: http://blogs.sun.com/GullFOSS
* Company Name: Oracle Deutschland B.V. & Co. KG
* Company URL: http://oracle.com/office
* Location: Hamburg, Germany
* Timezone: UTC+1 with DST rule TZ=CET-1CEST-2,M3.5.0/2,M10.5.0/3

== currently working on ==

* [http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula OASIS OpenDocument file format formula specification], ODFF aka OpenFormula.
* mentorship for implementors, review of patches and integration.
* Bits of formula compiler and interpreter changes.


== Work flow ==

My personal [[/WorkFlow| work flow and environment]] when working on code.

== Wiki stuff ==

Edit help: [[:Category:Help]]

=== Code syntax highlighting ===

Code syntax highlighting is possible with
<pre>
<source lang="$LANGUAGE">
...
</source>
</pre>

where ''$LANGUAGE'' is one of this list that was dynamically generated using <code><nowiki><source lang="invalid"></source></nowiki></code>

<source lang="invalid"></source>

'''NOTE:''' the old SwinBrain CodeSyntaxHighlight does not work anymore since the wiki upgrade on 2008-02-14
<pre>
<code>[language]
...
</code>
</pre>
produces rubbish now!

=== Templates ===

<code><nowiki>{{Documentation/Caution| Do or don't.}}</nowiki></code>
{{Documentation/Caution| Do or don't.}}

<code><nowiki>{{Documentation/Note| Note that.}}</nowiki></code>
{{Documentation/Note| Note that.}}

<code><nowiki>{{Template:Documentation/Tip| Tip.}}</nowiki></code>
{{Template:Documentation/Tip| Tip.}}

{{LinkBanner}}

For many more see
* [[Documentation/Dashboard/Wiki_Editing_Policy#List_of_Existing_Documentation_Templates]]
* [[:Category:Wiki_Templates]]
* [[Special:Mostlinkedtemplates]]

=== new topic ===
<nowiki>Insert non-formatted text here</nowiki>

Hackfest2010/de

2010-10-07T18:40:25Z

ErAck: I'm back in

{{DISPLAYTITLE:OpenOffice.org HackFest 2010}}

[[Hackfest2010|For the English version of this page, please click here.]]

 

Geschätzte OOo-Hacker,

die OOoCon ist nun zuende, und wir stellen mal wieder fest, wie wichtig und effektiv persönliche Treffen sind - leider haben wir davon im Jahr viel zu wenig. Um das Problem mal grundlegend zu fixen, kündigen wir hiermit das OOo HackFest in Hamburg an, ein Event speziell für und mit Entwicklern, bei dem wir gemeinschaftlich am Code arbeiten wollen.

'''Das OpenOffice.org HackFest findet am Wochenende vom 6./7. November 2010 im [http://wiki.attraktor.org/index.php/Mex Attraktor in Hamburg] statt''', das Programm wird in etwa folgendermaßen aussehen:

*Freitag abend - Bierchen & Kennenlernen
*Samstag morgen - Einführungsvorträge, Hands-on sessions
*Samstag nachmittag/nacht - gemeinschaftliches Hacken & Bugfixen
*Sonntag morgen - wrap-up, review, dokumentieren

Es wird ein limitiertes Budget für Reisekosten geben, für Übernachtungen steht ein großer (leider unbeheizter) Raum zur Verfügung, also an Isomatte und Schlafsack denken. Für etwas komfortablere und dennoch preiswerte Übernachtungsmöglichkeiten siehe die [[Sleeping in Hamburg|entsprechende Wikiseite]].

Wir freuen uns, euch dort zu sehen und versorgen euch bald mit weiteren Informationen zum Programm. Um euch anzumelden, genügt eine kurze formlose E-Mail an [mailto:hackfest@openoffice.org hackfest@openoffice.org], wir melden uns dann bei euch mit weiteren Infos. 

Viele Grüße von euren HackFest-Organisatoren

Eike, Florian & Thorsten [mailto:hackfest@openoffice.org hackfest@openoffice.org]

 

Location at OpenStreetMap: [http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M] Location at Google Maps: [http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18 http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18] 

{{CCBY}}

[[Category:Conferences]]

Hackfest2010

2010-10-07T18:39:47Z

ErAck: I'm back in

{{DISPLAYTITLE:OpenOffice.org HackFest 2010}}

[[Hackfest2010/de|Für die deutsche Version dieser Seite klickt bitte hier.]]

 

Dear OOo hackers,

the OOoCon just ended, and we realize how little time we can spend together face2face each year. To properly fix that problem, we hereby announce the next event around OpenOffice.org - a HackFest in Hamburg, specifically targeted to developers, to give all of us more face time & collectively work on the code.

'''The OpenOffice.org HackFest will take place on the weekend of November 6./7. 2010 in the [http://wiki.attraktor.org/index.php/Mex Attraktor in Hamburg]''', and a tentative program could look like this:

*Friday night - beer & fun, warming up
*Saturday morning - Intro talks, Hands-on sessions
*Saturday afternoon/night - collective hacking, bug fixing
*Sunday morning - wrap-up, review, document

For those who are in need for a bursary, we have a limited travel funding budget available. For sleeping, couchsurfing at the organizers is available. Be aware that would be in an unheated loft, so bringing a sleeping mat and a good sleeping bag would be essential. For more comfortable reasonably priced acommodations see [[Sleeping in Hamburg|the wiki page]]. 

We look forward to meet you there, stay tuned for further announcements around programme and sponsoring! To register yourself, just drop a short note to [mailto:hackfest@openoffice.org hackfest@openoffice.org] and we'll follow up with further information soon. 

Faithfully, your HackFest organizers

Eike, Florian & Thorsten [mailto:hackfest@openoffice.org hackfest@openoffice.org]

 

Location at OpenStreetMap: [http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M http://www.openstreetmap.org/?lat=53.603016&lon=10.022952&zoom=18&layers=M] Location at Google Maps: [http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18 http://maps.google.com/maps?f=d&source=s_d&saddr=53.602915,10.022873&daddr=&geocode=&hl=en&mra=dme&mrcr=0&mrsp=0&sz=19&sll=53.602983,10.022873&sspn=0.001372,0.00213&ie=UTF8&ll=53.603007,10.022691&spn=0.002744,0.004259&t=h&z=18] 

{{CCBY}}

[[Category:Conferences]]

NLC:New Translators Start here

2010-10-05T10:24:52Z

ErAck: some grammar

== Working together with OpenOffice.org L10n Team ==

OpenOffice.org L10n provides localized builds for many [[Languages|languages]]. Joining your native language project is a great opportunity to help making OpenOffice.org reach more users. Browse the [[Languages|languages list]] and get in touch with project leads.

To get in touch with the general OpenOffice.org translation community please come and say hello on the mailto:dev@l10n.openoffice.org mailing list [http://l10n.openoffice.org/servlets/SummarizeList?listName=dev (browse archive)].

'''For''' translation teams, with every new milestone (version of OpenOffice.org code) we provide source messages from both UI and Help to be translated.

'''From''' translation teams, we need a translation file, a <tt>SDF/GSI</tt> file containing all the English strings translated into your language (or at least 80% UI translated).

Translation teams have the possibility to maintain a localized web site at http://xx.openoffice.org (xx being a language code) if they become a native language project in the [[NLC|Native Language Confederation]], translate user documentation published on the wiki, upload localized templates and localize OpenOffice.org templates and extensions repositories web sites. It is possible to prepare and publish locale data, spellcheck and thesaurus dictionaries, hyphenation patterns and autocorrect data as well as advanced grammar checking support.

== Translating OpenOffice.org ==

Click here to view [[Translation:General_Information|general information on translating]] OpenOffice.org using either Pootle or using Gettext PO and managing translations outside Pootle.

== Starting a new localization project ==

First thing is to prepare new [[Adding_a_new_language_or_locale|language or locale support]] and [[How_to_submit_new_Locale_|submit it]] for integration.

== Testing localized builds ==

[[NLC/localizedQA|Testing your localized builds]]

== I need help ==

OpenOffice.org is a large and complex project, so it is particularly difficult for a newcomer. Don't feel discouraged if you become confused or can't get an overview of the project.

In any case, we are all here to help each other. Please ask on the [mailto:dev@l10n.openoffice.org dev@l10n.openoffice.org] mailing list if you have any problems. We will work things out together.

Good luck with your localization. :)

[[Category:Localization|!]]

Scaddins

2010-09-08T20:54:27Z

ErAck: point to category Add-In (singular), not Add-Ins

Source code module '''scaddins''' contains Add-Ins for the [[Calc]] spreadsheet application. For information about how to write an Add-In please see articles in the category [[:Category:Add-In|Add-In]].

Currently the module contains

* '''source/'''
** '''analysis/'''
**: Analysis Add-In for Microsoft Excel interoperability
** '''datefunc/'''
**: functions for date calculation

Please note that these Add-Ins make use of the OOo resource system for localized function names, depending on modules [[Tools]] and [[Vcl]], and thus are not pure UNO components using the SDK only.

[[Category:Source_directories]]
[[Category:Calc]]
[[Category:Add-In]]

Little Helpers

2010-09-08T20:48:14Z

ErAck: /* mkd */ enable parallel dmake

Here are some '''Little Helpers''' for the enthusiastic developer, such as
small scripts that help to tame the OOo code base.

== Tools for maintaining identifier databases ==

=== GNU ID-utils ===

The GNU ID-utils are a powerful set of utilities to generate and query a
database of file names and identifiers, invoke your favourite editor with the
resulting set of files, or accomplish any other task with the resultset. Be
sure to '''not''' use the original version 3.2, use the Debian package
instead, or maybe some other distribution's package. For details why and how
to patch a self-compiled version 3.2d see
[http://jroller.com/page/erAck?entry=gnu_id_utils this blog entry].

The ID-utils come with an 
'';;; id-utils.el -- emacs interface to `lid -R grep', a.k.a. `gid' '' 
For how to interface with the ''vim'' editor see the
[[Editor_Vim#Vim_and_the_GNU_ID-utils | Vim editor's GNU ID-utils]] section.
Generally, the editor invoking functionality of ID-utils uses the shell
variables ''VISUAL'' or ''EDITOR'', ''EIDARG'', ''EIDLDEL'' and ''EIDRDEL'', so
it should be possible to invoke any capable editor. Citing from the
documentation:

<pre>
`eid' invokes the editor defined by the environment variable
`VISUAL'. If `VISUAL' is undefined, it uses the environment variable
`EDITOR' instead. If `EDITOR' is undefined, it defaults to `vi'. It
is possible for `eid' to pass the editor an initial search pattern so
that your cursor will immediately alight on the token of interest.
This feature is controlled by the following environment variables:
`EIDARG'
A printf(3) format string for the editor argument to search for the
matching token. For `vi', this should be `+/%s/'.

`EIDLDEL'
The regular-expression meta-character(s) for delimiting the
beginning of a word (the ``eid' Left DELimiter'). `eid' inserts
this in front of the matching token when a word-search is desired.
For `vi', this should be `\<'.

`EIDRDEL'
The regular-expression meta-character(s) for delimiting the end of
a word (the ``eid' Right DELimiter'). `eid' inserts this in end
of the matching token when a word-search is desired. For `vi',
this should be `\>'.
</pre>

The ID-utils use an extension → language mapping file <tt>id-lang.map</tt>.
Either edit the system-wide file of your installation or a local copy thereof.
Here we're assuming a local copy as <tt>$HOME/devbase/id-lang.map</tt>, add the
following entries:

<pre>
# Treat OOo/SO resource header files as C files
*.hrc C
# Treat OOo/SO header files generated from *.idl as C++ files
*.hdl C++
# Treat OOo IDL files as C++ files, not exactly a header file, but ...
*.idl C++
# Treat OOo/SO resource files as C files
*.src C
# Treat OOo/SO *.mk files as makefiles
*.mk make
</pre>

'''Note:''' The ''*.mk make'' entry doesn't seem to work, the makefile.mk's IDs
are not added to the database, didn't investigate yet why.

Then the script below may be invoked either
* In a module's directory without parameters, creating an ID database for just the single module.
* In the ''$SRC_ROOT'' directory for all modules: <code>mkid-script '*'</code> Note the literal '*' asterisk that is not to be expanded by the shell. The file size of the generated ''ID'' file using this method currently (m223) is 31MB.
* In the ''$SRC_ROOT'' directory for specified modules: <code>mkid-script '{module1,module2,solver}'</code> Again, note the literal argument enclosed in single quotes for the file name expansion, which is done by the script. If the argument was not passed literally, only the first module would be included, and other strange things may happen.. Wildcards may be used as usual. It is a good idea to include the ''solver'' module to gather identifiers from delivered header files. Ignore messages like ''mkid: can't lstat `unxlngi4.pro' from `.../SRC680/src.m180/solver' '' or ''mkid: can't lstat `build' from `.../SRC680/src.m180/module1/unxlngi4.pro/misc' '' They result from the INPATH relevant arguments passed for each module and don't harm.

You may also manually invoke ''mkid'' in the ''$SRC_ROOT'' directory for all
modules, this is a safe bet but may include more than you want if you have
output directories for multiple platforms, all identifiers present there will
get duplicated, triplicated, ... the command line for this is 
<code>mkid --lang-map=$HOME/devbase/id-lang.map --statistics</code>

==== mkid-script ====

The module-wise script, suggested name: <tt>$HOME/devbase/mkid-script</tt>

<pre>
#!/bin/tcsh

# Either the current module, or all modules can be ID'ed if $1 is
# specified as literal '*' unexpanded. Will be expanded here.
# Instead of '*' _any_ shell wildcard should be possible, e.g. '{.,bf_*}'.
# Output directories except $INPATH/inc and $INPATH/misc/build are skipped in
# these cases.
# A simple ALL generator, not ignoring any directory, is the parameter 'all'.
# Warning, that may create a huge database and massively duplicated entries if
# more than one platform's output directory exists.

if ( { ( which mkid >> /dev/null ) } ) then
echo generating IDs
if ( "$1" == "-o" ) then
set output="--output=$2"
shift
shift
else
set output=""
endif
if ( "$1" == "" ) then
set module="."
#set exclude=./{common,unxlngi6,unxsols4,wntmsci10}{,.pro}
# Wildcards not only make updates unnecessary but also suppress "no
# match" error messages. The CVS* and .svn* directories are included
# for the case of a freshly checked out source that does not have any
# output directories yet. Otherwise that would still lead to a "no
# match" error if no wildcarded names matched.
set exclude=./{CVS*,.svn*,common*,*unxlng*,*unxsol*,*unxmac*,*wntmsc*}
else if ( "`basename '$1'`" == "*" ) then
set module="$1"
echo module: $module
# prevent command line overflow with a full exclude
set exclude="x"
echo exclude: $exclude
else if ( "$1" == "all" ) then
set module="$1"
echo module: $module
set exclude="nothing"
echo exclude: $exclude
else
set module="$1"
echo module: $module
set exclude=$1/{CVS*,.svn*,common*,*unxlng*,*unxsol*,*unxmac*,*wntmsc*}
echo exclude: $exclude
endif

if ( "`basename '$1'`" == "*" ) then
# test for ls overrun
set dcommand="ls -d $module/*"
if ( ! { ( $dcommand >> /dev/null ) } ) then
echo "$0 : ls overrun, trying find $module -mindepth 1 -maxdepth 1"
# test for find mindepth/maxdepth availability
set dcommand="find $module -mindepth 1 -maxdepth 1"
if ( ! { ( $dcommand >> /dev/null ) } ) then
echo "$0 : find doesn't know options -mindepth -maxdepth"
echo "$0 : too bad, giving up."
exit 1
endif
endif
# Only positive list of module subdirectories and files,
# excluding output directories except $INPATH/{inc,misc/build}
set dirs="$module/$INPATH/inc $module/$INPATH/misc/build `$dcommand | sed -e '/$\/\(CVS\|common\|.*unxlng\|.*unxsol\|.*unxmac\|.*wntmsc\|Jamfile\|cscope\.\|tags\|ID$\)\|^solver\//d'`"
echo dirs: $dirs
echo Creating output: $output
mkid --lang-map=$HOME/devbase/id-lang.map --include='C C++ asm perl java make' $output --statistics $dirs
else if ( "$1" == "all" ) then
echo Creating output: $output
mkid --lang-map=$HOME/devbase/id-lang.map --include='C C++ asm perl java make' $output --statistics
else
# all but negative list plus INPATH relevants
echo Creating output: $output
mkid --lang-map=$HOME/devbase/id-lang.map --include='C C++ asm perl java make' $output --statistics --prune="$exclude" $module $module/$INPATH/inc $module/$INPATH/misc/build
endif

else
echo no ID-utils
endif
</pre>

=== Exuberant Ctags ===

The Exuberant Ctags utility interfaces nicely with Emacs and Vim and enables
quick lookup for declarations and definitions of macros, typedefs, constants,
enums, variables, structs and classes and their methods and implementation. You
should get the latest version available at http://ctags.sourceforge.net/, which
currently (2006-08-27) is v5.6, older versions included by distributions for
example don't automatically recognize .mk files as makefiles, and v5.6 also
added a patch needed for the ''vim 7.0 omni-completion'' feature. Ctags creates
a file ''tags'' in the current directory, if not told otherwise.

As creating a tags file over all modules and directories exceeded the 2GB file
size limit, a positive directory list was used to go along with a '*'
parameter, identical to the one used in the ''mkid-script'' above. The file
size of the ''tags'' file generated for '*' currently (m182) is 398MB.

==== ctags-script ====

For use with the OOo code base a script with a syntax similar to the ID-utils
script above comes handy, suggested name: <tt>$HOME/devbase/ctags-script</tt>

<pre>
#!/bin/tcsh

# Either the current module, or all modules can be ctag'ed if $1 is
# specified as literal '*' unexpanded. Will be expanded here.
# Instead of '*' _any_ shell wildcard should be possible, e.g. '{.,bf_*}'.
# NOTE: ctags on '*' exceeded 2GB file size limit if for _all_ OOo modules and
# no positive dirs list was used.

if ( "$?MYCTAGS" == "0" ) then
set MYCTAGS="ctags"
endif

if ( { ( which "$MYCTAGS" >> /dev/null ) } ) then
echo generating ctags
# Options necessary for the Vim OmniCppComplete plugin,
# http://www.vim.org/scripts/script.php?script_id=1520
# --c++-kinds=+p : Adds prototypes in the database for C++ files.
# --fields=+iaS : Adds inheritance (i), access (a) and function
# signatures (S) informations.
# --extra=+q : Adds context to the tag name. Note: Without this
# option, the script cannot get class members.
set omnicppoptions="--c++-kinds=+p --fields=+iaS --extra=+q"
if ( "$1" == "--global" ) then
if ( ! $?UPDMINOREXT ) set UPDMINOREXT=""
"$MYCTAGS" -h "+.hdl.hrc" --langmap=c:+.hdl.hrc.src $omnicppoptions -R $SOLARVERSION/$INPATH/inc$UPDMINOREXT
else
if ( "$1" == "" ) then
set module="."
else
set module="$1"
echo module: $module
endif
# test for ls overrun
set dcommand="ls -d $module/*"
if ( ! { ( $dcommand >> /dev/null ) } ) then
echo "$0 : ls overrun, trying find $module -mindepth 1 -maxdepth 1"
# test for find mindepth/maxdepth availability
set dcommand="find $module -mindepth 1 -maxdepth 1"
if ( ! { ( $dcommand >> /dev/null ) } ) then
echo "$0 : find doesn't know options -mindepth -maxdepth"
echo "$0 : too bad, giving up."
exit 1
endif
endif
# Only positive list of module subdirectories and files,
# excluding output directories except $INPATH/{inc,misc/build}
set dirs="$module/$INPATH/inc $module/$INPATH/misc/build `$dcommand | sed -e '/$\/\(CVS\|\.svn\|common\|.*unxlng\|.*unxsol\|.*unxmac\|.*wntmsc\|Jamfile\|cscope\.\|tags\|ID$\)\|^solver\//d'`"
echo dirs: $dirs
"$MYCTAGS" -h "+.hdl.hrc" --langmap=c:+.hdl.hrc.src $omnicppoptions -R $dirs
endif
else
echo no ctags
endif
</pre>

Ignore messages like 
''ctags: Warning: cannot open source file "./unxlngi6.pro/misc/build" : No such file or directory'' 
or consider them purely informational.

Note that also here, if more than one module is to be specified, the shell
filename glob-patterns and metanotations have to be passed in single quotes.
Though tagging an entire OOo code base would result in a "file overflow" with
more than 2GB this isn't a problem in practice, at least with Vim, don't know
about other editors, since it may search the ''tags'' files going up the
directory hierarchy if a tag is not found in the current directory's tags file.
So generate the ''tags'' file in the modules you are interested in, using the
script without parameters, then <code>cd $SRC_ROOT</code> and invoke
<code>scriptname --global</code> to produce a tags file for the ''solver''.

A final <tt>ctags</tt> note: In some cases, you might have more than one version of <tt>ctags</tt> on your system. E.g., there is a version that ships with Emacs (and is often in <tt>/usr/local/bin</tt>) that doesn't support the same arguments as Exhuberant <tt>ctags</tt>; if this is the case (you'll see an error message from the script like "<tt>unrecognized option `--langmap=c:+.hdl.hrc.src'</tt>") then you can set the MYCTAGS variable, e.g., from a <tt>bash</tt> shell:
<pre>
MYCTAGS=/usr/bin/ctags $HOME/devbase/ctags-script --global
MYCTAGS=/usr/bin/ctags CTAGS=-e $HOME/devbase/ctags-script --global # generate TAGS for Emacs
</pre>
If all you have is the Emacs version, you will want to rewrite the script (or provide a better solution here).

=== Cscope ===

Cscope is another utility to query a database for code elements. It comes with
a cumbersome screen-oriented interactive tool to browse source files, but also
interfaces nicely with Vim and Emacs. Unfortunately it is not able to cope with
the entire OOo source base it seems, so for '*' even when called with a list of
files to work on, at the end it displayed
''Input string too long, limit 50251''
and no output was generated. Didn't investigate yet what exactly is the
problem. However, using it on a subset of several modules is possible.

==== cscope-script ====

This script may be used to generate a ''cscope.out'' database file, same
parameter syntax as the mkid-script and ctags-script above. Suggested name:
<tt>$HOME/devbase/cscope-script</tt>

<pre>
#!/bin/tcsh

# Either the current module, or all modules can be tagID'ed if $1 is
# specified as literal '*' unexpanded. Will be expanded here.
# Instead of '*' _any_ shell wildcard should be possible, e.g. '{.,bf_*}'.
# NOTE: cscope on '*' hanged if for _all_ OOo modules and no positive dirs list
# was used. Even with the generated cscope.files it still refuses to complete
# its work.

if ( { ( which cscope >> /dev/null ) } ) then
echo generating cscope
if ( "$1" == "" ) then
set module="."
else
set module="$1"
echo module: $module
endif
# test for ls overrun
set dcommand="ls -d $module/*"
if ( ! { ( $dcommand >> /dev/null ) } ) then
echo "$0 : ls overrun, trying find $module -mindepth 1 -maxdepth 1"
# test for find mindepth/maxdepth availability
set dcommand="find $module -mindepth 1 -maxdepth 1"
if ( ! { ( $dcommand >> /dev/null ) } ) then
echo "$0 : find doesn't know options -mindepth -maxdepth"
echo "$0 : too bad, giving up."
exit 1
endif
endif
# Only positive list of module subdirectories and files,
# excluding output directories except $INPATH/{inc,misc/build}
set dirs="$module/$INPATH/inc $module/$INPATH/misc/build `$dcommand | sed -e '/$\/\(CVS\|\.svn\|common\|.*unxlng\|.*unxsol\|.*unxmac\|.*wntmsc\|Jamfile\|cscope\.\|tags\|ID$\)\|^solver\//d'`"
echo dirs: $dirs
( find $dirs -name '*.[hc]' -o -name '*.[hc]xx' -o -name '*.[hc]pp' -o -name '*.[hs]rc' >cscope.files ) >>& /dev/null
if ( `uname` == "SunOS" ) then
cscope -b -c
else
cscope -b -c -q
endif
else
echo no cscope
endif
</pre>

Note that the ''find'' command is executed in a subshell with stderr redirected
to /dev/null to suppress all the ''find: ./unxlngi6.pro/misc/build: No such file or directory''
and the like warning messages. Remove the parentheses and the redirection in
case you suspect errors in your environment.

=== All together now ===

Surely we don't want to invoke all these scripts separately all the times, so
here's a small wrapper just to prove that the suggested names actually make
sense ;-) let's call it <tt>$HOME/devbase/tagsID</tt>

<pre>
#!/bin/tcsh

# Either the current module, or all modules can be tagID'ed if $1 is
# specified as literal '*' unexpanded. Will be expanded here.
# Instead of '*' _any_ shell wildcard should be possible, e.g. '{.,bf_*}'.
# NOTE: ctags on '*' exceeds 2GB file size limit if for _all_ OOo modules.
# NOTE: cscope on '*' hangs if for _all_ OOo modules.
# Which actually is the reason we invoke it last just in case we forgot..

${0:h}/ctags-script "$1"
${0:h}/mkid-script "$1"
${0:h}/cscope-script "$1"
</pre>

The same syntax as with the other scripts applies: filename glob-patterns and
metanotations have to be passed as literals, enquoted with single quotes.
Invoking it in a module's directory without passing an argument creates
databases for that single module.

== Build selected source code files with debug ==

Sometimes only a few files need to be build with debug instead of an entire
module, which significantly saves time. Change into the directory and invoke
the following script with the files of interest passed as arguments, for
example, in <tt>sc/source/core/tool</tt>

<source lang="bash">
mkd token.cxx compiler.cxx interpr*.cxx
</source>

To also link the library in the module's ''util'' directory pass the ''--link''
or ''-l'' option:

<source lang="bash">
mkd -l token.cxx compiler.cxx interpr*.cxx
</source>

=== mkd ===

<source lang="bash">
#!/bin/bash

# Compile source files (in current directory!) passed as arguments with debug.
# Option --link or -l also links the library in the module's util directory.

# Do parallel build, set to empty if not wanted.
PARALLEL="-P4"

if [ -z "$INPATH" ]; then
echo "No \$INPATH, source environment!"
exit 1
fi
UTIL=""
if [ "$1" == "--link" -o "$1" == "-l" ]; then
UTIL="Yes"
shift
fi

# Determine the current hierarchy depth by looking upwards for the prj/d.lst
# file, but no more than MAX levels up.
DLST="prj/d.lst"
SUBS=""
MAX=5
for (( LEVEL=0 ; LEVEL < MAX ; ++LEVEL )); do
if [ -f "${SUBS}${DLST}" ]; then
break
fi
SUBS="../$SUBS"
done
OUTP="${SUBS}${INPATH}/slo"
if [ $LEVEL == $MAX ]; then
echo "No ${SUBS}${DLST} found! (LEVEL $LEVEL)"
exit 1
fi

ERR=0
# Force compilation of files passed as arguments.
for x in "$@"; do
FILE="${x//*\//}"
BASE="${FILE%.*}"
FULL="${OUTP}/${BASE}.obj"
rm "$FULL"
if [ -z "$PARALLEL" ]; then
dmake debug=t "$FULL"
fi
ERR=$?
if [ $ERR != 0 ]; then
break
fi
done
# If no error, compile yet uncompiled files and create archive, if any.
if [ $ERR == 0 ]; then
dmake $PARALLEL debug=t
ERR=$?
fi
# Some modules, such as Writer, have an extra archiving step one level up, e.g.
# in sw/source/core/ if files in sw/source/core/layout/ were compiled.
# Do this only if deeper than in module level.
if (( LEVEL > 1 )); then
if [ $ERR == 0 -a -f ../makefile.mk ]; then
pushd ..
dmake debug=t
ERR=$?
popd
fi
fi
# If no error, link library if requested.
if [ $ERR == 0 -a -n "$UTIL" ]; then
UTIL="${SUBS}util"
if [ ! -d "$UTIL" ]; then
echo "No $UTIL directory, no linking."
exit
fi
cd "$UTIL"
dmake debug=t
ERR=$?
fi
exit $ERR
</source>

[[Category:Developer Tools]]

Calc/Implementation/Spreadsheet Functions

2010-08-13T19:58:57Z

ErAck: elaborate on non-scalar arguments

[[Category:Calc]]
[[Category:Implementation]]

Procedure to add a new [[Calc]] spreadsheet function.

== Introduction ==

Let's assume you want to implement a new spreadsheet function and the function
was defined by the
[http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office-formula OASIS OpenDocument Format Formula subcommittee],
see latest revision of the
[http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula specification (draft)].
Let's further assume the function's name is '''MYFUNC''' and will take
2 parameters, of which the second parameter is optional and defaulted to 0, and
returns a number, as following:

'''Syntax:''' MYFUNC( ''Number'' Param1 [ ; ''Number'' Param2 = 0 ] ) 
'''Returns:''' Number

== Make the formula compiler know the function ==

=== formula/inc/formula/compiler.hrc ===
'''''sc/inc/compiler.hrc''' up to and including version DEV300_m38''

These are the defines used by the resources for function names and the Function
Wizard, and the numerical values of OpCode for the formula compiler and
interpreter. Note that once defined the ''names'' '''must not be changed'''
because they are used by the localization tools as identifiers.

Add a new define, in this case for 2 parameters append it to the section for
functions with more than 1 parameter near the end of the file. Name the define
'''SC_OPCODE_MYFUNC''' and insert it right before the define of
SC_OPCODE_STOP_2_PAR, give it the value SC_OPCODE_STOP_2_PAR had, and
increment the values of SC_OPCODE_STOP_2_PAR and SC_OPCODE_LAST_OPCODE_ID. If
before the section looked like

<source lang="cpp">
#define SC_OPCODE_STOP_2_PAR 393

#define SC_OPCODE_LAST_OPCODE_ID 392 /* last OpCode */
</source>

it should then be

<source lang="cpp">
#define SC_OPCODE_MYFUNC 393
#define SC_OPCODE_STOP_2_PAR 394

#define SC_OPCODE_LAST_OPCODE_ID 393 /* last OpCode */
</source>

=== formula/inc/formula/opcode.hxx ===
'''''sc/inc/opcode.hxx''' up to and including version DEV300_m38''

Here the ''OpCodeEnum'' values are defined. Note that in a non-product build
(--enable-dbgutil during configure) there is a
<code>typedef OpCodeEnum OpCode;</code>
to show enum names in the debugger, while in a product build it is
<code>typedef OpCodeEnum USHORT;</code>
to save some memory, since compilers tend to produce an ''int'' for an enum.

Find a "right" place for the new enum. Although the way the definitions are
setup the placement doesn't matter, there are sections with different topics,
such as ''String functions'' and ''Statistical functions''. Maybe the correct
place for MYFUNC would be under ''miscellaneous''. Best practice is to add
a new OpCode to the end of such section. Name the OpCode '''ocMyFunc''' and add
the line

<source lang="cpp">
ocMyFunc = SC_OPCODE_MYFUNC,
</source>

=== formula/source/core/resource/core_resource.src ===
'''''sc/source/core/src/compiler.src''' up to and including version DEV300_m38''

These are the resources for function names. There are 3 resource bundles:

; RID_SC_FUNCTION_NAMES : English UI display names. These get localized for the UI of other languages.
; RID_SC_FUNCTION_NAMES_ENGLISH : These English names are used internally to store/load [[ODF]] v1.0/v1.1 and for [[API]] [http://api.openoffice.org/docs/common/ref/com/sun/star/sheet/XFunctionAccess.html XFunctionAccess]. Usually the name is identical to that in RID_SC_FUNCTION_NAMES. Once defined and "in the wild", the name '''must not be changed'''.
; RID_SC_FUNCTION_NAMES_ENGLISH_ODFF : These English names are used internally to store/load ODFF aka OpenFormula as of [[ODF]] v1.2. Once defined, the name '''must not be changed'''.

The new function name must be defined for all 3 resource bundles.

To the end of 
<code>Resource RID_SC_FUNCTION_NAMES</code> 
add

<source lang="cpp">
String SC_OPCODE_MYFUNC
{
Text [ en-US ] = "MYFUNC" ;
};
</source>

The <code>[ en-US ]</code> field tells the localization tools that the name may
be localized.

To the end of 
<code>Resource RID_SC_FUNCTION_NAMES_ENGLISH</code> 
add

<source lang="cpp">
String SC_OPCODE_MYFUNC { Text = "MYFUNC" ; };
</source>

The absence of the <code>[ en-US ]</code> field tells the localization tools
that the name '''must not''' be localized.

To the end of 
<code>Resource RID_SC_FUNCTION_NAMES_ENGLISH_ODFF</code> 
add

<source lang="cpp">
String SC_OPCODE_MYFUNC { Text = "MYFUNC" ; };
</source>

Again, the absence of the <code>[ en-US ]</code> field tells the localization
tools that the name '''must not''' be localized.

=== The compiler knows the function ===

After having added the necessary entries to <tt>formula/inc/formula/compiler.hrc</tt>, <tt>formula/inc/formula/opcode.hxx</tt>, and <tt>formula/source/core/resource/core_resource.src</tt> (<tt>sc/inc/compiler.hrc</tt>,
<tt>sc/inc/opcode.hxx</tt>, and <tt>sc/source/core/src/compiler.src</tt> respectively), the
formula compiler now knows the new function name and is able to compile an
expression where it is used, and it can be stored in and loaded from
a document. Of course nothing else works, the interpreter doesn't know how to
handle it and will generate an error if encountered. The function and its
parameters will not appear in the Function Wizard.

== Publish the function to the Function Wizard ==

=== sc/inc/scfuncs.hrc ===

Function groups (categories) and HelpIDs for functions are defined here. Lookup
the group where functions of ID_FUNCTION_GRP_... matching the new function's
category are defined and append an entry, incrementing the offset of the last
entry by one. For our function that could be

<source lang="cpp">
#define HID_FUNC_MYFUNC (HID_SC_FUNC_DUMMY+(ID_FUNCTION_GRP_MATH*ID_FUNCTION_OFFSET)+56)
</source>

=== sc/source/ui/src/scfuncs.src ===

This large resource file contains all elements necessary to display functions
in the Function Wizard. It defines the function's short description, the number
of parameters, whether they are optional, and the description of each
parameter. For a detailed description of fields see the comment on top of the
file.

Add the new function to the end of one of the two resource blocks
RID_SC_FUNCTION_DESCRIPTIONS1 or RID_SC_FUNCTION_DESCRIPTIONS2. Which one
doesn't really matter, but functions should be more or less equally distributed
over the two blocks. There are two blocks because one resource block couldn't
have more than 64k data, just another legacy from Win16 times.. looked up again
right now (2008-08-23) in the meantime this restriction seems to have been
obsoleted, which would have to be verified by a test build using one resource
block only though.

<source lang="cpp">
Resource SC_OPCODE_MYFUNC
{
String 1 // Description
{
Text [ en-US ] = "Calculates foo, optionally using bar." ;
};
ExtraData =
{
0;
ID_FUNCTION_GRP_MATH;
U2S( HID_FUNC_MYFUNC );
2; 0; 1;
0;
};
String 2 // Name of Parameter 1
{
Text [ en-US ] = "Number" ;
};
String 3 // Description of Parameter 1
{
Text [ en-US ] = "A value for which foo is to be calculated." ;
};
String 4 // Name of Parameter 2
{
Text [ en-US ] = "Number" ;
};
String 5 // Description of Parameter 2
{
Text [ en-US ] = "The bar value." ;
};
};
</source>

Some comments on the ExtraData block, for more details see scfuncs.src:
<pre>
ExtraData =
{
0; // The function is not suppressed and available in UI.
ID_FUNCTION_GRP_MATH; // The category in which the function is displayed.
U2S( HID_FUNC_MYFUNC ); // The HelpID of this function.
2; 0; 1; // 2 parameters, of which the 2nd is optional.
0; // None of the parameters are suppressed in the UI.
};
</pre>

=== sc/util/hidother.src ===

Here the HelpIDs to be used within the Function Wizard are propagated to the
help system. Go to the end of the section containing HID_FUNC_... and append an
entry,

<source lang="cpp">
hidspecial HID_FUNC_MYFUNC { HelpID = HID_FUNC_MYFUNC; };
</source>

=== The Function Wizard knows the function ===

Now the Function Wizard can display the function and its parameters, and
online-help may be authored.

== Let the interpreter handle the function ==

=== sc/source/core/inc/interpre.hxx ===

Add a member method to <tt>class ScInterpreter</tt> that will handle the new
function. Here this would be

<source lang="cpp">
void ScMyFunc();
</source>

Take care that the new member function doesn't resemble the name of some
already existing class, for example the method for the ADDRESS() function is
named ScAddressFunc() because ScAddress(), if called without
<tt>this-></tt> prefix, would be the ctor of class ScAddress instead. If in
doubt, add ...Func() to the name.

=== sc/source/core/tool/interpr4.cxx ===

In method ScInterpreter::Interpret() add to <code>switch ( eOp )</code> the
call to the member function for the OpCode:

<source lang="cpp">
case ocMyFunc : ScMyFunc(); break;
</source>

=== sc/source/core/tool/interpr?.cxx ===

Pick one of the interpr?.cxx source files where the new method may fit. There
is no general advice which file exactly that might be, be sensible. As a guide line

; interpr1.cxx : Basic math functions and informational functions.
; interpr2.cxx : Date functions and financial functions.
; interpr3.cxx : Statistical functions.
; interpr4.cxx : Interpreter managing and stack related functions, you shouldn't need to add anything there.
; interpr5.cxx : Matrix functions.
; interpr6.cxx : Some number crunching that in the past had to be compiled without optimizations, though in the mean time code changed and this probably is not necessary anymore.

For our function, since that expects two, one optional, numerical scalar
arguments, this would be:

<source lang="cpp">
void ScInterpreter::ScMyFunc()
{
BYTE nParamCount = GetByte();
// The MustHaveParamCount...() functions check the number of parameters and
// if they do not fit push an error on the stack, if the method fails
// (returns false) we return immediately.
if ( !MustHaveParamCount( nParamCount, 1, 2 ) )
return;

// Arguments are popped from the stack from right to left.
double fParam2;
if (nParamCount == 2)
fParam2 = GetDouble();
else
fParam2 = 0.0;

double fVal = GetDouble();
if ( /* does fVal meet all constraints */ )
{
double fResult = /* calculate foo */ ;
PushDouble( fResult );
}
else
PushIllegalArgument();
}
</source>

=== The not so easy case of non-scalar arguments ===

==== <tt>StackVar</tt> argument types ====

If the new function would handle parameters that are not scalar values, for
example a NumberSequence or matrix/array, they would have to be treated
explicitly, checking and reacting on the type of each argument. Lookout for
functions that use the <code>GetType()</code> call and handle <tt>StackVar</tt>
<code>svDoubleRef</code> or similar. Ask on the dev@sc mailing list if in
doubt.

The most common <tt>StackVar</tt> types obtainable with <code>GetStackType()</code>are:

; svDouble : A double value.
; svString : A literal string text.
; svSingleRef : A single cell reference.
; svDoubleRef : A cell range reference.
; svRefList : A list of cell range references.
; svMatrix : A matrix/array.

There are a few other types available with <code>GetRawStackType()</code> for
specific situations, these are converted to ''svDouble'' in
<code>GetStackType()</code> and returned as 0.0 by <code>PopDouble()</code> and
<code>GetDouble()</code>:

; svMissing : An empty parameter without value, if that should not be converted to 0.0 use <code>GetDoubleWithDefault(double)</code>.
; svEmptyCell : A previous expression returned an empty cell, it may depend on context whether that is to be interpreted as double or string.

The general template to act on each parameter in sequence from right to left is:

<source lang="cpp">
// Note: use short instead of BYTE when doing the (nParamCount-- > 0) loop below.
short nParamCount = GetByte();
if (MustHaveParamCountMin( nParamCount, 1)) // In case your function needs at least one parameter.
{
size_t nRefInList = 0;
while(nParamCount-- > 0)
{
if (nGlobalError)
Pop();
else
{
switch (GetStackType())
{
case svDouble :
{
double fVal = PopDouble();
if (!nGlobalError)
{
...
}
}
break;
case svString :
{
String aStr( PopString());
if (!nGlobalError)
{
...
}
}
break;
case svSingleRef :
{
ScAddress aAdr;
PopSingleRef( aAdr);
if (!nGlobalError)
{
ScBaseCell* pCell = GetCell( aAdr);
if (HasCellValueData( pCell))
{
double fVal = GetCellValue( aAdr, pCell);
if (!nGlobalError)
{
...
}
}
else
{
String aStr;
GetCellString( aStr, pCell);
if (!nGlobalError)
{
...
}
}
}
}
break;
case svDoubleRef:
case svRefList:
{
ScRange aRange;
PopDoubleRef( aRange, nParamCount, nRefInList);
if (!nGlobalError)
{
double fVal;
USHORT nErr = 0;
ScValueIterator aValIter( pDok, aRange );
if (aValIter.GetFirst( fVal, nErr))
{
do
{
if (nErr)
break;
...
} while (aValIter.GetNext( fVal, nErr));
}
SetError( nErr);
}
}
break;
case svMatrix:
{
ScMatrixRef pMat = GetMatrix();
if (pMat)
{
...
}
// else: GetMatrix did set errIllegalParameter
}
break;
default:
PopError();
SetError( errIllegalParameter);
}
}
}
Push...(...); // Don't forget to push a result ;-)
}
</source>

Of course your function may require specific treatment of parameters depending
on parameter types of other parameters, or bail out if a parameter type does
not match an expected type, this template is meant as guidance only.

==== sc/source/core/tool/parclass.cxx ====

Describes how parameters are to be treated if the function is used in an array
context expression, AKA array formula, where cell range references may be
treated differently from non-array context. If the function does not accept
other than scalar arguments, nothing has to be done here and the function does
not need an entry. Else the type of each parameter has to be set to one of:

; Value : Function expects a single scalar value.
; Reference : A cell range reference is passed as reference and not converted to array.
; Array : In array context a cell range reference is converted to array.
; ForceArray : A cell range reference is always converted to an array and the ForceArray context is propagated to all functions and operators in this parameter's expression.
; ReferenceOrForceArray : A cell range reference is not converted to an array, but a ForceArray context is propagated to all functions and operators in this parameter's expression. Only LOOKUP() uses this, other functions should not need it.

For a more detailed description of these types please read the comments for
<tt>ScParameterClassification::Type</tt> in
<tt>sc/source/core/inc/parclass.hxx</tt>. Ask on the dev@sc mailing list if in
doubt.

Set the <tt>ScParameterClassification::CommonData.bRepeatLast</tt> member
variable to <code>true</code> if the function accepts multiple parameters that
are of the same type as the last one specified, e.g. for SUM() that accepts
multiple ''Reference'' parameters. If the function does not accept multiple
parameters of the same type, set the value to <code>false</code>.

== Excel import/export ==

=== sc/source/filter/excel/xlformula.cxx ===

If the new function is also supported by Microsoft Excel®, for
import/export it has to be added to the binary filter as well. Depending on
from which version Excel knows the function, it has to be added to a
corresponding <code>XclFunctionInfo</code> table in <tt>xlformula.cxx</tt>. Ask
our Excel expert Daniel on the dev@sc mailing list for details. For details of
the tables' content see the declaration of <code>struct XclFunctionInfo</code>
in <tt>sc/source/filter/inc/xlformula.hxx</tt>.

=== oox/source/xls/formulabase.cxx ===

As if that wasn't enough, nearly the same has to be added to the new binary
filter for Microsoft Excel® that shares some mechanisms with the new
[[WikiPedia:Office_Open_XML | Microsoft Office Open XML (MOOXML)]] filter. The
implementation in <tt>sc/source/filter/{excel,xcl97}/</tt> will be deprecated
later. For details of the new tables see declaration of <code>struct FunctionInfo</code>
in <tt>oox/inc/oox/xls/formulabase.hxx</tt>.

Community Council Log 20100812

2010-08-12T20:54:14Z

ErAck: IRC Log 2010-08-12

{{Community_Council}}

== IRC Log 2010-08-12 ==

* Supposed start time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=12&month=08&year=2010&hour=18&min=30&sec=0&p1=0 18:30 UTC]
* Location: IRC

== Council Members ==

=== Attendees ===

*Andreas Bartel (Andreas_UX)
*Christoph Noack (christoph_n)
*Cor Nouws (CorNouws)
*Eike Rathke (erAck)
*Jürgen Schmidt (jsc)
*Stefan Taxhet (stx12)
*Olivier Hallot (olivierhallot)

=== Absent ===

*Charles-H. Schulz
*Louis Suárez-Potts
*Matthias Hütsch

== Log ==

Times are in CEST (UTC+2)

{| class="prettytable"
|-
| 20:52 || jsc || ok, let us start with the official meeting
|-
| 20:52 || jsc || The minutes from the last meeting can be found under http://wiki.services.openoffice.org/wiki/Community_Council/Minutes#2010-07-22
|-
| 20:53 || jsc || do you all agree and accept the minutes from the last meeting?
|-
| 20:53 || Andreas_UX || I do
|-
| 20:53 || stx12 || ok
|-
| 20:53 || olivierhallot || +1
|-
| 20:53 || Andreas_UX || by the way, can someone add me to the mailing list
|-
| 20:53 || Andreas_UX || or tell me how to do that myself
|-
| 20:54 || stx12 || i'll add you
|-
| 20:54 || jsc || 2010-03-04#2: Refresh Incubator and NLC Project processes -> Louis
|-
| 20:54 || jsc || Louis is not here today, so i expect no update.
|-
| 20:54 || Andreas_UX || thx stephan
|-
| 20:54 || olivierhallot || he already started somthing in the NLC list
|-
| 20:55 || jsc || 2010-03-04#3 : Publicize the open slot at the start of the CC meetings -> Juergen
|-
| 20:55 || jsc || ah ok thanks, but i would be nice if he would update the status in our agenda. I will remind him.
|-
| 20:56 || jsc || i have updated the status in the agenda ...
|-
| 20:56 || jsc || i have changed the name according the voting on the list and have added a template for a reminder email.
|-
| 20:57 || jsc || well the template could be changed or improved if necessary. I kept it simple.
|-
| 20:57 || jsc || i think this AI is done now.
|-
| 20:58 || jsc || any feedback?
|-
| 20:58 || stx12 || sounds good; i forgot about the schedule for this slot - every second cc meeting?
|-
| 20:58 || Andreas_UX || what about timing? Did we come to an agreement?
|-
| 20:59 || jsc || yes, that was the idea. The next would be in Budapest.
|-
| 20:59 || erAck || jsc: where is the template?
|-
| 20:59 || Andreas_UX || this one http://wiki.services.openoffice.org/wiki/Community_Council/Meeting_Guidelines/Public_Invitation_Reminder_Template
|-
| 20:59 || Andreas_UX || ?
|-
| 20:59 || jsc || it's a link under the related section in the meeting guidelines
|-
| 21:00 || * || stx12 thinks the item is done
|-
| 21:00 || jsc || i think the timeline was the first 30 min of our regular meeting. Please correct me if i am wrong
|-
| 21:01 || jsc || i can add a further sentence in the guidelines to make the timeline clear
|-
| 21:01 || jsc || it's a minor change. I am still thinking that it is done
|-
| 21:01 || jsc || next ...
|-
| 21:02 || jsc || 2010-03-04#6: Talk to Education Project Leads about structure and remit -> Cor
|-
| 21:02 || jsc || it's stalled ...
|-
| 21:02 || Andreas_UX || ok
|-
| 21:03 || Andreas_UX || can someone explain to me what this AI is all about?
|-
| 21:03 || Andreas_UX || thanks!
|-
| 21:03 || Andreas_UX || any specific focus?
|-
| 21:03 || jsc || 2010-04-01#7: Talk to NLC about ‘NLC of the Month’ for OOo Newsletter -> Charles
|-
| 21:03 || jsc || again, i expect no update because Charles is not here today. Does anybody else want to add something
|-
| 21:03 || stx12 || i think it's easier to explain this in a face2face meeting.
|-
| 21:04 || jsc || sorry, mmh yes but maybe we can discuss this in Budapest in detail.
|-
| 21:04 || -!- || christoph_n has joined #ooocouncil
|-
| 21:04 || jsc || yes i agree to Stefan on this point
|-
| 21:04 || Andreas_UX || i am ok with that
|-
| 21:04 || christoph_n || Sorry, I know I'm late :-(
|-
| 21:04 || olivierhallot || ok for me.
|-
| 21:05 || jsc || 2010-04-01#1: Community situation -> all
|-
| 21:05 || erAck || jsc: as 2010-04-01#7 says "This month the Hungarian team ..." we might at least update the Last Update date.
|-
| 21:05 || jsc || any updates
|-
| 21:06 || jsc || erAck: i will remind Charles to update it
|-
| 21:07 || jsc || i think this AI is one for Budapest as well. Cor send an email today with some points he want to discuss ...
|-
| 21:07 || jsc || this AI = 2010-04-01#1
|-
| 21:08 || jsc || anyway, anybody who wants to add something here and today?
|-
| 21:08 || erAck || I think that's best done face2face.
|-
| 21:08 || jsc || ok, next
|-
| 21:08 || christoph_n || Yes.
|-
| 21:09 || Andreas_UX || hi christoph!
|-
| 21:09 || christoph_n || Hi all!
|-
| 21:09 || jsc || 2010-04-29#2: scrolling, scrolling ... -> Missing OOo desktop presence -> Christoph, Stefan
|-
| 21:09 || stx12 || hi
|-
| 21:09 || olivierhallot || me too I have to bring an issue here...
|-
| 21:09 || christoph_n || Again, sorry for missing the first half hour ...
|-
| 21:10 || stx12 || no change since the last update Andreas_UX gave
|-
| 21:10 || christoph_n || Stefan, concerning this AI, did you get any update by Michael? Or, Andreas, is there any news?
|-
| 21:10 || jsc || no problem , you got 4 new AI's
|-
| 21:10 || christoph_n || jsc: only 4? ;-)
|-
| 21:10 || Andreas_UX || since the last chat, nothing really happend. at least nothing I know of
|-
| 21:11 || Andreas_UX || I am still expecting marketing to go public with their decision and ellaborate a bit
|-
| 21:11 || christoph_n || There have been some questions on the releases list. Some guessed there might be holiday time...
|-
| 21:11 || Andreas_UX || it really is
|-
| 21:11 || Andreas_UX || holiday time
|-
| 21:12 || jsc || we should ask marketing to come as soon as possible with an update -> AI owners???
|-
| 21:13 || christoph_n || Who is responsible here? Rosana?
|-
| 21:13 || stx12 || christoph_n: she is involved but depends on others. and is on vacation...
|-
| 21:13 || Andreas_UX || Rosana is the communication channel, yes
|-
| 21:14 || Andreas_UX || I'd guess at least
|-
| 21:14 || christoph_n || So pinging here doesn't make sense at the moment?
|-
| 21:14 || stx12 || not for a week.
|-
| 21:14 || jsc || can we expect something for Budapest?
|-
| 21:14 || Andreas_UX || I am. However, not sure about that.
|-
| 21:15 || stx12 || i would hope so; rosana has a talk about the topic anyway.
|-
| 21:15 || christoph_n || Ah, I didn't knew that. Maybe this could be added to the AI comments (I'll do that), if anybody has questions and may need some reference.
|-
| 21:16 || jsc || at least an update that it will take some more time would be a good one ;-)
|-
| 21:16 || stx12 || http://www.ooocon.org/index.php/ooocon/2010/paper/view/215
|-
| 21:16 || christoph_n || Well, the AI is already from end of April. I know, a rather young one (looking at the others), but nevertheless...
|-
| 21:17 || christoph_n || stx: " " :-)
|-
| 21:17 || jsc || with me as the CCC we will work on AI's :-)
|-
| 21:17 || -!- || CorNouws has joined #ooocouncil
|-
| 21:17 || christoph_n || jsc: :-)))
|-
| 21:17 || christoph_n || Hi Cor!
|-
| 21:17 || CorNouws || HI christoph_n, all
|-
| 21:18 || erAck || hi!
|-
| 21:18 || Andreas_UX || hey Core!
|-
| 21:18 || stx12 || hi cor; just in time to say goodbye ;-)
|-
| 21:18 || jsc || hi Cor, bye Cor we are already done ;-)
|-
| 21:18 || jsc || ok not really, do you want to share anything with us?
|-
| 21:18 || CorNouws || Sorry I missed some - prolly the most essetial part ot evening
|-
| 21:19 || CorNouws || jsc: Ah, not so much on the agenda?
|-
| 21:19 || jsc || did you finished the work on your floor?
|-
| 21:19 || * || erAck proposes to run a quick update on 2010-03-04#6, if there is any.
|-
| 21:19 || stx12 || just a heads up for CorNouws and christoph_n: the CC meeting is scheduled for tuesday 1600 and we plan to have dinner afterwards
|-
| 21:19 || CorNouws || partly ... have cleaned half of it, have to dry, new oil later this evening, and the second half tomorrow
|-
| 21:20 || CorNouws || stx12: great :-) where will the meeting be?
|-
| 21:20 || jsc || cor: sounds good and will make your family happy
|-
| 21:20 || stx12 || i talked to the organizers (peter); we will have a room at the university.
|-
| 21:21 || CorNouws || and since I am part of my family ;-)
|-
| 21:21 || christoph_n || stx12: Thanks!!!
|-
| 21:21 || erAck || CorNouws: sure? ;-)
|-
| 21:21 || jsc || stx12: i assume you will inform us in time with the details
|-
| 21:21 || stx12 || jsc: yes
|-
| 21:21 || CorNouws || OK, I will mail peter too, since we need three/four rooms close, for the various meetings, so that people are able to attend two at the same time
|-
| 21:22 || * || stx12 hopes that we will not feel like on a main station in the cc meeting
|-
| 21:23 || jsc || i would say we are done with the official meeting for today
|-
| 21:23 || Andreas_UX || seems to :-)
|-
| 21:23 || Andreas_UX || so
|-
| 21:23 || erAck || we skipped one AI, Cor, any news on 2010-03-04#6 Talk to Education Project Leads about structure and remit
|-
| 21:23 || CorNouws || stx12: I'll try to get other project plan their meetings at diferent times, slots so to say
|-
| 21:23 || olivierhallot || I have to bring an issue...
|-
| 21:24 || jsc || by the way, has anybody of you logged the meeting? I forgot it :-(
|-
| 21:24 || stx12 || olivierhallot: go ahead
|-
| 21:24 || Andreas_UX || shoot olivier
|-
| 21:24 || jsc || o sorry Olivier, please go ahead ...
|-
| 21:24 || erAck || jsc: my continuous log should be running.
|-
| 21:24 || olivierhallot || shooting... it is the new Broffice.org brand, comming closer to OO new brand...
|-
| 21:25 || olivierhallot || please look at http://qa.openoffice.org/issues/show_bug.cgi?id=113843
|-
| 21:25 || olivierhallot || I am uploading the files
|-
| 21:25 || CorNouws || erAck: no news on that, still same status
|-
| 21:25 || olivierhallot || we request to update the logo on the new release
|-
| 21:26 || stx12 || so you are looking for a contact that helps you to integrate the change?
|-
| 21:26 || CorNouws || olivierhallot: not that it really matters: but looks very good to me. And indeed, coming closer to.
|-
| 21:27 || olivierhallot || sort of. We are submitting this new brand design for approval of the CC.
|-
| 21:31 || stx12 || to me the design looks ok; have you heard any feedback from the branding list?
|-
| 21:31 || erAck || um.. is the CC in the position to approve a brand design?
|-
| 21:31 || CorNouws || Do they have a branding list in Brazil too?
|-
| 21:32 || CorNouws || erAck: IIRC, the cc decided about the special position of the BrOffice.org brand
|-
| 21:32 || christoph_n || erAck: For OOo, I would be sure that we speak for the community. For the BrOffice.org, I simply don't know.
|-
| 21:32 || olivierhallot || we have not a local lists but it was a decision of consensus among our NGO members
|-
| 21:32 || christoph_n || Especially since we didn't "approve" the OOo logo ...
|-
| 21:33 || CorNouws || so it is correct, or at least very polite, that Olivier/Br.Office ask the CC
|-
| 21:33 || Andreas_UX || �indeed good point
|-
| 21:33 || christoph_n || CorNouws: Correct.
|-
| 21:34 || christoph_n || From my side, if it goes well with the OOo logo, I recommend to use it. If the BrOffice.org community comes to another decision, it is their right to optimize the branding for their region (my personal thoughts).
|-
| 21:34 || christoph_n || By the way: This doesn't make sense only, if we get a trademark policy for the new logo that finally works!
|-
| 21:35 || christoph_n || (I mean the OOo logo)
|-
| 21:35 || olivierhallot || Christoph: we, as BrOffice.org, consider ourselves as OpenOffice.org in Brazil. Nothing more, nothing less.
|-
| 21:35 || stx12 || yes, the status of broffice.org/openoffice.org is still in discussion
|-
| 21:35 || christoph_n || oliverhallot: I know :-) But you did excellent work to grow BrOffice.org in your region ... so how should I be able to decide something like that? ;-)
|-
| 21:36 || stx12 || and so i think an update of the broffice.org design as proposed by olivierhallot is appropriate
|-
| 21:36 || CorNouws || olivierhallot: Yes, you expplained some time before (on a mil list?) the situation that it is not easy to change to OpenOffice.org in Brazil, because of the strong current brand, although legaly it woudl be possible now. Did I understand that correct?
|-
| 21:37 || jsc || olivier: sure and the Brazil community did a very good job ...
|-
| 21:37 || CorNouws || stx12: +1
|-
| 21:37 || jsc || +1
|-
| 21:38 || olivierhallot || Cor: exact. Thanks to Stephan recent mail to us with the Court decision, we have already a clear "legal" explanation. But market is another story.
|-
| 21:40 || stx12 || olivierhallot: i think we have to continue the evaluation of the legal aspects. as soon as we have this clarfied we should talk about the long term route.
|-
| 21:40 || stx12 || but in the meantime it makes sense that broffice follows the OpenOffice.org brand refresh
|-
| 21:41 || christoph_n || stx12: Stefan, if the community cannot safely use the OOo logo, does it make sense to integrate the new BrOffice.org logo?
|-
| 21:42 || olivierhallot || stx12: I am sure we will have time to talk about that in Budapest
|-
| 21:42 || stx12 || that's what i mean with follow the brand refresh; use the logo as proposed by olivierhallot that is close to the new design
|-
| 21:42 || stx12 || olivierhallot: yes, I'm looking forward to this.
|-
| 21:42 || Andreas_UX || I would support that
|-
| 21:43 || christoph_n || Mmmh, I don't get it.
|-
| 21:44 || Andreas_UX || what do you mean chris?
|-
| 21:44 || Andreas_UX || maybe I don't get that too ;-)
|-
| 21:44 || christoph_n || So I understand that it is desired to let BrOffice.org follow the brand refresh ...
|-
| 21:45 || christoph_n || ... this makes sense if the new logo is accepted and there is a clear policy how to use it. Otherwise ...
|-
| 21:45 || CorNouws || christoph_n: ...
|-
| 21:45 || CorNouws || what logo do we see in OpenOffice.org ?
|-
| 21:45 || christoph_n || ... it would make less sense. And here, it seems that we don't have the appropriate Trademark Policy.
|-
| 21:46 || christoph_n || So, if there is no clear idea for the community how to use the new OOo logo, why join the effort.
|-
| 21:46 || jsc || the proposed brand from Olivier for now. Ongoing discussion if the brand BrOffice.org can be moved into OpenOffice.org in a smooth and well prepared transition + a good and also well prepared marketing campaign ...
|-
| 21:47 || stx12 || i would not block olivier's activity by creating this dependency.
|-
| 21:48 || christoph_n || stx12: I don't want to block it. It is just a matter of being aware of it ... here we talk about months of waiting.
|-
| 21:48 || CorNouws || I see no special problem for the new BrOo logo. It can be used in the product just as the OOO new logo. And the policy will foolow soon.
|-
| 21:48 || jsc || sure not directly but it good be a way for the future if all agree
|-
| 21:48 || stx12 || i will follow up on the usage question in the next days. and basically it doesn't change anything for the broffice team.
|-
| 21:48 || christoph_n || stx12: That would be great. There is real demand to get this clarified.
|-
| 21:48 || CorNouws || oops s/OOO/OOo ;-)
|-
| 21:49 || christoph_n || CorNouws: ;-)
|-
| 21:49 || stx12 || christoph_n: yes, i'm aware of that
|-
| 21:50 || christoph_n || Okay, thanks!
|-
| 21:51 || jsc || to summarize it ...
|-
| 21:51 || jsc || we all accept the proposal from Olivier
|-
| 21:51 || jsc ||
|-
| 21:51 || Andreas_UX || yes
|-
| 21:51 || Andreas_UX || i do
|-
| 21:51 || erAck || +1
|-
| 21:51 || CorNouws || ok
|-
| 21:51 || stx12 || ok
|-
| 21:51 || olivierhallot || Gentlemen, thank you very much indeed.
|-
| 21:51 || jsc || anything else for today?
|-
| 21:52 || * || CorNouws my floor ...
|-
| 21:52 || christoph_n || +1 (by considering to the comments above)
|-
| 21:52 || christoph_n || CorNouws: flOOor
|-
| 21:52 || Andreas_UX || you're funny today ;-)
|-
| 21:52 || olivierhallot || Just a practical note: to whom should I assign this branding issue?
|-
| 21:53 || * || christoph_n is always funny :-)
|-
| 21:53 || CorNouws || :-D
|-
| 21:53 || stx12 || i think it need a bit more work; i guess we'll need exact replacements for the files.
|-
| 21:54 || stx12 || those affected like splash...
|-
| 21:54 || CorNouws || think I have to leave - erAck: can you pls send me the log (of the first part)?
|-
| 21:54 || erAck || CorNouws: I'll do.
|-
| 21:54 || stx12 || i'll see who can guide you there...
|-
| 21:54 || CorNouws || thnks all & bye bye
|-
| 21:55 || Andreas_UX || I will join you Core ;-)
|-
| 21:55 || jsc || bye Cor
|-
| 21:55 || erAck || bye
|-
| 21:55 || olivierhallot || bye
|-
| 21:55 || christoph_n || Bye Cor, bye Andreas!
|-
| 21:55 || Andreas_UX || Have a good one everybody!
|-
| 21:55 || -!- || CorNouws has left #ooocouncil []
|-
| 21:55 || -!- || Andreas_UX has quit [Quit: Andreas_UX]
|-
| 21:55 || olivierhallot || bye all!
|-
| 21:56 || -!- || olivierhallot has left #ooocouncil []
|-
| 21:56 || christoph_n || Okay, then I'll update the AI ... thanks to all and have a nice evening!
|}

=== URIs mentioned ===
* [[Community_Council/Minutes#2010-07-22]]   (jsc 20:52)
* [[Community_Council/Meeting_Guidelines/Public_Invitation_Reminder_Template]]   (Andreas_UX 20:59)
* http://www.ooocon.org/index.php/ooocon/2010/paper/view/215   (stx12 21:16)
* http://qa.openoffice.org/issues/show_bug.cgi?id=113843   (olivierhallot 21:25)

[[Category:Community_Council]]

User:ErAck/WorkFlow

2010-08-05T12:53:13Z

ErAck: /* System */ removed mentioning the totally outdated VirtualBox image

Here I'm noting down my work flow and environment I use when working on code,
hopefully giving some useful hints for others.

== System ==

Preferably Debian. Etch did it. Lenny does it better. Which is what I use at home. At work I use
Kubuntu, Solaris/SPARC, Solaris/x86, MacOSX/x86, and with a ten-foot pole only
when necessary Windows XP.

== Shell environment ==

With the migration to [[OOo_and_Subversion| SVN]] the .svn/* subdirectories'
content came in the way when using ''grep -r ...'', so in ''~/.bashrc''
I have
export GREP_OPTIONS='--exclude-dir=.svn'
respectively in ''~/.cshrc''
setenv GREP_OPTIONS '--exclude-dir=.svn'

'''Note:''' On some systems there's an old version of grep that doesn't know
that option and bails out if set. This will break the build later, so check by
setting the variable and invoke grep to see whether it complains, and if so do
not set the variable.

With the migration to [[Mercurial]] this is obsolete unless you plan to work
on old branches of the SVN repository, or have other sources managed by SVN.

== Vim editor ==

I'm a Vim addict since the mid 90s, so I use the stuff lined out in [[Editor Vim]].

=== A useful link for gvim ===

I usually use plain ''vim'' in a build environment shell, but to be able to
[[Editor_Vim#Compiling_a_source_from_within_Vim| compile sources]] also from
within a detached ''gvim'' I setup a symbolic link in ''$SRC_ROOT'' after having
[[#Configure| configured]] and sourced the build environment:

<source lang="bash">
ln -s LinuxX86Env.Set.sh ENV.$INPATH
</source>
for bash respectively
<source lang="bash">
ln -s LinuxX86Env.Set ENV.$INPATH
</source>
for tcsh.

== Building ==

Out of habits introduced at Sun Hamburg labs, I usually follow the same naming
scheme also at home when setting up [[CWS]]s, which is to checkout source code
into a subdirectory of <code>$CWS_WORK_STAMP/$WORK_STAMP/ooo</code>,
for example <tt>cwsname/DEV300/ooo</tt>

=== configure ===

When I don't need a full-blown tree because I don't plan to work on globally
used stuff that would also affect the much disregarded ''binfilter'' binary
filter module, I of course exclude that from the build, and I exclude many
others as well. This boils build time down to 3.5 hours for the entire tree
[hey, you Windows guys are getting envious, aren't you? ;-)]. My configure
call currently (2009-03-14) is

./configure --enable-dbgutil --disable-strip-solver --with-use-shell=bash --disable-binfilter --without-fonts --without-ppds --disable-build-mozilla --with-system-stdlibs --disable-systray --with-build-version="Built by erAck" --with-vendor="erAck" --disable-odk --disable-qadevooo --disable-pdfimport --disable-mediawiki --disable-reportdesign --disable-neon --with-system-zlib --with-system-openssl --with-system-jpeg

Especially note
; --enable-dbgutil : This builds a non-product version with assertions and various checks during runtime enabled. The output directories are without the ''.pro'' extension, for example ''unxlngi6'' instead of ''unxlngi6.pro''
; --disable-strip-solver : Symbols are not stripped from the libraries, so we'll have useful information in the debugger for backtraces.
; --with-use-shell=bash : use ''bash'' shell instead of the default ''tcsh''. '''Note:''' if you do not specify this and source the resulting <tt>LinuxX86Env.Set.sh</tt> to work in bash, the <tt>SHELL</tt> environment variable will still contain ''/bin/tcsh'', this may be needed for the build pocess [does it really? I'd consider it a bug], but will interfere with other tools attempting to invoke a shell that is thought to match the current shell, e.g. if you <code>source ENV.$INPATH</code> from within ''gvim'' as mentioned above in [[#A_useful_link_for_gvim| a useful link for gvim]].

=== More shell variables ===

I add these to the end of LinuxX86Env.Set.sh, replace ''cwsname'' and ''m42''
and the content of ''my_OOO_TREE'' as appropriate. For ''tcsh'' replace
''export var="..."'' with ''setenv var "..."'' and add to LinuxX86Env.Set
instead.

<source lang="bash">
export CWS_WORK_STAMP="cwsname"
export my_UPDMINOR="m42"
export WORKSPACE_STAMP="$CWS_WORK_STAMP"
export my_OOO_TREE="$HOME/ooo/src/$WORKSPACE_STAMP/$WORK_STAMP"
export TMP="/tmp"
export CCACHE_DIR="$my_OOO_TREE/.ccache_${INPATH}"
ccache -M 2G -F 100000
export LOCALINSTALLDIR="$my_OOO_TREE/inst.${my_UPDMINOR}"
export PKGFORMAT="installed"
export BUILD_COMMAND="perl $SRC_ROOT/solenv/bin/build.pl"
</source>

; TMP : For some reason (is there any?) configure does not inherit that, so set again.
; CCACHE_DIR and ccache : Speeds up things significantly when rebuilding source. Note that the cache directory is setup such that different milestones and product and non-product versions don't interfere.
; LOCALINSTALLDIR and PKGFORMAT : Building the installation set in module ''instsetoo_native'' creates a directly usable installation instead of packages. The location is, for example, .../cwsname/inst.m42/... See also [http://blogs.sun.com/GullFOSS/entry/the_fastest_way_to_get GullFOSS entry].
; BUILD_COMMAND : ''build'' actually is an alias, setting up a variable enables use in inherited shells, from within the editor, or simply in a <code>time $BUILD_COMMAND --all</code> invocation.

{{Documentation/Caution| Using LOCALINSTALLDIR with a build in instsetoo_native is not deterministic if not building with PKGFORMAT installed or building for several languages or building language packs.}}

In these cases it is necessary to not set LOCALINSTALLDIR and let the build create deb or rpm packages, and after a complete build use

<source lang="bash">
export LOCALINSTALLDIR=YourLocation
cd $SRC_ROOT/instsetoo_native/util
dmake openoffice_en-US PKGFORMAT=installed
</source>

If you also set <code>FORCE2ARCHIVE=TRUE</code> you'd get a .tar.gz archive you could extract to any place.

YMMV.. See [http://www.openoffice.org/servlets/ReadMsg?list=dev&msgNo=25968 this mail] for details about LOCALINSTALLDIR.

==== ccache ====

On my system I have setup a symbolic link
<tt>/usr/local/bin/gcc -> /usr/bin/ccache</tt>
so every source I build uses ccache, I never encountered problems with that.
If you want to use ccache selectively for OOo, add the following variables:

<source lang="bash">
export CC="ccache gcc"
export CXX="ccache g++"
</source>

=== build ===

In the OOo tree's root, effectively being <tt>.../cwsname/DEV300/ooo</tt>
in this example, execute

<source lang="bash">
source LinuxX86Env.Set.sh
./bootstrap
cd instsetoo_native
build --all -- -P2
</source>

Note that I don't invoke the ''dmake'' command in the tree's root.
Reasons are:

* Fine grained call of the ''build'' command, specifying the number of processes to use. Here I create 2 dmake processes per source directory entered by the build script. As a rule of thumb, use 2 processes per CPU core, so if one is waiting for disk IO the other can do useful things. Yes, this is a much simplified view.. For a CPU having 2 cores, this would make 4 processes. However, instead of simply specifying -P4 for dmake I prefer 2 build processes and 2 dmake processes per build process, which would be
** <code>build -P2 --all -- -P2</code>
* In case the build breaks, for example in module ''svx'', after having fixed things the build can be easily continued in that module by retrieving and editing the command line, while still in module ''instsetoo_native'':
** <code>build --all:svx -- -P2</code>
* In case I'm short of disk space, which may happen if I build both, product and non-product, I add the ''--dlv_switch -link'' option, that creates hard links of the files delivered to the solver instead of copying them, which may save 500MB or so per build.
** <code>build --dlv_switch -link --all -- -P2</code>
* Build can create a HTML status page to load in the browser and watch progress. Add the ''--html'' option and to still see the console output add ''--dontgraboutput'' as well. The HTML page is created as <tt>$SRC_ROOT/$INPATH.build.html</tt>
** <code>build --html --dontgraboutput --dlv_switch -link --all -- -P2</code>

Ah, and of course I use
<source lang="bash">
time $BUILD_COMMAND --html --dontgraboutput --dlv_switch -link --all -- -P2
</source>
instead and hope the build doesn't break so I can see 1:55:03 or some such ;-)

==== product and non-product ====

To build a product version additionally to the non-product version it would be
enough to configure again but omit the ''--enable-dbgutil'' option. However,
that would overwrite the already existing environment files, so

<source lang="bash">
mv LinuxX86.Set LinuxX86.non-pro.Set
mv LinuxX86.Set.sh LinuxX86.non-pro.Set.sh
rm ENV.$INPATH
ln -s LinuxX86.non-pro.Set.sh ENV.$INPATH
./configure ... with all other options except --enable-dbgutil ...
# Again, edit the environment files as mentioned above to add variables, but
# this time set LOCALINSTALLDIR to "$my_OOO_TREE/inst_pro.${my_UPDMINOR}"
# to not overwrite the non-pro installation!
mv LinuxX86.Set LinuxX86.pro.Set
mv LinuxX86.Set.sh LinuxX86.pro.Set.sh
source LinuxX86.pro.Set.sh
ln -s LinuxX86.pro.Set.sh ENV.$INPATH
</source>

Note that it is not needed to execute ''./bootstrap'' again, as the resulting
''dmake'' executable is copied to and executed from solenv/$OUTPATH/bin for
both, pro and non-pro. Having renamed the LinuxX86.Set.sh it wouldn't even work
because bootstrap sources that.

Note also that $INPATH contains either ''unxlngi6'' for non-product or
''unxlngi6.pro'' for product, whereas $OUTPATH contains always ''unxlngi6''
without any extension. This may be confusing, as one would assume $OUTPATH
would be used for the output directories. Just remember that $INPATH is used in
the ''solver'' path to pull in header files and libraries. In fact, $OUTPATH is
a base name that gets extended in makefiles with ''.pro'' for product output
directories, or may be extended with other extensions, for legacy reasons, see
<tt>solenv/inc/settings.mk</tt>

== Running ==

Run the office from the installation. Do not attempt to run it from the
''solver/bin'' directory, it won't work. Also do not run it from within the
build environment's shell, as libraries from the wrong path would be pulled in
and subsequent libraries not be found. Use a clean shell instead. In the
example used here, the executable to run would be
<tt>.../cwsname/DEV300/inst.m42/openoffice.org3/program/soffice</tt>, execute
it once to verify successful installation and step through the initial wizard.

To load documents attached to issues it is a good idea to set macro security
to the highest possible value, i.e. execute macros only if the document
resides in a specific location. Go to
''Tools → Options → OpenOffice.org → Security → Macro Security''
and choose ''Security Level'' '''Very high'''. If you need to execute macros to
reproduce a bug you may add a directory to ''Trusted Sources'' in which you put
such documents after having inspected the macros coming with the document.

Other options I modify:

* ''OpenOffice.org → Paths''
** Change ''My Documents'' to the desired location; I have a <tt>bugdocs</tt> folder.
* ''Load/Save → General''
** Uncheck ''Save AutoRecovery information every ... minutes''. It usually gets in the way at the most inconvenient point when debugging.
** Uncheck ''Size optimization for ODF format''. It's much easier to view the XML streams with each element on its own line when necessary, instead of everything on just one line. '''Hint:''' use the [[Xmlpp| XML pretty printer (xmlpp)]] to reformat streams of documents that were saved with this option enabled.
* ''Language Settings → Languages''
** I check ''Enabled for Asian languages'' and ''Enabled for complex text layout (CTL)'' because I also work on [[I18n|i18n]], not needed otherwise.

== Little Helpers ==

To tame the source base I heavily use exuberant ctags and GNU id-utils and
sometimes cscope. For scripts generating databases suitable for OOo see the
[[Little Helpers]].

=== Setting up the ctags and ID databases ===

In the build environment shell I create the ctags and GNU ID-utils databases
using the scripts mentioned:

<source lang="bash">
cd $SRC_ROOT
mkid-script '*'
ctags-script --global
cd sc
tagsID '{.,../formula}'
</source>

Note that '*' and '{.,../formula}' are enclosed in single quotes to prevent
pathname and brace expansion on the command line. This creates

; ID
: Id-utils database for the entire OOo tree; generating this takes some time, 20 minutes or so.
; tags
: Tag file for $SRC_ROOT/solver/inc, containing symbols of all delivered header files.
; sc/tags
: Tag file for modules ''sc'' and ''formula''.
; sc/ID
: Id-utils database for modules ''sc'' and ''formula''.
; sc/cscope.*
: Cscope database for modules ''sc'' and ''formula''.

Because I work within the ''sc'' module and the compiler and tokens are now
derived from classes declared in module ''formula'', I setup the combined
databases, so Vim sees them as one entity. The global ''tags'' file is pulled
in when an identifier is not found in the local ''tags'' file, and the global
''ID'' file comes in handy when working on changes that affect the entire
office, for example to lookup where a certain method is used.

== Debugging ==

Let assume we want to debug a call to an interpreter function. Let further
assume we don't know the implementation name and we don't bother looking it up
through the chain resource file, resource header file, opcode file, and guess
the corresponding interpreter function's method (for details see
[[Calc/Implementation/Spreadsheet_Functions| implementation of spreadsheet functions]]).

Per debug session, I prefer having a terminal with 3 tabs open:

# Shell with build environment, lets call it '''B'''uild.
# Shell from which I run the office, lets call it '''R'''un.
# Shell for debugger, lets call it '''D'''ebug.

This way they don't interfere with each other, preserving all stdout/stderr
from the office run and having a clean screen for the debugger, which should
not be started from within the build environment.

=== Build selected files with debug ===

Of course we could build just the entire ''sc'' module with debug, but
I suppose you're just too impatient to wait for it, as I am. Instead, lets
build just some objects with debug in the '''B'''uild shell:

<source lang="bash">
cd $SRC_ROOT/sc/source/core/tool
dmake killobj
dmake debug=t
cd ../../../util
dmake debug=t
</source>

; dmake killobj
: Removes object files corresponding to all source files in the current directory.
; dmake debug=t
: Builds all object files with debug that need to be rebuild.
The final ''dmake debug=t'' in ''util'' links the shared libraries.

The <tt>sc/unxlngi6/lib/libscli.so</tt> shared library now has debug
information for those objects.

==== mkd script ====

Now wait, instead of killing all objects in the ''tools'' directory,
selectively building only interpreter relevant files would be sufficient.
A [[Little_Helpers#mkd| script ''mkd'']] called as
<code>'''mkd interpr*.cxx'''</code> is a reusable solution. The second dmake
call in the script is to build the object archive or other targets for the
directory if all sources were successfully compiled. After that we still need
to cd into the ''util'' directory to link the library using ''dmake debug=t''.
This can be accomplished by passing the ''--link'' or ''-l'' option to the
script, so <code>'''mkd -l interpr*.cxx'''</code> does it all.

==== Formula compiler, tokens, interpreter and document access ====

To not only have the interpreter with debug but also the compiler and methods
that access the document and retrieve values from cells or interpret
recursively, this comes handy:

<source lang="bash">
# To get down to the compiler roots add module formula core
cd $SRC_ROOT/formula/source/core/api
mkd -l *.cxx
# Calc related
cd $SRC_ROOT/sc/source/core/tool
mkd compiler*.cxx token*.cxx interpr*.cxx
cd ../data
mkd -l doc*.cxx tab*.cxx col*.cxx cell*.cxx
</source>

=== Run the office ===

In '''R'''un shell

<source lang="bash">
# cd into the 3-layer office library directory
cd .../cwsname/DEV300/inst.m42/openoffice.org/basis3.0/program

# Create a backup of the original libraries and symbolic links to the debug
# libraries, only needed the first time of course:
mkdir bkp
cp -p libsc* bkp
cp -p libvba* bkp
cp -p libfor* bkp
ln -sf ../../../../ooo/sc/unxlngi6/lib/libsc* .
ln -sf ../../../../ooo/sc/unxlngi6/lib/libvba* .
ln -sf ../../../../ooo/formula/unxlngi6/lib/libfor* .
</source>

'''Note:''' This is explicitly for debugging Calc, other modules, other
libraries, of course.. You do not need this to run the office. Creating
symbolic links doesn't necessarily work with all libraries, as some of them
then won't find the appropriate run path to dlopen other libraries. Some need
to be copied instead. This may need experimenting. However, it works for the
Calc libraries.

Then execute the office:

<source lang="bash">
../../../openoffice.org3/program/scalc & sleep 8 ; ps
</source>

This starts Calc in the background, sleeps for 8 seconds during startup (you
may have to adapt the duration on a slower machine), and then displays the
process list, one of them being ''soffice.bin'', for example

1234 pts/6 00:00:01 soffice.bin

Remember the PID or copy it to the clipboard or selection.

=== Debug the beast ===

In the '''D'''ebug shell it is best to cd into some source code subdirectory,
for example <tt>sc/source/core/tool</tt>, otherwise the debugger sometimes may
not find included header files when stepping through inline methods. You may of
course also use the --cd option instead, or put a ''cd'' command in a gdb
command file and execute it on startup for frequent use. Consult the
documentation for details. Then invoke the ''gdb'' debugger with the Text User
Interface, ''gdbtui'', and attach it to the office executable already running:

<source lang="bash">
gdbtui --pid=1234
</source>

or, if that doesn't work

<source lang="bash">
gdbtui .../cwsname/DEV300/inst.m42/openoffice.org3/program/soffice.bin 1234
</source>

where ''1234'' is of course the actual PID of the running process. If your
system doesn't have ''gdbtui'', try <code>gdb -tui</code> or
<code>gdb --tui</code> or <code>gdb --interpreter=tui</code> instead. If that
still doesn't come up with an extra text frame, you're out of luck or on MacOSX
or both ;-)

When it loads the libraries you may have to press the enter key a few times
during the listing, and then it waits for command input, with the executable
being interrupted. To debug some interpreter function as mentioned above, the
central entry point would be to set a breakpoint at ScInterpreter::Interpret(),
so enter

b 'ScInterpreter::Interpret()'
c

where '''b''' sets a breakpoint, here at the entry of the desired function, and
'''c''' continues running the program. Note that you don't have to type the
full classname::method for the breakpoint, it is sufficient to type an
unambiguous portion of the name an press the ''Tab'' key for completion. This
might be

b 'ScInterpreter::Int<TAB>

Note that the leading single quote is needed for this functionality.

If you now enter a formula in a cell, the debugger breaks as soon as
ScInterpreter::Interpret() is reached and you may start stepping through. In
command line mode this would be pressing '''n''' ''Enter'' for next program
line, stepping over function calls, or '''s''' ''Enter'' stepping into function
calls. The previous command could be repeated by just pressing ''Enter''.

However, we started with the TUI, so we will take advantage of it. Press
''Ctrl-x'' '''s''' to switch to ''SingleKey'' mode, from now on you can use
just '''n''' or '''s'''. A single '''c''' continues execution. Other single
keys do different things, experiment or read the fine manual.. You may leave
SingleKey mode at any time by pressing '''q'''.

As detailed documentation for gdb and TUI sometimes is not installed on systems
(check <code>info gdb</code>) and the ''info'' program is cumbersome to use if
not used to, here's the online documentation:
[http://sourceware.org/gdb/current/onlinedocs/gdb_toc.html Debugging with GDB]
and the
[http://sourceware.org/gdb/current/onlinedocs/gdb_24.html GDB Text User Interface]

=== See also ===

The [[Debugging]] page gives useful hints and tips.

== Profiling ==

I use the great [[Callgrind]] and KCachegrind tools to create call graphs and
see where performance bottlenecks are.

Performance profiling of course needs to be done in a product version, compiled
with optimizations and without assertions and test code. So cd into
.../cwsname/DEV300/ooo and <code>source ENV.unxlngi6.pro</code>. Everything
needed to be done hopefully is explained in
[[Callgrind#Profiling_OpenOffice.org| profiling OOo with callgrind]].

OpenOffice.org Internship/Projects/2010/Add new spreadsheet functions and parameters according to ODFF

2010-07-28T13:37:27Z

ErAck: first shot

{{DISPLAYTITLE:Internship 2010: Add new spreadsheet functions and parameters according to ODFF}}

__TOC__

== Overview ==
The [[OpenDocument| OASIS OpenDocument Format (ODF)]] specification part 2, OpenFormula aka ODFF, standardizes on recalulcated formula expression as used by [[Calc]] and introduces new functions and parameters that need to be implemented.

== Project plan ==
* Align and enhance the already existing [[Calc/ODFF_Implementation/Examine_functions| overview and comparison]] of differences between implemented spreadsheet functions and the current ODFF draft.
* Determine the most important functions to be implemented.
* Implement functions in
** compiler
** interpreter
** function wizard resources

=== Documentation ===
* Code documentation.
* Function and parameter descriptions in the Formula Wizard.
* Provide input for the online help / documentation team.

== Project status ==
* The project is accepted for the OpenOffice.org summer internship program 2010
* Evaluation and comparison is ongoing.

[[Category:Marketing]]
[[Category:Development]]
[[Category:Calc]]

User:ErAck

2010-07-20T10:44:07Z

ErAck:

{| align="right"
| [[Image:ErAck_128x128.png‎]]
|}
* Name: Eike Rathke
* Nick: erAck
* OOo: er
* Working on:
** [[Calc]] spreadsheet application compiler, interpreter, engine
** number formatter
** [[I18npool|internationalization (i18n)]] and locale data, '''not''' localization (l10n)
*** .signature: number formatter stricken i18n transpositionizer
* IRC: irc://irc.freenode.net/#dev.openoffice.org
* Email Calc developers: [mailto:dev@sc.openoffice.org dev@sc.openoffice.org] mailing list
* Email personal: [mailto:er@openoffice.org er@openoffice.org], [mailto:eike.rathke@oracle.com eike.rathke@oracle.com]
* Private URL: http://www.erack.de/
* μBlog: http://identi.ca/erack
* Blog: http://jroller.com/erAck
* GullFOSS: http://blogs.sun.com/GullFOSS
* Company Name: Oracle Deutschland B.V. & Co. KG
* Company URL: http://oracle.com/office
* Location: Hamburg, Germany
* Timezone: UTC+1 with DST rule TZ=CET-1CEST-2,M3.5.0/2,M10.5.0/3

== currently working on ==

* [http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula OASIS OpenDocument file format formula specification], ODFF aka OpenFormula.
* mentorship for implementors, review of patches and integration.
* Bits of formula compiler and interpreter changes.


== Work flow ==

My personal [[/WorkFlow| work flow and environment]] when working on code.

== Wiki stuff ==

Edit help: [[:Category:Help]]

=== Code syntax highlighting ===

Code syntax highlighting is possible with
<pre>
<source lang="$LANGUAGE">
...
</source>
</pre>

where ''$LANGUAGE'' is one of this list that was dynamically generated using <code><nowiki><source lang="invalid"></source></nowiki></code>

<source lang="invalid"></source>

'''NOTE:''' the old SwinBrain CodeSyntaxHighlight does not work anymore since the wiki upgrade on 2008-02-14
<pre>
<code>[language]
...
</code>
</pre>
produces rubbish now!

=== Templates ===

See [[Documentation/Dashboard/Wiki Editing Policy]] and [[Special:Mostlinkedtemplates]] and [[:Category:Wiki_Templates_Expressing_Quality]] and [[:Category:Formatting_templates]].

<code><nowiki>{{Documentation/Caution| Do or don't.}}</nowiki></code>
{{Documentation/Caution| Do or don't.}}

<code><nowiki>{{Documentation/Note| Note that.}}</nowiki></code>
{{Documentation/Note| Note that.}}

<code><nowiki>{{Template:Documentation/Tip| Tip.}}</nowiki></code>
{{Template:Documentation/Tip| Tip.}}

<code><nowiki>{{Documentation/Outdated}}</nowiki></code>
{{Documentation/Outdated}}

{{LinkBanner}}

=== new topic ===
<nowiki>Insert non-formatted text here</nowiki>

User:ErAck

2010-07-15T08:59:25Z

ErAck: Oracle

{| align="right"
| [[Image:ErAck_128x128.png‎]]
|}
* Name: Eike Rathke
* Nick: erAck
* OOo: er
* Working on:
** [[Calc]] spreadsheet application compiler, interpreter, engine
** number formatter
** [[I18npool|internationalization (i18n)]] and locale data, '''not''' localization (l10n)
*** .signature: number formatter stricken i18n transpositionizer
* IRC: irc://irc.freenode.net/#dev.openoffice.org
* Email Calc developers: [mailto:dev@sc.openoffice.org dev@sc.openoffice.org] mailing list
* Email personal: [mailto:er@openoffice.org er@openoffice.org], [mailto:eike.rathke@oracle.com eike.rathke@oracle.com]
* Private URL: http://www.erack.de/
* μBlog: http://identi.ca/erack
* Blog: http://jroller.com/erAck
* GullFOSS: http://blogs.sun.com/GullFOSS
* Company Name: Oracle Deutschland B.V. & Co. KG
* Company URL: http://www.oracle.com/us/products/applications/open-office/index.html
* Location: Hamburg, Germany
* Timezone: UTC+1 with DST rule TZ=CET-1CEST-2,M3.5.0/2,M10.5.0/3

== currently working on ==

* [http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula OASIS OpenDocument file format formula specification], ODFF aka OpenFormula.
* mentorship for implementors, review of patches and integration.
* Bits of formula compiler and interpreter changes.


== Work flow ==

My personal [[/WorkFlow| work flow and environment]] when working on code.

== Wiki stuff ==

Edit help: [[:Category:Help]]

=== Code syntax highlighting ===

Code syntax highlighting is possible with
<pre>
<source lang="$LANGUAGE">
...
</source>
</pre>

where ''$LANGUAGE'' is one of this list that was dynamically generated using <code><nowiki><source lang="invalid"></source></nowiki></code>

<source lang="invalid"></source>

'''NOTE:''' the old SwinBrain CodeSyntaxHighlight does not work anymore since the wiki upgrade on 2008-02-14
<pre>
<code>[language]
...
</code>
</pre>
produces rubbish now!

=== Templates ===

See [[Documentation/Dashboard/Wiki Editing Policy]] and [[Special:Mostlinkedtemplates]] and [[:Category:Wiki_Templates_Expressing_Quality]] and [[:Category:Formatting_templates]].

<code><nowiki>{{Documentation/Caution| Do or don't.}}</nowiki></code>
{{Documentation/Caution| Do or don't.}}

<code><nowiki>{{Documentation/Note| Note that.}}</nowiki></code>
{{Documentation/Note| Note that.}}

<code><nowiki>{{Template:Documentation/Tip| Tip.}}</nowiki></code>
{{Template:Documentation/Tip| Tip.}}

<code><nowiki>{{Documentation/Outdated}}</nowiki></code>
{{Documentation/Outdated}}

{{LinkBanner}}

=== new topic ===
<nowiki>Insert non-formatted text here</nowiki>

Oracle Contributor Agreement

2010-07-06T16:25:35Z

ErAck: fax is dead

Submit a signed and filled-out copy of the [http://www.openoffice.org/licenses/sca.pdf Sun Microsystems Inc. Contributor Agreement (SCA)]. It is a pdf and you must print it out and scan a signed original and email to Copyrightfax@sun.com

We explain our reasons for requiring the SCA in the [http://www.openoffice.org/FAQs/faq-licensing.html#usinglicenses Licensing FAQ]. The FAQ further explain the use and advantages of our copyright policy.

OpenOffice.org maintains a [http://www.openoffice.org/copyright/copyrightapproved.html list of persons and companies] who have filed a copyright assignment. If you have filed an Agreement or prior form and your name is not on the list, please [mailto:webmasters@openoffice.org contact us]; additionally you may also add an entry to the [[Pending SCAs]] section to track the enquiry.

----
'''See also:''' [http://contributing.openoffice.org/programming.html#sca Contributing: How to submit code to OpenOffice.org]

[[Category:Policy]]

Calc/hacks/number of rows

2010-07-06T14:41:38Z

ErAck: Available as of m84

{{Documentation/Note| As of DEV300_m84 the number of rows was increased to 1048576 (1M).}}

Regard this article as historical, though the content is still applicable to columns or in case you want to increase the number of rows to 2097152 (2M ;-)

Now and then people ask whether increasing the row limit above 64k lines or the column limit above 256 columns for OpenOffice.org version 2.4 or [http://www.oooninja.com/2008/03/openofficeorg-30-new-features.html 1024 columns for 3.0] would be possible.

Well, it depends on your goal. For personal use, you may set <code>MAXROWCOUNT_DEFINE</code> in <tt>sc/inc/address.hxx</tt> to
a different value, multiple of 128, then recompile the application respectively the <tt>libsc680*.so</tt> and shove it under your existing installation. However, doing so implies that you don't save to any binary file format like Excel or whatsoever, otherwise you risk loss of data. You'll also encounter drawing layer misfits in higher row numbers, may experience performance problems, and there maybe other quirks. It generally works for data and formulas, but otherwise is completely untested.

For the number of columns, the same applies to the <code>MAXCOLCOUNT_DEFINE</code> in <tt>sc/inc/address.hxx</tt>, except that the value must be a multiple of 16 instead.

A successful proof of concept was done by Laurent Godard, using 2,000,000 rows and 32,000 columns, resulting in the lower right corner cell address '''AUHT2000000''' ... see http://blogs.nuxeo.com/dev/2006/08/the-spreadsheet-next.html

Please note again that this is a ''hack''. Although it may serve you for some data crunching, exchanging documents with other releases or applications will not work.

However, we should implement this expansion properly, also to be able to handle larger spreadsheet documents created with other applications. There are RFEs for this, http://qa.openoffice.org/issues/show_bug.cgi?id=30215 for number of rows and http://qa.openoffice.org/issues/show_bug.cgi?id=86049 for number of columns.

[[Category:Calc|Hack]]
[[Category:Hack]]

Calc/Drafts/Issue 33851

2010-07-06T14:22:09Z

ErAck: Category:Done

Before 2008-03 this used to be a '''specification draft''' for [http://www.openoffice.org/issues/show_bug.cgi?id=33851 issue 33851], which is about how filtered rows should be treated during cut/copy/paste/fill cells operations, and due to its length and controversial discussion is unlikely to be read and understood, so presenting the outcome in a wiki page and editing that instead is much more appropriate. Please bear in mind that this page is geared towards developing a '''specification''' (see also [[:Category:Specification]]), don't discuss here, use the Talk page ('''discussion''' link above) instead, or even better chime in to [http://ux.openoffice.org/servlets/BrowseList?list=discuss&by=thread&from=1971545 the thread on the discuss@ux mailing list]. Thanks.

With fixing the most critical issues of not overwriting data in {{CWS|filteredrows}} as discussed in the UX thread mentioned, behavior changed. For details please see the [http://sc.openoffice.org/servlets/ReadMsg?list=features&msgNo=265 announcement mail]. Sections in this page are marked with '''CWS filteredrows''' to line out the changes.

Due to time restrictions there is no implementation for cases where a fill operation starts on a single cell with no selection crossing filtered rows. These need still to be implemented and we have {{bug|89232}} for this.

== General overview ==

There's consensus that operations modifying the document's content should not modify content of rows that are not displayed due to an applied filter setting. Some simply argue ''do it like Excel'', however, that's not what Excel does, see single topics below.

== Copy cells ==

This sounds easy: just copy the cells that are visible (not filtered out).

Note that the current Calc implementation does not allow a multi-selection to be copied to the clipboard. It reached consensus that the current Calc behavior, to treat the visible rows as one area, is sufficient.

* For what to do during paste if the cells contain formulas with relative references see below under [[#Paste cells]].

'''CWS filteredrows:''' As an implementation detail always the entire selection is copied to the internal clipboard, differentiation is done during paste or when creating the transfer object for other applications.

== Cut cells ==

Sounds the same as ''copy cells'', just cut the cells that are visible. Though the paste case may be easier, probably the references should be adjusted the same way as usual in a cut/paste scenario.

* '''NOTE:''' Excel 2003 in this case cuts '''all''' cells, including filtered. ''Do it like Excel'' probably does not apply here.

Note that current Calc implementation does not allow a multi-selection to be copied to the clipboard.

* For what to do during paste if the cells contain formulas with relative references see below under [[#Paste cells]].

:Please note, that '''cut''' could break formulas inside the '''hidden cells''', so cutting only the visible portion is quite dangerous. I have added additional comments on this issue in the section on [[#Paste_cut_cells|''Paste Cut Cells'']] (also note, that this comment applies only to ''Cut'', '''NOT''' to ''Copy'') - [[User:Discoleo|Discoleo]] 20:16, 16 January 2007 (CET)

'''CWS filteredrows:''' Cut is disabled if the selection crosses filtered rows.

== Paste cells ==

Do not touch rows that are filtered-out.

* How to handle the case when the area in clipboard is larger than a selected area to be pasted to?
** Excel 2003 ignores the selection.
** '''CWS filteredrows:''' Asks for confirmation before using the enlarged area.
* How to handle the case when the selected area is larger than the area in clipboard?
** Excel 2003 ignores the selection except if a multiple of the columns of the clipboard content is selected.
*** I think we should ignore the selection, EXCEPT if pasting single cell, in which case we should respect the selection. --[[User:Kpalagin|Kpalagin]] 17:59, 14 January 2007 (CET)
** '''CWS filteredrows:''' Same as in an unfiltered selection the clipboard content is repeated until the selection is filled.

* '''NOTE:''' Excel 2003 pastes also to filtered rows. ''Do it like Excel'' probably does not apply here.
** Agreed here.--[[User:Kpalagin|Kpalagin]] 17:59, 14 January 2007 (CET)
** '''CWS filteredrows:''' Does not paste to filtered rows. The clipboard content is distributed over the visible rows.

=== Paste copied cells ===

It reached consensus that the current Calc behavior, to treat the visible rows as one area and thus paste as one area, is sufficient.

==== Paste copied cells with formulas ====

* '''NOTE:''' Excel 2003 does not paste the formulas if the cells were copied from a filtered range, only the values are pasted. ''Do it like Excel'' probably does not apply here.
** I think we should ''Do it like Excel''. We can have 3 cases:
**# Identical formulas in selected cells, in which case it is sufficient to copy just one cell.
**# Formulas are different, in which case trying to guess user's intention is fruitless.
**# Single cell is copied. This should be allowed regardless of filtering. --[[User:Kpalagin|Kpalagin]] 17:59, 14 January 2007 (CET)
** '''CWS filteredrows:''' Pastes the formulas as usual. Pasting values only can always be achieved by using Paste Special.

===== Paste copied cells with formulas containing cell references =====
Adjust formulas, as usual in copy/paste.

'''CWS filteredrows:''' References are adapted for each slice of visible rows as if it was pasted individually.

===== Paste copied formula cells to filtered rows =====
Do not touch hidden cells. --[[User:Kpalagin|Kpalagin]] 17:59, 14 January 2007 (CET)

'''CWS filteredrows:''' Filtered rows are not touched.

===== Paste copied formula cells to visible cells=====
Adjust references.--[[User:Kpalagin|Kpalagin]] 17:59, 14 January 2007 (CET)

* '''CWS filteredrows:''' References are adapted for each slice of visible rows as if it was pasted individually.

=== Paste cut cells ===

Because the '''Cut''' could/would break formulas in ''hidden cells''
* => cutting both '''hidden and non-hidden''' seems an option
* => alternative: provide user with the option to select between the 2 possibilities
Let's ask user.

NOTE:
* this is a problem specific for '''CUT'''
* it does NOT apply for '''Copy'''
** '''Copy''' does NOT break hidden cells
** therefore this comment applies soley to '''Cut'''

-- [[User:Discoleo|Discoleo]] 01:09, 12 January 2007 (CET)

NOTE: this section is about ''pasting'' cells that were cut, the comment belongs to [[#Cut cells]] instead.

'''CWS filteredrows:''' In general the handling is identical to pasting copied cells, with the exception that references are adapted as usual in cut/paste of course instead of copy/paste.

==== Paste cut cells with formulas ====

===== Paste cut cells with formulas containing cell references =====

Adjust references as usual in a cut/paste scenario.

'''CWS filteredrows:''' Does it.

===== Paste cut formula cells to filtered rows =====
Do not touch hidden cells. --[[User:Kpalagin|Kpalagin]] 17:59, 14 January 2007 (CET)

'''CWS filteredrows:''' Filtered rows are not touched.

===== Paste cut formula cells to visible cells=====
Adjust formulas, as usual in cut/paste.

'''CWS filteredrows:''' Does it.

== Fill cells ==

Fill only non-filtered (visible) rows.

'''CWS filteredrows:''' If a selection crosses filtered rows, Fill operations are disabled. Starting from a single row and dragging the corner currently does not take filtered rows into account. This needs to be implemented later.

=== Fill cells with formulas containing cell references ===

* How to adapt relative cell references?
** Treat as if the visible area was a contiguous area? Probably the best.
*** The same as if one single cell was copied to the clipboard and then pasted to several locations, leaving out the hidden rows. Most logical. And is also what Excel 2003 does.

== Fill series ==

# Fill continuously in the non-filtered (visible) rows?
# Or fill with gaps, leaving out the values that would go into the filtered rows?
# Or do nothing?
#* Excel 2003 disables Fill Series on filtered ranges.
#* Probably the best, fill series on a filtered range doesn't make much sense anyway.

'''CWS filteredrows:''' If a selection crosses filtered rows, Fill operations are disabled. Starting from a single row and dragging the corner currently does not take filtered rows into account. This needs to be implemented later.

=== Scenario 1 ===
If you want to get some serial numbering for visible data after filtering, ''Fill Series'' would be a good function to do that, if rows what have been filtered out will be ignored.
* Current behaviour: ''Fill Series'' will also fill invisible rows
* Desired behaviour: ''Fill Series'' should be available, but only touch visible cells.

[[Category:Calc|Drafts/Issue 33851]]
[[Category:Draft]]
[[Category:Done]]

Engineering and SI Number Format in Calc

2010-07-06T13:01:30Z

ErAck: added file formats placeholders

{{User Experience Community}}=Explanation of Notations=
The following is a short description of all the number formats to be discussed here.
==Engineering Notation==
This type of notation is an offshoot of Scientific Notation. The difference is that the exponent is only shown in multiples of 3. Thus a number such as 153,100 becomes 153.1E+3 in Engineering notation[[http://en.wikipedia.org/wiki/Engineering_notation]] instead of 1.531E+5 in scientific.
==SI Notation==
This is what's known as SI Prefix[[http://en.wikipedia.org/wiki/SI_prefix]] notation. Similar to Engineering Notation the exponent also runs in multiples of 3 (usually), but the difference is that instead of showing the E+/- notation a symbol is given for each exponent. E.g. 153,100 in SI notation would be 153.1k.
==Binary Prefix Notation==
This is very similar to SI, but is intended for use when referring to sizes of data storage. Binary Prefix[[http://en.wikipedia.org/wiki/Binary_prefix]] Notation works in much a similar way, but is not calculated using 10 as a multiple (as with Scientific). Rather the closest matching power of 2 is used. Thus instead of 1000 we get 1024. As a convention similar symbols to SI is used, but with an "i" suffix to distinguish then. E.g. 153,100 in Binary Prefix Notation would become 149.51Ki.
=Examples from other software=
Example of how other software handle these formats.
==Engineering Notation in Microsoft Excel 2003==
[[File:Excel2003_custom_notation.png]]
=Format Strings=
Each number format requires a format string to indicate not just what type of format to use, but also details as per how many decimals to display. In all numeric notations the format string could indicate how many digits to display for the fraction portion of the number. E.g. 0.00+E0 would force a 2 decimal fraction if needed or not.
==Engineering Notation==
The Excel format string for engineering notation is similar to the scientific notation, except that it starts with 3 hashes (#). See the sample above. The current scientific notation in both Excel and OOo Calc is the same except for this point. Both use E+ to indicate exponent notation. The digit(s) after this indicate how many digits to use for the exponent. E.g. 0.0+E000 would force 3 digits for the exponent, if not needed it becomes padded with zeros. A further use of the Excel format string is that not only normal engineering notation is possible, but also notation in other multiples. E.g. ####E+0 would format 153,100 as 15.310E+4.

An alternative mentioned would be to substitute F for E instead. In this case ###.000E+00 would be equivalent to 0.000F+0.
==SI Notation==
There is (yet) no sample format string for this. Therefore we need to decide on one. A proposed idea would be to use a S to force SI notation. E.g. 0.00S. There's has one problem as the s is also used to denote seconds when formatting numbers as time units. So a different character should be used. Thus not one of the following already used: A, D, E, H, I, M, P, S, Y. A suggestion would be T stemming from the 1st non-used letter in the word meTric.
==Binary Prefix Notation==
Simple really, use B as for SI. It's not used in any other normal format.

= File Format =
'''TODO:''' how to persistently store the feature in various file formats.
== ODF ==
== OOXML ==
== .xls and .doc binary formats ==

[[Category:Calc]]
[[Category:To-Do]]
[[Category:Feature]]
[[Category:Draft]]