date:20110420

Hi Júlio,

On Tue, 19 Apr 2011 20:49:57 -0300
Júlio Hoffimann
julio.hoffim...@gmail.com wrote:

 The gradual migration is the only way i see to change thousand of
 names. Even with regular expressions, the task is not easy to do.

There are feature branches. Absolutely no need to do this on master.

 Again, painful today, amazing tomorrow.

With today being the next five years. Five years that are absolutely
critical for the project.
With amazing being absolutely not the word I would use to describe
the result (see Christians reply too).
If this would be about renaming classes with misleading names to
something that that really describes its job or something like using
the same consistent internal variable naming scheme _that_ is helping in
the long run, ok.
Unlike that, changing one proper name com::sun::star:: to another
libreoffice:: is only providing minor benefits, but also has major
drawbacks.

 The truth: we have fear to make big changes and this is not a good
 paradigm, it turns LibreOffice just another fork and it's more than
 that.

Please dont tell me that I am afraid of changes. If you would know how
much I fought inside OOo for change, you would realize how ridiculous
that is.

Best,

Bjoern


-- 
https://launchpad.net/~bjoern-michaelsen


signature.asc
Description: PGP signature
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] OSL_ASSERT - remove backtrace or make abort

2011-04-20 Thread Tor Lillqvist

I fully agree. We need to make it clear what assertions really mean, and how 
they should be used. Currently it is somewhat of a disaster area. There are 
places in the code that cause assertion failures every time the code is run 
if built with debug=t. So does that then mean that the code is actually 
horribly broken and works by accident? Probably not in all cases.

In my opinion, an assertion failure should mean that the program finds itself 
in a situation where it doesn't know what has happened or how to proceed; where 
it knows that its data structures are in an inconsistent state, and it will 
probably crash soon.

The current situation seems to be that assertions are used to indicate that 
something might be slightly suboptimal, but then the code is fully prepared to 
handle that anyway. More like it would be nagging hey, somebody thought in 
2005 that this should be fixed some day later.

Another related thing that is broken is how the code often loses useful 
information associated with exceptions.

To take an example, the root cause to much breakage on Windows in the 3.4 beta1 
caused an exception with the nice message package2.dll: cannot get symbol: 
component_getImplementationEnvironment attached. That message says very 
clearly what the problem is. And the message indicates indeed a very serious 
problem with the UNO component shared library in question. But did this message 
show up anywhere (except that I by luck happened to see it in the debugger, as 
there was something to see, as the catch clause in this case actually caught 
the exception object)? Not anywhere where the user would have been able to 
report it at least.

--tml


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] GSoC, help conversion

2011-04-20 Thread Cedric Bosdonnat

Hallo Timo,

On Wed, 2011-04-20 at 01:57 +0200, Timo wrote:
 do you have questions or comments about my project proposal*? This week
 I am available until Thursday evening (UTC).

Let the comments happen in the proposal's comments.

Regards,

-- 
Cédric Bosdonnat
LibreOffice hacker
http://documentfoundation.org
OOo Eclipse Integration developer
http://cedric.bosdonnat.free.fr

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] no libreoffice-build-3.3.99.1 ?

2011-04-20 Thread Andreas Radke

Am Wed, 20 Apr 2011 06:10:25 +
schrieb Baptiste Daroussin b...@freebsd.org:

 Hi,
 
 I wanted to prepare the freebsd port for libreoffice 3.4 beta1, but I
 can find the distfile for libreoffice-build-3.3.99.1 on the
 mirrors, it is missing or I missed something and it is not needed
 anymore?
 
 regards,
 Bapt
 ___
 LibreOffice mailing list
 LibreOffice@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/libreoffice
 

from then 3.4beta1 announce mail:

The build repo is not tagged. We would like to get rid of it.


You will have to use the bootstrap way to do your 3.4 builds. The
patches dir has gone. Ask in #libreoffice-dev when you run into
problems. (make DESTDIR=... install is broken for me).

-Andy
ArchLinux package maintainer
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Promoting LibO to Vietnamese students by completing easy hacks

2011-04-20 Thread Cedric Bosdonnat

Hi Vu Hung,

On Wed, 2011-04-20 at 00:26 +0700, Nguyen Vu Hung (KiEi) wrote:
 As for the regulation of MHST, 
 I propose that I will firstly register LibO team as a mentor; and I
 will take care
 of the Vietnam side.

Could you enlighten us about some points about MHST? Is it working
exactly like GSoc (1 student, 1 project, one potential winner) or is it
more like a team project with one project? This would help us see what
kind of project(s) is needed for the students.

 Some important deadlines:
 
 2011/04/30: Deadline for mentor's (and his/her ideas) registration. 

Ok, sounds like we need to hurry up a bit then ;)

 2011/05/01 - 2011/05/29: (team of) students' proposal registration 
 2011/05/30 - 2011/06/05: Announce the list of selected teams and
 students
 2011/06/06 - 2011/09/04: Coding :)
 
 MHST 2011 Information
 http://www.olp.vn/mhst/thong-tin
 
 Prizes 
 http://www.olp.vn/mhst/giai-thuong
 
 Registration
 http://www.olp.vn/mhst/dang-ky
 
 List of MHST ideas 
 http://www.olp.vn/mhst/danh-sach-y-tuong
 
 Guidelines
 http://www.olp.vn/mhst/huong-dan

Google translate will be our friend here ;)

 The developers are the mentors and I step back as the one who fill the
 gaps between
 the developers and the students.

Cool! Are there some vietnamese developers that could help mentoring and
start gaining experience on the LO dev?

  Sure, but don't go too quickly with the tasks from the GSoc as the
  students aren't selected yet. 
 I didn't know that :) Anyway, the deadline for picking an idea is
 2011/04/30

What we can do: you copy the whole lot of ideas now and you remove the
ones selected for GSoc when Google has announced the selected students.
This way Vietnamese students can start working on their proposals.

We can keep some private communication about the topic you know
vietnamese students are about to pick: I could tell you if you would
need to redirect the student on another task.

  It's better to tell the students to be
  careful that some of  those projects may already have been picked. WRT
  the EasyHacks, tasks are sorted by difficulty and students should pick
  tasks in section 6 - Programming tasks.
 I see. Probably you have to fill some more programming tasks.
 
 My concern is, can we allocate the right developer as the mentor for a
 programming task?

The GSoc ideas page is pretty OK on that point, but not the easy hack
page. I'ld prefer keeping things on the GSoc ideas page.

Regards,

-- 
Cédric Bosdonnat
LibreOffice hacker
http://documentfoundation.org
OOo Eclipse Integration developer
http://cedric.bosdonnat.free.fr

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] Robert Nagy: Problems with your python library patch

2011-04-20 Thread Andreas Becker

Robert,
my patch:
http://cgit.freedesktop.org/libreoffice/bootstrap/commit/?h=libreoffice-3-4id=6c3539d8e1dbad13264b862e1344e3c3a8690dec
your patch:
http://cgit.freedesktop.org/libreoffice/bootstrap/commit/?id=2b03888a918b7020a1f9330686dc531222057573

 as far as i saw the reason to use an absolute path for linking instead of
 using -lpythonX.XX is that at least debian does not ship a shared object
 within
 the basic python3 package so you have to install the -dev package

Really not.
The reason is, that the old version does not always work:
For me, print(distutils.sysconfig.get_config_var('VERSION')); prints 3.2,
but the library
is libpython3.2mu.so.
The absolute path in my patch is always the right one and I do not know any
disadvantages
of an absolute path.


 (that's kinda weird^H^H^H^H^Hf***ed up).

...

--Andreas Becker
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [PATCH] [PUSHED] remove String with OUString

2011-04-20 Thread Noel Power


On 19/04/11 22:09, Caolán McNamara wrote:

You*did*  run the smoketest didn't you. I'm sure you did.
you *are* joking right? such confidence in me doing the right thing is 
completely misplaced, I am ashamed  I didn't run it :-( I did some 
touch testing with basic but I have to admit running the smoketest just 
didn't even occur to me. Ok, tried it now, and it works :-) ( phew )


Noel
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [PATCH] [PUSHED] remove String with OUString

On Wed, 20 Apr 2011 09:22:46 +0100
Noel Power nopo...@novell.com wrote:

 On 19/04/11 22:09, Caolán McNamara wrote:
  You*did*  run the smoketest didn't you. I'm sure you did.
 you *are* joking right? such confidence in me doing the right thing
 is completely misplaced, I am ashamed  I didn't run it :-(

I cant help a bit of sarcastic grinning while watching this exchange
from the sidelines. ;)

Best Regards,

Bjoern

-- 
https://launchpad.net/~bjoern-michaelsen


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Robert Nagy: Problems with your python library patch

On (2011-04-20 09:52), Andreas Becker wrote:
 Robert,
 my patch:
 http://cgit.freedesktop.org/libreoffice/bootstrap/commit/?h=libreoffice-3-4id=6c3539d8e1dbad13264b862e1344e3c3a8690dec
 your patch:
 http://cgit.freedesktop.org/libreoffice/bootstrap/commit/?id=2b03888a918b7020a1f9330686dc531222057573
 
  as far as i saw the reason to use an absolute path for linking instead of
  using -lpythonX.XX is that at least debian does not ship a shared object
  within
  the basic python3 package so you have to install the -dev package
 
 Really not.
 The reason is, that the old version does not always work:
 For me, print(distutils.sysconfig.get_config_var('VERSION')); prints 3.2,
 but the library
 is libpython3.2mu.so.
 The absolute path in my patch is always the right one and I do not know any
 disadvantages
 of an absolute path.

On some systems that will link to a *static* library. You changed something 
which
was not properly tested, so it got backed out, and i do not want to see someone 
linking
a .so with an absolute path.
If you want to make python3 work correctly then you have to find a way that 
will not
break anything.
If it's needed you will have to add platform specific code, like
http://svn.apache.org/repos/asf/subversion/trunk/build/get-py-info.py does.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Robert Nagy: Problems with your python library patch

Hi Andreas,

On Wed, 2011-04-20 at 09:52 +0200, Andreas Becker wrote:
 Really not. 
 The reason is, that the old version does not always work:
 For me, print(distutils.sysconfig.get_config_var('VERSION')); prints
 3.2, but the library is libpython3.2mu.so.
..
 The absolute path in my patch is always the right one and I do not
 know any disadvantages of an absolute path.

Clearly, random different linux's can put python in random different
places [ oh, the joys of anarchy ]. No idea how well an absolute path
works with LD_LIBRARY_PATH either.

So - in general, surely it is better not to hard-code the paths of the
libraries if at all possible.

Can we get more detail on cases where it doesn't work ?

ATB,

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] Git Artwork guide

Hi designers, Hi developers,

following the discussion on:

 https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/756895

I created a short tutorial for designers on how to get setup to
contribute artwork directly to the project at without a complete build:

 http://wiki.documentfoundation.org/Design/GitArtworkGuide

@Designers: Feel free to move it, beautify it and most of all: link to
it.
@Developers: Feel free to improve the guide, if I missed out some pits
that should be informed about.

Best Regards,

Bjoern

-- 
https://launchpad.net/~bjoern-michaelsen


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] no libreoffice-build-3.3.99.1 ?

2011-04-20 Thread Hanno Meyer-Thurow

On Wed, 20 Apr 2011 09:42:31 +0200
Andreas Radke a.ra...@arcor.de wrote:

 ... (make DESTDIR=... install is broken for me).

Hi all,
I would recommend my patch attached. For that one would need
to pass '--libdir=/usr/LIBDIR' to configure to behave. Otherwise it
installs to /LIBDIR. Improvements to the patch are welcomed!
Though, this way I came close to the old behaviour.

@Petr
Would you mind to commit if it is ok, please?


Regards,
Hanno--- Makefile.in.orig	2011-02-25 23:01:35.128013555 +0100
+++ Makefile.in	2011-02-25 23:04:53.404013587 +0100
@@ -16,11 +16,11 @@
 
 install:
 	@. ./*[Ee]nv.[Ss]et.sh  \
-	echo Installing in $${prefix:-@prefix@}...  \
-	ooinstall $${prefix:-@prefix@}  \
+	echo Installing in $${libdir:-@libdir@}/libreoffice...  \
+	ooinstall $${libdir:-@libdir@}/libreoffice  \
 	echo   \
 	echo Installation finished, you can now execute:  \
-	echo $${prefix:-@prefix@}/program/soffice
+	echo $${libdir:-@libdir@}/libreoffice/program/soffice
 
 dev-install:
 	@. ./*[Ee]nv.[Ss]et.sh  \
--- solenv/bin/ooinstall.orig	2011-02-25 23:09:13.484013610 +0100
+++ solenv/bin/ooinstall	2011-02-25 23:09:43.856013608 +0100
@@ -67,9 +67,9 @@
 $langs = join (,, @larr);
 
 $destdir='';
-if ( defined $ENV{OODESTDIR} 
- $ENV{OODESTDIR} ne  ) {
-$destdir = -destdir \$ENV{OODESTDIR}\;
+if ( defined $ENV{DESTDIR} 
+ $ENV{DESTDIR} ne  ) {
+$destdir = -destdir \$ENV{DESTDIR}\;
 }
 
 $strip='';
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] [PATCH] An updated Autolayout patch

2011-04-20 Thread cocofan

  This is another updated set of Autolayout patches.  I think I managed
to get the custom layout to work but sometimes there is a segmentation
fault connected with using a literal string (will investigate later).
The reading and writing to the xml file doesn't work right so it has
been disabled for now.  
   Over the weekend, I will look into these issues.

 Dona Hertel - coco...@mailbolt.com



Autolayout_patches_Apr20.tar.gz
Description: application/compressed-tar
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Promoting LibO to Vietnamese students by completing easy hacks


On Tue, 2011-04-19 at 07:42 +0700, Nguyen Vu Hung (KiEi) wrote:
 The reason we have our own version of Gsoc in Vietnam is that
 students' English skill is not so good.

Ho hum :-) I'd feel a lot better if you guys worked with Google to
translate task specifications to Vietnamese and stuck with their
process. There are problems with being seen as undermining GSOC.

 As to promote LibO *development* in Vietnam, I would like to ask 
 developers at LibO become a technical co-mentors, and myself will 
 be a co-mentor who bridges the gaps between you and the student(s).

This would be a great way to work with GSOC. Anyhow - of course, we are
always eager to get people funded to work on LibreOffice in whatever way
is possible.

ATB,

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Robert Nagy: Problems with your python library patch

On (2011-04-20 10:14), Michael Meeks wrote:
 Hi Andreas,
 
 On Wed, 2011-04-20 at 09:52 +0200, Andreas Becker wrote:
  Really not. 
  The reason is, that the old version does not always work:
  For me, print(distutils.sysconfig.get_config_var('VERSION')); prints
  3.2, but the library is libpython3.2mu.so.
 ..
  The absolute path in my patch is always the right one and I do not
  know any disadvantages of an absolute path.
 
   Clearly, random different linux's can put python in random different
 places [ oh, the joys of anarchy ]. No idea how well an absolute path
 works with LD_LIBRARY_PATH either.
 
   So - in general, surely it is better not to hard-code the paths of the
 libraries if at all possible.
 
   Can we get more detail on cases where it doesn't work ?
 
   ATB,
 
   Michael.
 
 -- 
  michael.me...@novell.com  , Pseudo Engineer, itinerant idiot
 
 

Andreas,

This should make python3 work too. What it basically does
is that it gets the correct library name from the python binary
itself and uses that to link.

diff --git a/configure.in b/configure.in
index 470aa39..430a7da 100755
--- a/configure.in
+++ b/configure.in
@@ -1344,6 +1344,11 @@ if test -z $GNUTAR; then
 fi
 AC_SUBST(GNUTAR)
 
+AC_PATH_PROG(OBJDUMP, objdump)
+if test -z $OBJDUMP; then
+AC_MSG_ERROR([objdump not found but needed. Install it.])
+fi
+
 dnl ===
 dnl Checks for --with-local-solenv invocation
 dnl TODO: Is this still required?
@@ -4108,11 +4113,11 @@ elif test -n $with_system_python -o -n 
$with_system_libs  \
AM_PATH_PYTHON([2.2])
 
python_include=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('INCLUDEPY'));`
-   python_version=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('VERSION'));`
+   python_lib=`$OBJDUMP -p $PYTHON | ${SED} -n 
's/.*\libpython\(.*\).so.*/python\1/p'`
python_libs=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('LIBS'));`
python_libdir=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('LIBDIR'));`
PYTHON_CFLAGS=-I$python_include
-   PYTHON_LIBS=-L$python_libdir -lpython$python_version $python_libs
+   PYTHON_LIBS=-L$python_libdir -l$python_lib $python_libs
 fi
 if test $with_system_python = yes ; then
SYSTEM_PYTHON=YES

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] LibreOffice Tinderbox?

2011-04-20 Thread Christian Lohmaier

On Wed, Apr 20, 2011 at 7:09 AM, Samphan Raruenrom samp...@osdev.co.th wrote:
 Firefox - Tinderboxpushlog : http://tbpl.mozilla.org/

Doing it this was is near impossible, as the repository is split into
multiple ones.

 Building LibreOffice from master or 3.4 branch is hard for beginners because
 we don't know which point in time that the branch are buildable on one's
 platform.

http://tinderbox.libreoffice.org/libreoffice-3-4/status.html (note
that the build did break because of errors in the translation files)

http://tinderbox.libreoffice.org/MASTER/status.html (bah, all red or old)

 So I'm wondering whether it is possible to setup Tinderbox for LibreOffice
 project?  So that more developers can work on the source.

There is already, see above. Unfortunately there is no integration
with the git commits yet, (because the repository is split on the one
hand, and on the other because nobody did catch on the easytask of
hooking up git 
http://wiki.documentfoundation.org/Development/Easy_Hacks#Add_git_history.2Flog_parser_for_tinderbox
)

So for now, basically the only way is to use the dates as revision,
see also this thread from two weeks ago:
http://lists.freedesktop.org/archives/libreoffice/2011-April/010286.html

ciao
Christian
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] [Bug 35673] LibreOffice 3.4 most annoying bugs

2011-04-20 Thread bugzilla-daemon

https://bugs.freedesktop.org/show_bug.cgi?id=35673

Petr Mladek pmla...@suse.cz changed:

   What|Removed |Added

 Depends on||36404

--- Comment #29 from Petr Mladek pmla...@suse.cz 2011-04-20 03:19:11 PDT ---
Really add bug 36404.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] [Bug 35673] LibreOffice 3.4 most annoying bugs

2011-04-20 Thread bugzilla-daemon

https://bugs.freedesktop.org/show_bug.cgi?id=35673

Bug 35673 depends on bug 36285, which changed state.

Bug 36285 Summary: LibO 3.4 beta1 – No available language modules, spell check 
is impossible
https://bugs.freedesktop.org/show_bug.cgi?id=36285

   What|Old Value   |New Value

 Resolution||WORKSFORME
 Status|NEW |RESOLVED

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] Summary: LibreOffice TSC call - Thur Apr 14th - 16:00 UTC

Hi all,

sorry for the late post, here a short summary of the last TSC call:

attendants: Kohei, Petr, Kendy, Norbert, David, Fridrich, Cedric, Bjoern

3.4 status (Petr):
- beta-1 upload should give us a better picture where we are by user
  feedback
- beta-2 and further steps should depend on that feedback
- fdo#33915 is nasty and should be fixed, but we need a
  reproducable scenario (user feedback from beta-1 might help here)

DEV300 imports (Kendy):
- we will do a very rough trial merge in a feature branch (- Kendy)
- we (all) will have a look at that (as a diff to the base) to see:
- if we can merge that in bulk
- or selectively
- decision might differ on a module by module basis

EasyHacks (Bjoern):
- bugzilla reports still missing on the wiki (- Bjoern/floeff)
- we can already make a draft selecting 10-20 tasks now (- Bjoern)

GSoC (Fridrich/Cedric):
- seven good applications, some still missing EasyHacks
- if you mentor a student without an EasyHack, nag him about it

GNU make (Fridrich/Bjoern):
- on GNU make 3.81 the current var2file implementation triggers
http://savannah.gnu.org/bugs/?20033
- GNU make 3.82 rumored to introduce new problems, esp. on cygwin,
  needs investigation
- using a patched version on release builders deemed acceptable
  (or rather: unavoidable) for now

Unittests:
- sc ucalc unittest is active again on master and 3.4
- the rdb setup stuff is still to cumbersome (- Bjoern)
- the objectlists stuff breaks on OSX -- naming issue? (- Bjoern)
- sw unittest should be activated soon too (- Bjoern)

split repos vs. one huge repo (Bjoern):
- push/pull operations should be a lot faster on one repo
- git blame has no significant performance difference
  (same assumed for git log)
- stuff that walks the tree might be impacted:
  git status/git commit -A/gitk (- Bjoern)
- we would loose the possibility to host a small private repo on
  github, shallow clones considered as an alternative, but might be
  too fragile
- decision will also need some serious testing on windows

TSC call timeslot:
- Next call will be 15:00 UTC for real (sorry guys)

Best,

Bjoern

-- 
https://launchpad.net/~bjoern-michaelsen


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Robert Nagy: Problems with your python library patch

Better diff (note that this still requires a shared library and will not work 
static ones):

diff --git a/configure.in b/configure.in
index 470aa39..0d06542 100755
--- a/configure.in
+++ b/configure.in
@@ -4108,11 +4108,11 @@ elif test -n $with_system_python -o -n 
$with_system_libs  \
AM_PATH_PYTHON([2.2])
 
python_include=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('INCLUDEPY'));`
-   python_version=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('VERSION'));`
+   python_lib=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('LDLIBRARY')); | $SED -rn 
's/lib(.*)\..*
python_libs=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('LIBS'));`
python_libdir=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('LIBDIR'));`
PYTHON_CFLAGS=-I$python_include
-   PYTHON_LIBS=-L$python_libdir -lpython$python_version $python_libs
+   PYTHON_LIBS=-L$python_libdir $python_lib $python_libs
 fi
 if test $with_system_python = yes ; then
SYSTEM_PYTHON=YES
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] make install broken?

2011-04-20 Thread Andreas Radke

Am Wed, 20 Apr 2011 11:25:39 +0200
schrieb Hanno Meyer-Thurow h@web.de:

 On Wed, 20 Apr 2011 09:42:31 +0200
 Andreas Radke a.ra...@arcor.de wrote:
 
  ... (make DESTDIR=... install is broken for me).
 
 Hi all,
 I would recommend my patch attached. For that one would need
 to pass '--libdir=/usr/LIBDIR' to configure to behave. Otherwise it
 installs to /LIBDIR. Improvements to the patch are welcomed!
 Though, this way I came close to the old behaviour.
 
 @Petr
 Would you mind to commit if it is ok, please?
 
 
 Regards,
 Hanno

Reverting a change can only be a temporary solution. But it doesn't
work for me. With --libdir=/usr/LIBDIR it fails for me:

make DESTDIR=${pkgdir} install

== Entering fakeroot environment...
== Starting package_libreoffice()...
Installing in /usr/LIBDIR/libreoffice...
mkdir /usr/LIBDIR: Permission denied at /build/src/build/solenv/bin/ooinstall 
line 32
make: *** [install] Error 255

I can install it using make OODESTDIR=$pkgdir install without
the permission error I get with the revert patch. But the files don't go
to the desired directories. Who has changed it for 3.4? 
What was the intention and how should we use it?

-Andy
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Robert Nagy: Problems with your python library patch


After discussing this with Michael it seems the best solution
would be to use python-config, it even makes configure.in smaller ;)
Please test it with python3 too.

diff --git a/configure.in b/configure.in
index 470aa39..4dd7a4e 100755
--- a/configure.in
+++ b/configure.in
@@ -4107,12 +4107,9 @@ elif test -n $with_system_python -o -n 
$with_system_libs  \
AC_MSG_RESULT([external])
AM_PATH_PYTHON([2.2])
 
-   python_include=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('INCLUDEPY'));`
-   python_version=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('VERSION'));`
-   python_libs=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('LIBS'));`
-   python_libdir=`$PYTHON -c import distutils.sysconfig; 
print(distutils.sysconfig.get_config_var('LIBDIR'));`
-   PYTHON_CFLAGS=-I$python_include
-   PYTHON_LIBS=-L$python_libdir -lpython$python_version $python_libs
+   python_config=$PYTHON-config
+   PYTHON_CFLAGS=`$python_config --includes`
+   PYTHON_LIBS=`$python_config --ldflags`
 fi
 if test $with_system_python = yes ; then
SYSTEM_PYTHON=YES

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] LibreOffice Tinderbox?

Hi Samphan,

On Wed, 2011-04-20 at 12:09 +0700, Samphan Raruenrom wrote:
 Building LibreOffice from master or 3.4 branch is hard for beginners
 because we don't know which point in time that the branch are
 buildable on one's platform.

Yes - this is bad; Caolan's idea was to have tags for the last
known-good builds from the existing tinderboxes.

Of course, on IRC you should be able to get a fix for your build
breakage quickly (for Linux at least) - that is recommended: don't think
it is just you :-)

Beyond that - what you could easily do - is to help out by hacking some
support into 'g' to download a set of revisions in a text file (one per
module) and checkout those versions. Would be nice to get some command
to output that too - essentially parsing and applying

./g show-ref 

output - shouldn't be so hard.

Then we can more easily plug that into the existing tinderbox stuff,
and make it easier for people who just checked out.

Is that something you could look into ? [ perhaps with some perl helper
- I hate shell, and 'g' is getting a tad big for shell ].

Thanks,

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Proposing a new Easy Hack - project consistent namespaces

2011-04-20 Thread Júlio Hoffimann

Thank you all for the replies, was a great discussion. :-) I won't persist
in this idea, even discording in the actual situation.

Let's go back for coding...

$ cd libo/wizards/com/sun/star/wizards :-(

Regards,
Júlio.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [PATCH] fix fdo#36399 - ScrollBar display bug on dialog boxes

2011-04-20 Thread Korrawit Pruegsanusak

Hello all,
After finding in the history, I found that this line was IMHO
accidentally deleted.
http://opengrok.libreoffice.org/diff/libs-gui/vcl/unx/gtk/gdi/salnativewidgets-gtk.cxx?r2=%2Flibs-gui%2Fvcl%2Funx%2Fgtk%2Fgdi%2Fsalnativewidgets-gtk.cxx%40944a11c1750f09de52d7623b313e3fd4ace56747r1=%2Flibs-gui%2Fvcl%2Funx%2Fgtk%2Fgdi%2Fsalnativewidgets-gtk.cxx%40d90386875b3e6ad581244830120ac2856b38e868
At Line 1069 on the left.
So it's better to take it back :)

Best Regards
--
Korrawit Pruegsanusak




On Wed, Apr 20, 2011 at 05:44, Robert Dargaud l...@bobiciel.com wrote:
 Hi Michael  All,

 Le 11/04/11 11:41, Michael Meeks a écrit :

 [...]

 on 3.4 build, I've a strange display bug on dialog boxes ScrollBar.

 But finding bugs is good - particularly if we have patches to discuss -
 do you think you could dig into these ?

 Last week, my answer was no. But this evening, after many printf, it's
 yes
 I've a patch who fixe this bug ;-)

 My printf() traces in scrbar.cxx, show me that getNativeControlRegion
 return sal_false for CTRL_SCROLLBAR
 And I've found a missing returnVal = sal_True; in
 salnativewidgets-gtk.cxx

 It's very strange than this line was deleted ! I try to find the origine of
 this delete with qgit and gitk. But I can't find it !

 Best regard

 Bob

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] If you got bounce notification, all is fine again

2011-04-20 Thread Korrawit Pruegsanusak

Thanks for your answer :)
Best Regards
--
Korrawit Pruegsanusak



On Tue, Apr 19, 2011 at 20:10, Jan Holesovsky ke...@suse.cz wrote:
 Hi Korrawit,

 We ban spammers from time to time manually; the ideal solution would
 mean updates in the freedesktop.org infrastructure, I am afraid.

 Regards,
 Kendy

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] LibreOffice Tinderbox?

2011-04-20 Thread Samphan Raruenrom

On Wed, Apr 20, 2011 at 5:07 PM, Christian Lohmaier 
lohmaier+libreoff...@googlemail.com wrote:

 On Wed, Apr 20, 2011 at 7:09 AM, Samphan Raruenrom samp...@osdev.co.th
 wrote:
  Firefox - Tinderboxpushlog : http://tbpl.mozilla.org/

 Doing it this was is near impossible, as the repository is split into
 multiple ones.

  Building LibreOffice from master or 3.4 branch is hard for beginners
 because
  we don't know which point in time that the branch are buildable on one's
  platform.

 http://tinderbox.libreoffice.org/libreoffice-3-4/status.html (note
 that the build did break because of errors in the translation files)

 http://tinderbox.libreoffice.org/MASTER/status.html (bah, all red or
 old)


Cool!  I should add the above URLs to build LO wiki page, agree?


-- 
_/|\_ Samphan Raruenrom. Open Source Development Co., Ltd.
Tel: +66 38 311816, Fax: +66 38 773128, http://www.osdev.co.th/
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] no libreoffice-build-3.3.99.1 ?

Hanno Meyer-Thurow píše v St 20. 04. 2011 v 11:25 +0200:
 On Wed, 20 Apr 2011 09:42:31 +0200
 Andreas Radke a.ra...@arcor.de wrote:
 
  ... (make DESTDIR=... install is broken for me).
 
 Hi all,
 I would recommend my patch attached. For that one would need
 to pass '--libdir=/usr/LIBDIR' to configure to behave. Otherwise it
 installs to /LIBDIR. Improvements to the patch are welcomed!
 Though, this way I came close to the old behaviour.

Cool. Thanks a lot for looking at it. I am still too busy with many
other things :-(

 @Petr
 Would you mind to commit if it is ok, please?

Looked fine. I have committed it, see
http://cgit.freedesktop.org/libreoffice/bootstrap/commit/?h=libreoffice-3-4id=c612724331a3d66d2ee488d91161a54f4d3576bd

I did some changes. I made the libreoffice dirname configurable by
--with-install-dirname option. Also I defined prefix, exec_prefix,
libdir values in Makefile.in.

The result is that the installation path is /usr/local/lib/libreoffice
instead of /libreoffice

I hope that my changes are fine for you.

I am looking forward to see more patches from you ;-)

Best Regards,
Petr

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] [PUSHED] fix fdo#36399 - ScrollBar display bug on dialog boxes

Hi Robert,

On Wed, 2011-04-20 at 00:44 +0200, Robert Dargaud wrote:
 Last week, my answer was no. But this evening, after many printf, it's 
 yes I've a patch who fixe this bug ;-)

Nice ! :-)

 It's very strange than this line was deleted ! I try to find the origine 
 of this delete with qgit and gitk. But I can't find it !

It seems you found it, and it was an error; nice work.

I've pushed the patch to master, and will merge it to libreoffice-3-4 -
what's next ? :-)

Thanks !

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice] consistent namespaces future breakage ...

Hi guys,

On Tue, 2011-04-19 at 23:17 +0200, Bjoern Michaelsen wrote:
 IMHO doing a gradual migration is not a good idea here. Such
 things should be done in one deep cut, because:

So - I think the tread came up with the right answer - which is
'later'; on this.

Nevertheless, the com::sun::star:: namespace, is not only an
anachronism, but a real source of bloat too - it makes our .rdb files
larger, it makes our symbol tables bigger and slower to resolve, it adds
bulk ~everywhere for nearly no benefit.

Having said that - I think we probably want to have a flag-day at some
stage perhaps a 4.0, and it is worth collecting things we want to do
then, so we remember to do them all - I suggest having a tracker bug for
that would be helpful. If we reconcile ourselves to breaking the plugin
ABI (and API) incompatibly, and the necessity of re-compiling plugins
for a next major version [ which seems to me to be sensible ], I guess
there are a lot of things we'd like to have then:

* drop the com::sun::star namespace (and the
  org::openoffice:: one too for something short  simple
  uno:: perhaps).

* un-'publish' a lot of pointlessly published interfaces -
  eg. the UNO accessibility API is never going to be used
  externally.

* replace 'sal_Bool' with 'bool' globally in UNO interfaces

* replace rtl::OUString with a UTF-8 string for better space
  efficiency, and Unicode coverage.

* remove rtl::OString - and do charset conversion at the
  code periphary

* drop the monstrous 'store' code, and the old types.rdb file

* perhaps re-work some of the horrible UNO APIs used by scripts
  to something more useful and familiar

* drop the pointless UNO-isation of the calc formula APIs

* kill the bogus Stream read method, misc. UNO API usefulness
  audit, cleanup and removal

* etc.

Of course, research on automated tools and scripts to get this stuff
done right quickly, would be great.

Having said this - I think this sort of disruptive change belongs in a
major version update, and I can't see it happening for the next year :-)
[ but we should prolly plan a date for it so it does end up happening ].
There is never a good time back-compatibility breakage - but now is a
particularly bad time for it I think :-)

And of course, we should extend the above list to cover all our pet
hates that we can't currently fix IMHO.

ATB,

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [PUSHED] fix fdo#36399 - ScrollBar display bug on dialog boxes

2011-04-20 Thread Korrawit Pruegsanusak

Hello all
May we close this fdo#36399 bug then?
Best Regards
--
Korrawit Pruegsanusak




On Wed, Apr 20, 2011 at 20:44, Michael Meeks michael.me...@novell.com wrote:
 Hi Robert,

 On Wed, 2011-04-20 at 00:44 +0200, Robert Dargaud wrote:
 Last week, my answer was no. But this evening, after many printf, it's
 yes I've a patch who fixe this bug ;-)

        Nice ! :-)

 It's very strange than this line was deleted ! I try to find the origine
 of this delete with qgit and gitk. But I can't find it !

        It seems you found it, and it was an error; nice work.

        I've pushed the patch to master, and will merge it to libreoffice-3-4 -
 what's next ? :-)

        Thanks !

                Michael.

 --
  michael.me...@novell.com  , Pseudo Engineer, itinerant idiot



___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] no libreoffice-build-3.3.99.1 ?

2011-04-20 Thread Hanno Meyer-Thurow

On Wed, 20 Apr 2011 15:43:07 +0200
Petr Mladek pmla...@suse.cz wrote:

 I did some changes. I made the libreoffice dirname configurable by
 --with-install-dirname option. Also I defined prefix, exec_prefix,
 libdir values in Makefile.in.
 
 The result is that the installation path is /usr/local/lib/libreoffice
 instead of /libreoffice
 
 I hope that my changes are fine for you.

They are perfectly fine for me. I just found a micro-optimization.
Instead of hard-wiring 'INSTALL_DIRNAME=libreoffice' I would prefer
it to be 'INSTALL_DIRNAME=$AC_PACKAGE_NAME', which is
generated by AC_INIT at the top of configure.in.

Though, $AC_PACKAGE_NAME would have uppercase letters. Is there any
posix function to lower-case that macro? Quite busy with other stuff, too,
right now ...


Regards,
Hanno
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [PUSHED] fix fdo#36399 - ScrollBar display bug on dialog boxes


On Wed, 2011-04-20 at 21:04 +0700, Korrawit Pruegsanusak wrote:
 May we close this fdo#36399 bug then?

Indeedie - always worth closing it if it got fixed; I just did that
myself :-)

Thanks guys,

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [ANNOUNCE] libreoffice-3.3.99.2 tag created (3.4.0-beta2)

Petr Mladek píše v Út 19. 04. 2011 v 19:27 +0200:
 Hi,
 
 I have just created the libreoffice-3.3.99.2 tag for 3.4.0-beta2 release.

We are sorry but some wrong strings caused build breakage for some
localizations. You might want to use the tag
libreoffice-3.3.99.2-hotfix1 from the translations repo:

cd clone/translations
git fetch --tags
git checkout -b tag-libreoffice-3.3.99.2 libreoffice-3.3.99.2-hotfix1


Best Regards,
Petr

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [REVIEW] letter wizard template files packed and installed in two copies fdo#35722


On Sat, 2011-04-16 at 22:22 +0200, Andras Timar wrote:
 Windows installer size could be further reduced, if letter wizard
 template files would not be packed in two copies for 26 languages.

Nice - fixes 35722 and shrinks our installer :-) presumably (as l10n
guru) you're happy that there is no l10n impact here.

I've cherry picked it to -3-4

Thanks,

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] LibreOffice Tinderbox?

2011-04-20 Thread Christian Lohmaier

Hi *,

On Wed, Apr 20, 2011 at 2:10 PM, Michael Meeks michael.me...@novell.com wrote:
 [how to tell what revisions are buildable]

        Beyond that - what you could easily do - is to help out by hacking some
 support into 'g' to download a set of revisions in a text file (one per
 module) and checkout those versions. Would be nice to get some command
 to output that too - essentially parsing and applying

        ./g show-ref

        output - shouldn't be so hard.

        Then we can more easily plug that into the existing tinderbox stuff,
 and make it easier for people who just checked out.

Tinderbox part is rather easy - you can add TinderboxPrint
statements into your log that will then appear in the build-status
boxes (I add the time needed for the bulid for example), and it's also
possible to include other data. It would be possible to embedd a small
file as well that then can be downloaded via tinderbox page. (just add
an uuencoded file to the log, and set tinderbox: binaryname:
buildrevisions or something similar)

ciao
Christian
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] consistent namespaces future breakage ...

Hi Michael, Hi all,

On Wed, 20 Apr 2011 15:02:06 +0100
Michael Meeks michael.me...@novell.com
wrote:
   Having said that - I think we probably want to have a
 flag-day at some stage perhaps a 4.0, and it is worth collecting
 things we want to do then, so we remember to do them all - I suggest
 having a tracker bug for that would be helpful. If we reconcile
 ourselves to breaking the plugin ABI (and API) incompatibly, and the
 necessity of re-compiling plugins for a next major version [ which
 seems to me to be sensible ], I guess there are a lot of things we'd
 like to have then:
 
 [... long list of snafus follows ...]

Agreed. Essentially you are proposing a new API version and to get rid
of all the known historic ugliness. I think we should start more
freeform on a wikipage before solidifying in the bug tracker at least
in the beginning, when the discussion is still very fluid. Otherwise we
would end up with endless bug splits and merges as the topics can be
highly interdependent.

   Having said this - I think this sort of disruptive change
 belongs in a major version update, and I can't see it happening for
 the next year :-) [ but we should prolly plan a date for it so it
 does end up happening ]. There is never a good time
 back-compatibility breakage - but now is a particularly bad time for
 it I think :-)
 
   And of course, we should extend the above list to cover all
 our pet hates that we can't currently fix IMHO.

I think that is the most important point. Esp. since sometimes we might
agree that the status quo is bad, but we might not (yet) agree on how a
better solution should look like. So we should create a wikipage now
discussing all possible changes and cooking it for at least one year.
That will ensure we have a plan once we get to this and:
a) that it has been discussed well enough by the bright minds on our
   project.
b) that people using the API see what is coming and can brace for
   impact.
c) Any flamewar about the implementation will have cooled down to
   slightly below one unit of emacs vs. vi
d) there will be no big OMGeverythingDifferent!!11! surprises.

Best,

Bjoern



-- 
https://launchpad.net/~bjoern-michaelsen


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [PATCH] fix fdo#36399 - ScrollBar display bug on dialog boxes

2011-04-20 Thread Robert Dargaud

After a long reflection, I confirm that this gigantesque contribution is 
under LGPLv3+/MPL

Bob


Le 20/04/11 16:20, Michael Meeks a écrit :

On Wed, 2011-04-20 at 00:44 +0200, Robert Dargaud wrote:

And I've found a missing returnVal = sal_True; in
salnativewidgets-gtk.cxx

Nice work - even though it's restoring code - it'd be great if you
could confirm that your contribution(s) are under LGPLv3+/MPL :-)

Thanks again,

Michael.



___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] no libreoffice-build-3.3.99.1 ?

Hanno Meyer-Thurow píše v St 20. 04. 2011 v 16:08 +0200:
 On Wed, 20 Apr 2011 15:43:07 +0200
 Petr Mladek pmla...@suse.cz wrote:
 
  I did some changes. I made the libreoffice dirname configurable by
  --with-install-dirname option. Also I defined prefix, exec_prefix,
  libdir values in Makefile.in.
  
  The result is that the installation path is /usr/local/lib/libreoffice
  instead of /libreoffice
  
  I hope that my changes are fine for you.
 
 They are perfectly fine for me. I just found a micro-optimization.
 Instead of hard-wiring 'INSTALL_DIRNAME=libreoffice' I would prefer
 it to be 'INSTALL_DIRNAME=$AC_PACKAGE_NAME', which is
 generated by AC_INIT at the top of configure.in.

Great idea. I have done the change, see
http://cgit.freedesktop.org/libreoffice/bootstrap/commit/?h=libreoffice-3-4id=6326baaba7534667c95c6cc8aac6287bb140580e

 Though, $AC_PACKAGE_NAME would have uppercase letters. Is there any
 posix function to lower-case that macro?

tr [[:upper:]] [[:lower:]] did the job. It should be cross-platform.

BTW: AC_PACKAGE_NAME is a macro and not a variable, so I needed to avoid
the dolar sign ;-)


Best Regards,
Petr

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] complete

Hi Timo,

On Thu, 2011-04-14 at 17:50 +0200, Timo wrote:
 Maybe this task should be moved to “completed”?
 http://wiki.documentfoundation.org/Easy_Hacks#Make_python_.2F_mail-merge_debuggable

I read your last mail, and I was not certain that it is working :-) so
sadly the code didn't get merged.

Do you think you could re-send your code as a patch vs. master: with
the new msgbox.py file added ? we should also have a patch for scp2/ to
install the new python file too (git grep for mailmerge.py in there).
Also good to add [PATCH] to the Subject to get some priority review :-)
[ also confirm the LGPLv3+/MPL license ].

  MessageBoxButtons as well as XSCRIPTCONTEXT do not exist for me. Python
  doesn´t find them and they are documented as “not published” [1]. 

Did you get over this ? presumably you are running this using the
python embedded with libreoffice, rather than some external python ?

  [3] see screenshot Bildschirmfoto.png

Looks nice :-)

Great work,

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] consistent namespaces future breakage ...

2011-04-20 Thread Júlio Hoffimann

Hi Michael,

Thanks for expose your opinion, it's so much professional than mine. :-)

Best regards,
Júlio.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [ANNOUNCE] libreoffice-3.3.99.2 tag created (3.4.0-beta2)

2011-04-20 Thread Miklos Vajna

On Tue, Apr 19, 2011 at 07:27:51PM +0200, Petr Mladek pmla...@suse.cz wrote:
 The build repo is not tagged. We would like to get rid of it.

Hi Petr,

One question: the old build repo created .txt filelists in the build/
directory which helped creating subpackages: we could just read
lang_*_list.txt to split languages and so on. As far as I see the
boostrap-based build does not generate anything like that.

Is it in fact there, just I'm blind or is it planned to have those
filelists back in some other way?

Thanks.


pgpqog0O1qK6C.pgp
Description: PGP signature
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] consistent namespaces future breakage ...

2011-04-20 Thread Lubos Lunak

On Wednesday 20 of April 2011, Michael Meeks wrote:
   And of course, we should extend the above list to cover all our pet
 hates that we can't currently fix IMHO.

 I don't want to comment on the specific items as that could make this thread 
grow into a monster, but could it be said more specifically what we cannot 
fix currently? As I understand it we cannot break backwards compatibility 
only for things related to extensions (UNO, what else?), but even there I'm 
not sure what that all means code-wise.

-- 
 Lubos Lunak
 l.lu...@suse.cz
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] consistent namespaces future breakage ...

2011-04-20 Thread Kohei Yoshida

On Wed, 2011-04-20 at 16:43 +0200, Bjoern Michaelsen wrote:
 Hi Michael, Hi all,
 
 On Wed, 20 Apr 2011 15:02:06 +0100
 Michael Meeks michael.me...@novell.com
 wrote:
  Having said that - I think we probably want to have a
  flag-day at some stage perhaps a 4.0, and it is worth collecting
  things we want to do then, so we remember to do them all - I suggest
  having a tracker bug for that would be helpful. If we reconcile
  ourselves to breaking the plugin ABI (and API) incompatibly, and the
  necessity of re-compiling plugins for a next major version [ which
  seems to me to be sensible ], I guess there are a lot of things we'd
  like to have then:
  
  [... long list of snafus follows ...]
 
 Agreed. Essentially you are proposing a new API version and to get rid
 of all the known historic ugliness. I think we should start more
 freeform on a wikipage before solidifying in the bug tracker at least
 in the beginning, when the discussion is still very fluid. Otherwise we
 would end up with endless bug splits and merges as the topics can be
 highly interdependent.

Yup, having a wiki page to collect our thoughts would be a great idea.
While we are talking about re-designing our API, I would also like to
reduce the use of UNO API in the core implementation code, which have
time and time again caused all sorts of performance issues,
over-complicating code, and made the code unbelievably hard to trace.
IMO there are places where we shouldn't have used UNO API at all, and
I'd like to keep clean separation between the core code and the API
layer (so that the core code won't depend on the API to do its thing too
much).

Kohei

-- 
Kohei Yoshida, LibreOffice hacker, Calc
kyosh...@novell.com

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] release plan : inconsistency between 3.3.3 and 3.4

Hi Pierre,

On Tue, 2011-04-19 at 21:45 +0200, Pierre-André Jacquod wrote:
 jumping late into the subject, but

:-)

 On 04/11/2011 12:25 PM, Michael Meeks wrote:
  The plan is (of course), to keep releasing 3.3.x releases as long as
  people are interested in creating them I suppose[1] - we should come up
..
 May I disagree ?? This is not a very predictable use for all involved: 
 users, distros, etc... When to jump to next version ?

When a user should jump to the next version is never clear - and it
depends on your risk aversion, and interest in features. We can't make a
single decision that is right for all users here. Our business users
want to change very infrequently, and have very long support timelines:
vendors will end up supporting some releases in enterprise products for
many years ;-)

Other users (and developers) want quick releases, with the latest
improvements and fixes, counting on the benefit of these to outweigh any
new bugs they might hit. They also want to report bugs that are useful
to improve the cutting edge.

  What happens for bug discovered in distros ?

They merge the bug fix to all the branches it applies to, and that they
care about. I expect people to decreasingly care about very old
releases. If people do care, they can back-port and test fixes - I don't
see why we should stop that.

 Especially if we have 3-4 X.Y release a year

Well - we have a 6 month cadence for major 3.X releases - so 2 releases
per year, and something like a monthly cadence for 3.X.Y releases - so
sure, we can end up with ~10 releases a year or so - of which, only the
latest versions of each will be interesting for developers.

 Could it be not possible to have some rules, like the release of version 
 X.Y.0 means end of support for X.(Y-2) version. En in case of X.0.0 
 version, only the latest (X-1).Y.Z version is supported ?

Sure - we could do that; but if vendors have to support those versions
anyway (as they will have to), and they actually care - I don't see any
reason why we should forbid them from putting their fixes into the git
branch and them doing releases.

Practically, I can't see enthusiastic build resources being applied to
3.3.x release for many more iterations once 3.4 is out - but if others
want to step in - why not ?

 So what about picking long term support, e.g. 3.5 is long term support, 
 means 2 years, what ever happens for the number of releases ?

Not a bad idea; but picking that version is difficult; and ultimately
I've not seen another up-stream Free Software project that does this. If
customers want endless support - it is a tedious job, and they should
pay someone, anyone to provide that for them.

 So if you get a bug report, you know against which release you have to 
 test / it will be tested.

Ultimately, I think we are only really interested in bug reports
against the latest stable, and development versions, otherwise we'll end
up with a clogged up bugzilla :-) let see ...

ATB,

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] no libreoffice-build-3.3.99.1 ?

2011-04-20 Thread Andreas Radke

Thanks for your work but I'm running into a permission issue:

== Entering fakeroot environment...
== Starting package_libreoffice()...
Installing in /usr/lib/libreoffice...
mkdir /usr/lib/libreoffice: Permission denied at 
/build/src/build/solenv/bin/ooinstall line 32
make: *** [install] Error 255


This has not happened when using plain beta1 source and using 
make OODESTDIR=foo install.

Any idea?

-Andy
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] consistent namespaces future breakage ...

Hi Lubos,

On Wed, 2011-04-20 at 17:08 +0200, Lubos Lunak wrote:
  I don't want to comment on the specific items as that could make this thread 
 grow into a monster, but could it be said more specifically what we cannot 
 fix currently ?

:-) from 10k feet anything in clone/ure/ is the public ABI/API.

That includes some monumental performance blunders - such as the
'store' code, and the IDL interfaces (in theory only the ones marked
'published' in the IDL).

 As I understand it we cannot break backwards compatibility 
 only for things related to extensions (UNO, what else?),
 but even there I'm not sure what that all means code-wise.

Just UNO; and of course key behaviours of the actual UNO interfaces
themselves - as implemented all over the place ;-)

HTH,

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] PyUno is Python 3 compatible

2011-04-20 Thread Andreas Becker

Hi Hanno,
First of all, it has nothing to do with that patch.

In configure.in, AM_PATH_PYTHON([2.2]) check is done. You can look into
aclocal.m4 line 205 ff. and try to debug.
You should perhaps update automake (my version is 1.11).

Maybe is works when you set $PYTHON=python before running autogen.sh.
--Andreas becker
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Smart art like functionality

2011-04-20 Thread KAMI911 KAMI911

Hi Michael,

Does it provide user interface for LO to create such smart arts? Where is
the current code, branch?

Best regards,
KAMI

2011/4/20 Michael Meeks michael.me...@novell.com

 Hi Kami,

 On Wed, 2011-04-20 at 17:14 +0200, KAMI911 KAMI911 wrote:
  We are very excited about the possibilities of LibreOffice, so we
  decided to try to rewrite Diagram extension [1] in C as a separated
  module.

 Nice ! :-)

   Are there any ongoing development to create SmartArt related thing?

 Well - we have a prototype of this, which is badly need for OOXML
 import - since the SmartArt stuff is serialised as XML entities with no
 preview (last I looked).

   Maybe the best would be to as like the Chart2 module. But we need
  help for the first steps. How can we start it? Or are there any
  related documentation, design draft, goal etc?

 So - Thorsten has some code for this, and we'd love to help mentor
 it -
 as you say, it is a huge missing piece - and we'd really love to have
 that integrated with the core.

ATB,

Michael.

 --
  michael.me...@novell.com  , Pseudo Engineer, itinerant idiot



___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] [ANNOUNCE] libreoffice-3.3.99.2 tag created (3.4.0-beta2)

Miklos Vajna píše v St 20. 04. 2011 v 17:00 +0200:
On Tue, Apr 19, 2011 at 07:27:51PM +0200, Petr Mladek pmla...@suse.cz wrote:
The build repo is not tagged. We would like to get rid of it.

Hi Petr,

One question: the old build repo created .txt filelists in the build/
directory which helped creating subpackages: we could just read
lang_*_list.txt to split languages and so on. As far as I see the
boostrap-based build does not generate anything like that.

Is it in fact there, just I'm blind or is it planned to have those
filelists back in some other way?

Yes, we need to port the support from the build repo. The target is to
get it working with:

make DESTDIR=/var/tmp/lo-packaging install

Hanno, did a fix in this area today, see
http://cgit.freedesktop.org/libreoffice/bootstrap/commit/?h=libreoffice-3-4id=c612724331a3d66d2ee488d91161a54f4d3576bd

With this fix, and the above call, it should start producing some file
lists into the /var/tmp/lo-packaging directory. They should have names
according to the scp2 module names, e.g. gid_Module_Prg_Base_Bin,
gid_Module_Brand_Prg_Impress, gid_Module_Optional_Javafilter.

We need to port all the hacks from libreoffice/build/bin/package-ooo to
create the expected .txt filelists from the gid_* ones. I guess that we
want the .txt file lists because the have more reasonable grouping.

Any volunteer for this?

Caolan, AFAIK, you create the subpackages another way. I hope that the
above activity does not break you. It should be easy to remove the
generated file lists if you do not like them.

Best Regards,
Petr

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] no libreoffice-build-3.3.99.1 ?

2011-04-20 Thread Hanno Meyer-Thurow

On Wed, 20 Apr 2011 17:35:47 +0200
Andreas Radke a.ra...@arcor.de wrote:

 This has not happened when using plain beta1 source and using 
 make OODESTDIR=foo install.

The only thing changed there was OODESTDIR to DESTDIR.
So it should stay in the sandbox. Would you mind to pastebin
the log of the installer and maybe some logs of your package
tool, please?


Regards,
Hanno
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Smart art like functionality

2011-04-20 Thread Thorsten Behrens

KAMI911 KAMI911 wrote:
 We are very excited about the possibilities of LibreOffice, so we decided to
 try to rewrite Diagram extension [1] in C as a separated module. Are there
 any ongoing development to create SmartArt related thing? Maybe the best
 would be to as like the Chart2 module. But we need help for the first steps.
 How can we start it? Or are there any related documentation, design draft,
 goal etc?
 
Hi Kami,

just played a bit with that extension, really nice - but why would
you want to go for a _C_ lib?

As Michael mentions, there's a prototype patch to handle Smart art
in Draw/Impress, it's here:
http://cgit.freedesktop.org/libreoffice/build/tree/patches/dev300/oox-smartart-import.diff

Would be cool to work on that jointly!

Cheers,

-- Thorsten


pgpJgJ4BUo1Sh.pgp
Description: PGP signature
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Smart art like functionality

2011-04-20 Thread KAMI911 KAMI911

Hi Thorsten, Michael,

As we discussed before, java is not preferred around LibreOffice. That is
why we decided to check the possible ways. However we have a never (interm)
release with more diagrams, possibilities like converting between diagrams,
etc. What do you think about? I hope we can gang up on smart art thing but
we prefer to create tools for end user to create diagrams in user friendly
way.


Cheers,

KAMI

2011/4/20 Thorsten Behrens t...@documentfoundation.org

 KAMI911 KAMI911 wrote:
  We are very excited about the possibilities of LibreOffice, so we decided
 to
  try to rewrite Diagram extension [1] in C as a separated module. Are
 there
  any ongoing development to create SmartArt related thing? Maybe the best
  would be to as like the Chart2 module. But we need help for the first
 steps.
  How can we start it? Or are there any related documentation, design
 draft,
  goal etc?
 
 Hi Kami,

 just played a bit with that extension, really nice - but why would
 you want to go for a _C_ lib?

 As Michael mentions, there's a prototype patch to handle Smart art
 in Draw/Impress, it's here:

 http://cgit.freedesktop.org/libreoffice/build/tree/patches/dev300/oox-smartart-import.diff

 Would be cool to work on that jointly!

 Cheers,

 -- Thorsten

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] First attempt to build LO3.4

Hi there,

On Wed, 2011-04-20 at 17:06 +0200, KAMI911 KAMI911 wrote:
 So I should create option like --enable-oxygenoffice, and add my
 stuffs here ? All things depending in the code directly ?

I couldn't see my reply elsewhere. But I would add an OxygenOffice
distro config in distro-config/ and then add individual configuration
options for each feature you want to add.

  How should I make the download conditional? I really don't want to
 enforce anybody to download our extra stuffs, extensions, etc without
 using   --enable-extra-gallery, --enable-extra-template,
   --enable-extra-sample, --enable-extra-font and all --with-ext-*
 (extension) switches.

Sure :-) if we don't make that conditional already, then we should. I
guess it is a matter of moving ooo.lst to ooo.lst.in  and having some
@FOO_EXTRA_DOWNLOAD@ macros in ooo.lst.in and processing it in configure
(?).

But yes - the --enable-extra-gallery stuff all sounds great to have in
the stock build, rather than in patches - so more people can use and get
familiar with your great work. [ We should really have a talk from you
at the conference about why it is that we havn't shipped that stuff in
the past - I forget the details ;-].

ATB,

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] When can we import xml data

2011-04-20 Thread Fernand Vanrie


Hi Michael ,

Thanks for your interest, With xml-data i mean a data-dump from a SQL 
database. Where records becomes rows and fields becomes columbs. MS Exel 
can flawless open this xml-files.
The xml structure depends on the Table of the database but mostly its 
something like:


?xml version='1.0'?
NewDataSet
Table
id1/id
linkid76497/linkid
TextBoxANC/TextBoxTypeWeek/Type
FormaatExecutive - 148x210mm/Formaat
Formaatuitz /
Kaftik heb reeds een kaft/Kaft
emaila...@pmg.be/email
/Table
Table
id2/id
linkid76502/linkid
TextBoxSAF/TextBox
TypeDag/Type
FormaatExecutive - 148x210mm/Formaat
Formaatuitz /
Kaftik heb nog geen kaft/Kaft
emails...@pmg.be/email
/Table

The StarXpert import filter clould handles this dumps at condition that 
all fields (also empty radio buttons etc..)  where represented by a tag.


Hope it helps

Fernand



Hi Fernand,

On Wed, 2011-04-13 at 10:29 +0200, Fernand Vanrie wrote:

I am just a humble advanced user, The extentsion from StarXpert is a
scrumbled jar file.

:-) with no source code ? if so, hard to deal with.


Its not the Extension who is faulty, its simple a lack of XML
import for Calc in LO and OO .

We import lots of styles and dialects of XML - what would really help
is a well-formed report: what kind of XML do you want to import ? where
is it specified ? is there an example set of files etc. ?


Just hoped to find here a coder who can/will make this happen or can
rewrite the StarXpert java Code into a nex etxtension.

Well, importing some sort of XML sounds pretty trivial to me - we could
make it an easy hack, if it is a popular dialect, and there are good
docs I guess. Can you file a bug with all the relevant details, and
reply to this mail with the number ?

Thanks,

Michael.



___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] OSL_ASSERT - remove backtrace or make abort

2011-04-20 Thread Thorsten Behrens

Lubos Lunak wrote:
  I'd like to remove the backtrace printing from OSL_ASSERT and friends, or, 
 even better and if possible, make these functions work properly, i.e. abort 
 on failure (I'm not really holding my breath on the second one, but refusing 
 that one will at least support the first one).
 
 [...]
 
  Opinions?
 
Yes - first of all, there's SAL_DIAGNOSE_ABORT, to optionally enable
your desired behaviour. Then, there's sal-disable-backtrace.diff,
which I can happily merge - just set DISABLE_SAL_BACKTRACE then.

Regarding the problem itself, it's festering since many years, and 
not easily reconcilable - in the sal/uno area, assertions *are*
serious, and should lead to aborts. Especially in the
application/filter area, though, those were indeed often used in a
um, not sure, looks fishy here, let's do something-kinda way.

Generally, cleaning that up (and converting the mis-used assertions
I mentioned into some warning) would be greatly appreciated.
Something for past-3-4 and a feature branch? IIRC OOo had some plans
to make at least smoketest completely 'assertion'-free.

Cheers,

-- Thorsten


pgpxuwrUUZTL8.pgp
Description: PGP signature
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] When can we import xml data

Hi Fernand,

On Wed, 2011-04-20 at 18:43 +0200, Fernand Vanrie wrote:
 Thanks for your interest, With xml-data i mean a data-dump from a SQL 
 database.

Fine - so please open the bug as requested:

http://bugs.freedesktop.org/

And please provide a sample XML document, and work out where the
documentation for the XML dialect is (MSDN?). Also a link to the old
converter would be helpful.

 The xml structure depends on the Table of the database but mostly its 
 something like:

Is it required to throw up a UI to do this ? or can we just whack it
straight into a set of spreadsheet tables ?

 Hope it helps

Yes, but not enough to actually do anything about it (yet) more data
required :-)

ATB,

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] Promoting LibO to Vietnamese students by completing easy hacks

2011-04-20 Thread Nguyen Vu Hung (KiEi)


Hello,

I CC'ed Nguyen Hong Quang, the one who has founded MHST.

(2011/04/20 14:47), Cedric Bosdonnat wrote:

Could you enlighten us about some points about MHST?

Perhaps Mr. Quang can do that better than me :)


Is it working
exactly like GSoc (1 student, 1 project, one potential winner) or is it
more like a team project with one project? This would help us see what
kind of project(s) is needed for the students.

Mentors and students can team up.
Last year, most team consists of 3 or 4 students.
And the winners are team, not a person in a team.




The developers are the mentors and I step back as the one who fill the
gaps between
the developers and the students.

Cool! Are there some vietnamese developers that could help mentoring and
start gaining experience on the LO dev?

I will try but I can not promise anything.
The open source movement in Vietnam is still quite immature; and we find 
it very hard
creating an active Linux users' group. That means, it is even harder 
find FOSS developers.



Sure, but don't go too quickly with the tasks from the GSoc as the
students aren't selected yet.

I didn't know that :) Anyway, the deadline for picking an idea is
2011/04/30

What we can do: you copy the whole lot of ideas now and you remove the
ones selected for GSoc when Google has announced the selected students.
This way Vietnamese students can start working on their proposals.

+1

We can keep some private communication about the topic you know
vietnamese students are about to pick: I could tell you if you would
need to redirect the student on another task.

Please send me the list off-list.

The GSoc ideas page is pretty OK on that point, but not the easy hack
page. I'ld prefer keeping things on the GSoc ideas page.


And can add more ideas if you have, we have to finish them anyway.

--
Nguyen Vu Hung (Nguyyễn Vũ Hưng)
LibreOffice, Vietnamese Translation Team.

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [Libreoffice] consistent namespaces future breakage ...