Re: [Libreoffice] GSoC: Easy Hack: Make python / mail-merge debuggable

On Sat, 2011-04-09 at 02:22 +0200, Timo wrote:
> Is there a way to test the pythonfile within office ?

        So ... I notice you did in fact attach your implementation: which is
great. I was a tad worried about:

        rect = uno.createUnoStruct('com.sun.star.awt.Rectangle')
        stype, buttons = self.getFlags(flag)
        box = self.Toolkit.createMessageBox(self.Parent, rect,
                stype, buttons, title, message)

        which looks like it might create a zero sized message box quite
easily ;-) prolly need some details in the rect; -but- I couldn't get to
actually having this python script rub.

        So - then I went to prod at the mailmerge gui:

        sw/source/ui/dbui/mmoutputpage.hxx
        sw/source/ui/dbui/mailmergechildwindow.cxx

        which (apparently) includes a wonderful m_aStatusFL (a fixed line of
text - cf. the .src file) that has a constant status string that is
never updated, containing:

       Text[ en-US ] = "The connection to the outgoing mail server has
been established";

        Whether any connection has been established or not ;-)

        So - I guess one trick is perhaps to read both sides of this, so we get
a good view of the limitations of both. cf. particularly
sw/source/ui/dbui/mailmergehelper.cxx

        Another thing to do is prolly to get a much simpler python test macro
installed and running (somehow) to prototype the error dialog inside,
without it being coupled to the existing mail-merge mess.

        HTH,

                Michael.

-- 
 michael.meeks@novell.com  <><, Pseudo Engineer, itinerant idiot