[prev in list] [next in list] [prev in thread] [next in thread]
List: calligra-devel
Subject: Re: GSoC idea
From: Sebastian Sauer <mail () dipe ! org>
Date: 2012-02-23 13:36:07
Message-ID: 4F4640C7.7090900 () dipe ! org
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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?
> 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?
>
> 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)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 02/23/2012 01:31 PM, Smit Patel wrote:
<blockquote
cite="mid:CAA-PzozeaC9zMXkkWPt51+etTd7trdb2dZz0Wnd_Of7Mmaxqkg@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<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>
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?<br>
<br>
<blockquote
cite="mid:CAA-PzozeaC9zMXkkWPt51+etTd7trdb2dZz0Wnd_Of7Mmaxqkg@mail.gmail.com"
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>
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?<br>
<br>
<blockquote
cite="mid:CAA-PzozeaC9zMXkkWPt51+etTd7trdb2dZz0Wnd_Of7Mmaxqkg@mail.gmail.com"
type="cite">
<div> <br>
</div>
<div> I like comments and hints for this project idea. </div>
<div> <br>
</div>
</blockquote>
<br>
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>
</body>
</html>
_______________________________________________
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