-
 KDE-Apps.org Applications for the KDE-Desktop 
 GTK-Apps.org Applications using the GTK Toolkit 
 GnomeFiles.org Applications for GNOME 
 MeeGo-Central.org Applications for MeeGo 
 CLI-Apps.org Command Line Applications 
 Qt-Apps.org Free Qt Applications 
 Qt-Prop.org Proprietary Qt Applications 
 Maemo-Apps.org Applications for the Maemo Plattform 
 Java-Apps.org Free Java Applications 
 eyeOS-Apps.org Free eyeOS Applications 
 Wine-Apps.org Wine Applications 
 Server-Apps.org Server Applications 
 apps.ownCloud.com ownCloud Applications 
--
-
 KDE-Look.org Artwork for the KDE-Desktop 
 GNOME-Look.org Artwork for the GNOME-Desktop 
 Xfce-Look.org Artwork for the Xfce-Desktop 
 Box-Look.org Artwork for your Windowmanager 
 E17-Stuff.org Artwork for Enlightenment 
 Beryl-Themes.org Artwork for the Beryl Windowmanager 
 Compiz-Themes.org Artwork for the Compiz Windowmanager 
 EDE-Look.org Themes for your EDE Desktop 
--
-
 Debian-Art.org Stuff for Debian 
 Gentoo-Art.org Artwork for Gentoo Linux 
 SUSE-Art.org Artwork for openSUSE 
 Ubuntu-Art.org Artwork for Ubuntu 
 Kubuntu-Art.org Artwork for Kubuntu 
 LinuxMint-Art.org Artwork for Linux Mint 
 Arch-Stuff.org Art And Stuff for Arch Linux 
 Frugalware-Art.org Themes for Frugalware 
 Fedora-Art.org Artwork for Fedora Linux 
 Mandriva-Art.org Artwork for Mandriva Linux 
--
-
 KDE-Files.org Files for KDE Applications 
 OpenTemplate.org Documents for OpenOffice.org
 GIMPStuff.org Files for GIMP
 InkscapeStuff.org Files for Inkscape
 ScribusStuff.org Files for Scribus
 BlenderStuff.org Textures and Objects for Blender
 VLC-Addons.org Themes and Extensions for VLC
--
-
 KDE-Help.org Support for your KDE Desktop 
 GNOME-Help.org Support for your GNOME Desktop 
 Xfce-Help.org Support for your Xfce Desktop 
--
openDesktop.orgopenDesktop.org:   Applications   Artwork   Linux Distributions   Documents    LinuxDaily.com    Linux42.org    OpenSkillz.com   
 
Apps
News
Groups
Knowledge
Events
Forum
People
Jobs
Register
Login


Sponsoring


-
- Content .- Fans  .- Knowledge Base  . 

KWirelessMonitor

   0.5.91  

KDE Networking Tool

Score 75%
KWirelessMonitor
zoom


KWirelessMonitor
zoom


KWirelessMonitor
zoom


Link:  Link
Minimum required   KDE 3.1.x
Downloads:  25304
Submitted:  Mar 25 2004
Updated:  Jan 2 2005

Description:

KWirelessMonitor is a small KDE application that docks into the system tray and monitors the wireless network interface. It supports both Linux (tested on several major distributions) and FreeBSD (tested on 5.2.1). The systray icon shows the signal quality and the bit rate using a "bar graph" and a "pie chart", respectively. In the configuration dialog, you can change the bit rate and power management settings of the wireless interface. It is also able to automatically enable power management when using battery power and/or automatically disable power management during data transfer. By default, KWirelessMonitor tries to automatically detect the wireless interface. You can also manually set the interface name if necessary. Starting with version 0.5.91, KWirelessMonitor can connect to a network specified by the user (experimental). For more information, please check out the homepage.




Changelog:

0.5.91:
# Experimental: Added support for connecting to a network specified by the user. User can enter the appropriate network name (ESSID) and click Ok/Apply to connect to the network. (Currently only supports unencrypted networks.)

Note: Tested on Fedora Core 2, Mandrake 10, and FreeBSD 5.2.1, which are supported by distribution-specific code. For other distributions, it falls back to generic code, which _theoretically_ should work. However, given the quirks I have encountered in the above three distributions, there are likely problems with other distributions as well. Please test this feature and report problems if it does not work.

0.5.4:
# After settings are enabled, the previously saved settings are now immediately applied.
# Added menu item for enabling settings.

0.5.2:
# Changed manual power management setting UI: ``Enable'' and ``Disable'' are now push buttons.

0.5.0:
# New user interface for power management settings: manual and automatic settings are now mutually exclusive.

0.4.8:
# Available bit rates are now automatically detected, so now 802.11g bit rates can be selected. (Linux only.)

0.4.6:
# Improved AC status detection with ACPI on Linux.
# Improved quality calculation heuristics on Linux. (Hopefully this will support driverloader/ndiswrapper users who previously encountered "No signal" or similar problems.)
# The status window is now sticky (i.e., appearing on all desktops) and without its own task bar entry.

0.4.4:
# Added timeout heuristic for "automatically disable PM" to improve performance.

0.4.2:
# FreeBSD support for "automatically disable power management during data transfer".

0.4.0:
# Automatically disable power management during data transfer (Linux only).

Pre-0.4.0 features (both Linux and FreeBSD):
# Automatically enable power management when using battery power. (Requires kernel ACPI or APM support on Linux; requires kernel APM support on FreeBSD.)
# Truly transparent systray icons.
# Allow changing bit rate and power management settings from the configuration dialog. kdesu is used to launch a helper process as root.
# Display network name, signal quality, bit rate, and current power management mode in tooltip and status window.
# Auto-detect the wireless interface.
# Display signal quality and bit rate graphically.




LicenseGPL
(Source)
(Fedora Core 1 RPM, should also work on Red Hat 9)
(Fedora Core 2 RPM)
(Mandrake 10.0 RPM)
(SuSE 9.0 RPM)
(SuSE 9.1 RPM)
Send to a friend
Subscribe
Other  Apps  from pach
Report inappropriate content



goto page: prev   1  2  3  4  5  6 

-

 icon

 
 by atac on: May 16 2004
 
Score 50%

would be nice if you made the
background on the new icon transparent :-)

keep up the good work!


Reply to this

-

 Re: icon

 
 by pach on: May 17 2004
 
Score 50%

Could you elaborate on what you mean by "transparent background"? Thanks!


Reply to this

-

 Re: Re: icon

 
 by atac on: May 19 2004
 
Score 50%

hm, sorry. i opened the icon-files in photoshop and saw that they already had transparent background, though they have a white background in my tray :-/


Reply to this

-

 Re: icon

 
 by pach on: May 20 2004
 
Score 50%

Yes, the pngs are transparent. However, the actual tray icon is constructed by merging two pngs together, and currently I haven't figured out a way to do this that preserves the transparency.

Right now, the background color of the icon is set to the color of the system tray when the application is started, so it should "feel" transparent (if you don't change the color theme after it's started).

If the icon background you see is always white regardless of the system tray color, then there's probably a bug somewhere. Could you confirm if this is the case?


Reply to this

-

 Re: Re: icon

 
 by atac on: May 20 2004
 
Score 50%

yepp, it's always white in my case.


Reply to this

-

 Re: icon

 
 by pach on: May 21 2004
 
Score 50%

Mm... could you tell me which distribution and version you are using? Since I've tested RH9 and FC2, I guess you are using a different distribution, and somehow (!?) the same function call returns different results on different distributions. If that's the case, I'll have to install the particular distribution to look for the problem...


Reply to this

-

 Re: Re: icon

 
 by atac on: May 22 2004
 
Score 50%

hm, that sounds weird since it should be a kde specific problem.
i'm running kde 3.2.2, qt 3.3.2 under gentoo with the 2.6.6 kernel.



-

 Re: icon

 
 by pach on: May 22 2004
 
Score 50%

Actually, I think it's more likely a Qt problem, but who knows, it might even be an underlying library (though unlikely). It could be due to different KDE/Qt/other libs versions or because of distribution-specific patches.

Unfortunately, I don't think I will have enough time to install gentoo. But I will try to install another distribution (probably SuSE) to see if I can replicate your problem.



-

 Re: icon

 
 by pach on: May 25 2004
 
Score 50%

Ok, I think I've found where the problem is. My guess is that you are using a background image for the panel. In other words, the actual color of your panel/systray is white, and what you are seeing on the panel/systray is the background image.

The problem is, the kwirelessmonitor icon is filled with the color of the systray, not the background image. If you go to "Control Center->Appearance->Colors" and change the "Color Scheme", then my systray icon should pick up the color when starting up. However, if you go to "Control Center->Appearance->Panels" and choose "Enable background image", then this background image will be on top of the actual systray color, and my icon will use the actual color.

I guess to support background image for panels, I'll just have to figure out a way to merge two pixmaps together and preserve the transparency.


Reply to this

-

 Re: icon

 
 by pach on: Jun 13 2004
 
Score 50%

I think I have solved the transparency issue in the latest release (0.2.2). It is done by creating a custom mask when merging two pixmaps, so this should be able to handle both changing panel color and using background image on panel. Please try the new version and let me know if it works for you. Thanks!


Reply to this

-

 actually transparent

 
 by geekmug on: May 17 2004
 
Score 50%

As it is right now, your icon has a whit background to match the standard theming, but some people (like myself) definitely don't have a white docking area, and in fact, mine is faux transparent, so your icon is an eye-soar. Nice app otherwise.


Reply to this

-

 Re: actually transpa

 
 by pach on: May 18 2004
 
Score 50%

Are you sure it's always white? The background color for the icon is set to the color of the system tray at the time you start the application, so it should "feel" transparent. Of course, if you change the color theme after the application is started, then the color would become incorrect, but it should not always be white. Could you confirm if this is the case?

The current implementation is a temporary solution. I'm still trying to figure out a better way, for example, bitblt two pixmaps together while maintaining transparency (which I haven't figured out how to do), or use the fake transparency but construct the icon on the fly (which would impact performance).


Reply to this

-

 Re: actually transpa

 
 by pach on: Jun 13 2004
 
Score 50%

I think I have solved the transparency issue in the latest release (0.2.2). It is done by creating a custom mask when merging two pixmaps, so this should be able to handle both changing panel color and using background image on panel. Please try the new version and let me know if it works for you. Thanks!


Reply to this

-
.

 no signal

 
 by mfernau on: May 21 2004
 
Score 50%
mfernaumfernau
FERNAUSOFT GmbH
Home

hm, your program work fine. It automaticly find my wireless card! But, I'm successfully connected to my accesspoint but kwirelessmonitor tell me, that there's no signal...

if i manually
cat /proc/net/wireless, I get the following info:
mfe@blackeye mfe $ cat /proc/net/wireless
Inter-| sta-| Quality | Discarded packets | Missed | WE
face | tus | link level noise | nwid crypt frag retry misc | beacon | 16
eth1: 0020 100. 183. 158. 0 0 0 52 0 0

where is the problem?


Reply to this

-

 Re: no signal

 
 by pach on: May 21 2004
 
Score 50%

(1) If you are compiling from source, it's possible that your running kernel and your glibc kernel headers (in /usr/include/linux) are of different versions.

This could happen, for example, when you upgrade to the latest kernel without upgrading the headers.

(2) If you are using one of the RPMs, make sure it's compiled for your distribution and version.


Reply to this

-
.

 thx

 
 by mfernau on: May 21 2004
 
Score 50%
mfernaumfernau
FERNAUSOFT GmbH
Home

ok, thanks.
I will try to upgrade the header-files and recompile your program.
Because I now have no accesspoint, I can't try it now but I will repost here on next monday

thx


Reply to this

-

 no signal but...

 
 by Tanis on: Jun 6 2004
 
Score 50%

Hi:

I've seen the post about the no signal, but in my case, i have compiled my kernel, so i have good headers... only that the drivers for the card are external (madwifi) I'm using gentoo with 2.6.5. What can be the problem? thanks a lot


Reply to this

-

 Re: no signal but...

 
 by pach on: Jun 10 2004
 
Score 50%

Sorry for the late reply. I was on vacation without network access for a week. I just took a quick look at madwifi, and it seems to implement the wireless extensions, so that shouldn't be the problem. Could you do the following:

grep WIRELESS_EXT /usr/include/linux/wireless.h | grep define

and let me know the result? Thanks!


Reply to this

-

 Re: Re: no signal bu

 
 by Tanis on: Jun 12 2004
 
Score 50%

You don't have to be sorry! Thanks for replying!. The result of your instruction is this:

#define WIRELESS_EXT 15

Does it say anything to you?


Reply to this

-

 Re: no signal

 
 by pach on: Jun 12 2004
 
Score 50%

That probably means your glibc kernel headers were not updated when you upgraded the kernel. You can double check this by comparing the file (/usr/include/linux/wireless.h) with the one from your kernel source (i.e., <your_kernel_source_dir>/include/linux/wireless.h).

For 2.6.5, WIRELESS_EXT should be 16, not version 15 as you saw in your glibc kernel header.


Reply to this

-

 Re: Re: no signal bu

 
 by Tanis on: Jun 12 2004
 
Score 50%

so, then, do i have to recompile the kernel? only glibc? what did I do wrong? Why glibc has the wrong version?

Thanks a lot for your help!!


Reply to this

-

 Re: no signal

 
 by pach on: Jun 13 2004
 
Score 50%

I'm not sure about gentoo... On Red Hat/Fedora, there's a package called "glibc-kernheaders" that includes everything in /usr/include/linux. Maybe there is something equivalent in gentoo?

In the worst case, I guess you could try copying the "wireless.h" file in your kernel source to /usr/include/linux/ and recompile the application (of course, back up the original file before trying this).


Reply to this

-

 Re: Re: no signal bu

 
 by Tanis on: Jun 13 2004
 
Score 50%

I've copied the wireless.h from source and now it's all ok! Thanks a lot for your help!! This new version with transparency is great :)


Reply to this

-
.

 nice job

 
 by gillesm on: Jun 13 2004
 
Score 50%

Nice tool ! but why do I need to lauch it as root ... it is launh at start and ask me root password. If I don't give it, all is fine.


Reply to this

-

 Re: nice job

 
 by pach on: Jun 14 2004
 
Score 50%

root is needed to change the wireless settings, and yes, if you click "Ignore", you can still see the interface status (you just can't change the settings).


Reply to this

-

 Re: Re: nice job

 
 by mlg9000 on: Jun 14 2004
 
Score 50%

Is there someway to disable the password check though? It's annoying even if you can just click out of it. I understand the purpose but with standard su you can specify command s users can run without requiring a password. With kdesu I can't find an option to do that anywhere. Even if disabling the password check sets it to "user mode" where setting can only be viewed that's better then getting the nag screen everytime I load KDE. (Kwireless in autostart)


Reply to this

-

 Re: nice job

 
 by pach on: Jun 15 2004
 
Score 50%

Yes, you are right. It is a bit annoying. At first, I thought about simply installing the binary setuid root, but since most people consider that a security risk, kdesu is the compromise solution I decided to use. Unfortunately, as you said, I don't think kdesu supports the sudoers thingy.

I'm trying to figure out a more convenient way to do this. Hopefully you'll find something better in the next release.


Reply to this

-

 Re: nice job

 
 by pach on: Jun 27 2004
 
Score 50%

In the new version (0.2.4), I re-implemented the way kdesu is used. Now the application doesn't ask for the root password until the first time you try to change the wireless settings (i.e., switching to the "Settings" page in the configuration dialog). Personally, I think it is much less annoying now. I hope you also find this solution better than the previous implementation!


Reply to this

goto page: prev   1  2  3  4  5  6 

Add commentBack






-
-
Do you like or dislike Ubuntu Unity?
 Yes, unity is alien technology!
 It is less confusing than Gnome 3 default, shell.
 Granny thinks it is much more usable than Gnome 2
 Canonical is embarrasing itself with this split project
 Gnome 3 default shell is much better
 I dislike Unity, Gnome 3 default shell is alien technology!
 None of the above, I like the 2Gb for free and Apple alike behavior. Will post a comment instead

resultmore
 
 
 Who we are
Contact
More about us
Frequently Asked Questions
Register
Twitter
Blog
Explore
Apps
Jobs
Knowledge
Events
People
Updates on identi.ca
Updates on Twitter
Facebook App
Content RSS   
Events RSS   

Participate
Groups
Forum
Add App
Public API
About KDE-Apps.org
Legal Notice
Spreadshirt Shop
CafePress Shop
Advertising
Sponsor us
Report Abuse
 

Copyright 2003-2014 KDE-Apps.org Team  
All rights reserved. KDE-Apps.org is not liable for any content or goods on this site.
All contributors are responsible for the lawfulness of their uploads.
KDE and K Desktop Environment are trademarks of KDE e.V.