Re: [kde-community] QtCurve
Hi, we get to welcome QtCurve to KDE today. \o/ The migration is done, the code now resides in kde:qtcurve and Bugzilla and ReviewBoard have been set up as well. The KDE i18n crew is currently working on integrating the existing translations into their infra and letting scripty loose on them. Cheers, Eike ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] QtCurve
On Wednesday 23 July 2014 23:15:42 Eike Hein wrote: Hi, we get to welcome QtCurve to KDE today. \o/ The migration is done, the code now resides in kde:qtcurve and Bugzilla and ReviewBoard have been set up as well. welcome and thanks Eike for helping on getting this important piece of our Plasma workspaces to the KDE infrastructure. Time to run kdesrc-build ;-) Cheers Martin signature.asc Description: This is a digitally signed message part. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] QtCurve
понеділок, 27-січ-2014 09:54:01 Yichao Yu написано: On Mon, Jan 20, 2014 at 9:29 AM, David Edmundson da...@davidedmundson.co.uk wrote: In short we leave this thread for a few days for anyone else to make positive or negative comments about the software entering KDE. Then if everyone approves we merge your code into our repos. It then goes through a mandatory 2 weeks in kdereview where people discuss any technical/license/translation issues. It has been a week since I sent the initial email and 6 days since the last reply in the thread. I'm wondering if it is the time to proceed (or should we wait longer or is there anything else I should do before that). Happy Chinese new year. Yichao Yu Hi, Just want to notice that QtCurve has well-established translation infrastructure unlike some recent approved KDE projects. It would be great to have it with ready-to-release translations in KDE catalogs. :) Best regards, Yuri ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] QtCurve
On Mon, Jan 27, 2014 at 10:32 AM, Yuri Chornoivan Just want to notice that QtCurve has well-established translation infrastructure unlike some recent approved KDE projects. It would be great to have it with ready-to-release translations in KDE catalogs. :) As for translation, I actually have a few questions: 1, If the translations of QtCurve is merged with kde-i18n, is it still possible to release the translations along with QtCurve itself? Will this also make it harder to make git package? (like this[1]). 2, I've noticed that KDE has automatic tools to merge tranlations into desktop files. I'm wondering if its behavior can be custimized. E.g. is it possible to make the merge at build time (not so bad if this is not possible) and can it support non-standard (QtCurve specific) desktop file (or maybe I should call it ini file). I might want to add sth like this to QtCurve in the near future (mainly for the configure system) and I don't think it is a good idea to modify the KDE scripts for QtCurve because I would like to keep the freedom to change how these QtCurve internal files are handled. Yichao Yu [1] https://aur.archlinux.org/packages/qtcurve-git/ ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] QtCurve
On Mon, Jan 20, 2014 at 9:29 AM, David Edmundson da...@davidedmundson.co.uk wrote: In short we leave this thread for a few days for anyone else to make positive or negative comments about the software entering KDE. Then if everyone approves we merge your code into our repos. It then goes through a mandatory 2 weeks in kdereview where people discuss any technical/license/translation issues. It has been a week since I sent the initial email and 6 days since the last reply in the thread. I'm wondering if it is the time to proceed (or should we wait longer or is there anything else I should do before that). Happy Chinese new year. Yichao Yu ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] QtCurve
написане Mon, 27 Jan 2014 17:55:20 +0200, Yichao Yu yyc1...@gmail.com:
On Mon, Jan 27, 2014 at 10:32 AM, Yuri Chornoivan
Just want to notice that QtCurve has well-established translation
infrastructure unlike some recent approved KDE projects. It would be
great to
have it with ready-to-release translations in KDE catalogs. :)
As for translation, I actually have a few questions:
1, If the translations of QtCurve is merged with kde-i18n, is it still
possible to release the translations along with QtCurve itself? Will
this also make it harder to make git package? (like this[1]).
Sure. Just use release script from kdesdk to download the translations
from SVN and package QtCurve traball. The ready-to-use tarball can be
placed on KDE ftp or anywhere else if you like. Not sure if it can be
automated for the releases without any tag (just a modification hash in
git) though.
2, I've noticed that KDE has automatic tools to merge translations into
desktop files. I'm wondering if its behavior can be customized. E.g.
is it possible to make the merge at build time (not so bad if this is
not possible) and can it support non-standard (QtCurve specific)
desktop file (or maybe I should call it ini file). I might want to add
sth like this to QtCurve in the near future (mainly for the configure
system) and I don't think it is a good idea to modify the KDE scripts
for QtCurve because I would like to keep the freedom to change how
these QtCurve internal files are handled.
Yes, this can be done. Just name these files with .desktop extension then
rename them with CMake magic at the installation time.
Example:
install( FILES
sth.desktop
DESTINATION ${DATA_INSTALL_DIR}/qtcurve/ini
RENAME sth.ini
)
Hope this helps.
Best regards,
Yuri
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] QtCurve
On Mon, Jan 27, 2014 at 11:21 AM, Yuri Chornoivan yurc...@ukr.net wrote:
написане Mon, 27 Jan 2014 17:55:20 +0200, Yichao Yu yyc1...@gmail.com:
On Mon, Jan 27, 2014 at 10:32 AM, Yuri Chornoivan
Just want to notice that QtCurve has well-established translation
infrastructure unlike some recent approved KDE projects. It would be
great to
have it with ready-to-release translations in KDE catalogs. :)
As for translation, I actually have a few questions:
1, If the translations of QtCurve is merged with kde-i18n, is it still
possible to release the translations along with QtCurve itself? Will
this also make it harder to make git package? (like this[1]).
Sure. Just use release script from kdesdk to download the translations from
SVN and package QtCurve traball. The ready-to-use tarball can be placed on
KDE ftp or anywhere else if you like. Not sure if it can be automated for
the releases without any tag (just a modification hash in git) though.
2, I've noticed that KDE has automatic tools to merge translations into
desktop files. I'm wondering if its behavior can be customized. E.g.
is it possible to make the merge at build time (not so bad if this is
not possible) and can it support non-standard (QtCurve specific)
desktop file (or maybe I should call it ini file). I might want to add
sth like this to QtCurve in the near future (mainly for the configure
system) and I don't think it is a good idea to modify the KDE scripts
for QtCurve because I would like to keep the freedom to change how
these QtCurve internal files are handled.
Yes, this can be done. Just name these files with .desktop extension then
rename them with CMake magic at the installation time.
The problem is not with the extension names, but the names of the
fields. I.e. the names of the fields may not starts with _ and may not
have the standard translatable names (e.g. Name, Comment etc.)
Example:
install( FILES
sth.desktop
DESTINATION ${DATA_INSTALL_DIR}/qtcurve/ini
RENAME sth.ini
)
Hope this helps.
Best regards,
Yuri
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] QtCurve
El Dilluns, 27 de gener de 2014, a les 09:54:01, Yichao Yu va escriure: On Mon, Jan 20, 2014 at 9:29 AM, David Edmundson da...@davidedmundson.co.uk wrote: In short we leave this thread for a few days for anyone else to make positive or negative comments about the software entering KDE. Then if everyone approves we merge your code into our repos. It then goes through a mandatory 2 weeks in kdereview where people discuss any technical/license/translation issues. It has been a week since I sent the initial email and 6 days since the last reply in the thread. I'm wondering if it is the time to proceed (or should we wait longer or is there anything else I should do before that). Looks good to me, are you planning a standlone repo or want to merge the code into an existing repo as David was suggesting? Cheers, Albert Happy Chinese new year. Yichao Yu ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] QtCurve
El Dilluns, 27 de gener de 2014, a les 10:55:20, Yichao Yu va escriure: On Mon, Jan 27, 2014 at 10:32 AM, Yuri Chornoivan Just want to notice that QtCurve has well-established translation infrastructure unlike some recent approved KDE projects. It would be great to have it with ready-to-release translations in KDE catalogs. :) As for translation, I actually have a few questions: 1, If the translations of QtCurve is merged with kde-i18n, is it still possible to release the translations along with QtCurve itself? Depends on the answer you make to my previous email (separate repo or in existing one) Will this also make it harder to make git package? (like this[1]). Yes. 2, I've noticed that KDE has automatic tools to merge tranlations into desktop files. I'm wondering if its behavior can be custimized. E.g. is it possible to make the merge at build time (not so bad if this is not possible) No, merge at build time is not possible since it means you would need a checkout of all the languages to build, which given how big the svn l10n repo is, it is something you don't really want :D Cheers, Albert and can it support non-standard (QtCurve specific) desktop file (or maybe I should call it ini file). I might want to add sth like this to QtCurve in the near future (mainly for the configure system) and I don't think it is a good idea to modify the KDE scripts for QtCurve because I would like to keep the freedom to change how these QtCurve internal files are handled. Yichao Yu [1] https://aur.archlinux.org/packages/qtcurve-git/ ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] QtCurve
El Dilluns, 27 de gener de 2014, a les 18:21:58, Yuri Chornoivan va escriure:
написане Mon, 27 Jan 2014 17:55:20 +0200, Yichao Yu yyc1...@gmail.com:
On Mon, Jan 27, 2014 at 10:32 AM, Yuri Chornoivan
Just want to notice that QtCurve has well-established translation
infrastructure unlike some recent approved KDE projects. It would be
great to
have it with ready-to-release translations in KDE catalogs. :)
As for translation, I actually have a few questions:
1, If the translations of QtCurve is merged with kde-i18n, is it still
possible to release the translations along with QtCurve itself? Will
this also make it harder to make git package? (like this[1]).
Sure. Just use release script from kdesdk to download the translations
from SVN and package QtCurve traball. The ready-to-use tarball can be
placed on KDE ftp or anywhere else if you like. Not sure if it can be
automated for the releases without any tag (just a modification hash in
git) though.
2, I've noticed that KDE has automatic tools to merge translations into
desktop files. I'm wondering if its behavior can be customized. E.g.
is it possible to make the merge at build time (not so bad if this is
not possible) and can it support non-standard (QtCurve specific)
desktop file (or maybe I should call it ini file). I might want to add
sth like this to QtCurve in the near future (mainly for the configure
system) and I don't think it is a good idea to modify the KDE scripts
for QtCurve because I would like to keep the freedom to change how
these QtCurve internal files are handled.
Yes, this can be done. Just name these files with .desktop extension then
rename them with CMake magic at the installation time.
That's a bit nasty when we have ExtraDesktop.sh file you can use to feed the
.desktop extractor files that don't have the .desktop file extension but still
have the .desktop syntax.
Cheers,
Albert
Example:
install( FILES
sth.desktop
DESTINATION ${DATA_INSTALL_DIR}/qtcurve/ini
RENAME sth.ini
)
Hope this helps.
Best regards,
Yuri
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] QtCurve
On Mon, Jan 20, 2014 at 10:12 AM, Kevin Ottens er...@kde.org wrote: Hello, Note there's the incubator now for existing projects willing to join: http://community.kde.org/Incubator I have seen the email of the restarted Incubator project before but I thought it was mainly for start up projects? QtCurve (although being not very polished) is already stable and have made several releases that are packaged by a number of distributions. Is there anything I am missing here? Yichao Yu ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] QtCurve
On Monday 20 January 2014 17:13:47 Yichao Yu wrote: QtCurve (although being not very polished) is already stable and have made several releases that are packaged by a number of distributions. Is there anything I am missing here? I think Kevin just wanted to point out there's an additional wiki page we can link now :) I think this thread and the steps that have been discussed basically meet what's outlined there, so it's all good. It comes down to the Manifesto and the kdereview-en-route- to-Extragear thing, and since the former's already been covered and QtCurve is a well-established codebase that's working for real people for a long time already I don't think there's likely to be significant problems. BTW: Super-happy to hear about this, welcome! Yichao Yu Cheers, Eike ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
