Awesome Tim!
I look forward to not having to use those libreoffoce native dialogs anymore :-)
Calvin On May 13, 2012 4:05 PM, "Timothy Pearson" kb9vqf@pearsoncomputing.net wrote:
FYI:
http://lists.freedesktop.org/archives/libreoffice/2012-May/031676.html
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
FYI:
http://lists.freedesktop.org/archives/libreoffice/2012-May/031676.html
Does this mean we have to rebuild LibreOffice or is this patch included in the upstream LibreOffice sources?
Darrell
FYI:
http://lists.freedesktop.org/archives/libreoffice/2012-May/031676.html
Does this mean we have to rebuild LibreOffice or is this patch included in the upstream LibreOffice sources?
Darrell
I am trying very hard to get this into the upstream LO sources. :-)
Tim
Does this mean we have to rebuild LibreOffice or is this patch included in the upstream LibreOffice sources?
I am trying very hard to get this into the upstream LO sources. :-)
Sounds good.
If I understand correctly, building LO takes several hours, even on bleeding edge hardware. If the patch gets merged then most users need only use their package manager to obtain a Trinity compatible LO package.
Darrell
Does this mean we have to rebuild LibreOffice or is this patch
included in
the upstream LibreOffice sources?
I am trying very hard to get this into the upstream LO sources. :-)
Sounds good.
If I understand correctly, building LO takes several hours, even on bleeding edge hardware. If the patch gets merged then most users need only use their package manager to obtain a Trinity compatible LO package.
Darrell
You are correct about the build times; it takes several hours here on a dedicated 2.8GHz 8 core Opteron machine.
Regarding user installation, that depends on whether or not the upstream providers package LO with TDE support or not. I will try to do so for Debian and Ubuntu, but other distros probably will not.
Tim
Does this mean we have to rebuild LibreOffice or is this patch
included in
the upstream LibreOffice sources?
I am trying very hard to get this into the upstream LO sources. :-)
Sounds good.
If I understand correctly, building LO takes several hours, even on bleeding edge hardware. If the patch gets merged then most users need only use their package manager to obtain a Trinity compatible LO package.
Darrell
You are correct about the build times; it takes several hours here on a dedicated 2.8GHz 8 core Opteron machine.
Regarding user installation, that depends on whether or not the upstream providers package LO with TDE support or not. I will try to do so for Debian and Ubuntu, but other distros probably will not.
Tim
And we're official!
http://cgit.freedesktop.org/libreoffice/core/commit/?id=07b3d083b49b4cbb248b...
This should ship with LibreOffice 3.6.
Tim
And we're official!
http://cgit.freedesktop.org/libreoffice/core/commit/?id=07b3d083b49b4cbb248b...
This should ship with LibreOffice 3.6.
Will TDE dialog support be enabled by default, or disabled by default and needing a build option to enable?
Darrell
And we're official!
http://cgit.freedesktop.org/libreoffice/core/commit/?id=07b3d083b49b4cbb248b...
This should ship with LibreOffice 3.6.
Will TDE dialog support be enabled by default, or disabled by default and needing a build option to enable?
Darrell
Disabled by default, as it requires access to a functional tqt3/tqtinterface/arts/tdelibs stack to compile.
Pass --enable-tde to the LibreOffice configuration script to enable TDE support.
Tim
On Tuesday 15 May 2012 10:09:23 Timothy Pearson wrote:
Disabled by default, as it requires access to a functional tqt3/tqtinterface/arts/tdelibs stack to compile.
Pass --enable-tde to the LibreOffice configuration script to enable TDE support.
It seems you simply copied the KDE integration.
I fail to see how this will enable the file picker as it is not available for KDE3 as of now.
On 05/15/2012 04:11 AM, Ilya Chernykh wrote:
It seems you simply copied the KDE integration.
I fail to see how this will enable the file picker as it is not available for KDE3 as of now.
Ilya,
LO will put the removed code back in to enable it for 3.6 -- if I understand correctly.
What about your gcc 4.7 builds -- Have you seen the kwrite crash on line-wrap problem in suse?
On 05/15/2012 04:11 AM, Ilya Chernykh wrote:
It seems you simply copied the KDE integration.
I fail to see how this will enable the file picker as it is not available for KDE3 as of now.
Ilya,
LO will put the removed code back in to enable it for 3.6 -- if I understand correctly.
What about your gcc 4.7 builds -- Have you seen the kwrite crash on line-wrap problem in suse?
-- David C. Rankin, J.D.,P.E.
Ilya,
I don't know what you did wrong when building KDE3/LO, but I just tested the TDE integration module from LO GIT against TDE GIT and it worked perfectly as of the merge date (a couple days ago).
Regarding "just making a copy", I was *specifically asked* by the LibreOffice developers to keep as much common code between the KDE3 and TDE integration modules as possible, and the patch in LO GIT is the result of that work.
Tim
On Wednesday 16 May 2012 22:34:59 Timothy Pearson wrote:
I don't know what you did wrong when building KDE3/LO, but I just tested the TDE integration module from LO GIT against TDE GIT and it worked perfectly as of the merge date (a couple days ago).
So you possibly enabled the file picker for TDE only. Do you have an option to use system dialogs in the settings panel?
On Wednesday 16 May 2012 22:34:59 Timothy Pearson wrote:
I don't know what you did wrong when building KDE3/LO, but I just tested the TDE integration module from LO GIT against TDE GIT and it worked perfectly as of the merge date (a couple days ago).
So you possibly enabled the file picker for TDE only. Do you have an option to use system dialogs in the settings panel?
I don't have the test machine online right now, but everything worked as expected IIRC, including that option.
Tim
Will TDE dialog support be enabled by default, or disabled by default and needing a build option to enable?
Disabled by default, as it requires access to a functional tqt3/tqtinterface/arts/tdelibs stack to compile.
Pass --enable-tde to the LibreOffice configuration script to enable TDE support.
Looks like we all are stuck rebuilding LO. :-)
We probably should provide a README or wiki article to note that information.
Darrell
Will TDE dialog support be enabled by default, or disabled by default
and
needing a build option to enable?
Disabled by default, as it requires access to a functional tqt3/tqtinterface/arts/tdelibs stack to compile.
Pass --enable-tde to the LibreOffice configuration script to enable TDE support.
Looks like we all are stuck rebuilding LO. :-)
We probably should provide a README or wiki article to note that information.
Darrell
Not all, as once Debian/Ubuntu releases packaging files for LO I will be able to offer the TDE integration in binary form for those platforms. Others will have to see if their TDE packaging provider would be willing to do something similar.
Tim
On 05/15/2012 12:39 PM, Timothy Pearson wrote:
Not all, as once Debian/Ubuntu releases packaging files for LO I will be able to offer the TDE integration in binary form for those platforms. Others will have to see if their TDE packaging provider would be willing to do something similar.
Tim
That's where a "how to" would be good. How do you just build the binary files to provide integration without having to rebuild LO? Can you just build a subset of LO to get the integration binary out?
On 05/15/2012 12:39 PM, Timothy Pearson wrote:
Not all, as once Debian/Ubuntu releases packaging files for LO I will be able to offer the TDE integration in binary form for those platforms. Others will have to see if their TDE packaging provider would be willing to do something similar.
Tim
That's where a "how to" would be good. How do you just build the binary files to provide integration without having to rebuild LO? Can you just build a subset of LO to get the integration binary out?
-- David C. Rankin, J.D.,P.E.
No, all of LO must be built to get the integration module out, but (in theory) the handful of integration files produced by that build should be binary compatible within a given major version (x.y.*) of LO.
Tim
No, all of LO must be built to get the integration module out, but (in theory) the handful of integration files produced by that build should be binary compatible within a given major version (x.y.*) of LO.
What does "binary compatible" mean (theoretically) with respecting to building LO or updating to the next point version?
Darrell
No, all of LO must be built to get the integration module out, but (in theory) the handful of integration files produced by that build should be binary compatible within a given major version (x.y.*) of LO.
What does "binary compatible" mean (theoretically) with respecting to building LO or updating to the next point version?
Darrell
Theoretically the integration files from 3.6.0 could be used with 3.6.1, for example. I'm not sure if this breaks down in practice though; LO is quite complex and I only partially understand its inner workings.
Tim
Not all, as once Debian/Ubuntu releases packaging files for LO I will be able to offer the TDE integration in binary form for those platforms. Others will have to see if their TDE packaging provider would be willing to do something similar.
That's where a "how to" would be good. How do you just build the binary files to provide integration without having to rebuild LO? Can you just build a subset of LO to get the integration binary out?
Yes, this is a good candidate for the wiki. I don't look forward to building the entire LO package set. I am interested in learning possible shortcuts to the process to use the TDE dialogs. If only the "libs" portion of LO needs to be rebuilt, or whatever equivalent that might be, then this would allow a huge sigh of relief from many of us.
Regarding OpenOffice, I am open to the same patch being offered to those developers too. Like many people I have moved to LO. Yet if OO is faster and more reliable, then perhaps I should reconsider my decision. Unfortunately for me, I don't think anybody in the Slackware community still supports OO. I don't mind building packages, because I do that with all non stock Slackware packages anyway. I just don't look forward to the time commitment to build either OO or LO. :-(
Darrell
-
Calvin Morrison -
Darrell Anderson -
David C. Rankin -
Ilya Chernykh -
Timothy Pearson