[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-24 4:51:24
Message-ID: 4F47174C.2020004 () dipe ! org
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 02/23/2012 05:52 PM, Smit Patel wrote:
>
> On Thu, Feb 23, 2012 at 3:36 PM, Sebastian Sauer <mail@dipe.org
> <mailto: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.
I just had a quick look at xbiblio, kbibtex:and bibus. Am I right that
none of them comes with a dbus daemon? So, I seriously ask myself why
you like to drag dbus in? Why not just do it the same way it's done in
e.g. Kile (I assume linking against a lib)?
I just bring up the topic cause your proposal explicit names dbus but
does not name a reason why and for what. So, I suggest to either make
very clear in your proposal for what and why you will use dbus XOR
change the proposal do not make that given but turn it into something
you need to investigate/research during the gsoc-time to see if that's
the best approach. So, something like "investigate and research
technology-choices to integrate bibliography engines like xbiblio,
kbibtex and bibus into Calligra".
> 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.
Ah, good to know[1] :) I would definitively add to your proposal
references of the work you did already. Its a *huge* advantage your
proposal has over all other proposals that you already did some of the
work. So, imho your proposal should include some words what you have
already and how exactly you like to spend the gsoc-time to improve that.
[1] Well, I did know you worked on that topic before but have no clue in
what state that work is. Means what is done and what you like to do
during the gsoc-time. But yes, that's maybe a bit to much input for a
first "gsoc idea" mail but more material for the final proposal. In any
case lot of thanks for hacking on that important topic!
[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 05:52 PM, Smit Patel wrote:
<blockquote
cite="mid:CAA-Pzow6FQThMWo5vANPr77RyeK9GzT146uqQrSG7Ej=b=rcOw@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<br>
<div>On Thu, Feb 23, 2012 at 3:36 PM, Sebastian Sauer <span><<a
moz-do-not-send="true" href="mailto:mail@dipe.org">mail@dipe.org</a>></span>
wrote:<br>
<blockquote>
<div>
<div> 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>
</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.</div>
</div>
</blockquote>
<br>
<span>I just had a quick look at xbiblio, kbibtex:and bibus</span>.
Am I right that none of them comes with a dbus daemon? So, I
seriously ask myself why you like to drag dbus in? Why not just do
it the same way it's done in e.g. Kile (I assume linking against a
lib)?<br>
<br>
I just bring up the topic cause your proposal explicit names dbus
but does not name a reason why and for what. So, I suggest to either
make very clear in your proposal for what and why you will use dbus
XOR change the proposal do not make that given but turn it into
something you need to investigate/research during the gsoc-time to
see if that's the best approach. So, something like "investigate and
research technology-choices to integrate <span>bibliography engines
</span>like <span>xbiblio, kbibtex and bibus</span> into Calligra".<br>
<br>
<blockquote
cite="mid:CAA-Pzow6FQThMWo5vANPr77RyeK9GzT146uqQrSG7Ej=b=rcOw@mail.gmail.com"
type="cite">
<div>
<div>For other options I haven't try studying them in detail.
We'll discuss about it on IRC.</div>
<blockquote>
<div>
<div>
<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>
</div>
</blockquote>
<br>
Ah, good to know[1] :) I would definitively add to your proposal
references of the work you did already. Its a *huge* advantage your
proposal has over all other proposals that you already did some of
the work. So, imho your proposal should include some words what you
have already and how exactly you like to spend the gsoc-time to
improve that.<br>
<br>
[1] Well, I did know you worked on that topic before but have no
clue in what state that work is. Means what is done and what you
like to do during the gsoc-time. But yes, that's maybe a bit to much
input for a first "gsoc idea" mail but more material for the final
proposal. In any case lot of thanks for hacking on that important
topic!<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