Please check it out. If everything is ok, it will be the 2.1 release.
As usual the package is here: http://bmpanel2.googlecode.com/files/bmpanel2-2.1pre1.tar.gz
I’ve finished theme integration to the source tree. Here is the list of themes which were integrated:
The reason why I’ve included these themes into the source tree is because they are nicely showing what can you do with bmpanel2.
And now the important part:
All themes in the source tree are named like that: “long-theme-name” (e.g. alduin-glossy, xsocam-dark, flora-green, etc.). It means that after updating to the latest git or to 2.1 you’ll probably need to clean a little bit your ~/.local/share/bmpanel2/themes directory and maybe tweak a config file. Please notice that “xsocam_dark” was renamed to “xsocam-dark” too.
Changes since 2.0.1a (basicly just a copy&paste from git log):
The 2.1 release isn’t here yet. But soon it will be there.
I hope now it is somewhat complete. Check it out there: http://nsf.110mb.com/bmpanel2themeref.
If something isn’t clear, mail me. If you know how to explain some things better than I do, or you’ve spotted a misspelling – mail me also. My english sucks and I wish I could make the reference better somehow. Also if you want to translate it or do something else with it – feel free to do it, I don’t care about any kind of copyrights here.
See ya!
P.S. You can find sources of this reference in the git.
I had integrated the bmpanel2cfg into the build system yesterday and now I’ve returned the previous build chain for man page. In order to build man page properly you need to have asciidoc package and docbook-xsl stylesheets. Currently CMake build script tries to detect the a2x tool and if it’s here then tries to build the man page. A2x toolchain manager is a part of the asciidoc package usually and in the archlinux for example asciidoc depends on the docbook-xsl package too, so.. everything should be ok here. But I have no idea how it will work in other linux distributions. If you have any problems – mail me.
P.S. Even though writing a comment on the blog seems like a faster way to give your feedback to me. It’s actually not. WordPress spam filter often sucks up your comments and I don’t get any mail notifications in that case. I check spammed messages rarely. So.. really.. if you have something to ask – mail me. Fortunatelly, the gmail has the best spam filter I’ve ever seen and it hardly ever puts important mail in a spam folder.
Recently I’ve been working on bmpanel2cfg integration into cmake build chain. And it looks like everything works now. If CMake sees the python interpreter it will install the bmpanel2cfg script along with bmpanel2. DESTDIR should work too. But if you’re packaging bmpanel2 and encountering some problems with that, please let me now.
Actually there are very few things left before I will make the 2.1 release. I think the project has accumulated a lot of changes and it’s time to make a fresh release. But before that I need to:
As you may have noticed, the wiki pages on the code.google.com site are gone. It’s the result of me trying to make a Mercurial mirror for bmpanel2. But apparently code.google.com totally can’t do wiki repository conversions. So.. There is a big mess. I’m trying to get over those bugs, but currently I can’t do anything about it.
Btw, the contents of wiki pages are saved. Probably all this may result in a project hosting migration. I’m really disappointed about code.google.com. The *only* thing I like there is the bug tracker.
UPDATE: The wiki is back..
But comments are lost, sorry for that. I think it’s not critical.
It is in the git repository. You can find it using this path: extra/py
There are few files:
You can try out this tool using the script directly (./bmpanel2cfg) or install it first using the standard way (python setup.py install) and then just run directly (bmpanel2cfg).
There are few caveats however, for example script currently will work only with single instance of bmpanel2 and there are still no support for multiple launch bars (support for this also lacks in the panel, so it makes sense).
Anyway, just try it out and say what you think. Bug reports -> here <-.
Don’t forget to backup your bmpanel2rc
It’s almost there. All functions are complete, but I need to test it a bit more for rare usage cases before uploading to public. It looks like this:
All changes in the tool are immediately reflected on the panel. And as far as I’ve tested it, this amount of reconfigure signals doesn’t burst the CPU up, so it should be really nice addition to the panel. I’ll try to upload it in few days, keep watching blog for updates.