[prev in list] [next in list] [prev in thread] [next in thread] 

List:       calligra-devel
Subject:    Re: Roadmap to Calligra Mini
From:       Sebastian Sauer <mail () dipe ! org>
Date:       2013-06-17 19:11:40
Message-ID: 51BF5F6B.50207 () dipe ! org
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On 06/18/2013 12:50 AM, Shantanu Tushar Jha wrote:
> During the sprint we started work on reusable Qt Quick components for
> Calligra. The idea was to make it easy for people to create apps as they'll
> just have to use the right QML component and everything else will just work
> magically. All this lies in the branch active-calligratouch-shantanu (which
> adds a new toplevel dir qtquick/ in calligra and then active/ uses those
> components to show docs). It has couple of hardcoded paths, but works very
> well with just this code (Test.qml) -
> 
> import QtQuick 1.1
> import org.calligra.CalligraComponents 0.1 as Calligra
> 
> Flickable {
> Calligra.PresentationCanvas {
> id: canvas
> source: "presentation.odp"
> anchors.fill: parent
> }
> }
> 
> There are similar components for Text docs, spreadsheets as well. This
> should save a lot of reinvention when trying to render documents on a QML
> based UI.

Yep, Calligra Active was even the starting point when I begun that. I 
switched away when going full threaded cause that was requiring a 
complete different architecture and design. In Coffice all of Calligra 
runs in another thread then the UI/QML. That means all operations are 
asynchronous in Coffice unlike in Active and Calligra will never be able 
to block the UI. Also I bundle all plugins into one plugin, all filters 
into one filter and delay loading in Coffice plus don't use KDE 
plugin-lookup (aka sycoca) cause sycoca isn't present, I rewrote the kde 
factory/plugin/kpart stuff, etc. pp.

Since all that happened Qt5 progressed and meanwhile (means not so long 
ago) work on scenegraph-based QTextDocument/QTextEdit landed. So, for 
Qt5 there may an option (with very likely lots of additional work needed 
for our use-cases) to solve the no-go all-in-one-thread problem at 
another level. On the other hand there would still be work needed to get 
potential long-blocking operations like loading threaded which is all 
solved in Coffice as of today already.... Well, we will see.

> 
> 
> On Mon, Jun 17, 2013 at 2:22 PM, Sebastian Sauer <mail@dipe.org> wrote:
> 
> > Aloha,
> > 
> > so you may have noticed that I did land last few weeks work in the
> > Coffice-branch. I am giving here a short status-update on the work done and
> > the work I plan to do towards releasing the first release of the Calligra
> > Mini successor of Coffice. Note that this is only my personal roadmap and
> > subject to change anytime. So, if you think there is something missing,
> > something not so important, etc. please just raise voice and I can shift.
> > 
> > === Work published ===
> > 
> > Current version (as published in Google Play) is 1.5. 1.5 is the first
> > release I not see as "alpha release" but as "beta release". Its stable,
> > fast, loads and displays ODT/DOC/DOCX. Its "good enough to be usable" but
> > there is still plenty to do from my pov.
> > 
> > === Work landed ===
> > 
> > What I did withint last ~2 months is to focus on 2 areas:
> > 
> > 1) SailfishOS version.
> > 
> > So far Coffice builds and runs on Linux desktop and Android. SailfishOS is
> > the second mobile SDK targetted (by me). It compiles and runs but doesn't
> > display, etc. yet. Remaining work is on the UI (Silicia components) only.
> > 
> > 2) Sheets integration.
> > 
> > Calligra Sheets compiles now using the fake-lib on desktop, Android and
> > SailfishOS. It compiles and links but not more. Means missing here is the
> > UI-integration.
> > 
> > === Work to do ===
> > 
> > What I would like to do before releasing a first Calligra Mini version is
> > to finish Sheets and make loading and displaying a ODS file proper working.
> > 
> > That's the only thing I have atm on my table. Estimate would be in the
> > range of <3 months depending on the amount of spare time that is left.
> > 
> > === Feedback ===
> > 
> > If there is anything you think that is missing from current version 1.5
> > (as available in Google Play), that needs to be changed/added/removed
> > before a Calligra Mini x.y release then please let me know now. Thanks in
> > advance :)
> > ______________________________**_________________
> > calligra-devel mailing list
> > calligra-devel@kde.org
> > https://mail.kde.org/mailman/**listinfo/calligra-devel<https://mail.kde.org/mailman/listinfo/calligra-devel>
> >  
> 
> 
> 
> 
> _______________________________________________
> calligra-devel mailing list
> calligra-devel@kde.org
> https://mail.kde.org/mailman/listinfo/calligra-devel


[Attachment #5 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 06/18/2013 12:50 AM, Shantanu Tushar
      Jha wrote:<br>
    </div>
    <blockquote
cite="mid:CABQ4Km-Y1qU9Ob-t0HM6wvB8UpVpWk_3wUE_L_Dxf4UOuz_NBg@mail.gmail.com"
      type="cite">
      <pre wrap="">During the sprint we started work on reusable Qt Quick components \
for Calligra. The idea was to make it easy for people to create apps as they'll
just have to use the right QML component and everything else will just work
magically. All this lies in the branch active-calligratouch-shantanu (which
adds a new toplevel dir qtquick/ in calligra and then active/ uses those
components to show docs). It has couple of hardcoded paths, but works very
well with just this code (Test.qml) -

import QtQuick 1.1
import org.calligra.CalligraComponents 0.1 as Calligra

Flickable {
    Calligra.PresentationCanvas {
        id: canvas
        source: "presentation.odp"
        anchors.fill: parent
    }
}

There are similar components for Text docs, spreadsheets as well. This
should save a lot of reinvention when trying to render documents on a QML
based UI.</pre>
    </blockquote>
    <br>
    Yep, Calligra Active was even the starting point when I begun that.
    I switched away when going full threaded cause that was requiring a
    complete different architecture and design. In Coffice all of
    Calligra runs in another thread then the UI/QML. That means all
    operations are asynchronous in Coffice unlike in Active and Calligra
    will never be able to block the UI. Also I bundle all plugins into
    one plugin, all filters into one filter and delay loading in Coffice
    plus don't use KDE plugin-lookup (aka sycoca) cause sycoca isn't
    present, I rewrote the kde factory/plugin/kpart stuff, etc. pp.<br>
    <br>
    Since all that happened Qt5 progressed and meanwhile (means not so
    long ago) work on scenegraph-based QTextDocument/QTextEdit landed.
    So, for Qt5 there may an option (with very likely lots of additional
    work needed for our use-cases) to solve the no-go all-in-one-thread
    problem at another level. On the other hand there would still be
    work needed to get potential long-blocking operations like loading
    threaded which is all solved in Coffice as of today already....
    Well, we will see.<br>
    <br>
    <blockquote
cite="mid:CABQ4Km-Y1qU9Ob-t0HM6wvB8UpVpWk_3wUE_L_Dxf4UOuz_NBg@mail.gmail.com"
      type="cite">
      <pre wrap="">


On Mon, Jun 17, 2013 at 2:22 PM, Sebastian Sauer <a class="moz-txt-link-rfc2396E" \
href="mailto:mail@dipe.org">&lt;mail@dipe.org&gt;</a> wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">Aloha,

so you may have noticed that I did land last few weeks work in the
Coffice-branch. I am giving here a short status-update on the work done and
the work I plan to do towards releasing the first release of the Calligra
Mini successor of Coffice. Note that this is only my personal roadmap and
subject to change anytime. So, if you think there is something missing,
something not so important, etc. please just raise voice and I can shift.

=== Work published ===

Current version (as published in Google Play) is 1.5. 1.5 is the first
release I not see as "alpha release" but as "beta release". Its stable,
fast, loads and displays ODT/DOC/DOCX. Its "good enough to be usable" but
there is still plenty to do from my pov.

=== Work landed ===

What I did withint last ~2 months is to focus on 2 areas:

1) SailfishOS version.

So far Coffice builds and runs on Linux desktop and Android. SailfishOS is
the second mobile SDK targetted (by me). It compiles and runs but doesn't
display, etc. yet. Remaining work is on the UI (Silicia components) only.

2) Sheets integration.

Calligra Sheets compiles now using the fake-lib on desktop, Android and
SailfishOS. It compiles and links but not more. Means missing here is the
UI-integration.

=== Work to do ===

What I would like to do before releasing a first Calligra Mini version is
to finish Sheets and make loading and displaying a ODS file proper working.

That's the only thing I have atm on my table. Estimate would be in the
range of &lt;3 months depending on the amount of spare time that is left.

=== Feedback ===

If there is anything you think that is missing from current version 1.5
(as available in Google Play), that needs to be changed/added/removed
before a Calligra Mini x.y release then please let me know now. Thanks in
advance :)
______________________________**_________________
calligra-devel mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:calligra-devel@kde.org">calligra-devel@kde.org</a> <a \
class="moz-txt-link-freetext" \
href="https://mail.kde.org/mailman/**listinfo/calligra-devel">https://mail.kde.org/mailman/**listinfo/calligra-devel</a><a \
class="moz-txt-link-rfc2396E" \
href="https://mail.kde.org/mailman/listinfo/calligra-devel">&lt;https://mail.kde.org/mailman/listinfo/calligra-devel&gt;</a>


</pre>
      </blockquote>
      <pre wrap="">


</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
calligra-devel mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:calligra-devel@kde.org">calligra-devel@kde.org</a> <a \
class="moz-txt-link-freetext" \
href="https://mail.kde.org/mailman/listinfo/calligra-devel">https://mail.kde.org/mailman/listinfo/calligra-devel</a>
 </pre>
    </blockquote>
    <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