--===============1964579440== Content-Type: multipart/alternative; boundary=001636c599a624b40b04693af2de --001636c599a624b40b04693af2de Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 > 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 > > --001636c599a624b40b04693af2de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 cor= rect 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 KPresent= er but all KOffice.

You can see what exactly have been done here, an= d have a look on the difficulties of the team just looking on this product = backlog : http://spreadsheets.google.com/pub?key=3Dp6LzBn8zyAXtmshMWJFHaT= g

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 docu= ment 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 th= ere 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 s= ome 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 th= ese 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 in= put 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 r= esults
when they are in ...

As an example of what I'm looking for, here's the answer set of Pla= sma:

In the last year:

=A0 =A0 =A0 =A0* Parity with KDE3 desktop/panels
=A0 =A0 =A0 =A0* Finished out the foundational pieces (extenders, activiti= es, scripting..)
=A0 =A0 =A0 =A0* Moved libplasma to kdelibs

Focus points in 2009:

=A0 =A0 =A0 =A0* Ease of creating Plasma components (Plasmate)
=A0 =A0 =A0 =A0* Netbook interface
=A0 =A0 =A0 =A0* Media center components
=A0 =A0 =A0 =A0* Remote plasmoids
=A0 =A0 =A0 =A0* Social desktop features
=A0 =A0 =A0 =A0* Improved integration with Nepomuk and rest of workspace
Major point points:

=A0 =A0 =A0 =A0* x.org driv= er quality
=A0 =A0 =A0 =A0* QGraphicsView is still going through growing pains
=A0 =A0 =A0 =A0* newness of our own codebase resulting in larger #s of def= ects

Major technologies we rely (or will be relying) on:

=A0 =A0 =A0 =A0* x.org and = kwin compositing features
=A0 =A0 =A0 =A0* QGraphicsView
=A0 =A0 =A0 =A0* Solid
=A0 =A0 =A0 =A0* 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 w= hat we
were striving towards: we had the Pillars, these new big chunks of technolo= gy
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 term= s
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 communicati= ng 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 a= round
the world" tour, or at least that's sometimes how it felt ;). It w= as 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 =A0EE75 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


--001636c599a624b40b04693af2de-- --===============1964579440== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ koffice-devel mailing list koffice-devel@kde.org https://mail.kde.org/mailman/listinfo/koffice-devel --===============1964579440==--