On Monday 28 March 2011, you wrote:
> Hi all,
> an update on this issue,
> I had got permission from the authors to relicense under the LGPL all the
> files that were GPL.
>
> If there are not significant issues, i would like to move this into master,
> in the experimental folder, meaning changes
On Tuesday 22 February 2011, Stephen Kelly wrote:
> Marco Martin wrote:
> > Hi all,
> > in kdelibs there is since some time a branch called plasma/declarative
> > that contains a new little library, that depends at the moment on kdecore
> > and kdeui (probably is possible to make it depend only fro
On Tuesday 22 February 2011, Stephen Kelly wrote:
> Marco Martin wrote:
> > Hi all,
> > in kdelibs there is since some time a branch called plasma/declarative
> > that contains a new little library, that depends at the moment on kdecore
> > and kdeui (probably is possible to make it depend only fro
On Tuesday 22 February 2011, Ian Monroe wrote:
> On Tue, Feb 22, 2011 at 14:41, Marco Martin wrote:
> > Hi all,
> > in kdelibs there is since some time a branch called plasma/declarative
> > that contains a new little library, that depends at the moment on
> > kdecore and kdeui (probably is possib
On Wednesday 23 February 2011, Artur de Souza wrote:
> Quoting Ian Monroe :
> > So should there be a Qt.components.plasma? Its not really clear to me
> > how Qt.components.meego would be inappropriate for Plasma though.
>
> Because they will have the look&feel of meego and we have our own look&fee
On Wednesday, February 23, 2011, Artur de Souza wrote:
> Quoting Ian Monroe :
> > So should there be a Qt.components.plasma? Its not really clear to me
> > how Qt.components.meego would be inappropriate for Plasma though.
>
> Because they will have the look&feel of meego and we have our own look&f
Em quarta-feira, 23 de fevereiro de 2011, às 13:47:49, Artur de Souza
escreveu:
> Quoting Ian Monroe :
> > So should there be a Qt.components.plasma? Its not really clear to me
> > how Qt.components.meego would be inappropriate for Plasma though.
>
> Because they will have the look&feel of meego an
Quoting Ian Monroe :
So should there be a Qt.components.plasma? Its not really clear to me
how Qt.components.meego would be inappropriate for Plasma though.
Because they will have the look&feel of meego and we have our own look&feel :)
MeeGo also have some widgets that are only useful when usi
On Wed, Feb 23, 2011 at 05:54, Artur de Souza wrote:
> Quoting Ian Monroe :
>>
>> I understand the need to provide to the QML developer stuff like i18n
>> and a way to look up the location of icons, but I'm less sure having
>> an actual QIcon/KIcon object. We're going to want to make use of Qt
>>
Quoting Ian Monroe :
I understand the need to provide to the QML developer stuff like i18n
and a way to look up the location of icons, but I'm less sure having
an actual QIcon/KIcon object. We're going to want to make use of Qt
Components right? So until thats sorted out and we're able to
"sub-cl
On Tue, Feb 22, 2011 at 14:41, Marco Martin wrote:
> Hi all,
> in kdelibs there is since some time a branch called plasma/declarative that
> contains a new little library, that depends at the moment on kdecore and kdeui
> (probably is possible to make it depend only from kdecore) that is meant to
Marco Martin wrote:
> Hi all,
> in kdelibs there is since some time a branch called plasma/declarative
> that contains a new little library, that depends at the moment on kdecore
> and kdeui (probably is possible to make it depend only from kdecore) that
> is meant to be used in QML applications.
Hi all,
in kdelibs there is since some time a branch called plasma/declarative that
contains a new little library, that depends at the moment on kdecore and kdeui
(probably is possible to make it depend only from kdecore) that is meant to be
used in QML applications.
see http://mail.kde.org/pipe
13 matches
Mail list logo
