On Tue, Aug 20, 2013 at 12:23 PM, Martin Graesslin wrote:
> wait, did you apply the patch from the review request I posted yesterday?
> Because that requires adjustments in kde-workspace, too.
Yes! I have applied patch to ECM.
___
Plasma-devel mailing
On Tuesday 20 August 2013 12:14:28 Bhushan Shah wrote:
> Hello,
>
> Here is relevant cmake --trace log, if that helps..
> http://paste.kde.org/p48e12dc6/
wait, did you apply the patch from the review request I posted yesterday?
Because that requires adjustments in kde-workspace, too.
>
> Thanks
Hello,
Here is relevant cmake --trace log, if that helps..
http://paste.kde.org/p48e12dc6/
Thanks
On Tue, Aug 20, 2013 at 11:52 AM, Martin Graesslin wrote:
> On Tuesday 20 August 2013 11:36:58 Bhushan Shah wrote:
>> Hello,
>>
>> Even I have tried with complete re installation of KUbuntu and fre
On Tuesday 20 August 2013 11:36:58 Bhushan Shah wrote:
> Hello,
>
> Even I have tried with complete re installation of KUbuntu and fresh
> clone of the kde-workspace, but something is still wrong. Here is what
> I do to compile.
it looks fine. I'm out of ideas. Maybe talk to the neon devs on IRC (
Hello,
Even I have tried with complete re installation of KUbuntu and fresh
clone of the kde-workspace, but something is still wrong. Here is what
I do to compile.
$ cd ~/kde-workspace
$ git checkout frameworks-scratch
$ mkdir build && cd build
$ neon5-env
$ neon5-cmake ..
and also
cmake ..
Th
Hello,
Now that's double annoying to me, I have more packages installed then you, still
bshah@kubuntu:~$ aptitude search xcb | grep dev
i libx11-xcb-dev - Xlib/XCB interface library (development he
i libxcb-composite0-dev - X C Binding, composite extension, developm
On Tuesday 20 August 2013 10:21:21 Bhushan Shah wrote:
> On Tue, Aug 20, 2013 at 12:25 AM, Martin Graesslin
wrote:
> > I'm pretty sure that some dev package is missing and that they are
> > available on Ubuntu otherwise project-neon could not compile 4.11 ;-)
>
> So only thing I am missing is li
On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote:
> 3. ‘2’ ... why “two” if this is version 5? well, libplasma is actually going
> to be version 6 iirc, so it isn’t the library. i also am not a big believer
> in branding after version numbers. neither are any of our proprietary
> competitors
On Tue, Aug 20, 2013 at 12:25 AM, Martin Graesslin wrote:
> I'm pretty sure that some dev package is missing and that they are available
> on Ubuntu otherwise project-neon could not compile 4.11 ;-)
So only thing I am missing is libxcb-cursor-dev and it is not
available for raring or saucy(?)...
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111849/
---
(Updated Aug. 20, 2013, 4:37 a.m.)
Review request for Plasma.
Changes
--
On Monday, August 19, 2013 23:08:15 Marco Martin wrote:
> On Monday 19 August 2013, Kevin Ottens wrote:
> > On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote:
> > > 3. ‘2’ ... why “two” if this is version 5? well, libplasma is actually
> > > going to be version 6 iirc, so it isn’t the library.
On Monday 19 August 2013 23:08:15 Marco Martin wrote:
> On Monday 19 August 2013, Kevin Ottens wrote:
> > On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote:
> > > 3. ‘2’ ... why “two” if this is version 5? well, libplasma is actually
> > > going to be version 6 iirc, so it isn’t the library.
>
On Monday 19 August 2013, Kevin Ottens wrote:
> On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote:
> > 3. ‘2’ ... why “two” if this is version 5? well, libplasma is actually
> > going to be version 6 iirc, so it isn’t the library.
>
> Not that its relevant for the rest of the discussion, but
On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote:
> 3. ‘2’ ... why “two” if this is version 5? well, libplasma is actually going
> to be version 6 iirc, so it isn’t the library.
Not that its relevant for the rest of the discussion, but as the library
number itself is concerned you can make
I agree with Marco,
Just would like to remark that building the styles for qtquickcontrols
should be top priority.
2013/8/19 Marco Martin
> On Monday 19 August 2013, Aaron J. Seigo wrote:
> > no matter how wonderful it is to have a single shared implementation
> > upstream so we don’t have to
On Monday 19 August 2013, Aaron J. Seigo wrote:
> no matter how wonderful it is to have a single shared implementation
> upstream so we don’t have to do anything but implement applications, we
> have to hit the three points above.
>
> in the end API, stability and device spectrum are what matters
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112127/#review38171
---
Ship it!
Ship It!
- Sebastian Kügler
On Aug. 16, 2013, 8:58
On Monday, August 19, 2013 22:17:43 Ivan Čukić wrote:
> Can we move it for Wednesday? I have a meeting tomorrow.
I have one on wednesday. :)
Let's just get over it, we can always talk off-meeting.
--
sebas
http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
Can we move it for Wednesday? I have a meeting tomorrow.
Cheers,
Ivan
On 19 August 2013 22:13, Sebastian Kügler wrote:
> Hey,
>
> Due to a "party-induced incapacitation" this Monday, our weekly meeting is
> scheduled for Tuesday, 12:00 Europe/Amsterdam.
>
> See you!
> --
> sebas
>
> http://w
Hey,
Due to a "party-induced incapacitation" this Monday, our weekly meeting is
scheduled for Tuesday, 12:00 Europe/Amsterdam.
See you!
--
sebas
http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
___
Plasma-devel mailing list
Plasma-dev
Hi...
after seeing the Nth time that we don’t know if the next release will be
called Plasma Workspaces 2 or something else, i’d like to find consensus on
this point so we can move forward in communication with confidence.
the first point that we’ve all been around a million times, but i will c
On Monday, August 19, 2013 01:05:50 David Edmundson wrote:
> After discussions with a few people, I decided for an experiment to port
> PlasmaComponents Button to use QtQuickControls [1] internally but use the
> styles API [2] to make it look like the original PlasmaComponents button.
the things s
On Monday 19 August 2013 20:55:49 Martin Graesslin wrote:
> On Monday 19 August 2013 22:38:09 Bhushan Shah wrote:
> > Hello,
> >
> > I am using project-neon5 on KUbuntu 13.04. I have every packages
> > installed on my computer which is required to build. I can not build
> > kwin, kstyles and power
On Monday 19 August 2013 22:38:09 Bhushan Shah wrote:
> Hello,
>
> I am using project-neon5 on KUbuntu 13.04. I have every packages
> installed on my computer which is required to build. I can not build
> kwin, kstyles and powermanagement data engine so I have to disable it
> for building kde-work
Hello,
I am using project-neon5 on KUbuntu 13.04. I have every packages
installed on my computer which is required to build. I can not build
kwin, kstyles and powermanagement data engine so I have to disable it
for building kde-workspace.
CMake exits saying that XCB Libraries are not installed. [
> On Aug. 17, 2013, 2:26 a.m., Marco Martin wrote:
> > Hmm, not sure about it, the packages were defined as archives with
> > metadata.desktop in the root, this would basically allow a quirks mode, do
> > we want to support malformed packages?
Ok, I just tried repackaging Helium from kde-look.
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112157/#review38149
---
Ship it!
One comment below needs addressing.
engineexplorer/
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112157/
---
Review request for Plasma.
Description
---
Hello,
* this replaces th
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112143/
---
(Updated Aug. 19, 2013, 2:19 p.m.)
Status
--
This change has been mar
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112143/
---
(Updated Aug. 19, 2013, 2:15 p.m.)
Review request for Plasma.
Changes
--
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112143/
---
Review request for Plasma.
Description
---
Enable compilation of the
Right, that's basically what I had in mind when I said I can split things
into the style files.
The key thing I was trying to stress is that we don't need to implement a
whole style before we can start using it from some PlasmaComponents to get
benefits and that we don't need to port all the plasm
On Monday 19 August 2013, Eike Hein wrote:
> On Monday 19 August 2013 11:55:14 Marco Martin wrote:
> > for being able to do a decent desktop application (or even just the
> > settings dialogs) some things are still needed, in part feature missing,
> > in part making it play well with oxygen (and ox
On Monday 19 August 2013 11:55:14 Marco Martin wrote:
> for being able to do a decent desktop application (or even just the settings
> dialogs) some things are still needed, in part feature missing, in part
> making it play well with oxygen (and oxygen play well with them) since it's
> a qstyle inf
On Monday 19 August 2013, David Edmundson wrote:
> > If this will be how we proceed, it shouldn't be done inline, but as a
> > standalone style together the others.
>
> So there's 3 proposals being talked about here:
> - We keep Plasma Components as is
> - We create a proper QtQuick Controls sty
On Mon, Aug 19, 2013 at 10:55 AM, Marco Martin wrote:
> On Monday 19 August 2013, David Edmundson wrote:
> > After discussions with a few people, I decided for an experiment to port
> > PlasmaComponents Button to use QtQuickControls [1] internally but use the
> > styles API [2] to make it look li
On Monday 19 August 2013, David Edmundson wrote:
> After discussions with a few people, I decided for an experiment to port
> PlasmaComponents Button to use QtQuickControls [1] internally but use the
> styles API [2] to make it look like the original PlasmaComponents button.
>
> This is pushed in
On Monday 19 August 2013 01:05:50 David Edmundson wrote:
> I think given the current API changes it makes sense to use this
> opportunity to make this change. I believe we will get better more stable
> code for it. I can do most the changes.
I'm with you on this, and I'm really relieved it turned
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112073/#review38112
---
This is ... extremely surprising.
plasma-desktop registers to D
> On Aug. 19, 2013, 10:33 a.m., Aleix Pol Gonzalez wrote:
> > FWIW this is also being used in the KTp chat plasmoid, in a hack so the
> > dialog doesn't appear in the tasks list.
well that should be done differently. IIRC the PlasmaCore.Dialog already
exposes a flags attribute, so we should ma
On Mon, Aug 19, 2013 at 2:05 AM, David Edmundson wrote:
> After discussions with a few people, I decided for an experiment to port
> PlasmaComponents Button to use QtQuickControls [1] internally but use the
> styles API [2] to make it look like the original PlasmaComponents button.
>
> This is pu
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112033/#review38100
---
FWIW this is also being used in the KTp chat plasmoid, in a hac
Hello,
On Mon, Aug 19, 2013 at 1:33 PM, Martin Graesslin wrote:
> And to fix this problem I just split XCB into components:
> https://git.reviewboard.kde.org/r/112151/
So this will require me to rebuild plasma-framework and then
kde-workspace.. okay but which xcb packages I need to install in
KU
On Monday 19 August 2013 07:40:11 Kevin Ottens wrote:
> On Sunday 18 August 2013 09:50:48 Bhushan Shah wrote:
> > Hello,
> >
> > On Sat, Aug 17, 2013 at 11:55 PM, Giorgos Tsiapaliokas
> >
> > wrote:
> > > show us the cmake errors :)
> >
> > http://paste.kde.org/pd1e6e267/
> >
> > I have XCB de
On Mon, Aug 19, 2013 at 11:10 AM, Kevin Ottens wrote:
> XCB packages are generally modularized by distros. Are you sure you have the
> devel packages for xcb keysyms and xcb xtest? Those two are reported as
> missing.
Yes! I am using KUbuntu. And tried installing libxcb*-dev packages,
xcb-proto
45 matches
Mail list logo
