Mext week the biggest mobile congress will start in Barcelona from 27 February
to 1 March. I got an invitation for the developing area and I'm planning to do
some networking KDE related and I want to go well prepared :)
So far this is what I got:
-I will download all our Harmattan apps
-I will
A Quarta, 22 de Fevereiro de 2012 10:46:53 Richard Hughes você escreveu:
First, I apologise about the cross posting. Please drop any list which
isn't relevant in your replies, and please also cc me as I'm not
subscribed to either list.
GNOME has been a color managed desktop by default for
On Wednesday 22 February 2012 Feb, Nuno Pinheiro wrote:
A Quarta, 22 de Fevereiro de 2012 10:46:53 Richard Hughes você escreveu:
First, I apologise about the cross posting. Please drop any list which
isn't relevant in your replies, and please also cc me as I'm not
subscribed to either list.
On Wednesday 22 February 2012 11:46:53 Richard Hughes wrote:
GNOME has been a color managed desktop by default for two releases
[...]
Basically, I need a KDE dude.
Our color management KDE dude is Kai-Uwe Behrmann from Oyranos
team. See git/playground/graphics/kolor-manager for what is
On 22 February 2012 11:30, Christoph Feck christ...@maxiom.de wrote:
Our color management KDE dude is Kai-Uwe Behrmann from Oyranos
team. See git/playground/graphics/kolor-manager for what is already
available.
I gave up on working with Kai-Uwe a long time ago. Oyranos and colord
are competing
Oyranos CMS is about preparing a release and then the existing KDE Color
Management panel will be ready to continue inclusion into KDE. I
appologies for the delay. The KDE Color Management panel or kolor-manager
in kde git provides a front end to the Oyranos API, including
configuration of
Excellent plans, Alex !
Please add the available applications on Harmattan in here, if the
list is not complete, outdated and so forth:
http://community.kde.org/KDE_Mobile/Harmattan#Ported_Application
Off topic: Keep an eye on Nokia ;) http://www.youtube.com/watch?v=iZlE4uWnFqI
Best Regards,
Am 22.02.12, 11:52 - schrieb Richard Hughes:
On 22 February 2012 11:30, Christoph Feck christ...@maxiom.de wrote:
Our color management KDE dude is Kai-Uwe Behrmann from Oyranos
team. See git/playground/graphics/kolor-manager for what is already
available.
I gave up on working with Kai-Uwe
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/103973/#review10820
---
Ship it!
Ship It!
- David Faure
On Feb. 21, 2012, 6:35
Hello,
Toma's blog
posthttp://www.omat.nl/2012/02/18/sysadmin-needs-help-with-bugzilla-installation/
inspired
me to send you this mail.
Right now our bugzilla is a mess. We have so many bug entries which we
can't handle.
Everyone is able to open a new bug, but only a few people are able to
On Wednesday 22 February 2012 16:15:45 Giorgos Tsiapaliwkas wrote:
Hello,
Toma's blog
posthttp://www.omat.nl/2012/02/18/sysadmin-needs-help-with-bugzilla-instal
lation/ inspired
me to send you this mail.
Right now our bugzilla is a mess. We have so many bug entries which we
can't
On Wed, Feb 22, 2012 at 4:11 PM, David Faure fa...@kde.org wrote:
give rights to everyone, and remove rights when
someone abuses them. This is also what we do for SVN/GIT, so why don't we do
this for bugzilla? Presuming people are innocent upfront, rather than guilty
What we do for SVN/Git is
If KDE include a color management based on Oyranos, what's about
applications which have already a Color Management system, based on
another library ?
For ex, in digiKam we have used LCMS ver1 and we currently port to
LCMS ver 2 (http://www.littlecms.com)
We will need to break all LCMS based
On Wednesday 22 February 2012 11:47:36 Ben Cooksley wrote:
We will likely be upgrading to the latest version of the 4.x series.
Make sure it's the 4.0.4 as it solves some issues with the perl packages
related to JSON (versioning problems)
We have not deliberately disabled REST/JSON/XMLRPC in
Gilles Caulier caulier.gil...@gmail.com schrieb:
If KDE include a color management based on Oyranos, what's about
applications which have already a Color Management system, based on
another library ?
For ex, in digiKam we have used LCMS ver1 and we currently port to
LCMS ver 2
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/103973/#review10821
---
This review has been submitted with commit
On 22 Feb 2012 11:29, Boudewijn Rempt b...@valdyas.org wrote:
On Wednesday 22 February 2012 Feb, Nuno Pinheiro wrote:
A Quarta, 22 de Fevereiro de 2012 10:46:53 Richard Hughes você escreveu:
First, I apologise about the cross posting. Please drop any list which
isn't relevant in your
Am 22.02.12, 16:42 - schrieb John Layt:
On 22 Feb 2012 11:29, Boudewijn Rempt b...@valdyas.org wrote:
On Wednesday 22 February 2012 Feb, Nuno Pinheiro wrote:
A Quarta, 22 de Fevereiro de 2012 10:46:53 Richard Hughes você escreveu:
First, I apologise about the cross posting. Please drop
On Wednesday 22 February 2012 11:57:25 Parker Coates wrote:
On Wed, Feb 22, 2012 at 10:23, Stefan Majewsky wrote:
On Wed, Feb 22, 2012 at 4:11 PM, David Faure wrote:
give rights to everyone, and remove rights when
someone abuses them. This is also what we do for SVN/GIT, so why don't
we
The suggestion remains: to allow everyone to edit and close bugs, as is
apparently the case in some other bug trackers.
+1.
Worked fine on the MeeGo bugzilla for instance, I previously used.
Best Regards,
Laszlo Papp
Am 22.02.2012 18:13, schrieb Laszlo Papp:
The suggestion remains: to allow everyone to edit and close bugs, as
is
apparently the case in some other bug trackers.
+1.
Worked fine on the MeeGo bugzilla for instance, I previously used.
Personally I'm not sure whether the MeeGo bugzilla can be
On Wednesday, February 22, 2012 07:00:26 PM Martin Gräßlin wrote:
Am 22.02.2012 18:13, schrieb Laszlo Papp:
The suggestion remains: to allow everyone to edit and close bugs, as
is
apparently the case in some other bug trackers.
+1.
Worked fine on the MeeGo bugzilla for instance, I
Am 22.02.2012, 16:11 Uhr, schrieb David Faure fa...@kde.org:
In case that a user finds a true bug, he can go to the project's irc
and
to ask from someone to
open the new bug.
Doesn't sound very open
[Disclaimer: Describing a custom, proprietary and vastly expensive system
;-)
No
Am 22.02.12, 09:38 -0800 schrieb Daniel Nicoletti:
As Richard said Oyranos is doing all this by it self on the CPU so it
would act like a proxy between your application,
and the window manager which sounds like killing performance.
( I might have misunderstood but I can't see any other way of
Am 22.02.2012 20:01, schrieb Kai-Uwe Behrmann:
Am 22.02.12, 09:38 -0800 schrieb Daniel Nicoletti:
As Richard said Oyranos is doing all this by it self on the CPU so
it
would act like a proxy between your application,
and the window manager which sounds like killing performance.
( I might have
On Wed, Feb 22, 2012 at 7:11 AM, David Faure fa...@kde.org wrote:
Doesn't sound very open
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5
First of all, the bugzilla is supposed to be a communication tool between
the user
On Wednesday, February 22, 2012 04:11:57 PM David Faure wrote:
He asked me why we don't do this, and the only reply I could come
up with was the few cases where bugs turned into actual political
flamewars; his answer was obviously give rights to everyone, and remove
rights when someone
27 matches
Mail list logo
