Emdek / plasmoid-adjustable-clock

Plasmoid to show date and time in adjustable format
GNU General Public License v2.0
20 stars 5 forks source link

KDE5 port #16

Open Emdek opened 9 years ago

KottV commented 9 years ago

Yea. We want it and we need it.

jesusdaz commented 9 years ago

About this port,

debian bug #795109 reads: "Plasma 5 has arrived to debian testing a few weeks ago and so all Plasma 4 widgets have become unusable."

Emdek commented 9 years ago

@jesusdaz, yeah, Plasma5 requires QML with is sad...

jesusdaz commented 9 years ago

Yes, I have been told that the UI must be QML. Questions at #plasma on FreeNode, or related.

Let me know if you want I ask for the removal of the Debian package.

jesusdaz commented 9 years ago

I have requested the removal of the package from Debian testing and Debian unstable, as it is unusable to the Plasma5 is already there.

Emdek commented 9 years ago

@jesusdaz, just when I'm about to start porting? ;-)

jesusdaz commented 9 years ago

Do not worry, I will package it again.

Just let me know when it is ready. Add a comment here or send me an email.

Best regards

Emdek commented 9 years ago

@jesusdaz, sure, I'll reference this ticket in commits. I'm not familiar with possible consequences, won't it break changelog continuity and stuff?

jesusdaz commented 9 years ago

@Emdek , I have canceled the removal, to make all easier.

Emdek commented 9 years ago

@jesusdaz, OK.

KottV commented 8 years ago

Hmmm. Any news/chances?

Emdek commented 8 years ago

@KottV, sorry, no progress yet. But since Mageia is going to adopt KDE5 soon I will be forced to finally solve QtWebKit vs QtWebEngine issue, I'm not sure if the latter is even viable option for this specific use case yet. :-/

fancywriter commented 8 years ago

Hi @Emdek! Do you have any luck? As far as I understand, this version is incompatible with KDE-5, right?

I don't like the standard plasmoid because font is too small.

Do you need any help?

Emdek commented 8 years ago

@p-kozlov, nothing so far, but soon I'll be forced to do something about that anyway... I don't think that there are any areas where I could get some help, I'll need to research current state of data engines and APIs exposed to QML myself anyway...