Am 22.03.12, 22:49 +0100 schrieb Thomas Lübking:
Am 22.03.2012, 19:20 Uhr, schrieb Kai-Uwe Behrmann :
I was tould by the graphics community to keep the X Color Management spec
backward compatible with the ICC Profile in X spec, so we did. Thus old
style applications see a sRGB profile through th
> On March 18, 2012, 11:04 p.m., Stephen Kelly wrote:
> > Nice, thanks and sorry for the noise, and thanks for making the branch.
>
> Dario Freddi wrote:
> Np, hope you'll be able to have a quick look at it as well, it would be
> great :)
>
> Stephen Kelly wrote:
> Mostly it looks fine
Am 22.03.2012, 19:20 Uhr, schrieb Kai-Uwe Behrmann :
I was tould by the graphics community to keep the X Color Management spec
backward compatible with the ICC Profile in X spec, so we did. Thus old
style applications see a sRGB profile through the ICC Profile in X spec,
and they continue to wo
On Thursday 22 March 2012 19:20:11 Kai-Uwe Behrmann wrote:
> Something like that is technical possible. But let me repeat, you get then
> a mixture of colour managed and non colour managed apps with the same
> toolkit, which is completely non understandable for users.
First of all: users don't know
Sorry I missed to answere you somehow.
Am 21.03.12, 10:25 +0100 schrieb todd rme:
On Wed, Mar 21, 2012 at 8:39 AM, Kai-Uwe Behrmann wrote:
Am 20.03.12, 21:17 +0100 schrieb Thomas Lübking:
Am 20.03.2012, 20:12 Uhr, schrieb Martin Graesslin :
A fully color corrected compositor seems feasible
Am 22.03.12, 18:41 +0100 schrieb Thomas Lübking:
Am 22.03.2012, 08:55 Uhr, schrieb Kai-Uwe Behrmann :
Lets hypothetical assume some effort is initiated to bring CM to Qt and
that happens during Qt 5 life time. The new design says by default all
content is considered sRGB, which is by itself rea
> [: David Jarvie :]
> I understand from your email that you are only proposing to remove KUIT
> semantic tags, not KUIT context markers. Can you confirm this?
I confirm. They are used much more than tags, and have no problems on their
own; they are simply useful whenever present. They would only
Am 22.03.2012, 08:55 Uhr, schrieb Kai-Uwe Behrmann :
Lets hypothetical assume some effort is initiated to bring CM to Qt and
that happens during Qt 5 life time. The new design says by default all
content is considered sRGB, which is by itself reasonable. However
existing applications will initia
On Thu, March 22, 2012 10:25 am, Chusslove Illich wrote:
> Starting with KDE 4.0, i18n() functions act as XML processors under the
> hood, expecting the strings to be well-formed XML and resolving some tags
> (KUIT tags) to a target format (HTML or pure text). These KUIT tags
> include
> , , , etc.
> On March 18, 2012, 11:04 p.m., Stephen Kelly wrote:
> > Nice, thanks and sorry for the noise, and thanks for making the branch.
>
> Dario Freddi wrote:
> Np, hope you'll be able to have a quick look at it as well, it would be
> great :)
>
> Stephen Kelly wrote:
> Mostly it looks fine
This looks wrong to me; strictEqual is used for ===, which is defined
in 11.9.6, and doesn't do any freaky deviations from IEEE FP. You'll
likely need a separate version for SameValue proper.
On 3/21/12, Bernd Buschinski wrote:
>
> ---
> Th
Shift-reduce conflicts in the parser.
On 3/21/12, Bernd Buschinski wrote:
>
>
>> On March 20, 2012, 9:30 p.m., Maks Orlovich wrote:
>> > Can I presume this change doesn't changer # of conflicts?
>> >
>
> I don't understand what conflicts you mean. If you mean failing tests in
> ecmascript262, i
2012/3/22 Sune Vuorela :
> On 2012-03-22, Daniel Nicoletti wrote:
>> people draw API they have this in mind and we don't need a whole new Qt just
>> to
>> introduce a new feature, easy solution:
>> QApplication::setColorCorrected(true);
>
> That's crap API thoug.h
>
> QApplication::setBehaveSane
On 2012-03-22, Daniel Nicoletti wrote:
> people draw API they have this in mind and we don't need a whole new Qt just
> to
> introduce a new feature, easy solution: QApplication::setColorCorrected(true);
That's crap API thoug.h
QApplication::setBehaveSane(true);
QApplication::setPleaseDontCrash
2012/3/22 Kai-Uwe Behrmann :
> Here my thoughts, why I think CM in Qt is not easily introduced during a
> minor Qt 5 release. [Preparation of CM for Qt 6 is a different story.]
>
> Lets hypothetical assume some effort is initiated to bring CM to Qt and that
> happens during Qt 5 life time. The new
Em Wednesday 21 March 2012, Lamarque V. Souza escreveu:
> Em Wednesday 21 March 2012, Aaron J. Seigo escreveu:
> > On Tuesday, March 20, 2012 22:31:57 Lamarque V. Souza wrote:
> > > There is a crash in WeatherEngine (kde-workspace) triggered by the
> > > fact
> > >
> > > that Plasma::DataEngin
Starting with KDE 4.0, i18n() functions act as XML processors under the
hood, expecting the strings to be well-formed XML and resolving some tags
(KUIT tags) to a target format (HTML or pure text). These KUIT tags include
, , , etc.
I would like to drop this support in KDE Frameworks 5.0. There wo
Am 22.03.12, 07:34 +0100 schrieb Martin Gräßlin:
On Thursday 22 March 2012 07:02:27 Kai-Uwe Behrmann wrote:
Am 21.03.12, 20:34 +0100 schrieb Martin Gräßlin:
Do you have any references showing that it is impossible to add color
correction to Qt during the lifecycle of Qt 5? I'm sorry, but I don'
Am 21.03.12, 22:25 +0100 schrieb Thomas Zander:
Color management in Qt is a bit of a weird statement; first of all, support is
already possible as Krita proves. Second, I doubt that 94% of the widgets
Krita does colour management inside Krita. IMO that does not belong to a
discussion about Qt
19 matches
Mail list logo
