[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: 2009 introspective
From: Jean-Nicolas Artaud <jeannicolasartaud () gmail ! com>
Date: 2009-05-06 9:23:18
Message-ID: 4816864d0905060223u260f26aasc35c3871e5247340 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hello.
I'm making global response cause some guys (like Zagge or Cyrille) wants to
look at this.
If I say something wrong, they will correct me directly !
I will talk about the koffice-isi which has been created on October (or
something like that).
His main goal was to add functionalities to* KPresenter*, and to make
students learn the Qt-KDE development. Some features not only help
KPresenter but all KOffice.
You can see what exactly have been done here, and have a look on the
difficulties of the team just looking on this product backlog :
http://spreadsheets.google.com/pub?key=p6LzBn8zyAXtmshMWJFHaTg
To sum up here are the points :
* Implement "line ends"
* Add functionality for rehearsal
* Allow users to paint and emphasize texts fields in the presentation
* Context menu on clicking in left document view
* Import of slideshows
Zagge and TZander had helped us to make this.
Zagge is cleaning up the branch to prepare a merge on the trunk, but there
is a lot of things to do.
If you want more details, just say it !
Best regards.
Jean-Nicolas Artaud
2009/5/4 Aaron J. Seigo <aseigo@kde.org>
> Hi...
>
> I'm putting together a "where are we now, where are we going" snapshot of
> as
> many of the "big pieces" in KDE 4 as possible, and I'd like some input from
> you on Krita, Kexi, KWord, KSpread, KPresenter, KPlato, Karbon, etc.
>
> In particular, what I'm looking for are 2-4 bullet items for each of these
> two
> questions:
>
> * What have been the defining achievements in the last year?
>
> * What are the main focus points and or goals for the project in 2009?
>
>
> If you're feeling extra helpful, you might want to also provide some input
> on:
>
> * What are the major pain points in your project right now?
>
> * Outside of the core libs (kdecore, kdeui, kio, kfile) what are the most
> critical pieces of KDE technologies that your project is relying on?
>
>
> You can reply to me directly; I'll be collating and making public the
> results
> when they are in ...
>
> As an example of what I'm looking for, here's the answer set of Plasma:
>
> In the last year:
>
> * Parity with KDE3 desktop/panels
> * Finished out the foundational pieces (extenders, activities,
> scripting..)
> * Moved libplasma to kdelibs
>
> Focus points in 2009:
>
> * Ease of creating Plasma components (Plasmate)
> * Netbook interface
> * Media center components
> * Remote plasmoids
> * Social desktop features
> * Improved integration with Nepomuk and rest of workspace
>
> Major point points:
>
> * x.org driver quality
> * QGraphicsView is still going through growing pains
> * newness of our own codebase resulting in larger #s of defects
>
> Major technologies we rely (or will be relying) on:
>
> * x.org and kwin compositing features
> * QGraphicsView
> * Solid
> * Nepomuk
>
>
>
> As for why I'm doing this survey, here's an excerpt from
> http://aseigo.blogspot.com/2009/04/trailheads.html:
>
> "The pre-4.0 development of KDE was helped along by everyone knowing what
> we
> were striving towards: we had the Pillars, these new big chunks of
> technology
> we were busy slotting into place so that we could build ever better
> applications on top of; we had a renewed focus on clean, usable interfaces;
> we
> were also aiming for beauty and greater platform independence.
>
> The individual projects around the KDE universe all swirled around these
> shared goals. Each headed in their own direction that reflected their own
> interpretation of these goals as weighted by their development team in
> terms
> of importance. Not remarkably, while there was variance in execution, there
> was a remarkable harmony in the overall approach and results.
>
> That didn't happen by accident: it happened because we were communicating
> with
> each other about our goals and in-the-moment situations. I was part of only
> a
> fraction of these conversations, but I remember the huge number of informal
> meet ups both online and in person (part of my "coffee shop meetings around
> the world" tour, or at least that's sometimes how it felt ;). It was
> inspiring
> and helpful and marked a high water point in KDE community togetherness for
> me.
>
> We're into 2009 now and it's time to stoke those fires again."
>
> Thanks for your time and energy in advance :)
>
> --
> Aaron J. Seigo
> humru othro a kohnu se
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
>
> KDE core developer sponsored by Qt Software
>
>
>
>
>
>
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
>
[Attachment #5 (text/html)]
Hello.<br><br>I'm making global response cause some guys (like Zagge or Cyrille) \
wants to look at this.<br>If I say something wrong, they will correct me directly \
!<br><br>I will talk about the koffice-isi which has been created on October (or \
something like that).<br> His main goal was to add functionalities to<b> \
KPresenter</b>, and to make students learn the Qt-KDE development. Some features not \
only help KPresenter but all KOffice.<br><br>You can see what exactly have been done \
here, and have a look on the difficulties of the team just looking on this product \
backlog : <a href="http://spreadsheets.google.com/pub?key=p6LzBn8zyAXtmshMWJFHaTg">http://spreadsheets.google.com/pub?key=p6LzBn8zyAXtmshMWJFHaTg</a><br>
<br>To sum up here are the points :<br>* Implement "line ends"<br>* Add \
functionality for rehearsal<br>* Allow users to paint and emphasize texts fields in \
the presentation<br>* Context menu on clicking in left document \
view<br>
* Import of slideshows<br><br>Zagge and TZander had helped us to make this.<br>Zagge \
is cleaning up the branch to prepare a merge on the trunk, but there is a lot of \
things to do.<br><br>If you want more details, just say it !<br> <br>Best \
regards.<br>Jean-Nicolas Artaud<br><br><div class="gmail_quote">2009/5/4 Aaron J. \
Seigo <span dir="ltr"><<a \
href="mailto:aseigo@kde.org">aseigo@kde.org</a>></span><br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> Hi...<br>
<br>
I'm putting together a "where are we now, where are we going" snapshot \
of as<br> many of the "big pieces" in KDE 4 as possible, and I'd like \
some input from<br> you on Krita, Kexi, KWord, KSpread, KPresenter, KPlato, Karbon, \
etc.<br> <br>
In particular, what I'm looking for are 2-4 bullet items for each of these \
two<br> questions:<br>
<br>
* What have been the defining achievements in the last year?<br>
<br>
* What are the main focus points and or goals for the project in 2009?<br>
<br>
<br>
If you're feeling extra helpful, you might want to also provide some input \
on:<br> <br>
* What are the major pain points in your project right now?<br>
<br>
* Outside of the core libs (kdecore, kdeui, kio, kfile) what are the most<br>
critical pieces of KDE technologies that your project is relying on?<br>
<br>
<br>
You can reply to me directly; I'll be collating and making public the results<br>
when they are in ...<br>
<br>
As an example of what I'm looking for, here's the answer set of Plasma:<br>
<br>
In the last year:<br>
<br>
* Parity with KDE3 desktop/panels<br>
* Finished out the foundational pieces (extenders, activities, \
scripting..)<br>
* Moved libplasma to kdelibs<br>
<br>
Focus points in 2009:<br>
<br>
* Ease of creating Plasma components (Plasmate)<br>
* Netbook interface<br>
* Media center components<br>
* Remote plasmoids<br>
* Social desktop features<br>
* Improved integration with Nepomuk and rest of workspace<br>
<br>
Major point points:<br>
<br>
* <a href="http://x.org" target="_blank">x.org</a> driver quality<br>
* QGraphicsView is still going through growing pains<br>
* newness of our own codebase resulting in larger #s of defects<br>
<br>
Major technologies we rely (or will be relying) on:<br>
<br>
* <a href="http://x.org" target="_blank">x.org</a> and kwin compositing \
features<br>
* QGraphicsView<br>
* Solid<br>
* Nepomuk<br>
<br>
<br>
<br>
As for why I'm doing this survey, here's an excerpt from<br>
<a href="http://aseigo.blogspot.com/2009/04/trailheads.html" \
target="_blank">http://aseigo.blogspot.com/2009/04/trailheads.html</a>:<br> <br>
"The pre-4.0 development of KDE was helped along by everyone knowing what we<br>
were striving towards: we had the Pillars, these new big chunks of technology<br>
we were busy slotting into place so that we could build ever better<br>
applications on top of; we had a renewed focus on clean, usable interfaces; we<br>
were also aiming for beauty and greater platform independence.<br>
<br>
The individual projects around the KDE universe all swirled around these<br>
shared goals. Each headed in their own direction that reflected their own<br>
interpretation of these goals as weighted by their development team in terms<br>
of importance. Not remarkably, while there was variance in execution, there<br>
was a remarkable harmony in the overall approach and results.<br>
<br>
That didn't happen by accident: it happened because we were communicating \
with<br> each other about our goals and in-the-moment situations. I was part of only \
a<br> fraction of these conversations, but I remember the huge number of informal<br>
meet ups both online and in person (part of my "coffee shop meetings around<br>
the world" tour, or at least that's sometimes how it felt ;). It was \
inspiring<br> and helpful and marked a high water point in KDE community togetherness \
for<br> me.<br>
<br>
We're into 2009 now and it's time to stoke those fires again."<br>
<br>
Thanks for your time and energy in advance :)<br>
<font color="#888888"><br>
--<br>
Aaron J. Seigo<br>
humru othro a kohnu se<br>
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43<br>
<br>
KDE core developer sponsored by Qt Software<br>
<br>
<br>
<br>
<br>
<br>
<br>
</font><br>_______________________________________________<br>
koffice-devel mailing list<br>
<a href="mailto:koffice-devel@kde.org">koffice-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/koffice-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/koffice-devel</a><br> \
<br></blockquote></div><br>
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic