[prev in list] [next in list] [prev in thread] [next in thread]
List: calligra-devel
Subject: Re: GSoC idea
From: Smit Patel <smitpatel24 () gmail ! com>
Date: 2012-02-23 16:52:47
Message-ID: CAA-Pzow6FQThMWo5vANPr77RyeK9GzT146uqQrSG7Ej=b=rcOw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Thu, Feb 23, 2012 at 3:36 PM, Sebastian Sauer <mail@dipe.org> wrote:
> **
> On 02/23/2012 01:31 PM, Smit Patel wrote:
>
> Hi everyone,
>
> I'd like to propose a GSoC project. Here's the brief description about
> project idea.
> Provide a dbus API that provides an generic interface that can be used by
> external bibliography engines (xbiblio, kbibtex, bibus)
>
>
> dbus is optional[1] and so would be everything that depends on it. So, why
> dbus? Why not just a plugin? If it should be in another process (stability,
> long-running things, shared among Words-processes, etc) then why not for
> example QLocalServer?
>
If dbus is not available for windows and OSX then we can rule that out. We
can consider what bibliography engines like bibus, kbibtex etc are using
for the same thing with LO and MS Office. For other options I haven't try
studying them in detail. We'll discuss about it on IRC.
> Calligra words doesn't have a good way to manage references. These
> engines can manage references and insert bibliography using interface
> provided.
>
>
> Guess there would be quit some work needed in core-code to make it proper
> update references on loading/saving/editing. Does what ODF specifies cover
> what you propose? If yes then it should maybe not be optional and no be
> available for so many platforms[1]. If not then how to you plan to keep
> interoperability? I think your proposal includes loading/saving?
>
Yes. I need to change some core-code but bibliography engine is in place.
So it won't be a big problem. I think the confusion is because I haven't
merged my branch words-references-bibliography-smit with master. My branch
has all the changes done so far for bibliography support.
> I like comments and hints for this project idea.
>
>
> I like the idea (except the dbus-part) and while I think there are many
> things that could be done within a gsoc and have a higher priority I think
> it would make a good gsoc-proposal.
>
> [1] not available on Symbian, Android, OSX and Windows at least
>
>
[Attachment #5 (text/html)]
<font><font face="verdana,sans-serif"><br></font></font><br><div \
class="gmail_quote">On Thu, Feb 23, 2012 at 3:36 PM, Sebastian Sauer <span \
dir="ltr"><<a href="mailto:mail@dipe.org">mail@dipe.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><u></u>
<div bgcolor="#ffffff" text="#000000"><div class="im">
On 02/23/2012 01:31 PM, Smit Patel wrote:
<blockquote type="cite">
<span>Hi everyone,</span><br>
<br>
<span>I'd like to propose a </span><span>GSoC</span><span> project.
Here's the brief description about project idea.</span>
<div>
<span>Provide a dbus API that provides an generic interface that
can be used by external bibliography engines (xbiblio,
kbibtex, bibus)</span></div>
</blockquote>
<br></div>
dbus is optional[1] and so would be everything that depends on it.
So, why dbus? Why not just a plugin? If it should be in another
process (stability, long-running things, shared among
Words-processes, etc) then why not for example QLocalServer?<div \
class="im"></div></div></blockquote><div> </div><div>If dbus is not available for \
windows and OSX then we can rule that out. We can consider what bibliography engines \
like bibus, kbibtex etc are using for the same thing with LO and MS Office. For other \
options I haven't try studying them in detail. We'll discuss about it on \
IRC.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div bgcolor="#ffffff" text="#000000"><div class="im"> \
<blockquote type="cite">
<div> Calligra words doesn't have a good way to manage references.
These engines can manage references and insert bibliography
using interface provided. </div>
</blockquote>
<br></div>
Guess there would be quit some work needed in core-code to make it
proper update references on loading/saving/editing. Does what ODF
specifies cover what you propose? If yes then it should maybe not be
optional and no be available for so many platforms[1]. If not then
how to you plan to keep interoperability? I think your proposal
includes loading/saving?</div></blockquote><div><br></div><div>Yes. I need to \
change some core-code but bibliography engine is in place. So it won't be a big \
problem. I think the confusion is because I haven't merged my branch \
words-references-bibliography-smit with master. My branch has all the changes done so \
far for bibliography support.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div bgcolor="#ffffff" text="#000000"><div \
class="im"><blockquote type="cite">
<div> I like comments and hints for this project idea. </div>
<div> <br>
</div>
</blockquote>
<br></div>
I like the idea (except the dbus-part) and while I think there are
many things that could be done within a gsoc and have a higher
priority I think it would make a good gsoc-proposal.<br>
<br>
[1] not available on Symbian, Android, OSX and Windows at least<br>
<br>
</div>
</blockquote></div><br>
_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic