Hi list The themes are merged in. Update lxqt-common and try them out! J. Leclanche
On Wed, May 21, 2014 at 3:20 AM, Jerome Leclanche <adys...@gmail.com> wrote: > Hi, > > Quick comment first: Let's leave the -opaque versions out of the > repository for now. Will figure out the compositing issues before 0.8 > release as they're targeted. > I'll explain how to do it; can't hurt. > Little set up first though: you will need git installed. If you've > never used git before, you will need to set your real name and an > email address of your choice with `git config --global user.name "My > Name"` and `git config --global user.email "<m...@example.com>"`. > Remember to also set a SSH key in your Github account in order to be > able to be able to read/write with ssh! > > Once you got those things ready: > > - First step is to fork the lxqt-common repository to your github > account by clicking the "Fork" link at the top right of the > repository. > - Then, clone your fork of the repository locally with git clone > g...@github.com:<your-account>/lxqt-common.git. > - In your local repository, create a new branch. Call it, say, > new-themes with "git checkout -b new-themes" > - Move your themes to lxqt-common/themes/ and add them to the tree; > one per commit please. Do this with git add flat-dark && git commit -m > "Add dark theme"; git add plasma-next && git commit -m "Add > plasma-next theme" > - You can now push your branch to your personal fork of the > lxqt-common repository. That fork (remote) was automatically assigned > the name "origin" when you cloned. Usually, you would just do "git > push", but on your first push from a branch you need to be more > specific: `git push --set-upstream origin new-themes` > - If everything went well, you should have successfully pushed your > changes to your fork in the "new-themes" branch. If you go to the web > URL for that fork (github.com/<you>/lxqt-common.git), you will see a > green button at the top of the repository that detected that push and > will suggest you to open a pull request. Do so, and you are done :-) > > PS: If you ever need to modify code in a pull request, you can do so > with more advanced git commands (git commit --amend, for example) and > then use `git push --force` to force-push destructive changes to your > fork. Github is smart and will update the PR for you. > > Let me know if you can do all this; I know it can be a bit overwhelming. > J. Leclanche > > > On Wed, May 21, 2014 at 2:52 AM, Inti <intialo...@gmail.com> wrote: >> Jerome, could you help me pulling the themes to the repo? I was unable to do >> it. >> >> Here are the latest versions (including the credit for KDE and small fixes): >> http://goo.gl/7CgSd4 >> >> >> >> 2014-05-19 20:24 GMT-05:00 Jerome Leclanche <adys...@gmail.com>: >> >>> On Tue, May 20, 2014 at 1:58 AM, Inti <intialo...@gmail.com> wrote: >>> > Writing from my Gmail account, shame on you Yahoo! >>> >>> =/ >>> >>> > >>> > As told you earlier today, the KDE VIsual Team have no problems with >>> > the >>> > port I did from their Plasma Next theme, just asked for some credits. >>> > >>> >>> Yay KDE team :) >>> >>> > I included a comment at the begining of panel.qss and wallpaper.cfg, >>> > which >>> > are the main parts where the port take place. >>> >>> Please also make sure you add a mention in the lxqt-common README >>> file. Something like "LXQt 'Plasma' theme based on KDE Plasma by the >>> KDE Visual Team". >>> >>> > >>> > Both themes are unfinished, but Im trying to pull them to github and I >>> > must >>> > confess Im a little lost (Im a graphic designer!), I understand I must >>> > fork >>> > the repo (lxqt-common) then add my themes, push them to my forked repo >>> > and >>> > then pull the request to the upstream one. It is right? >>> >>> Using git is optional for one-time contributors, though if you intend >>> to do lots of contributions you will want to set it up at some point. >>> Here is a document by Github on how to use pull requests: >>> https://help.github.com/articles/using-pull-requests >>> You can ping me on IRC (Freenode/OFTC #lxde jleclanche) when I'm awake >>> if you need help with this. >>> >>> > >>> > One more question: I did two versions of each theme (Transparent and >>> > opaque) >>> > because in my system the panel turn invisible if I apply a theme with >>> > transparency and without compositing (i saw a bug about this) so the >>> > workaround I found was to have two versions of the theme. Am I right? >>> >>> This is a known bug. We don't really know what to do about it right >>> now. For now, just assume compositing is on, no need to do a second >>> version. >>> >>> > >>> > >>> > ------------------------------------------------------------------------------ >>> > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE >>> > Instantly run your Selenium tests across 300+ browser/OS combos. >>> > Get unparalleled scalability from the best Selenium testing platform >>> > available >>> > Simple to use. Nothing to install. Get started now for free." >>> > http://p.sf.net/sfu/SauceLabs >>> > _______________________________________________ >>> > Lxde-list mailing list >>> > Lxde-list@lists.sourceforge.net >>> > https://lists.sourceforge.net/lists/listinfo/lxde-list >>> > >> >> ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Lxde-list mailing list Lxde-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxde-list
