I'm glad to see that many people are into wmi but if you try it and find it buggy please take in consideration that it is still under heavy development.
No kidding, the improvement from 0.8 to 0.9 in so little time was an impressive feat. The next version ought to be just right.
Dusty
]]>Also there's a major change being implemented in the floating windows engine. I think it'll make it easier to solve some of the present conflicts.
]]>I'm preferring wmi to ion now, it allows floating and tiled windows on the same workspace. It's better than ion in some ways, but occasionally buggy.
After reading this I decided to chceck that wmi... Whoah! It's really great. It has few shortcomings (I can't dock my Psi icon! But I saw some screenshots with wmi and WMaker dockapps - psi can make WMaker icon, so it may be a solution), but I like it. Especially when coding, then I need to have many windows opened, and with wmi I can navigate between them very efficient (it was horrible under WindowMaker). Time will show if I will like it, but now... I doubt it (yeah, that ugly old habits are over me).
]]>In Ion, not all windows are full screen. You break it up into tiles, so you can have multiple windows *that don't overlap*. The nonoverlapping takes all the mouse positioning out of it.
I'm preferring wmi to ion now, it allows floating and tiled windows on the same workspace. It's better than ion in some ways, but occasionally buggy.
Dusty
]]>But I don't like to have all windows full-screened.
There are ways of making a rather normal-looking desktop-ish thing in ion. I think it was called floating desktop. (haven't used ion in a while..so i dont really remember) In this desktop, windows are not maximized by default and you can even resize them.
]]>Poor WMs?? You evidently don't know what you're talking about. :twisted:
Yhm, I tried aewm, evilwm (realy poor) and ion. The last one isn't really bad, I would even say it's a bit usable But I don't like to have all windows full-screened.
There's many ways. Sound. Popups. etc. etc.
Oh, right. I haven't thought about it
]]>Dusty wrote:centericq doesn't know anything about desktop trays... it's smart enough to ignore things like retarded GUI features.
Btw. Does centericq support äöå-letters? I couldn't get it working with them when I used centericq some time ago... is it possible?
I don't really use the non-ascii letters, but on my keyboard, if I'm using centericq and I press the alt key plus any of the keyboard letters, I get the extended character set. I don't know exactly how they map though.
Dusty
]]>Mhm... I'm just interested how you use IM programs with those poor WMs. How do you know when someone's sending you a message since you don't have a blinking icon in tray?
i use kopete and it has systray-icons + kde-notification popups - both fine working in xfce4
]]>centericq doesn't know anything about desktop trays... it's smart enough to ignore things like retarded GUI features.
Btw. Does centericq support äöå-letters? I couldn't get it working with them when I used centericq some time ago... is it possible?
]]>Mhm... I'm just interested how you use IM programs with those poor WMs.
Poor WMs?? You evidently don't know what you're talking about. :twisted:
How do you know when someone's sending you a message since you don't have a blinking icon in tray?
There's many ways. Sound. Popups. etc. etc.
]]>dp wrote:pygtk 2.3.94 is stable enough, but i dont want to flag it ood (out of date), because it's officially classified unstable --- de maintainainer of pygtk should decide if we go to 2.3 or wait for 2.4
Maybe there should be a package for in in unstable or testing?
Dusty
pygtk-devel i can add to unstable (already had the idea sometimes before), BUT (!!!), as for now, pacman do not support provides=('pkg=2.3') but only provides=('pkg'), there is no clean way to do so
if i add a pygtk-devel to unstable, and make wmizer depend on it (instead of making it depend on pygtk>=2.3 and use provides('pkg=2.3') in pygtk-devel), when the pygtk 2.4 comes out i need to modify wmizer to depend on pygtk>=2.4 instead of the pygtk-devel pkg
if pacman would support provides=() inkl. the version number, then it would be possible (and already done ;-) )
(that's also the reason we have 'x-server' as a virtual dependency: xorg (aka x) had provides=(xfree86), but unfortunately they had different pkgvers) --- as they are equal (in versioning), a virtual dependency is possible; pygtk and pygtk-devel are not equal in versioning, so no virtual dependency is possible
]]>pygtk 2.3.94 is stable enough, but i dont want to flag it ood (out of date), because it's officially classified unstable --- de maintainainer of pygtk should decide if we go to 2.3 or wait for 2.4
Maybe there should be a package for in in unstable or testing?
Dusty
]]>dp: I'm the author of wmizer and pygtk 2.4 should be out until September. I've tryed to port it to stable libs but i got into a few problems so I decided to stick with unstable. Also 2.3.94 is very stable.
A new version of wmizer should be out soon...I already added support for common.conf...working on actions.conf now. Thanks for the PKGBUILD.
cool, didn't know that you are the author - great job!
pygtk 2.3.94 is stable enough, but i dont want to flag it ood (out of date), because it's officially classified unstable --- de maintainainer of pygtk should decide if we go to 2.3 or wait for 2.4
i tested 2.3 and didnt have any problems with it, but now, i'm back to 2.2 to be "current" for building
as soon as we have a pygtk in the repos with that wmizer works, i will include it in extra (it's altready in my local tree, but not commited)
The problems you're having with it is not related to arch. Wmi still has a few bugs but the development is very active. Be sure to post you're bugs and they'll get fixed very fast.
good to know :-) i will have a look at the bugs there, thanx
wmi looks really promising - hope for a great 10 release
]]>