Re: [Libreoffice] [PUSHED] Disable Adabas D client library
On Sun, Jun 12, 2011 at 08:17:41AM +0200, Francois Tigeot wrote: > > The attached patch disables the Adabas D client library in -master (but does > not remove the driver code itself). Patch pushed this day. -- Francois Tigeot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] Refactor PaintRangeFinder to only iterate needed entries.
I'll have a look at them. 2011/6/15 Rafael Dominguez > Only update needed entries instead of iterating over the whole list. > > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice > > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] [Bug 35673] LibreOffice 3.4 most annoying bugs
https://bugs.freedesktop.org/show_bug.cgi?id=35673 Jean-Baptiste Faure changed: What|Removed |Added Depends on||37771 --- Comment #149 from Jean-Baptiste Faure 2011-06-14 21:22:20 PDT --- Nominate bug 37771: the ridiculous password size for protected sections, make this function unusable. -- 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
Re: [Libreoffice] [GSOC] Report #3: Wizards
Hi, I'm sorry I didn't say anything yesterday but I was all day long at my university and I didn't have time to test anything. Before i went to sleep I did a "make clean && make" ( why ? I guess i didn't have anything to loose ) and now everything works correctly. it looks like the problem was fixed yesterday. Thank you anyway. @John, yeah, you're right but this time was different. Even "make clean" didn't work so at that point I decided to compile it from scratch. 2011/6/14 John LeMoyne Castle > Actually not at all sure where to clean+build to get missing uno symbols in > the log > Looks like an assortment of dirs may be involved > Help would be appreciated as it is ~necessary for me to proceed here. > -- jlc > > -- > View this message in context: > http://nabble.documentfoundation.org/GSOC-Report-3-Wizards-tp3060259p3064324.html > Sent from the Dev mailing list archive at Nabble.com. > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] [PUSHED] Replace List with vector<> in SC
Hi Rafael, All patched pushed to master, with some follow-up corrections. The rationale for my corrections are given in those commit messages. Thanks a lot! Kohei -- Kohei Yoshida, LibreOffice hacker, Calc ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] [PATCH] Refactor PaintRangeFinder to only iterate needed entries.
Only update needed entries instead of iterating over the whole list.
From 9d431bbe0227594473f8179d84389166730feb99 Mon Sep 17 00:00:00 2001
From: Rafael Dominguez
Date: Fri, 3 Jun 2011 22:31:15 -0430
Subject: [PATCH 19/21] Remove rebundant check since we already know its in boundaries.
---
sc/source/ui/view/gridwin4.cxx | 18 --
1 files changed, 8 insertions(+), 10 deletions(-)
diff --git a/sc/source/ui/view/gridwin4.cxx b/sc/source/ui/view/gridwin4.cxx
index 9441425..5046c15 100644
--- a/sc/source/ui/view/gridwin4.cxx
+++ b/sc/source/ui/view/gridwin4.cxx
@@ -804,16 +804,14 @@ void ScGridWindow::Draw( SCCOL nX1, SCROW nY1, SCCOL nX2, SCROW nY2, ScUpdateMod
for (sal_uInt16 i=0; iGetObject(i);
-if (pData)
-{
-ScRange aRef = pData->aRef;
-aRef.Justify();
-if ( aRef.aStart.Tab() >= nTab && aRef.aEnd.Tab() <= nTab )
-aOutputData.DrawRefMark( aRef.aStart.Col(), aRef.aStart.Row(),
-aRef.aEnd.Col(), aRef.aEnd.Row(),
-Color( ScRangeFindList::GetColorName( i ) ),
-sal_True );
-}
+
+ScRange aRef = pData->aRef;
+aRef.Justify();
+if ( aRef.aStart.Tab() >= nTab && aRef.aEnd.Tab() <= nTab )
+aOutputData.DrawRefMark( aRef.aStart.Col(), aRef.aStart.Row(),
+aRef.aEnd.Col(), aRef.aEnd.Row(),
+Color( ScRangeFindList::GetColorName( i ) ),
+sal_True );
}
}
}
--
1.7.3.4
From cc840f34c9ae7efef51755b41c6ca1305c527fe9 Mon Sep 17 00:00:00 2001
From: Rafael Dominguez
Date: Fri, 3 Jun 2011 22:34:55 -0430
Subject: [PATCH 20/21] Remove rebundant check since we already know its in boundaries.
---
sc/source/ui/view/gridwin.cxx |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/sc/source/ui/view/gridwin.cxx b/sc/source/ui/view/gridwin.cxx
index fb2506d..d8885a2 100644
--- a/sc/source/ui/view/gridwin.cxx
+++ b/sc/source/ui/view/gridwin.cxx
@@ -4545,7 +4545,7 @@ sal_Bool ScGridWindow::HitRangeFinder( const Point& rMouse, sal_Bool& rCorner,
// rueckwaerts suchen, damit der zuletzt gepaintete Rahmen gefunden wird
--i;
ScRangeFindData* pData = pRangeFinder->GetObject(i);
-if ( pData && pData->aRef.In(aAddr) )
+if ( pData->aRef.In(aAddr) )
{
if (pIndex) *pIndex = i;
if (pAddX) *pAddX = nPosX - pData->aRef.aStart.Col();
@@ -4709,8 +4709,6 @@ void ScGridWindow::RFMouseMove( const MouseEvent& rMEvt, sal_Bool bUp )
if (!pRangeFinder || nRFIndex >= pRangeFinder->Count())
return;
ScRangeFindData* pData = pRangeFinder->GetObject( nRFIndex );
-if (!pData)
-return;
// Mauszeiger
--
1.7.3.4
From 8fb136cdb4e24968261525ea238fc1ef1c7b1ede Mon Sep 17 00:00:00 2001
From: Rafael Dominguez
Date: Sat, 4 Jun 2011 07:30:58 -0430
Subject: [PATCH 21/21] Refactor PaintRangeFinder to only iterate needed entries.
Added a helper function PaintRangeFinderEntry.
---
sc/source/ui/inc/tabview.hxx | 13
sc/source/ui/view/tabview3.cxx | 136 +---
2 files changed, 85 insertions(+), 64 deletions(-)
diff --git a/sc/source/ui/inc/tabview.hxx b/sc/source/ui/inc/tabview.hxx
index fa0f2ed..a86a6a6 100644
--- a/sc/source/ui/inc/tabview.hxx
+++ b/sc/source/ui/inc/tabview.hxx
@@ -43,6 +43,7 @@ class ScRowBar;
class ScColBar;
class ScTabControl;
class ScTabViewShell;
+class ScRangeFindData;
class SfxPrinter;
class ScDrawView;
class SvBorder;
@@ -200,6 +201,18 @@ private:
voidSkipCursorHorizontal(SCsCOL& rCurX, SCsROW& rCurY, SCsCOL nOldX, SCsROW nMovX);
voidSkipCursorVertical(SCsCOL& rCurX, SCsROW& rCurY, SCsROW nOldY, SCsROW nMovY);
+/**
+ *
+ * @brief Update marks for a selected Range. This is a helper function
+ * for PaintRangeFinder.
+ *
+ * @param pData: Range to update for painting.
+ * @param nTab: Current tab.
+ *
+ **/
+
+voidPaintRangeFinderEntry (ScRangeFindData* pData, SCTAB nTab);
+
protected:
void UpdateHeaderWidth( const ScVSplitPos* pWhich = NULL,
const SCROW* pPosY = NULL );
diff --git a/sc/source/ui/view/tabview3.cxx b/sc/source/ui/view/tabview3.cxx
index 2b28a05..26d3d50 100644
--- a/sc/source/ui/view/tabview3.cxx
+++ b/sc/source/ui/view/tabview3.cxx
@@ -1940,6 +1940,67 @@ void ScTabView::PaintArea( SCCOL nStartCol, SCROW nStartRow, SCCOL nEndCol, SCRO
// is set (width or height changed).
}
+void ScTabView::PaintRangeFinderEntry
[Libreoffice] Fwd: development summary: year 2011, week 23 - into wiki
On Tue, Jun 14, 2011 at 12:57 PM, Petr Mladek wrote: > John LeMoyne Castle píše v Po 13. 06. 2011 v 15:27 -0700: > > Hi Petr, > ... > Anything else that should go into -wikify? > > ... The [wiki] output might be quite > similar after all. > I will add a new format option ... > Note that I use the command also the generate commit statistics for > releases. It needs to filter the log also by tags, ... > Please, keep this possibility. > Got it. > I suggest to separate the date and output format definitions. Will do > Anyway, I do not say that the current options are the best way to > define all the things. Feel free to come up with a better proposal. > A proposal that seems much better than my first thought: I will tinker with lo-commit-stat but will try to avoid major refactor: After poking at lo-commit-stat a little bit last night, I think the best plan is to write a lo-commit-wikify wrapper that converts year&week to git-args --after/since and --before/until and then calls lo-commit-stat . The wrapper would also help us catch up with an -all [weeks] arg or some such and drive lo-commit-stat through the branch tags separately. This step through the branch/tags idea was so the log output doesn't have to be rewritten or parsed. But after re-reading the note above about --log-suffix I see it may be easier that I thought... The main additions in lo-commit-stat would be output changes: wiki formatted lines (headers for sub-repos), wrapping the bug numbers to wiki external links and (maybe) log append lo-commit-wikify would create the other parts of the wiki page before and after the commit list from lo-commit-stat. I will attempt some other improvements as well re: bug numbers and ordering commits by time (so msgs like: fixed prev commit [/somebody] are clearer) I will also look at rolling-up some stats like: # commits and #changes I will not do the extraction of common to all because there is also the case of common to a few and - you have reminded me that a) it isn't trivial and b) it will all be moot if sub-repos are merged. I do see that checking all branches for the presence of a patch or patch set is valuable, but code config study/debug is different than this statistic generator CPAN provides access to handy week functions in DateTime so converting week/year to start/end dates looks straightforward > Also feel free to refactor the whole script. It is possible that you > would need another structure of the subroutines, more parameters, ... I will try to avoid this if possible - at least on the first pass. Perhaps in future after gaining experience > I am looking forward to see changes from you. > > Feel free to ask if you are in doubts with anything. OK here goes... I know I need to pull to get the latest commits. After $> ga pull -r in a repo on , do I have the commit info for *all* branches/tags? Thanks. I will put your name on it. --jlc LeMoyne Best Regards, > Petr > > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Do we need the search engines page on the options form?
Bug #38146 (https://bugs.freedesktop.org/show_bug.cgi?id=38146) says that the search engines page on the option form is unnecessary now. Before I create a patch, I want to ensure that everyone agrees we need to remove it. Thanks! Samuel Cantrell P.S. Of course, that's assuming that what I did does what I think it should...I'm waiting for the compilation to finish. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PUSHED] [PATCH] Code cleanup in impress
Nice catch, pushed! Thanks, -- Thorsten pgp1pefZ4x7Au.pgp Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [GSoC 2011][svgexport] Get selected slides in Impress left Pane
Marco wrote: > So the best compromise looks the XPropertySet interface. > A minimal implementation could be enough. > What do you think of the following one : > I like minimal things that work. :) > I would like to implemement some code to handle variable text > fields like page numbers and dates, but there is two issue: > 1) text is exported by tspan svg tags where it is set up > the position of each character; > 2) it looks that only used character glyphs are available, > so I could have the glyph for "1" but not the glyph for "2" > or I could have all glyphs for write "June 15, 2011" but not > for "July 7, 2011" and so on. > There's not much you can do here - either write out canned versions of those fields in your (normal) slide export, or switch the whole text rendering away from individual glyph positioning. Everything else will suck sooner or later. Cheers, -- Thorsten pgp6iZfdorY7M.pgp Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] component prefix change
Hi Matus, On Tue, 2011-06-14 at 22:35 +0200, Matúš Kukan wrote: > Finally I was able to call toolkit_component_ methods. Whoot :-) nice work Matus ! hopefully a learning experience too: if you can hack on LibreOffice successfully, then there is nothing too scary out there :-) > It's now possible to add prefix for component. Great. > But writeSharedLibComponentInfo in shlib.cxx does not use new prefix > parameter. Ok - I -think- that method is deprecated; we don't introspect libraries any more, we just use the XML descriptions. > I don't know if this function is used somewhere but if yes, probably > will need some change also. Nah - we're fine there :-) > What's next? So - I guess testing the toolkit components to check them, and then updating other shlib entry points that we might want to merge together. We should prolly also do an analysis of which pieces of code it makes sense to glup together: ie. what is always loaded for each component (writer, base, calc etc.) - so we can fix them first: can you look into that ? 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] [GSoC 2011][svgexport] Get selected slides in Impress left Pane
On Mon, 13 Jun 2011 10:17:07 +0200, Thorsten Behrens
wrote:
Marco wrote:
What I get is an XView object that does not support any service.
I look into the implementation code for SlideSorter and I found
out that this object, which I get, is indeed a fake XView:
its real type is a ViewShellWrapper from which we can get
a SlideSorterViewShell that owns a method to provide a
XDrawSubController interface for the view.
Hi Marco,
wow, nice detective work - and you're almost there:
Thanks! :)
Now as I said my problem is that to utilize these classes I have
to include the headers under "sd/source/ui/inc/" but they are not
delivered to "solver/340/unxlngx6.pro/inc".
So what should I do ?
Well, this is purposefully not accessible from the outside - what
you want to do, is to make that XDrawSubController available via
API. A very cheap cop-out would be to add something like
com::sun::star::beans::XMaterialHolder to the ViewShellWrapper
interfaces (add it to ViewShellWrapperInterfaceBase, and use
WeakComponentImplHelper5 instead of WeakComponentImplHelper4) - and
have the implementation hand out the result of calling
mpViewShell->CreateSubController() for that new interface.
There are surely cleaner ways to do that, API-wise, e.g. by
implementing an XPropertySet, and/or the DrawingDocumentDrawView
service - maybe Christian has suggestions on how to best evolve
that.
Well, the XMaterialHolder solution is more simple but really dirty:
it is a one shot method, imo. Once you have used it get something
you can't use it for anyrhing else.
The DrawingDocumentDrawView looks a too big service.
So the best compromise looks the XPropertySet interface.
A minimal implementation could be enough.
What do you think of the following one :
//-XPropertySet --
virtual uno::Any SAL_CALL ViewShellWrapper::getPropertyValue( const
::rtl::OUString& PropertyName )
throw (beans::UnknownPropertyException, lang::WrappedTargetException,
uno::RuntimeException)
{
uno::Any aResult;
if( aPropertyName.equalsAsciiL( RTL_CONSTASCII_STRINGPARAM(
"SubController" ) ) )
{
Reference< drawing::XDrawSubController > xSubController;
if( GetViewShell() )
{
xSubController =
this->GetViewShell()->CreateSubController();
}
aResult <<= xSubController;
}
else
{
throw beans::UnknownPropertyException();
}
return aResult;
}
// the left methods are only fake implementations
virtual uno::Reference< beans::XPropertySetInfo > SAL_CALL
ViewShellWrapper::getPropertySetInfo( )
throw (uno::RuntimeException)
{
return NULL;
}
virtual void SAL_CALL ViewShellWrapper::setPropertyValue( const
::rtl::OUString& aPropertyName, const uno::Any& aValue )
throw (beans::UnknownPropertyException, beans::PropertyVetoException,
lang::IllegalArgumentException, lang::WrappedTargetException,
uno::RuntimeException)
{
if( aPropertyName.equalsAsciiL( RTL_CONSTASCII_STRINGPARAM(
"SubController" ) ) )
throw beans::PropertyVetoException();
else
throw beans::UnknownPropertyException();
}
virtual void SAL_CALL ViewShellWrapper::addPropertyChangeListener
( const ::rtl::OUString& aPropertyName, const uno::Reference<
beans::XPropertyChangeListener >& xListener )
throw (beans::UnknownPropertyException, lang::WrappedTargetException,
uno::RuntimeException)
{
if( aPropertyName.equalsAsciiL( RTL_CONSTASCII_STRINGPARAM(
"SubController" ) ) )
return;
else
throw beans::UnknownPropertyException();
}
virtual void SAL_CALL ViewShellWrapper::removePropertyChangeListener
( const ::rtl::OUString& aPropertyName, const uno::Reference<
beans::XPropertyChangeListener >& aListener )
throw (beans::UnknownPropertyException, lang::WrappedTargetException,
uno::RuntimeException)
{
if( aPropertyName.equalsAsciiL( RTL_CONSTASCII_STRINGPARAM(
"SubController" ) ) )
return;
else
throw beans::UnknownPropertyException();
}
virtual void SAL_CALL ViewShellWrapper::addVetoableChangeListener
( const ::rtl::OUString& PropertyName, const uno::Reference<
beans::XVetoableChangeListener >& aListener )
throw (beans::UnknownPropertyException, lang::WrappedTargetException,
uno::RuntimeException)
{
if( aPropertyName.equalsAsciiL( RTL_CONSTASCII_STRINGPARAM(
"SubController" ) ) )
return;
else
throw beans::UnknownPropertyException();
}
virtual void SAL_CALL ViewShellWrapper::removeVetoableChangeListener
( const ::rtl::OUString& PropertyName, const uno::Reference<
beans::XVetoableChangeListener >& aListener )
throw (beans::UnknownPropertyException, lang::WrappedTargetException,
uno::RuntimeException)
{
if( aPropertyName.equalsAsciiL( RTL_CONSTASCII_STRI
Re: [Libreoffice] Status of unlimited conditional formatting
Hi Christoph and All, After you've suggested to me this new idea. Last month I've started to work on a new version with new dialog based on CustomProperties classes and it seems a good base to create a generic control for this sort of UI list. Work is in progress ... But the patch I've submitted on Mon, 11 Apr 2011 01:09:00 +0200 based on standard dialog box is fully operational and can be a first step with not a lot of change for the user. Regards Bob Le 14/06/11 19:41, Christoph Noack a écrit : Hi Kohei, sorry, I don't know the current status - the last mail I'm aware about is dated 20.04.2011 01:18:33 ... Rob mentioned that - concerning the new stuff - he "can't work on it these days but I will try to propose something in the begining of may." Agree, would be cool if there is a chance to continue this great work! Cheers, Christoph Am Montag, den 13.06.2011, 19:03 -0400 schrieb Kohei Yoshida: Hi there, I'm just checking to see if there is any activities on Robert's nice unlimited conditional formatting rework. I had thought that this already went into master, but then I just checked& realized that the dialog looks the same as before (i.e. only supports up to 3 conditions). Has this been stalled, or did this go in but somehow accidentally got reverted, or ... ? I'd love to get this piece included& I'd hate to see this work go unhandled. Thanks, Kohei ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] component prefix change
Hi there, Finally I was able to call toolkit_component_ methods. It's now possible to add prefix for component. But writeSharedLibComponentInfo in shlib.cxx does not use new prefix parameter. I don't know if this function is used somewhere but if yes, probably will need some change also. What's next? Matus ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] [ANNOUNCE] Branch libreoffice-3-4-1 created
Hi all, there have been created the libreoffice-3-4-1 branch. It will be used for fine tuning of the 3.4.1 bugfix release. It is based on the the tag libreoffice-3.4.1.1 for 3.4.1-rc1 release. The following rules apply: + preferably just translation or blocker fixes + only cherry-picking from libreoffice-3-4 branch + 2 additional reviews needed; 2nd reviewer pushes + no regular merges back to anything The 'libreoffice-3-4' branch is still active, will be used for the next bugfix release (3.3.2). Please read more at http://wiki.documentfoundation.org/ReleasePlan http://wiki.documentfoundation.org/Development/Branches Now, if you want to switch your clone to the libreoffice-3-4-1 branch, please do: ./g pull -r ./g checkout -b libreoffice-3-4-1 origin/libreoffice-3-4-1 Hopefully it will work for you :-) Most probably, you will also want to do (if you haven't done it yet): git config --global push.default tracking When you do git push with this, git will push only the branch you are on; ie. libreoffice-3-4-1 when you have switched to it. This will save you some git shouting at you. Happy hacking, Petr ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] [ANNOUNCE] libreoffice-3.4.1.1 tag created (3.4.1-rc1)
Hi, there have been created the libreoffice-3.4.1.1 tag for 3.4.1-rc1 release. The corresponding official builds will be available by the end of the week. See the attached list of changes against 3.4.0-final. You might switch your current 3-4 source tree to it using: ./g fetch --tags ./g checkout -b tag-libreoffice-3.4.1.1 libreoffice-3.4.1.1 See also the schedule at http://wiki.documentfoundation.org/ReleasePlan#3.4_release and release criteria at http://wiki.documentfoundation.org/Release_Criteria Best Regards, Petr + artwork + fix wrong-sized toolbar mimetype icons. (fdo#33229) [Thorsten Behrens] + replace OOo icon to LibO icon (fdo#33229) [Andras Timar] + replace OOo icons to LibO icons in Tools - Options dialog (fdo#33229) [Andras Timar] + bootstrap + fix layout of MSI Custom Install dialog (esp. German) (fdo#36990) [Andras Timar] + calc + convert split win Y coord to 16bit int before xls export (fdo#38154) [Katarina Machalkova] + correctly import sheet-local named ranges. (fdo#37947) [Kohei Yoshida] + don't cache the array size but query it dynamically. (fdo#37520) [Kohei Yoshida] + fix a crasher during HTML import on Windows. (fdo#37673) [Kohei Yoshida] + fix a crasher in datapilot table when moving a field button. (fdo#37816) [Kohei Yoshida] + fix a dialog layout problem (fdo#37985) [Andras Timar] + fix a layout problem in Export text (CSV) dialog (fdo#37418) [Andras Timar] + fix broken transposition during paste of cell range. (fdo#37356) [Kohei Yoshida] + fix for (binary import crash) (fdo#37322) [Katarina Machalkova] + fix for Correct autofilter import from ODS. (fdo#37323) [Markus Mohrhard] + fix for Insert sheets in a protected spreadsheet document (fdo#37772) [Markus Mohrhard] + fix for InsertNames->InsertAll doesn't insert anything (fdo#37548) [Markus Mohrhard] + fix for crash when copy/paste table from writer to calc (fdo#37429) [Markus Mohrhard] + fix for we don't allow points in range names any more (fdo#37872) [Markus Mohrhard] + fix incorrect font attribute lookup during XLS import. (fdo#37622) [Kohei Yoshida] + fixed cell function N. (fdo#33705) [Kohei Yoshida] + fixed selection by arrow keys around merged cells. (fdo#34214) [Kohei Yoshida] + fixed undisplayed calc page and header / footer borders (fdo#36688) [Cédric Bosdonnat] + get ISBLANK() to work correctly with external refs. (fdo#37764) [Kohei Yoshida] + prevent crash on named range deletion. (fdo#37458) [Kohei Yoshida] + prevent crash on pivot table with invalid database connection. (fdo#36719) [Norbert Thiebaud] + query the sheet for the presence of anonymous DB ranges (fdo#35345) [Katarina Machalkova] + sign number must be either 1 or -1, never 0. (fdo#37326) [Regina Henschel] + use real function objects with standard algorithms. (fdo#37226) [Kohei Yoshida] + components + fix 'Ctrl+A' in the Basic IDE. (fdo#37211) [Noel Power] + fix for Keyboard navigation broken in tools - options (fdo#37761) [Andre Schnabel] + polish branding - fix langpack mac installer icon (fdo#33229) [Thorsten Behrens] + replace OOo to TDF or %PRODUCTNAME respectively (fdo#37998) [Andras Timar] + extras + replace StarOffice icons to LibreOffice icons in Web Wizard (fdo#33229) [Andras Timar] + filters + don't crash on missing graphics (rhbz#710556) [Caolán McNamara] + fix for ( docx import of hyperlinks ) (fod#37367) [Noel Power] + revert "fix for ( docx import of hyperlinks )" (fod#37367) [Noel Power] + impress + add sanity check before dereference, (bnc#694119) [Tor Lillqvist] + libs-core + - updated license information (fdo#37001) [Andras Timar] + avoid crash when pasting a form control into chart. (fdo#37646) [Kohei Yoshida] + don't assume you'll always find a match. (fdo#37252) [Kohei Yoshida] + fix auto-correction crash (fdo#38000) [Michael Meeks] + fix for bug (fdo#37590) [Noel Power] + fixed crash when reading malformed fieldmark tags in ODT (fdo#34997) [Cédric Bosdonnat] + initialize resource manager to get verbose basic errors (fdo#37370) [Noel Power] + make style:layout-grid-snap-to-characters fit to ODF spec. (fdo#37390) [Cédric Bosdonnat] + replace "seagull" icons to LibreOffice icons (fdo#37617) [Andras Timar] + sanity checks that fix crash (fdo#36495) [Tor Lillqvist] + sanity test, seems to fix (fdo#37930) [Tor Lillqvist] + libs-extern-sys + remove added license header that caused parse error (fdo#37433) [Andras Timar] + update: Brazilian portuguese spelling dictionary & hyphenation (fdo#37671) [Andras Timar] + libs-gui + bitwise operations on signed numbers (fdo#37668) [Caolán McNamara] + don't broadcast setting changes during painting of button. (fdo#36690) [Kohei Yoshida, Noel Power] + fix a bug about presssed button state (fdo#36613) [Lucas Baudin] + fix gtk FMR on shutdown (fdo#37302) [Michael Meeks] + fixed t
Re: [Libreoffice] development summary: year 2011, week 23 - into wiki
John LeMoyne Castle píše v Po 13. 06. 2011 v 15:27 -0700: > Hi Petr, > I was thinking about cranking through the past emails like this one and > generating Development Summary pages on the wiki by hand. > Then I discovered the related easy hack -- > http://wiki.documentfoundation.org/Development/Easy_Hacks_Complete_List#Weekly_summary_.2F_Release_summary > > > I am now looking at adding a -w= (weekly wikify) option to > lo-commit-stat that would generate a suitable weekly wiki page entire. Then > only the page creation is manual labor that I can look forward to. I see > from the wiki that the bug number handling could be more powerful, there may > be ways to look more deeply at the commits and the resulting bug numbers on > the Wiki should be links back to the related bug @ xxx. There is also the > extraction of commits common to all repos. Sounds like a great plan. I am happy that someone is interested into improving the lo-commit-stat tool. > I assume that you wrote lo-commit-stat... > Anything else that should go into -wikify? I think that we still could improve unification of the messages. It currently modifies the message to use lower case in the beginning, put bugzilla numbers into brackets at the end of the message, ... The bugzilla number detection is still not perfect. For example, the sentence "fix for fdo#12345" is transformed into "fix for (fdo#12345)" which is even more dumb than the original summary ;-) Also it would be great to remove the dot "." from the end of the line if it is there... This transformations are currently done in the subroutines "search_bugs" and "standardize_summary" > Any internal tips? I guess that you need to clone the suboutines: "print_stat" and "print_summary_in_stat". The clones should generate the output that is suitable for wiki. Alternatively you might just modify them to give different result for text file and for wiki. The output might be quite similar after all. Note that bugzilla numbers are already filtered out of the original message and stored separately. It might help you to create the links from them. Hmm, it still does not detect common messages. It happens only from time to time, so I modify the generated result by "sed" manually. I am not sure if we need to implement it. It is not trivial. We are going to reduce the number of git repositories and merge most of them into a single one. Anyway, if you would want to implement it, I would compare original strings before they are unified and before the bug numbers are removed. Note the it is not enough to count the number of string occurrences because the sting might be repeated in the same module. You need to make sure that the same string is used in all git modules. You could create a hash of hashes. The global key will be the original string. It will point to hash with names of used modules. You could count the number of modules at the end and move the common strings to a separate hash. > What is standard week boundary here (i.e. Monday->Sunday)? Yes, it is from Monday to Sunday. I define the exact dates on the command line as the filter for the "git log" command, e.g. --after="2011-05-15" --before="2011-05-23" I call the it as: bin/lo-commit-stat --log-suffix=week-2011-20 . --after="2011-05-15" --before="2011-05-23" bin/lo-commit-stat --bugs --log-suffix=week-2011-20 . --after="2011-05-15" --before="2011-05-23" Note that I use the command also the generate commit statistics for releases. It needs to filter the log also by tags, ... For example, I use bin/lo-commit-stat --log-suffix=release-libreoffice-3.4.1.1 . libreoffice-libreoffice-3.4.0.2..libreoffice-3.4.1.1 bin/lo-commit-stat --bugs --log-suffix=release-libreoffice-3.4.1.1 . libreoffice-libreoffice-3.4.0.2..libreoffice-3.4.1.1 Please, keep this possibility. I suggest to separate the date and output format definitions. For example, you could add the option --wiki to force the output for wiki. If you want to define the week, just by the week number, you could add new option --week=. Then you need to implement the code that will define the correct --before and --after options for the "git log" command. Anyway, I do not say that the current options are the best way to define all the things. Feel free to come up with a better proposal. Also feel free to refactor the whole script. It is possible that you would need another structure of the subroutines, more parameters, ... > Can I put a (c) TDF header on it? Good point. We should define the copyright and license in the file. It will be part of the LO sources (bootstrap module), so I would use the preferred header, for example, see bootstrap/Module_tail_build.mk. It means that the license will be MPL 1.1 / GPLv3+ / LGPLv3+. The copyright should belong to authors. It would be me: Petr Mladek , you and other potential contributors. I am looking forward to see changes from you. Feel free to ask if you are in doubts with anything. Best Regards, Petr _
Re: [Libreoffice] [GSOC] Report #3: Wizards
Actually not at all sure where to clean+build to get missing uno symbols in the log Looks like an assortment of dirs may be involved Help would be appreciated as it is ~necessary for me to proceed here. -- jlc -- View this message in context: http://nabble.documentfoundation.org/GSOC-Report-3-Wizards-tp3060259p3064324.html Sent from the Dev mailing list archive at Nabble.com. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [GSOC] Report #3: Wizards
HI Bjoern, Xisco and all, =After smoketest fails in master like so: officeconnection.cxx:140:Assertion Test name: N12_GLOBAL__N_14TestE::test setUp() failed - equality assertion failed - Expected: 2 - Actual : 0 Failures !!! Run: 1 Failure total: 1 Failures: 1 Errors: 0 (which looks like failure to connect to soffice) * * with additional message (from gdb) in a message box: * * The application cannot be started. loading component library failed: file:///home/jlcastle/LibOdev/skky/solver/350/unxlngi6.pro/installation/opt/program/../basis-link/program/liboffaccli.so * =attempt to run soffice from solver fails like so: (no /install symlink available) ~/LibOdev/skky/solver/350/unxlngi6.pro/installation/opt/program$ ./soffice LibreOffice: Using system memory allocator. LibreOffice: This is for debugging only. To disable, LibreOffice: unset the environment variable G_SLICE. LibreOffice: Using system memory allocator. LibreOffice: This is for debugging only. To disable, LibreOffice: unset the environment variable G_SLICE. terminate called after throwing an instance of 'com::sun::star::loader::CannotActivateFactoryException' * >From bug 37290, this commit http://cgit.freedesktop.org/libreoffice/components/commit/?h=feature/gsoc2011_wizards&id=264c9ed93f3d338f6aee84310135569710705783 seems to be in master as well (from switching branch selector at cgit.freedesktop) Will keep working to get ure symbols into the gdbtrace.log for specifics from connector.uno.so, uuresolver.uno.so, unoexceptionprotector.so, etc. smoketest gdb log in pastebin -- http://pastebin.com/bKt0Uvnv -- jlc -- View this message in context: http://nabble.documentfoundation.org/GSOC-Report-3-Wizards-tp3060259p3064225.html Sent from the Dev mailing list archive at Nabble.com. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [Libreoffice-ux-advise] style selector / abandonware ...
Hi Michael, cool, looks like a _very_ promising start :-) Am Dienstag, den 14.06.2011, 11:04 +0100 schrieb Michael Meeks: > Hi guys, > > I have to task switch for a week or so now, so I just dumped my latest > (hackish) re-hash of the style preview / selection pane I was working on > here (click the navigator paint-can): > > http://people.gnome.org/~michael/data/2011-06-14-style-preview.diff > > It looks like this: > > http://people.gnome.org/~michael/images/2011-06-14-style-preview.png Okay, so at the moment it is "just" a matrix like preview in a separate window. Each of the previews seems to render the name of the style in 100% size, centered. Correct? > I had a few questions: > > a) ux guys - would you like a side-bar a bit like this ? > could we make that a 'mode' of the style navigator ? > + what interaction modes would work well here: > mouse-over style preview ? Some QuickThoughts (tm): * Toolbar Drop-Down for Paragraph Styles (m x n matrix instead of a plain list) * Paragraph Styles in the Stylist (preview for each list entry, for all modes but hierarchical view) * Character Styles in the Stylist (preview for each list entry, for all modes but hierarchical view) Of course, the devil is in the details - we want to keep this list manageable (size, number of items), the styles (easily) editable, the stuff accessible (keyboard nav etc.). So, these thoughts are a start, I think. > + context specific style/palette adaption ? Mmh, what do you have in mind - we already have some (more or less working) context specific context adaptations in the Stylist. > > b) any more thoughts on that ? > > c) since this is essentially a stolen (re-factored) 'preview' > widget from the existing 'style' dialog - I wondered ... > are there other easy-to-steal preview widgets that we can > re-use to make applying these things easier ? > [ perhaps border selectors ? ]. Mmh, don't know whether this fits technically (we'll need that anyway, soon *g*), but how about the new toolbar drop-down selectors in Impress. See: http://www.youtube.com/watch?v=WnfZlYU0SNc (interesting part starts exactly at minute one). Furthermore, the slide sorter preview, or the master slide preview might be other candidates. > d) Do we have an enterprising hacker wanting to play with > creating a more attractive navigator / style pane here? > + it is slightly complicated due to the shared > nature of sfx's style code between all components > > Thoughts ? Hackers? :-) Cheers, Christoph ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] [REVIEW] Regression from 3.3
Hi there, I would like to cherry-pick the following commit on master http://cgit.freedesktop.org/libreoffice/calc/commit/?id=478533a86b29341e00128fb6eda8237dfb9cf3cf to the -3-4 branch (and -3-4-1 if it makes sense). There is no bug report associated with this (yet), but this accidentally changes the behavior of ScMatrix pre- and post-refactoring. When GetString() is called on an empty element, the old code would return an empty string, but the new code sets an error instead. I made this change, and this change was unintentional. GetString() should still return an empty string when called on an empty element. Review & sign-off appreciated. -- Kohei Yoshida, LibreOffice hacker, Calc ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] Removes find/replace dialog button from standard toolbar
Hi Caolan, hi Sam! Caolan, I think the proposal by Sam will work well ... and if we need a button, then it should rather open the search toolbar. For the next step in the "Evolution of Search" (tm) I proposed to provide the S&R-Dialog via an "Advanced ..." button (the final naming may differ), see: http://lists.freedesktop.org/archives/libreoffice-ux-advise/2011-June/31.html So, if we can improve the find bar a bit, the overall experience should be greatly improved. Cheers, Christoph Am Dienstag, den 14.06.2011, 07:30 -0700 schrieb Samuel Cantrell: > Caolán, > > It's true that the find button allows for access to the find/replace > dialog, which allows more functionality. Do more people use the find > button, or use the menus to find the find/replace dialog though? I > know I use the menus, however, it would obviously be fallacious to > assume that my use-case is the majority one. > > I did only hide the find button so that any user could add it back to > the toolbar if he so wished. > > Thanks for your comment! > > Samuel Cantrell > > On Tue, Jun 14, 2011 at 7:09 AM, Caolán McNamara wrote: > > On Sat, 2011-06-11 at 07:35 -0700, Samuel Cantrell wrote: > >> These patches remove the find/replace dialog button from Calc and > >> Writer (per > >> http://wiki.documentfoundation.org/Development/Default_UI_Improvements). > >> As we have the new find toolbar, these buttons seem unnecessary. > > > > hmm, well the find toolbar only finds, while the button to launch > > find/replace allows replacement as well. > > > > C. > > > > ___ > > LibreOffice mailing list > > LibreOffice@lists.freedesktop.org > > http://lists.freedesktop.org/mailman/listinfo/libreoffice > > > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Status of unlimited conditional formatting
Hi Kohei, sorry, I don't know the current status - the last mail I'm aware about is dated 20.04.2011 01:18:33 ... Rob mentioned that - concerning the new stuff - he "can't work on it these days but I will try to propose something in the begining of may." Agree, would be cool if there is a chance to continue this great work! Cheers, Christoph Am Montag, den 13.06.2011, 19:03 -0400 schrieb Kohei Yoshida: > Hi there, > > I'm just checking to see if there is any activities on Robert's nice > unlimited conditional formatting rework. I had thought that this > already went into master, but then I just checked & realized that the > dialog looks the same as before (i.e. only supports up to 3 conditions). > > Has this been stalled, or did this go in but somehow accidentally got > reverted, or ... ? > > I'd love to get this piece included & I'd hate to see this work go > unhandled. > > Thanks, > > Kohei > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] Removes find/replace dialog button from standard toolbar
Caolán, It's true that the find button allows for access to the find/replace dialog, which allows more functionality. Do more people use the find button, or use the menus to find the find/replace dialog though? I know I use the menus, however, it would obviously be fallacious to assume that my use-case is the majority one. I did only hide the find button so that any user could add it back to the toolbar if he so wished. Thanks for your comment! Samuel Cantrell On Tue, Jun 14, 2011 at 7:09 AM, Caolán McNamara wrote: > On Sat, 2011-06-11 at 07:35 -0700, Samuel Cantrell wrote: >> These patches remove the find/replace dialog button from Calc and >> Writer (per >> http://wiki.documentfoundation.org/Development/Default_UI_Improvements). >> As we have the new find toolbar, these buttons seem unnecessary. > > hmm, well the find toolbar only finds, while the button to launch > find/replace allows replacement as well. > > C. > > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] Support font effects "Capitals", "Lowercase" and "Title" in HTML export
On Sun, 2011-06-12 at 19:17 +0300, Harri Pitkänen wrote: > By the way, this change does nothing if HTML compatibility option (Options -> > Load/Save -> HTML Compatibility) is set to Netscape Navigator. This is not > nice since it seems to be the default... I would think that removing these > obsolete browsers from compatibility options would be the best thing to do. > It > should be possible to serve all modern browsers with single html output, or > am > I missing something? Nah, the html export is just archaic. Yeah, it doesn't make much sense IMO anymore to have all the compatibility foo in there, single unified html output would be better. Only catch might be that our html import isn't awesome either, and probably works best with the default export settings :-) C. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] [PUSHED] Re: [PATCH] Support font effects "Capitals", "Lowercase" and "Title" in HTML export
On Sun, 2011-06-12 at 19:03 +0300, Harri Pitkänen wrote: > Export Writer font effects "Capitals", "Lowercase" and "Title" (see Format -> > Character -> Font effects) to HTML using CSS text-transform property. Looks good to me, pushed, thanks for this. C. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] Removes find/replace dialog button from standard toolbar
On Sat, 2011-06-11 at 07:35 -0700, Samuel Cantrell wrote: > These patches remove the find/replace dialog button from Calc and > Writer (per > http://wiki.documentfoundation.org/Development/Default_UI_Improvements). > As we have the new find toolbar, these buttons seem unnecessary. hmm, well the find toolbar only finds, while the button to launch find/replace allows replacement as well. C. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [GSOC] Report #3: Wizards
On Mon, 13 Jun 2011 21:41:17 +0200 Xisco Faulí wrote: > After i did my first commit last tuesday i worked for 2 days on > adding the button listeners and fixing some errors: > http://cgit.freedesktop.org/libreoffice/components/?h=feature%2Fgsoc2011_wizards > Then, > on Thursday and on Friday I started to optimize it ( it takes 10 sec > for showing the dialog ) but I made a mess in the git tree ( git and > I aren't good friends ) and I decided eventually to delete the source > and download it again from scratch. Now I already have it compiled > but when I run libo I get this error: terminate called after throwing > an instance of > 'com::sun::star::loader::CannotActivateFactoryException'. Any idea ? Some UNO component cant be initialized: http://api.openoffice.org/docs/common/ref/com/sun/star/loader/CannotActivateFactoryException.html most likely you are missing some libraries in the install or they are at the wrong location. Is that with the current state of the gsoc2011_wizards feature branch? Best Regards, Bjoern -- https://launchpad.net/~bjoern-michaelsen ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Fwd: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
On Tue, 2011-06-14 at 14:09 +0100, Caolán McNamara wrote: > Sure, though personally I'd just use createTempFile throughout to keep > things simple. The same opinion here, so that people that want to hack something similar don't find several ways and try to figure out the rationale. F. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Duplicate code: libs-core/framework/test/typecfg/cfgview.cxx
On Thu, 2011-06-02 at 22:07 +0200, Chr. Rossmanith wrote:
> Hi,
>
> while waiting for a successful build I had a look at cfgview.cxx which
> has two very similar methods
> CFGView::impl_generateFilter{Modul}?ListHTML(). Shall I continue or is
> it "only" a test?
Yeah, that framework/test dir isn't built. I'm unconvinced that its
recoverable to turn into a modern cppunit test. I suggest you go ahead
and git rm -rf that dir and just ditch it.
C.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Fwd: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
On Sat, 2011-06-11 at 15:37 +0200, Julien Nabet wrote: > So I thought this : > 1) for common part between Windows and other systems (Unix/Linux/BSD > and Mac) or for Windows specific, only createTempFile should be used. > 2) for Unix/Linux/BSD and Mac only part, mkstemp/mktemp should be used > (to avoid overhead) > > So tmpnam shouldn't be used at all. > > Is this ok ? Sure, though personally I'd just use createTempFile throughout to keep things simple. C. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Notice of absence
Hi there, Just FYI, I'll be away from June 16 til July 6. I'll be back on July 7. I may be checking my emails for my gmail accounts, but no idea how often I'll be checking mails. Kohei -- Kohei Yoshida, LibreOffice hacker, Calc ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [libreoffice-accessibility] Re: Backend APIs to work in headless mode
On Tue, 2011-06-14 at 15:43 +0530, Sanjeev Kumar Mittal wrote: > I wonder if I could use the Libre Jars in the same project with > minimum changes. It should "just work", or with minimal changes like path changes or so. > My fear is I might have to rewrite the complete JodConeverter project > that exploites the Libre functionality in the same way as OO. Shouldn't be a big effort, about as much as say OpenOffice.org 3.2 to 3.3 C. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [libreoffice-accessibility] Re: Backend APIs to work in headless mode
Hi, Thanks for the info. I am able to successfully convert word doc to PDF using JodConeverter with OO in background. However, with the same project setting & jars, I wonder if I could use the Libre Jars in the same project with minimum changes. My fear is I might have to rewrite the complete JodConeverter project that exploites the Libre functionality in the same way as OO. It would be great if some one have already done so, and I could benefit from that project code/Jars that uses Libre Office in the backend rather than OO. Thanks a lot, sanjeev On Tue, May 10, 2011 at 9:32 AM, Jason White wrote: > Sanjeev Kumar Mittal wrote: > >I am using JODConverter from Google project along with Open Office at the > >backend. > > > >I wanted to know if Libre Office suite have any headless operation mode > >also? > > Yes, it does. I am using unoconv with LibreOffice to convert documents into > HTML for reading with text-based browsers such as W3M, Emacs/W3, Lynx, etc. > > This works even without an X server running, which is how I normally use > it; I > do almost all of my work in console sessions and I only run X when I need > it. > > Unless you're doing this for accessibility-related reasons, you're asking > on > the wrong mailing list, incidentally; this list is devoted to issues of > disability access. > > In my case, the reason for using unoconv is partly accessibility-related > anyway. > > > > -- > Unsubscribe instructions: E-mail to accessibility+h...@libreoffice.org > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.libreoffice.org/www/accessibility/ > All messages sent to this list will be publicly archived and cannot be > deleted > > -- Best Regards, Sanjeev Kumar Mittal ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] style selector / abandonware ...
Hi guys, I have to task switch for a week or so now, so I just dumped my latest (hackish) re-hash of the style preview / selection pane I was working on here (click the navigator paint-can): http://people.gnome.org/~michael/data/2011-06-14-style-preview.diff It looks like this: http://people.gnome.org/~michael/images/2011-06-14-style-preview.png I had a few questions: a) ux guys - would you like a side-bar a bit like this ? could we make that a 'mode' of the style navigator ? + what interaction modes would work well here: mouse-over style preview ? + context specific style/palette adaption ? b) any more thoughts on that ? c) since this is essentially a stolen (re-factored) 'preview' widget from the existing 'style' dialog - I wondered ... are there other easy-to-steal preview widgets that we can re-use to make applying these things easier ? [ perhaps border selectors ? ]. d) Do we have an enterprising hacker wanting to play with creating a more attractive navigator / style pane here? + it is slightly complicated due to the shared nature of sfx's style code between all components Thoughts ? Michael. -- michael.me...@novell.com <><, Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] hwpfilter
On Tue, 2011-06-14 at 10:04 +0100, Caolán McNamara wrote: > There are two .hwp files there, one old format 3.0 which does work, > eventually anyway, and one (I think new format) that doesn't. Which reminds me, Wikipedia says these file formats documentation is available at http://en.wikipedia.org/wiki/Hangul_%28word_processor% 29#cite_note-2 Its all in Korean however, so perhaps an interesting semi-fun task for someone proficient in Korean to poke around at. C. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Fwd: Formula Crash
On Tue, 2011-06-14 at 16:56 +0800, jeffrey chang wrote: > Here is the gdb error log for when I call the division fraction button > first thing on LO3.4 Formula on OpenSuse. Seems like the application > is throwing a SIGSEV. backtrace looks like https://bugs.freedesktop.org/show_bug.cgi?id=37668 I believe the fix for the immediate cause of the crash in now in the 3-4 branch for 3.4.1, but not in 3.4.0. That said, I don't know why we end up in glyph fallback there so deep in math. C. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Duplicate code: hwpreader.cxx
On Wed, 2011-06-08 at 21:19 +0200, Chr. Rossmanith wrote: > Hi, > > I've found a .hwp document here > http://openoffice.org/bugzilla/show_bug.cgi?id=31091, tried to open it > but only get a blank page - no error message. Where would I start to > analyze what's going wrong? If hwpfilter is not working, maybe it's no > use to improve the code... There are two .hwp files there, one old format 3.0 which does work, eventually anyway, and one (I think new format) that doesn't. There wasn't a typedetection implemented for that filter to make it do the right thing automatically. So I quickly stuck one in there to detect the supported formats, so the "hangul97-3.0.hwp" example should work out of the box now. So I gbuildized hwpfilter, added correct typedetection and a cppunit test to ensure that "hangul97-3.0.hwp" remains working. C. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Fwd: Formula Crash
Here is the gdb error log for when I call the division fraction button first
thing on LO3.4 Formula on OpenSuse. Seems like the application is throwing a
SIGSEV.
Also, Formula seems to shut down inexplicably when I call +-{}>}.
(ie placing the formula elements within the <> rather than replacing the <>
with the formula. Can anyone confirm this problem? I discovered this when
looking around bug 32062.
Thanks
--
--Jeffrey Chang
GNU gdb (GDB) SUSE (7.2-3.3)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i586-suse-linux".
For bug reporting instructions, please see:
Re: [Libreoffice] About fd and session ends.
On Mon, 2011-06-13 at 22:13 +0200, Stef Bon wrote: > I agree totally. But you have to offer a "safe remove" command. > What do you do for SUSE? direct io? We don't offer a safe-remove command; and we do very aggressive write-through, so we do not cache much data on hot-pluggable file-systems: once the USB key light goes out - you're good to unplug. That at least is the theory ;-) ATB, Michael. -- michael.me...@novell.com <><, Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
