Re: [kde-community] QtCurve
On Mon, Jan 27, 2014 at 1:48 PM, Albert Astals Cid wrote: > 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 >> >> 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? I'm thinking pretty much the same thing with oxygen-gtk and oxygen-transparent. Is that a standalone repo? Yichao Yu > > 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
On Mon, Jan 27, 2014 at 11:21 AM, Yuri Chornoivan wrote:
> написане Mon, 27 Jan 2014 17:55:20 +0200, Yichao Yu :
>
>
>> 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
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 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
On Tue, Jan 21, 2014 at 4:44 PM, Jeremy Whiting wrote: > On Tue, Jan 21, 2014 at 2:19 PM, Yichao Yu wrote: >> Sorry but I'm a little bit confused. >> According to what I have heard before, supports from the sysadmin and >> other teams are necessary anyway if a project want to join the KDE >> community and the list on the wiki page are very similar to what I >> have heard of before incubator. So what's the difference between going >> through the incubator or not? Is it a new name and a more organized >> procedure to deal with all that's necessary for joining the community? > > Yes, the Incubator is basically just making sure the process of > joining the community is documented. It also > can help make sure someone in the community is available to help those > members of the outside project > become familiar with our community policies, how everything works, etc. In which case it seems to be a necessary step and useful resources for joining projects (including QtCurve if it is accepted) and I'm glad to learn how all these works once we are there. Yichao Yu ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] QtCurve
On Tue, Jan 21, 2014 at 1:18 AM, Kevin Ottens wrote: > > That *and* the incubator is also meant for projects having a "not yet part of > KDE" team joining. For instance if VLC would ever want to join (random Not sure how VLC ppl feel but I am happy to see that happen. =) > example) it would go through the incubator still, even though it is "is > already stable and have made several releases that are packaged by a number of > distributions". The purpose of the incubator is not just technical but also to > make sure projects are well alive, active and integrated in the community. > > Now, does it apply to QtCurve? At a glance I thought it did, I can't really > say for sure and could be totally wrong. :-) > Sorry but I'm a little bit confused. According to what I have heard before, supports from the sysadmin and other teams are necessary anyway if a project want to join the KDE community and the list on the wiki page are very similar to what I have heard of before incubator. So what's the difference between going through the incubator or not? Is it a new name and a more organized procedure to deal with all that's necessary for joining the community? Thank you for you clarification Yichao Yu ___ 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 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 Mon, Jan 20, 2014 at 12:32 PM, Martin Sandsmark wrote: > On Mon, Jan 20, 2014 at 08:53:34AM -0500, Yichao Yu wrote: >> I would like to move QtCurve to the KDE infrastructure > > Yes! :-D > > I've been using QtCurve for a while now, and I'd even argue for replacing > Oxygen with it for KDE Plasma Desktop Framework Visual Team Studio 5 SC > Edition 2014.1, with the right default configuration it would be a refreshing > new default style. But I don't have the argument stamina for that. :-P I'm glad you like it and thank you for you support ;). However, I don't really think it is a good idea to replace the default theme right now both because it is not as polished as oxygen (which is what I'm mainly working on) and because it has similar blacklist problem with oxygen-transparent (because it also provide transparent background support, which is actually an advantage of not being the default theme). I do think that it will be helpful to make it an alternative to the oxygen theme and that's also why I am sending the email. Yichao Yu P.S. at the same time, your email remind me a point that I was missing. AFAIK, QtCurve is the first and only 3rd party Qt5 theme that has been packaged by distribution (ArchLinux). This should be useful before Oxygen-Qt5/KF5 is released :-P. > > -- > Martin Sandsmark > ___ > 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 9:29 AM, David Edmundson wrote: > Brilliant. > > So the next page to read is > http://techbase.kde.org/Policies/Application_Lifecycle. It explains > the entrance process and the SC vs extragear. > Yes, I've also read that and thank you for your explaination. I believe QtCurve will fit into extragears if it is merged. > Slightly off-topic: If you have QtQuickControls rendering issues, can > you please message me privately with a list of bugs. > ___ > 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 9:11 AM, David Edmundson wrote: > I think this makes a lot sense and I would welcome QtCurve into KDE. Thank you for your support. > > Can you read though http://manifesto.kde.org/ and confirm you would > agree to all the commitments > (http://manifesto.kde.org/commitments.html) of a KDE Yes, I've already read them and I agree with all of them. For license, although there isn't any public libraries in QtCurve yet, in order to minimize confision if part of the API in QtCurve is made public (unlikely but possible for configure UI's) I've already relicensed[3] all the code under LGPL instead of GPL two months ago. [3] https://github.com/QtCurve/qtcurve#license project. > > David > ___ > 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
[kde-community] QtCurve
Hi, My name is Yichao Yu (yuyichao). I started to use KDE as my main DE about one and two years ago and started contributing to some KDE projects soon after including konsole, kdelibs, dolphin etc.. I have recently (about half a year ago) adopted QtCurve[1], a highly configurable theme engine for Qt3, Qt4, Qt5, KWin4 and Gtk2. For those who don't know QtCurve yet, it is the theme engine used by more than half of the widget themes on kde-look. The project was started by Craig Drummond in (or before) 2006 and is now included in most distributions. I would like to move QtCurve to the KDE infrastructure for several reasons. Besides the most obvious ones like making use of the repo, wiki, bug trackers etc. : - As a KDE friendly cross toolkit style engine, this will help me and future QtCurve developer to keep up-to-date with API changes in KDE (e.g. the shadow handling change in 4.8 and the appmenu support in 4.10). - It will also make it easier for KWin developers to make sure their API changes "are sane", especially for the KF5 port. Personally, I have always been hoping to join the KDE community and get involved in the development more. I was not very sure whether QtCurve can fit into the KDE community since kdelibs is just a minor optional dependency and I'm still working on making it to work better outside KDE. However, Martin (the KWin one...) convinced me that KDE is not just a collection of softwares that links to kdelibs or can only run in KDE (the desktop environment) and that's the reason I'm sending this email. Looking forward to hear from you soon. Yichao Yu [1] https://github.com/QtCurve/qtcurve [2] http://kde-look.org/content/show.php?content=40492 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
