DockbarX

DockbarX Themes by M7S 997 comments

Thanks for the report. I need more information, though. Step by step, how do I reproduce? Do you get any error messages if you run it in window from a terminal? dockbarx.py run-in-window

By ver. up to date, do you mean last release or code from the bazaar bransh? - Oct 10 2009
NameBar

Various Gnome Stuff by M7S 39 comments

I could add that to the next version - Oct 10 2009
DockbarX

DockbarX Themes by M7S 997 comments

Thanks for the bug report. A fix is uploaded to the bazaar branch and will be include in the next release. - Oct 07 2009
NameBar

Various Gnome Stuff by M7S 39 comments

Two ways:
- If you use compiz, open compiz settings manager and go to decorations. Change decoration windows from "any" to "!state=maxvert". That should do it. If you want all windows to be without borders and not just maximized windows, use "none" instead.

- Second option: Install maximus. It should be in the repository, I think.If you don't want all windows maximized all the time there's a gconf setting for that. I don't remember the specifics right now but google is your friend. - Oct 03 2009
DockbarX

DockbarX Themes by M7S 997 comments

Which theme do you use? Some themes blur more than other.

Does the icon theme you use have icons in suitable size? Otherwise the blurring comes from the stretching that takes place when is resized.

You can try to resize the panel some. With a little luck you'll find a setting where the icons looks sharp. - Sep 26 2009
DockbarX

DockbarX Themes by M7S 997 comments

Since I've only runned dockbarx in a virtual hardy box, I've been unable to check the compiz stuff properly. If your up to it we could try to debug opacify properly for hardy. Send me a pm here on gnome-look or re-open the bug on launchpad that dealt with opacify on hardy. - Sep 24 2009
DockbarX

DockbarX Themes by M7S 997 comments

Thanks for reporting.

I've used syntax that isn't implemented before python 2.6, it seems (hardy uses 2.5). This is quite easy to fix.

When trying dockbarx x.0.23.1 in a virtual hardy machine I noticed another show stopping "bug" for hardy users as well. Will fix both soon.


If you don't feel like waiting you could open dockbarx.py in a texteditor remove import glib at line 27 and then replace all "glib" with "gobject" and all "Exception as detail" with "Exception, detail" (quickly done with "find & replace" in gedit.) Then it should work fine with Hardy. - Sep 23 2009
DockbarX

DockbarX Themes by M7S 997 comments

That tip will go into the faq. Thanks.

As for your tip, if you go to launchpad (link above) there's a blueprint about feedback on launching. It's still under discussion so please leave any suggestions or comments about it there. - Sep 18 2009
NameBar

Various Gnome Stuff by M7S 39 comments

Thanks for the bug report. It's not every day I get one that well written! I will look into it. - Sep 18 2009
DockbarX

DockbarX Themes by M7S 997 comments

That's not supposed to happen. If you entered the correct resource class name when adding the launcher, the "task" will be at the launcher. - Sep 05 2009
DockbarX

DockbarX Themes by M7S 997 comments

If you mean that you want applications from notification area like amarok or pidgin to live in dockbarx instead, I don't know how to do that. I'm not sure if it's possible at all with the current implementations of notifiaction area in gnome/freedesktop. I would very much like this functionality myself, though. Maybe one day... - Sep 05 2009
DockbarX

DockbarX Themes by M7S 997 comments

Nice to see some more themes out there. :)


IHMO it would look better if you moved down
<if type="!launcher">
<composite bg="back_dropp" fg="self" />
</if>

so it comes after
<if type="active">
<glow color="active_color" opacity="active_opacity" />
</if>

That way you wouldn't get the glow on the triangle, but this might be a question of personal taste.

Be aware that you'll have to change <icon_pixmap></icon_pixmap> to <button_pixmap></button_pixmap> when the next version of dockbarx comes out. - Aug 22 2009
DockbarX

DockbarX Themes by M7S 997 comments

Yes, this was reported on launchpad a while back (I'm assuming it's the same bug). I installed Karmic Alpha 4 in VirtualBox yesterday to be able to fix this bug, but I've not been able to fix it yet. It seems to be caused by a changed (and undocumented?) behavior in wnck (or perhaps a bug in Karmic's current version of wnck?), not in python-numpy. - Aug 19 2009
DockbarX

DockbarX Themes by M7S 997 comments

I've not enabled any compiz depending actions as default. I don't know if I should change that. - Jul 29 2009
White theme for DockbarX 0.23.2

DockbarX Themes by pi4sek 3 comments

To make this a dockbarx 0.21.10 theme, just open the default.tar.gz file, change the name argument in <theme name = "Default"> in the config file to what you want and replace the launcher_icon.png file in pixmaps folder to your icon. And then go tell the world that you've made the first 3d party theme for dockbarx. ;) - Jul 12 2009
DockbarX

DockbarX Themes by M7S 997 comments

Yes, there are still room for improvement in that area (there has been some over the previous updates but there are still a lot to do). - Jul 07 2009
DockbarX

DockbarX Themes by M7S 997 comments

Ok, that sounds more like a bug. ;)

Could you explain it in more detail still? - Jul 07 2009
DockbarX

DockbarX Themes by M7S 997 comments

Opacify doesn't set opacity for dockbarx. It makes other windows transparent while when you roll over a window name in the window popup, a bit like the opacify plugin in compiz. - Jul 05 2009
DockbarX

DockbarX Themes by M7S 997 comments

You can make folders as launchers by making a program starter with "Nautilus PATH_TO_FOLDER" as command and dragging that to dockbar. Every folder that opens will use that icon though. - Jul 04 2009
DockbarX

DockbarX Themes by M7S 997 comments

First question, to get opacify to work you need to use compiz and have the Opacity, Brightness and Saturation plugin activated.

Secaond question... I've not heard about that problem before. Launchers are supposed to be saved to the file ~/.dockbar/lauchers.list. Maybe that file can't be read from or written to (that would probably result in a non-working dockbar, though)? Try run dockbarx in window and see if there are any errors:
dockbarx.py run-in-window - Jul 04 2009
DockbarX

DockbarX Themes by M7S 997 comments

This is not a bug it's the intended behavior. The setting for "Workspace behavior on Select group" doesn't affect the behavior on "Select window". Why would you want to move individual windows to current workspace when selecting them? What would make sense though is a new "move window to current workspace" window button action. It could be bound to shift+left mouse button by default. - Jul 04 2009
DockbarX

DockbarX Themes by M7S 997 comments

That's a bug I haven't been able to solve. Deleting ~/.dockbar/launchers.list should fix it. - Jun 15 2009
DockbarX

DockbarX Themes by M7S 997 comments

Ok, now I am unsure if I understood what you meant in the first place. Maybe screenshots would be good anyway.

Have you tried Namebar (see link in desciption)? It's not what you ask for (I guess?) but maybe it's a solution to the same problem your suggestions aims to solve? - Jun 15 2009
DockbarX

DockbarX Themes by M7S 997 comments

If I understood you correctly, all these things you ask for will be possible to add in a theme when theme-ability is added to dockbarx (it will take a while still, I'm pretty busy during this summer :( ).

Personally I wouldn't like the buttons to expand since that would mean that launchers wouldn't always be in exaltly the same space on the screen at all time, but that's just my opinion.

And I do like feedback, so thanks for your suggestion. - Jun 14 2009
DockbarX

DockbarX Themes by M7S 997 comments

DockbarX looks like that when it's chrashed. Try run in window, in a terminal write:

dockbarx.py run-in-window


Check if there are any error messages. - Jun 14 2009
DockbarX

DockbarX Themes by M7S 997 comments

It a reasonable request (and you are not the first person to request this) but it's not very easy to add it to the current code base. I will look into it eventually but not right now. - Jun 10 2009
DockbarX

DockbarX Themes by M7S 997 comments

I'm glad you like it.


About your suggestion... I can't make the "pinning" work automagically in a consitent way. If I added "pinning" it would something like what's in AWN. You would have to enter the command for the program and possibly choose an icon as well. In some situations is it possible to for dockbarx to automagically guess the icon and the command but not always and adding features that just works sometimes will lead to frustrated users. - Jun 06 2009
DockbarX

DockbarX Themes by M7S 997 comments

Very good point and not stupid at all. I will look into it when I've got time. If you could add it as a blueprint in launchpad, so that I won't forget it, that would be great. - Jun 01 2009
DockbarX

DockbarX Themes by M7S 997 comments

Then there would be no grouping of wine apps whatsoever. If a wine program should have two windows they should get different group buttons. I don't know which situation that are more frequent, that people at one time uses one wine program with several windows or that people at one time uses several different wine programs. If the later is the case I could make the change. - May 31 2009
DockbarX

DockbarX Themes by M7S 997 comments

I've thought of that, I just don't know how to do it in a good way. The optimal sollution would be to move all programs without windows from the notification area, since that's only meant for notification icons, and move them to dockbar. Sadly I don't think that would be possible without changing quite a few things in gnome.

The easiest option would be to hardcode these menu items for the most used programs. Another options would be to keep some kind of config files in ~/.dockbar for these things. A third option would be to read AWN plugins.

Right now I will let it rest, anyway. I'll have to focus on the new theme-engine for now. - May 28 2009
DockbarX

DockbarX Themes by M7S 997 comments

I do appreciate both bug reports and feature requests. Don't stop. I just might say no once in a while. (The statistics shows I'm quite good at saying yes as well, though.;) )

And yes, I will continue to support metacity without compositing, if that's what you mean. - May 27 2009
DockbarX

DockbarX Themes by M7S 997 comments

I've thought about it and discarded it. It would require quite a rewrite of the code. Also, my personal experience with it (in Ubuntu remix's window picker) is that it's impractical to have several identical buttons.

When you make things like taskbars, I do believe that it's important to keep a clear philosophy that you use whenever you make a decision. Otherwise the program/applet will be a unintuitive feature bloat. The philosophy I have when programming dockbar is that an application with all its windows is the instance, not a window in itself. This is closer to the MacOS philosophy (a window is a document) than the Windows philosophy (a window is a program). Read this excellent ars technica article for more in dept information: http://arstechnica.com/software/news/2009/01/dock-and-windows-7-taskbar.ars - May 27 2009
DockbarX

DockbarX Themes by M7S 997 comments

Do you mean that you are unable to right click on group buttons or the handle (so that you can't open dockbar preference dialog) or both?

If it's just the group buttons, check your button configuration on preference dialog. is Right mouse button preference set to "show menu" is Double click checkbutton for right mouse button checked? - May 26 2009
DockbarX

DockbarX Themes by M7S 997 comments

I agree with that last request. If you have any idea how that can be made with the current theme, please tell me. The simplest sollution would be a number in the lower right corner of the icon, but that's not really good-looking. I like windows 7's sollution on this.

I probably implement this feature after or parallell with the theme-ability feature. - May 25 2009
DockbarX

DockbarX Themes by M7S 997 comments

Quote:I really liked the way how, on Win7, the launchers were icons, and when you launched a program, the icon was replaced by a "regular" bar displaying the icon plus title (as you have in vanilla gnome). This makes it far more easy to distinguish between launchers and open programs without the need to make the icon smaller and put some other highlight icon over it (which I personally dislike, mainly that the icon gets smaller).
Windows7 does that? Interesting. I haven't seen that in any youtube video. I wouldn't like a feature like this, since it would mean that launchers wouldn't stay in the same position if the width of launched and unlaunched launchers wouldn't be the same.

I'm planning to make dockbarx theme-able, so there will surely be a theme for dockbarx with consistent icon sizes as soon as the feature is ready.

Quote:Also I turned off grouping on win7, making it easier to distinguish between different instances of open programs.
It would take quite some work to implement this in dockbar with it's current codebase. A dock that has launchers that extends to regular window bars and doesn't group makes some sense, I guess, but that is so different to what dockbarx does that it would be better of as an own applet than a part of dockbarx, IMHO.

Quote:And lastly I also liked having a preview of the window on mouseover. I can turn this on in compiz, but it only takes the first instance of the program (if it even works, which is flaky). This last one is less important however, because the current mouseover works fine as well.
If you mean that you would like to see all windows of a program next to each other in a popup when hovering group button like in windows 7, that's impossible for me to do. It would require a new plugin to compiz.

What I could do is this: When the popup window for a program is open, the minimize areas moves from the group button to the titles in the popup. Then you could activate the window preview in compiz and get a preview when you hower the window name in the popup list. I'm not sure if it would work, but I'm willing to try it if there are a interest in such a feature. Personally I think opacify makes such a feature unnecessary, though. - May 25 2009
NameBar

Various Gnome Stuff by M7S 39 comments

I'm not sure if I understand your question, but I'll try to answer anyway.

In the video you see netbook remix's window picker. The left part of the window picker (the part with buttons) are not as good as DockBar(X). Most important difference: Window picker doesn't group applications. If you open three firefox windows you get three buttons in window picker, while you get one in DockBar(X). Namebar was made to give dockbar the one killer feature window picker had that dockbar didn't, the right half, the title and close button.

So to answer what I guess was the question: Yes. Dockbar+namebar is quite similar to Ubuntu netbook-remix's window picker. It just has some more features in the dockbar(x) part of the combo than you'll find in the left half of window picker.

Or still more plainly expressed: Dockbar+namebar is meant to be a replacement for Ubuntu netbook-remix's window picker. - May 22 2009
NameBar

Various Gnome Stuff by M7S 39 comments

Thanks for your feedback. The second request should be easy enough to implement and the feature will probably show up in next version of namebar.

I will see what I can do about that behavior suggestion. It shouldn't be imposible. - May 20 2009
DockbarX

DockbarX Themes by M7S 997 comments

I won't add an option for "disappear delay", since adding too many options is a bad way to design programs, but I will change the code so that "disappear delay" never is higher than popup delay. - May 18 2009
DockbarX

DockbarX Themes by M7S 997 comments

Thanks but could you make a bug report instead? - May 15 2009
DockbarX

DockbarX Themes by M7S 997 comments

I've only used awn briefly, so I don't know what plugins it has. I will try it out soon, I need to document how to install dockbarx as a awn plugin anyway (unless someone wants to do that for me).

My opinion is that since dockbarx is an applet it shouldn't do things that could be done by a separate applet just as well, but I don't know whether that applies to awn plugins or not. - May 15 2009
DockbarX

DockbarX Themes by M7S 997 comments

Those buttons are indeed good-looking. I take it you have working code for this, it's not just an mockup? Either way it should be a piece of cake to implement if I get the pixmaps.

Another option I've been considering for a while is to make dockbarx theme-able. It shouldn't be impossibly hard, but it sure should take some time. - May 12 2009
DockbarX

DockbarX Themes by M7S 997 comments

Thanks for your feedback.

The dnd indicator is a black triangle/arrow on the side of the empty area. If you use a very dark panel background you probably can't see it.



"(Would be fine if the same feature was available for Metacity.)"
I don't thing that is possible, sorry. - May 10 2009
NameBar

Various Gnome Stuff by M7S 39 comments

First feature request. Yay! :)

I will add that to the next version. I didn't know about window buttons applet, thanks for pointing it out. - May 09 2009
DockbarX

DockbarX Themes by M7S 997 comments

onmouseover effect will be tried in next version. onclick effect will be tried for launchers in a later version when I've decided how to make it look good.

I will check on youtube if I find any videos showing the interactiveness of windows 7 taskbar. What I like about window 7's frame around all icons is that it tells you if there are more than one window opened for a program. Beside that I like to think that the normal state of icons should be as uncluttered as posible. That's why there are no frame or anything on icons for programs with open windows in dockbarx. (I also like to think of the unlaunched launchers as programs stuck in a glass button waiting on being released. ;) )

Greyed out minimized icons will stay until someone sugests a better way to show that programs has minimized windows. I won't sacrifice functionality for looks, but if there are ways to get looks without loosing functionality I'm prepared to work a bit to get there. - May 08 2009
DockbarX

DockbarX Themes by M7S 997 comments

I would like to implement this if someone would draw a good looking mockup showing how all different states of window should look (how the button should look for a normal window, how should it change when the window becomes active/minimized/urgent/mouseover etc.).

This is quite a big change and I wouldn't want to start doing it without a pretty clear goal for how it should look when it's done. Especially when most of the users seems to be happy with current look of dockbarx (I expected to get lots of request like yours when I first presented the new look for dockbarx). - May 08 2009
DockbarX

DockbarX Themes by M7S 997 comments

I don't think this is the way to go for dockbar. It looks good on docky and makes sense there since docky is a bit of a swiss army knife (if I didn't use dockbarx I would use docky). I do think it looks a bit too cluttered for dockbar though. I would like to keep actions that deals with all windows of a program (close all, minimize all etc.) to be separated from the popup window that deals with individual windows. The "right click menu" or button actions is the right place for these kind of things. I will add more options than just "close all" to the "right click menu" soon. - May 08 2009
DockbarX

DockbarX Themes by M7S 997 comments

I can't replicate this bug. And it doesn't make much sense to me.

Do you get any error messages if you use run-in-window? If you don't get this error when runned in window you can try this to get errormessages for dockbarx in panel in a terminal:

1) in terminal write "killall dockbarx.py". If dockbar is running you should get a dialog asking you if you want to restart dockbar. If not try adding dockbarx to panel before running killall.
2) Ignore the dialog for now. Write "dockbarx.py" in terminal instead.
3) Now you can press "restart applet" (or whatever the dialog actually says).
4) Watch the terminal for any error messages. - May 07 2009
DockbarX

DockbarX Themes by M7S 997 comments

A hover effect is easy to add, I just didn't think it was necessary when there are popups whenever you hover an icon. I could bring back the bright-up hover effect dockbarX used to have on launchers but for all icons this time, if you want (as a test).

Do you miss onclick effect on launchers or on all icons? On launchers I agree, it would look better with an onclick effect. On other icons I haven't missed it since something should happen immediately after a click anyway.

Do you with "it doesn't look nice like windows 7" mean that it doesn't have small previews of the windows? If so, I can't do anything about that. I would if I could. If you are talking about something else, please be more specific. - May 07 2009
DockbarX

DockbarX Themes by M7S 997 comments

Thank you for a detailed bug report. I can spot the bug from the error messages. A fix should be quite easy to write. - May 01 2009
DockbarX

DockbarX Themes by M7S 997 comments

No, it sounds like you've done everything right.

Doesn't anything at all appear in the panel when you add dockbarx? Not even the handle (the three dots, the line or whatever your gtk theme uses)? If the handle is shown, there could be a bug in dockbarx.py, that only affects dockbar when it's run in the panel.

You could try running dockbar in panel while getting the output in terminal. To do that you should:
1) in terminal write "killall dockbarx.py". If dockbar is running you should get a dialog asking you if you want to restart dockbar. If not try adding dockbarx to panel before running killall.
2) Ignore the dialog for now. Write "dockbarx.py" in terminal instead.
3) Now you can press "restart applet" (or whatever the dialog actually says).
4) Watch the terminal for any error messages. - Apr 30 2009