Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


I have created more patches.

It should be possible to start collaboration only for the document
ScDocShell::GetShellByNum(0)
from the contacts widget without the need to use LIBO_TUBES.
(I don't know how to find current ScDocShell)

Maybe I am supposed to just push to the branch and then revert or
correct if something is wrong ?

On 13 June 2012 22:54, Matúš Kukan <matus.kukan@gmail.com> wrote:
Also I've reduced TeleManager::get() calls a little..

This is in a separate patch now.

What do you suggest to do next ?
Well, I need to do the last school exam :-( but then..

I have passed all school exams now and I will have a look at telepathy
code for multi-user chat-rooms.
But I am going on vacation and will be back on June 27.
I hope something useful will be done before mid-term evaluations around July 11.

Thanks,
Matus

Attachment: 0001-tubes-add-File-Collaborate-menu-entry-to-launch-cont.patch
Description: Binary data

Attachment: 0002-tubes-ScDocFuncSend-store-pointer-to-TeleManager.patch
Description: Binary data

Attachment: 0003-tubes-start-collaboration-from-the-contacts-widget.patch
Description: Binary data

Attachment: 0004-tubes-extract-class-definitions-to-sendfunc.hxx.patch
Description: Binary data

Attachment: 0005-tubes-create-InitTeleManager-method.patch
Description: Binary data

Attachment: 0006-tubes-add-listen-button-to-start-TeleManager.patch
Description: Binary data


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.