On Friday 20 July 2012, Aleix Pol wrote:
> > keep in mind the instant the qgv part is dropped 100% of the shells, all
> > plasmoids, all bindings and a good chunk of 3rd party plasmoids needs to
> > be ported (and i would be surprised if the qml1 plasmoids would work in
> > a qml2 version without b
On Fri, Jul 20, 2012 at 10:48 AM, Marco Martin wrote:
> On Friday 20 July 2012, Alex Fiestas wrote:
>> On Thursday 19 July 2012 21:18:50 Marco Martin wrote:
>> > anybody can think about technical problems about it that may be lurking?
>> > it may mean a release of the workspace that doesn't use co
On Friday 20 July 2012 10:48:44 Marco Martin wrote:
> keep in mind the instant the qgv part is dropped 100% of the shells, all
> plasmoids, all bindings and a good chunk of 3rd party plasmoids needs to be
> ported (and i would be surprised if the qml1 plasmoids would work in a qml2
> version witho
On Friday 20 July 2012, Alex Fiestas wrote:
> On Thursday 19 July 2012 21:18:50 Marco Martin wrote:
> > anybody can think about technical problems about it that may be lurking?
> > it may mean a release of the workspace that doesn't use completely
> > frameworks, so both old kdelibs and the framewo
On Friday 20 July 2012 00:47:35 Alex Fiestas wrote:
> On Thursday 19 July 2012 21:18:50 Marco Martin wrote:
> > anybody can think about technical problems about it that may be lurking?
> > it may mean a release of the workspace that doesn't use completely
> > frameworks, so both old kdelibs and the
On Friday 20 July 2012 01:50:35 Aleix Pol wrote:>
> Well, the "only" problem would be that any application using plasma
> wouldn't be able to be ported to KF5.
not if KF5 contains a libplasma1
signature.asc
Description: This is a digitally signed message part.
On Fri, Jul 20, 2012 at 2:47 AM, Alex Fiestas wrote:
> On Thursday 19 July 2012 21:18:50 Marco Martin wrote:
>> anybody can think about technical problems about it that may be lurking?
>> it may mean a release of the workspace that doesn't use completely
>> frameworks, so both old kdelibs and the
On Thu, Jul 19, 2012 at 9:18 PM, Marco Martin wrote:
> On Thursday 19 July 2012, Martin Gräßlin wrote:
>> On Thursday 19 July 2012 20:35:51 Marco Martin wrote:
>> > but the most important thing is that kf5 is kinda the last chance for big
>> > incompatime changes, at least for a long while.
>>
>>
On Thursday 19 July 2012 21:18:50 Marco Martin wrote:
> anybody can think about technical problems about it that may be lurking?
> it may mean a release of the workspace that doesn't use completely
> frameworks, so both old kdelibs and the frameworks will have to be
> distributed for some time, may
On Thursday 19 July 2012, Martin Gräßlin wrote:
> On Thursday 19 July 2012 20:35:51 Marco Martin wrote:
> > but the most important thing is that kf5 is kinda the last chance for big
> > incompatime changes, at least for a long while.
>
> do we need a libplasma in KF 5.0? Would it be a huge issue t
On Thursday 19 July 2012 20:35:51 Marco Martin wrote:
> but the most important thing is that kf5 is kinda the last chance for big
> incompatime changes, at least for a long while.
do we need a libplasma in KF 5.0? Would it be a huge issue to say libplasma is
split out of frameworks but not release
On Thu, Jul 19, 2012 at 7:27 PM, Marco Martin wrote:
> Hi all,
>
> as you know the hardest thing, by far in plasma2 is splitting anything related
> to qgraphics* out of libplasma.
> that basically means graphics-less Applet, Containment and Corona, and this
> will have to happen in time for framew
On Thursday 19 July 2012, Aleix Pol wrote:
> On Thu, Jul 19, 2012 at 7:27 PM, Marco Martin wrote:
> > Hi all,
> >
> > as you know the hardest thing, by far in plasma2 is splitting anything
> > related to qgraphics* out of libplasma.
> > that basically means graphics-less Applet, Containment and C
On Thu, Jul 19, 2012 at 7:27 PM, Marco Martin wrote:
> Hi all,
>
> as you know the hardest thing, by far in plasma2 is splitting anything related
> to qgraphics* out of libplasma.
> that basically means graphics-less Applet, Containment and Corona, and this
> will have to happen in time for framew
Hi all,
as you know the hardest thing, by far in plasma2 is splitting anything related
to qgraphics* out of libplasma.
that basically means graphics-less Applet, Containment and Corona, and this
will have to happen in time for frameworks5, regardless having a qml2 version
ready or not (i would
15 matches
Mail list logo
