Re: Post Sprint Processing

Jos Poortvliet <jospoortvliet <at> gmail.com>
2009-12-01 08:00:05 GMT

I made a list of blogs will send later today when im behind a proper keyboard...
--
send on my N900 via Nokia Messaging
----- Oorspronkelijk bericht -----
> Hello everybody!
>
> First of all I'd like to thank everybody who their time to fly to cold
> and expensive Oslo, it was good t have you all in one room. Special
> thanks go to Inge for moderating the discussion and taking care of the
> schedule, to Jos for the writing (and the fags) and to Thomas for
> helping to organize all of this. [1]
>
> There are however some things left to do. All the decisions taken
> during the weekend need to be documented on the wiki. Since I couldn't
> attend most of the meeting, I can't really make a list of topics.
> Jean-Nicholas, you took notes, didn't you? :) As soon as we have that
> list we should decide who takes care of which topic and starts a wiki
> page.
>
> Personally, I would like to ask you to send me the URLs of your blogs
> about the weekend, so I have the needed material to counter pointy
> haired requests. I asked Jos about that already but I guess it is
> easier if everybody just quickly drops me a mail with their own URLs
> so we don't overlook any articles. We can then put them all on
> koffice.org too. :)
>
> That's all for now. Have a great week while I recover from my cold...
>
> Alex
>
> [1] In alphabetical order and hopefully close to complete. ;)
> --
> Alexandra Leisse
> Sent from Oslo, 03, Norway

Re: Post Sprint Processing

Inge Wallin <inge <at> lysator.liu.se>
2009-12-01 08:44:20 GMT

On Monday 30 November 2009 17:10:05 Alexandra Leisse wrote:
> Hello everybody!
>
> First of all I'd like to thank everybody who their time to fly to cold
> and expensive Oslo, it was good t have you all in one room. Special
> thanks go to Inge for moderating the discussion and taking care of the
> schedule, to Jos for the writing (and the fags) and to Thomas for
> helping to organize all of this. [1]
>
> There are however some things left to do. All the decisions taken
> during the weekend need to be documented on the wiki. Since I couldn't
> attend most of the meeting, I can't really make a list of topics.
> Jean-Nicholas, you took notes, didn't you? :) As soon as we have that
> list we should decide who takes care of which topic and starts a wiki
> page.
I have minutes from the discussions. I will merge that with the info from
Pierre's and boud's mail to the ML and put it on the Wiki. I'll do that
tonight if I can make the network on the hotel work.
-Inge

Re: Review Request: Add struct KoFontFace

Inge Wallin <inge <at> lysator.liu.se>
2009-12-01 11:19:59 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard.kde.org/r/2257/
-----------------------------------------------------------
(Updated 2009-12-01 11:19:59.550371)
Review request for KOffice.
Changes
-------
Third version of the patch
Summary
-------
Here is the first patch in a small patchset that will add filters for the MS 2007 XML file formats. Note that I
am only the middle man here.
This patch adds the struct KoFontFace that is a public data structure representing a font style. It is saved
as a style:font-face element. Before this patch, only the font name was available, which was saved as a
style:name attribute of style:font-face. Also, svg:font-family was saved as a copy.
Now the old behaviour is still available but in addition, new attributes can be specified in order to make
the description of a font more accurate
(style:font-family-generic, svg:font-style, style:font-pitch). These are needed for increasing
quality of import/export filters and is already used in the MSOOXML filters. The ODF specification
offers even more attributes.
The patch also contains fix for use of m_mainStyles->addFontFace() in two places, both in KWord.
Diffs (updated)
-----
trunk/koffice/filters/kword/msword-odf/document.cpp 1055949
trunk/koffice/filters/kword/msword-odf/texthandler.cpp 1055949
trunk/koffice/libs/odf/CMakeLists.txt 1055949
trunk/koffice/libs/odf/KoFontFace.h PRE-CREATION
trunk/koffice/libs/odf/KoFontFace.cpp PRE-CREATION
trunk/koffice/libs/odf/KoGenStyles.h 1055949
trunk/koffice/libs/odf/KoGenStyles.cpp 1055949
Diff: http://reviewboard.kde.org/r/2257/diff
Testing
-------
Thanks,
Inge

Re: 2.2 Release plan

On a side note, about Qt/KDE dependencies. We had a lot of discussion in the
past on the subject, but no real conclusion. What is sure is that Krita 2.2
will require Qt 4.6 (and therefor KDE 4.4), the reason is that 4.6 brings
important fix to tablet support. Since there is no real reason to impose that
dependency on other applications (unless other applications want to), that
requirement would apply only to Krita. As for the deadline, I suggest to wait
after the 4.4 release, and to wait for Krita developers to have available
upgrades from their distributions.
--
--
Cyrille Berger

Re: 2.2 Release plan

Jaroslaw S <kexipl <at> gmail.com>
2009-12-01 13:45:45 GMT

2009/12/1 Cyrille Berger <cberger <at> cberger.net>:
> On a side note, about Qt/KDE dependencies. We had a lot of discussion in the
> past on the subject, but no real conclusion. What is sure is that Krita 2.2
> will require Qt 4.6 (and therefor KDE 4.4), the reason is that 4.6 brings
> important fix to tablet support. Since there is no real reason to impose that
> dependency on other applications (unless other applications want to), that
> requirement would apply only to Krita.
From the packagers POV:
But how to do that if Krita comes in the same tarball as the other apps?
Is there a plan to have #ifdefs in Krita to support builds for OSes
that are based on Qt 4.5
(OK for those that agree with the degraded feature(s) or performace)?
--
--
regards / pozdrawiam, Jaroslaw Staniek
Kexi & KOffice (http://www.kexi-project.org, http://www.koffice.org)
KDE Libraries for MS Windows (http://windows.kde.org)
http://www.linkedin.com/in/jstaniek

Re: 2.2 Release plan

On Tue, 1 Dec 2009, Jaroslaw S wrote:
> But how to do that if Krita comes in the same tarball as the other apps?
When we make the move, I want Krita to be disabled if Qt 4.6 isn't present.
>
> Is there a plan to have #ifdefs in Krita to support builds for OSes
> that are based on Qt 4.5
> (OK for those that agree with the degraded feature(s) or performace)?
For 2.2 and later I really don't want to make Krita availalble for
Qt 4.5.
Boudewijn

Re: 2.2 Release plan

On Tuesday 01 December 2009, Jaroslaw S wrote:
> From the packagers POV:
> But how to do that if Krita comes in the same tarball as the other apps?
>
> Is there a plan to have #ifdefs in Krita to support builds for OSes
> that are based on Qt 4.5
> (OK for those that agree with the degraded feature(s) or performace)?
To be explicit, Qt 4.5 => no krita 2.2, there is no #ifdef that can save you
from that, since what we are interested in the bug fix deep in Qt 4.6 that
makes tablet work out of the box, instead of having to tell users that they
need to edit their hal files.
Since Krita is advertised as a paint application, it is a must have. So OSes
that are based on Qt 4.5 and won't have 4.6 (is there any ?) won't have krita
2.2.
--
--
Cyrille Berger

Re: Dockers

Cyrille Berger <cberger <at> cberger.net>
2009-12-01 14:47:30 GMT

I have put the list of issues on the wiki now:
http://wiki.koffice.org/index.php?title=Dockers/Issues
I also tried to find if the issues where already in Qt's bugzilla, but I
couldn't find any.
I had a look (again) at the docker code in Qt, it is extremely hard to read
(and not that well documented either...) so I am not confident that I will be
able to fix anything on that list... So we will have to report them, and hope
someone care to fix the issues at some point, and in the meantime, we will have
to keep our work around, I am also going to experiment a bit on having better
one though.
--
--
Cyrille Berger

Re: 2.2 Release plan

Jaroslaw S <kexipl <at> gmail.com>
2009-12-01 15:30:23 GMT

2009/12/1 Cyrille Berger <cberger <at> cberger.net>:
> On Tuesday 01 December 2009, Jaroslaw S wrote:
>> From the packagers POV:
>> But how to do that if Krita comes in the same tarball as the other apps?
>>
>> Is there a plan to have #ifdefs in Krita to support builds for OSes
>> that are based on Qt 4.5
>> (OK for those that agree with the degraded feature(s) or performace)?
> To be explicit, Qt 4.5 => no krita 2.2, there is no #ifdef that can save you
> from that, since what we are interested in the bug fix deep in Qt 4.6 that
> makes tablet work out of the box, instead of having to tell users that they
> need to edit their hal files.
> Since Krita is advertised as a paint application, it is a must have. So OSes
> that are based on Qt 4.5 and won't have 4.6 (is there any ?) won't have krita
> 2.2.
This is your choice of course and the discussion is not new.
It is 100% OK assuming:
a) all supported users are tablet users
b) there are no improvements in 2.2 other than tabled support
c) only users able to upgrade their OSes can benefit from advancements
made in Krita
(not all users can: not all own the running computers, suboptimal
policies e.g. in schools can prevent that,
or technically upgrade is not possible because the OS is based on
LiveCD/DVD/other readonly medium)
Why I am asking is not because _I_ cannot upgrade or I cannot help
others to do so:
I am trying to extract a more generic idea how to behave in such case
when we can offer the folowing options:
1. Stay with previous version of an app
2. Allow to devote some new features in exchange of giving some other new
(all the above assuming the option can be made with little development effort)
--
--
regards / pozdrawiam, Jaroslaw Staniek
Kexi & KOffice (http://www.kexi-project.org, http://www.koffice.org)
KDE Libraries for MS Windows (http://windows.kde.org)
http://www.linkedin.com/in/jstaniek