On Tuesday, May 10, 2011 17:18:58 Alex Merry wrote:
On 10/05/11 09:26, Aaron J. Seigo wrote:
we also have some blighted API that remains that needs cleaning up, but
we also need to exercise restraint. since we don't need to make huge
changes to many parts of Platform, we should try and show
On Tuesday 10 May 2011 10.04.34 Aaron J. Seigo wrote:
we have already been putting together plans, including documenting them
feature by feature in iceScrum
For those of us who this is the first time we hear about icsscrum where is it,
who can use it and for what?
/Regards
Torgny
On Thu, May 12, 2011 at 8:38 AM, Torgny Nyblom nyb...@kde.org wrote:
On Tuesday 10 May 2011 10.04.34 Aaron J. Seigo wrote:
we have already been putting together plans, including documenting them
feature by feature in iceScrum
For those of us who this is the first time we hear about icsscrum
On Thursday, May 12, 2011 14:38:57 Torgny Nyblom wrote:
On Tuesday 10 May 2011 10.04.34 Aaron J. Seigo wrote:
we have already been putting together plans, including documenting them
feature by feature in iceScrum
For those of us who this is the first time we hear about icsscrum where is
On Thursday, May 12, 2011 14:38:57 Torgny Nyblom wrote:
On Tuesday 10 May 2011 10.04.34 Aaron J. Seigo wrote:
[...]
Shaun gave the location; it's still experimental for us, though. We're
using
it for the next three months of plasma development, with a focus on Plasma
Active issues, as a
On Monday 09 May 2011 May, Olivier Goffart wrote:
- Do we want KDE 5 to be a big change, or just a small increment?
Given that an app like krita has only just now reached enough maturity to reach
an audience, any hint of big changes to the KDE platform make me really afraid.
We (the krita
On Wednesday, 11 de May de 2011 08:03:25 Boudewijn Rempt wrote:
On Monday 09 May 2011 May, Olivier Goffart wrote:
- Do we want KDE 5 to be a big change, or just a small increment?
Given that an app like krita has only just now reached enough maturity to
reach an audience, any hint of big
On Tuesday 10 May 2011, Alex Merry wrote:
On 10/05/11 09:26, Aaron J. Seigo wrote:
we also have some blighted API that remains that needs cleaning up, but
we also need to exercise restraint. since we don't need to make huge
changes to many parts of Platform, we should try and show caution
On Wednesday 11 May 2011, Thiago Macieira wrote:
On Wednesday, 11 de May de 2011 08:03:25 Boudewijn Rempt wrote:
On Monday 09 May 2011 May, Olivier Goffart wrote:
- Do we want KDE 5 to be a big change, or just a small increment?
Given that an app like krita has only just now reached
On Tuesday, May 10, 2011 00:35:17 Markus Slopianka wrote:
Qt 5 results in no need to think about KDE5 because there will be no such
thing as KDE4.
The only thing Qt 5 does is to enforce KDE Platform 5 because of the
broken binary compatibility.
KDE Plasma Workspaces can stay at 4.x and build
On 05/09/11 19:53, John Layt wrote:
I'll leave the graphics stack to those who know better, but I suspect the
leap
to QML will be too disruptive and dely things too much. Perhaps continue
calling the QWidget KDE v4 and save the v5 for QML after another 6-12 months?
No one is forcing us to
Hi,
During the last tokamak I've created this wiki page for issues and
required features that we want to see fixed in QML2:
http://community.kde.org/QML_issues
Please, fill this page with issues and required features, an improved
QML is a required feature for Qt/KDE 5 :)
Bye,
Davide Bettio.
On Monday, May 9, 2011 18:41:34 Andreas Hartmetz wrote:
- Do we want to focus on QML, or stay with QWidget?
I think this one is both obvious and difficult: Everything else being equal
QML because it is, for all we know now, more future compatible.
which shouldn't be confused with QWidget
On Monday, May 9, 2011 20:17:37 Alberto Mattea wrote:
3) Core apps, or shall we change again everything?. It took at least 3
minor releases (or 2 years since KDE 4.0) to have a fully crash-free
experience with the plasma shell. Now it looks fantastic, it is modular
(desktop, netbook, media
On Monday, May 9, 2011 18:03:18 Olivier Goffart wrote:
With Qt5 around the corner[1], I think it is time to start thinking about
KDE5
thanks for kicking this off. :)
- Do we want KDE 5 to be a big change, or just a small increment?
scoping within our resources is certainly part of it, and
On Tuesday, 10 de May de 2011 09:54:01 Aaron J. Seigo wrote:
There are many open questions:
- Can we migrate QWidget-based code in some way?
personally, i don't think this should be a focus for a KDE 5. QWidget will
remain in Qt, just in maintenance mode. they work and are very reliable.
On Tuesday, May 10, 2011 10:34:32 Thiago Macieira wrote:
KIO needs some love, but I don't think we should take the BC opportunity to
open the floodgates again.
agreed, but i do think there is an opportunity here to try and separate the
platform integration bits out of KIO. otherwise KIO almost
On 10/05/11 09:26, Aaron J. Seigo wrote:
we also have some blighted API that remains that needs cleaning up, but we
also need to exercise restraint. since we don't need to make huge changes to
many parts of Platform, we should try and show caution in changing things
just because we can. we
Hi,
With Qt5 around the corner[1], I think it is time to start thinking about KDE5
Raw summary:
- Qt5 is planed to be released in about one year from now if everything goes
well.
- It should be mostly source compatible with Qt4, and is just an opportunity
to break binary compatibility.
-
- It should be mostly source compatible with Qt4, and is just an opportunity
to break binary compatibility.
Well, even if we do nothing, we are breaking ABI. So, from my point of
view, this is a perfect time to do some API cleanup (all those
deprecated methods, faking virtuals with slots etc.)
I am probably being a bit selfish here, but I don't see how we can
ever build on a toolkit that requires OpenGL ES2.0 level hardware.
That would leave many machines that currently run KDE4 solidly (e.g.
my laptop) unable to run KDE5 for no good reason. I doubt it's the
only one out there with a
On Monday 09 May 2011 18:03:18 Olivier Goffart wrote:
Hi,
With Qt5 around the corner[1], I think it is time to start thinking about
KDE5
Raw summary:
- Qt5 is planed to be released in about one year from now if everything
goes well.
- It should be mostly source compatible with Qt4,
On Monday 09 May 2011 12:27:14 Maksim Orlovich wrote:
I am probably being a bit selfish here, but I don't see how we can
ever build on a toolkit that requires OpenGL ES2.0 level hardware.
I think it would make sense to have at least optionally the legacy code
(QWidget + X11)
without an OpenGL
On Monday 09 May 2011 18:03:18 Olivier Goffart wrote:
Hi,
With Qt5 around the corner[1], I think it is time to start thinking about KDE5
Raw summary:
- Qt5 is planed to be released in about one year from now if everything goes
well.
- It should be mostly source compatible with Qt4,
Le Monday 09 May 2011, Andreas Hartmetz a écrit :
- Do we want to focus on QML, or stay with QWidget?
I think this one is both obvious and difficult: Everything else being equal
QML because it is, for all we know now, more future compatible.
There are many open questions:
Thanks for the
suspect we will have to skip a release cycle and take 9-12
months to do it properly, probably starting around teh Qt 5.0 release.
Personally here's my Qt5/KDE5 wish/todo list:
* QDateTime to gain proper timezone and calendar system support so we can drop
ours, otherwise fix my mistakes
On Monday 09 May 2011, Olivier Goffart wrote:
Hi,
With Qt5 around the corner[1], I think it is time to start thinking about
KDE5
agreeing with many of the things saind in this thread
a) yes should be called 5, and
b) yes we should wait a bit, but is too early to see how big that bit should
Hi there,
on this occasion where future direction of KDE is being defined, here's just a note from a linux 'power user' who turned from full
KDE (3.5) fanboyness to using xfce, coping with some kde apps (yakuake, konqueror, okular, the games)...
- Do we want KDE 5 to be a big change, or
On 09.05.2011 21:17, Alberto Mattea wrote:
2) Binary compatibility. It has taken four years to port most KDE3 apps to
the
new infrastructure, and some (like Kooka) never did it. Many projects just
ended the transition from KDE3. Experience shows that even a well alive
project may not
On Monday 09 May 2011, marcel partap wrote:
Hi there,
on this occasion where future direction of KDE is being defined, here's
just a note from a linux 'power user' who turned from full KDE (3.5)
fanboyness to using xfce, coping with some kde apps (yakuake, konqueror,
okular, the games)...
Alberto Mattea albe...@mattea.info writes:
2) Binary compatibility. It has taken four years to port most KDE3 apps to
the
new infrastructure, and some (like Kooka) never did it. Many projects just
Er, just for info Kooka did finally make it to a KDE4 port (although
not as an official part
Folks please. Let's not make this an endless bikeshedding exercise.
Let's keep this focused.
This is not the right place for users to complain about KDE 4.0.
Thanks!
Cheers
Lydia, k-c-d moderator
--
Lydia Pintscher
Amarok community manager
kde.org - amarok.kde.org - kubuntu.org
On Monday 09 May 2011, Lydia Pintscher wrote:
Folks please. Let's not make this an endless bikeshedding exercise.
Let's keep this focused.
This is not the right place for users to complain about KDE 4.0.
I have seen only one email with a complaint in this still short and young
thread.
Not
On Monday, 9 de May de 2011 22:02:28 Alexander Neundorf wrote:
With Qt5 around the corner[1], I think it is time to start thinking
about KDE5
That's quite surprising for me.
The last statements I heard about a Qt5 were not planned for the forseeable
future. And now next year is quite
On Monday 09 May 2011 19:31:18 Olivier Goffart wrote:
QML starts almost from scratch.
Don't tell anyone QML is the successor to QWidgets. If you do, they are asking
for _every single feature_ in QML that QWidgets had.
Programmers like the challenge to start from scratch. Users don't unless you
Am Montag 09 Mai 2011, 18:03:18 schrieb Olivier Goffart:
Hi,
With Qt5 around the corner[1], I think it is time to start thinking about
KDE5
Sad to see that even our own guys still don't get the rebranding even after
almost two
years.
Qt 5 results in no need to think about KDE5 because
36 matches
Mail list logo
