Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 02 Oct 2014, 03:11
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Network
Frisbee Network Manager - Beta 2
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 11 of 26 Posts_count   Goto page: Previous 1, 2, 3, ..., 9, 10, 11, 12, 13, ..., 24, 25, 26 Next
Author Message
Argolance


Joined: 06 Jan 2008
Posts: 1830
Location: PORT-BRILLET (Mayenne - France)

PostPosted: Thu 07 Feb 2013, 12:56    Post_subject:  

Hello,
Question: Why to persist in using carved xpm picutres that are very ugly most of the time while it is so easy to use smooth png pictures for the tray? Evil or Very Mad
Sometimes, it is possible to bypass this (retrovol for example) in using pictures.png with links to them named "pictures.xpm". But this doesn't work with frisbee tray Confused. Indeed, it should be much better to let everyone keep the existing ones or customize them as he wants and modify source files for!

Cordialement.
Back to top
View user's profile Send_private_message Visit_website 
rerwin


Joined: 24 Aug 2005
Posts: 1519
Location: Maine, USA

PostPosted: Thu 07 Feb 2013, 16:26    Post_subject:  

Argolance,
Barry is about to consider taking the integrated-frisbee packages. I need to have them robust and ready. So, for now, I have made all of the internationalization/wordsmithing changes I am comfortable with. I added your suggestions for the window titles, for all of the windows. Since frisbee will reside in the puppy repository, it should be easy to update as we continue polishing frisbee.

I also fixed another place that could be causing the remainder of your wpa_supplicant messages. If the connection status is "disconnected" or there is no interface, a "disconnect" is done, which also did not check for there being no wifi interface. Now, it does. Please test the new package, which is now in the "kit" but is available by itself, here:
http://www.murga-linux.com/puppy/viewtopic.php?p=662521#662521

About the icons: I explained my thinking earlier in this thread somewhere. I chose to remain consistent with the current icon size, so the size issue would not impact Barry's acceptance of the kit. That will have to be worked with Barry, since he is final word about it.
Richard
Back to top
View user's profile Send_private_message 
ASRI éducation


Joined: 09 May 2009
Posts: 2472
Location: France

PostPosted: Thu 07 Feb 2013, 16:58    Post_subject:  

rerwin wrote:
...
Barry is about to consider taking the integrated-frisbee packages.
...

Excellent !
Back to top
View user's profile Send_private_message Visit_website 
Argolance


Joined: 06 Jan 2008
Posts: 1830
Location: PORT-BRILLET (Mayenne - France)

PostPosted: Fri 08 Feb 2013, 07:38    Post_subject:  

Quote:
Barry is about to consider taking the integrated-frisbee packages.
This is a really good news for Frisbee and for users... Very Happy

Cordialement.
Back to top
View user's profile Send_private_message Visit_website 
peebee


Joined: 21 Sep 2008
Posts: 1434
Location: Malvern, Worcs, UK

PostPosted: Sun 10 Feb 2013, 10:02    Post_subject: Test on Precise 5.5Alpha  

BK has announced the Precise 5.5 Alpha containing the infrastructure needed for the "new" Frisbee.

I have tested -
Quote:
Pristine frugal install of Precise 5.4.90 - added frisbee-1.0-20130207.pet and network_tray-2.6-20130203.pet - successfully established wifi connection which was persistent through a reboot using the Broadcom wl driver.

Cheers
peebee
capture20381.png
 Description   
 Filesize   79.92 KB
 Viewed   1188 Time(s)

capture20381.png


_________________
LxPup-14.03 = Puppy + LXDE
Back to top
View user's profile Send_private_message 
Argolance


Joined: 06 Jan 2008
Posts: 1830
Location: PORT-BRILLET (Mayenne - France)

PostPosted: Sun 10 Feb 2013, 12:28    Post_subject:  

Hello,
2 questions:
I didn't see, directly from Frisbee interface (while it is obvious using BK/dougal GUIs) how to:
    - give the preference to a wireless network when several available?
    - load another driver if the "wrong" one is automatically loaded at startup or when the Windows one is required (using ndiswrapper)?

Thank you.
Cordialement.
Back to top
View user's profile Send_private_message Visit_website 
rerwin


Joined: 24 Aug 2005
Posts: 1519
Location: Maine, USA

PostPosted: Sun 10 Feb 2013, 13:39    Post_subject: Closer to final revision of internationalization?  

Argolance wrote:
I didn't see, directly from Frisbee interface (while it is obvious using BK/dougal GUIs) how to:
    - give the preference to a wireless network when several available?
    - load another driver if the "wrong" one is automatically loaded at startup or when the Windows one is required (using ndiswrapper)?
I don't think Jemimah addressed either of those issues. The preference seems like something I can try to add to frisbee. But the driver item is best left to SNS. The selection would be a one-time change. With the new frisbee, there is no problem switching among the network managers. The betas seemed to assume Frisbee is exclusive.

Now, back to the internationalization: I have done more fine tuning of the GUI windows to add more of Argolance's recommendations, although sometimes in a different way, particularly, moving the Exit button outside of the tabs (so it is active when wireless is greyed out), shortening of more button labels and re-organizing some of the buttons to put only 2 per line and be pleasing to the eye.

I attach a test version of what I hope to release, as well as screenies of the 4 windows. Note that the Exit button is gone from the secondary windows, requiring that they be closed with the X button. Argolance and anyone, please report any remaining issues/problems, so I can fix them right away. Thanks.
Richard

UPDATE 2/12/2012: Re-uploaded frisbee (after download #12), which is the same as before except for 3 fixes to reduce or eliminate annoying wpa_supplicant messages when there is no wifi hardware installed. They also fix a hang of frisbee while it waits for wpa_supplicant to time out (if it ever does) when there is no wifi interface to be found.

EDIT: I re-loaded frisbee-1.0 after download #13, to fix a potential problem for internationalization. A test was made in "connection-check" for the text, "Connected to", which is only part of the message being tested. If a translation put the interface ID before the translation of "Connected to", the test would fail, resulting in an inappropriate message that wpa_supplicant failed in some way. I added true/false return status from the current-status function, true meaning "connected". Therefore, apparently, that message, as well as "IP Address: ...", was not internationalized; now they are.

Please verify I did no harm, by ensuring you can connect to a wireless network. Thanks.
Richard

UPDATE 2/13/2013: Re-uploaded again, to add one more internationalized text string and change 2 icons, per Argolance's recommendations.

UPDATE 2/19/2013: Re-uploaded 20130213 without the .pot file and without the dependency on wag_profiles. No functional changes.

UPDATE 2/20/2013: Uploaded version with corrections for the eval_gettext function, to restore connection status and other text involving variables. Reported by peebee -- thank you.
EDIT: Re-uploaded 20130220 with further corrections: "Manage Saved Networks" "SSID:" initialization to avoid residue and change "Reset DHCP" to "Restart DHCP", to be consistent with "Restart Networks".

UPDATE 2/27/2013: Uploaded version 20130227 to reduce the size of the ever-growing wpa_supplicant log. The Diagnostics dialog now has a checkbox to enable debug-level logging, defaulted to unchecked. Previous frisbees always log at the debug (-d) level, creating a large and growing file in /tmp (which is not infinite in capacity). That would be a "showstopper" for long-running puppy sessions, thus this last-minute fix. Also eliminated output of a few remaining wpa_supplicant warning messages.
EDIT: Uploaded 20130228 after download #4 to add compatibility with slacko (in the pinstall script), but to improve a test. There is no functional difference from 20130227, which is only vulnerable if, unlikely, there are multiple matches for "/usr/local/lib/X11/mini-icons/networkdead-eth*.*"
EDIT: I re-uploaded the last 20130228 version of frisbee, to reset the download count, in the hope that earlier downloaders will want to ensure they have the latest. I had to make incremental updates that downloaders #5 & #6 do not have.

UPDATE 3/4/2013: Uploaded 20130304 version to correct a failure found in testing on racy and wary, reported by mavrothal and peebee. The problem was an "-f" option passed to wpa_supplicant that is now being rejected, causing wpa_supplicant to not start, at all. The mystery is that "-f" seemed to work in precise, although it apparently does no longer. Please test this on precise and racy soon, so I can offer it for beta2. Thank you for focusing my attention on this issue.
frisbee-1.0-20130304.pet
Description  Polished frisbee with corrected internationalization and minimal wpa_supplicant log file
pet

 Download 
Filename  frisbee-1.0-20130304.pet 
Filesize  13.93 KB 
Downloaded  241 Time(s) 
frisbee-Configure-wireless.png
 Description   
 Filesize   24.52 KB
 Viewed   1179 Time(s)

frisbee-Configure-wireless.png

frisbee-Configure-interfaces.png
 Description   
 Filesize   27.08 KB
 Viewed   1185 Time(s)

frisbee-Configure-interfaces.png

frisbee-Configure-manage.png
 Description   
 Filesize   21.96 KB
 Viewed   1180 Time(s)

frisbee-Configure-manage.png

frisbee-Configure-diagnostics.png
 Description   
 Filesize   27.04 KB
 Viewed   1183 Time(s)

frisbee-Configure-diagnostics.png


Edited_times_total
Back to top
View user's profile Send_private_message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: Sun 10 Feb 2013, 19:37    Post_subject:  

rerwin wrote:
About the icons: I explained my thinking earlier in this thread somewhere. I chose to remain consistent with the current icon size, so the size issue would not impact Barry's acceptance of the kit. That will have to be worked with Barry, since he is final word about it.
Richard


Yes, it was a deliberate design decision on my part to use xpm images. At 24x24 pixels, they are "sharp". The so-called "smooth" png icons can also be described as blurred or fuzzy, and often do not look good at that size. The tiny icons used in the MS Windows tray are an example of really crappy icons.

Anyway, it was a design decision by me, and I would prefer a consistent look to all the icons in the tray. Of course, png (or svg) icons can also be created that look "sharp".

_________________
http://bkhome.org/news/
Back to top
View user's profile Send_private_message Visit_website 
Argolance


Joined: 06 Jan 2008
Posts: 1830
Location: PORT-BRILLET (Mayenne - France)

PostPosted: Tue 12 Feb 2013, 11:59    Post_subject:  

Hello,
BarryK wrote:
The so-called "smooth" png icons can also be described as blurred or fuzzy, and often do not look good at that size. The tiny icons used in the MS Windows tray are an example of really crappy icons.
I totally agree with this point of view. I tried to make such "smooth" icons for my own, but, most of the time, couldn't feel really satisfied of the result. The word "smooth" was not the correct one, I was meaning without "aliasing".
BarryK wrote:
Of course, png (or svg) icons can also be created that look "sharp".
It is why I thought it might be interesting to choose an intermediate solution: keep the simple "sharped" look of xpm pictures and, as far as possible, get rid of aliasing which is really... "crappy" too! Wink

Cordialement.
original.png
 Description   
 Filesize   17.2 KB
 Viewed   967 Time(s)

original.png

example_1.png
 Description   
 Filesize   4.68 KB
 Viewed   1073 Time(s)

example_1.png

example_2.png
 Description   
 Filesize   6.69 KB
 Viewed   1114 Time(s)

example_2.png

example_3.png
 Description   
 Filesize   3.42 KB
 Viewed   1083 Time(s)

example_3.png

example_4.png
 Description   
 Filesize   2.18 KB
 Viewed   1082 Time(s)

example_4.png

example_5.png
 Description   
 Filesize   4.43 KB
 Viewed   1098 Time(s)

example_5.png

example_6.png
 Description   
 Filesize   8.92 KB
 Viewed   1126 Time(s)

example_6.png

example_8.png
 Description   
 Filesize   11.33 KB
 Viewed   1070 Time(s)

example_8.png

example_9.png
 Description   
 Filesize   10.56 KB
 Viewed   1072 Time(s)

example_9.png


Edited_times_total
Back to top
View user's profile Send_private_message Visit_website 
Argolance


Joined: 06 Jan 2008
Posts: 1830
Location: PORT-BRILLET (Mayenne - France)

PostPosted: Tue 12 Feb 2013, 12:31    Post_subject:  

Hello,
All seems working as well as possible for me but I am always getting strange things in xerrs.log!
Don't know if this is my own configuration which is the cause of that and if it is really important?
Quote:
/usr/local/bin/frisbee: line 20: 7391 Terminated () { CONNECTED=`wpa_cli -i $INTERFACE status|grep wpa_state|cut -f2 -d "="`;
if [[ $CONNECTED != "COMPLETED" ]]; then
echo "Not Connected";
return;
fi;
SSID=`wpa_cli -i $INTERFACE status|grep ^ssid |cut -f2 -d "="`;
IP=`wpa_cli -i $INTERFACE status|grep ip_address|cut -f2 -d "="`;
echo "Connected to $SSID"
}
ifconfig: SIOCGIFFLAGS: No such device
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
dhcpcd[7545]: version 5.6.4 starting
dhcpcd[7545]: all: configured as a router, not a host
dhcpcd[7545]: forking to background
dhcpcd[7545]: forked to background, child pid 7576
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
ifconfig: SIOCGIFFLAGS: No such device
ifconfig: SIOCGIFFLAGS: No such device
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument

Cordialement.
Back to top
View user's profile Send_private_message Visit_website 
mavrothal


Joined: 24 Aug 2009
Posts: 1636

PostPosted: Tue 12 Feb 2013, 16:16    Post_subject:  

Argolance wrote:
Hello,
All seems working as well as possible for me but I am always getting strange things in xerrs.log!
Don't know if this is my own configuration which is the cause of that and if it is really important?


I also got those but I thought it was because I was trying it on Archpup.
It is like is trying to connect after it is connected.

BTW The frisbee and network_tray pets and optionaly dhcpcd-dropwait, should be sufficient to make it work in any distro right?

_________________
Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too Very Happy
Back to top
View user's profile Send_private_message 
rerwin


Joined: 24 Aug 2005
Posts: 1519
Location: Maine, USA

PostPosted: Tue 12 Feb 2013, 16:32    Post_subject: Upgraded frisbee and networy_tray packages  

Argolance wrote:
All seems working as well as possible for me but I am always getting strange things in xerrs.log!
Don't know if this is my own configuration which is the cause of that and if it is really important?
Argolance,
Yes, it is important. It is one of the problems I fixed in frisbee-1.0-20130212, which I have uploaded to replace "0209", here:
http://www.murga-linux.com/puppy/viewtopic.php?p=684092#684092

Thanks for testing 0209 and reporting your experience with it. It now seems ready to recommend to Barry for the alpha, or addition to the repo.

On the network_tray side, I have corrected and improved it for dialup. I provide a set of icons for wireless (cellphone system) modems as well as analog/wireline icons, currently defaulted to the wireless set created by 01micko. It will take an external script to switch between the dialup types, which I plan to add soon.

Also, I reworked the "networkdead" icons to add ones for wireless and dialup. For all of them I changed the red "prohibited" overlay symbol to an X, to conform to the existing "dead" icon. The wireless dead icon is displayed if there is no wired ethernet hardware present; if both are down, the ethernet icon will display. The dialup dead icon will display after disconnecting from a call if neither wireless nor ethernet are active, until either of those becomes active.
Richard

UPDATE 2/14/2013: Re-uploaded the network_tray package which now uses icons derived from the current puppy "globe-and-terminal" icons. This is consistent with making frisbee an part of puppy -- integrating it.

UPDATE 2/15/2013: Re-uploaded the network_tray package and matching source tarball, to make small improvements to some of the icons. Added internationalized script, modemiconset, to select analog or wireless dialup icons -- see its --help for details. For now, run it from a console.
network_tray-2.6-20130215.pet
Description  Network_tray package with "integrated" icons
pet

 Download 
Filename  network_tray-2.6-20130215.pet 
Filesize  10.25 KB 
Downloaded  255 Time(s) 
network_tray-2.6-20130215.tar.gz
Description  Network_tray source tarball with "integrated" icons.
No source code changes from 20130211 tarball.
gz

 Download 
Filename  network_tray-2.6-20130215.tar.gz 
Filesize  13.15 KB 
Downloaded  238 Time(s) 

Edited_times_total
Back to top
View user's profile Send_private_message 
rerwin


Joined: 24 Aug 2005
Posts: 1519
Location: Maine, USA

PostPosted: Tue 12 Feb 2013, 16:51    Post_subject:  

mavrothal wrote:
BTW The frisbee and network_tray pets and optionaly dhcpcd-dropwait, should be sufficient to make it work in any distro right?
The network_tray and dhcpcd-dropwait functions are compiled, so are subject to whatever constraints there are in migrating between distros. But, I would think they should work in recent 32-bit puppies. The frisbee package is constrained only by accompanying them with the 3 architecture fix packages that are in the 5.5 alphas. (Actually, you need only the woof_update and wag_profiles packages.) If a puppy was created with a recent woof tool, the architecture packages should work with it, too.

If you want to be sure about frisbee and archpup, please obtain a difference (diff) listings of the files in the "woof_updates" package, compared to the versions in archpup, and PM the listings to me. I don't know what archpup is derived from, so would need to see the difference listings.
Richard
Back to top
View user's profile Send_private_message 
mavrothal


Joined: 24 Aug 2009
Posts: 1636

PostPosted: Wed 13 Feb 2013, 01:46    Post_subject:  

rerwin wrote:
mavrothal wrote:
BTW The frisbee and network_tray pets and optionaly dhcpcd-dropwait, should be sufficient to make it work in any distro right?
The network_tray and dhcpcd-dropwait functions are compiled, so are subject to whatever constraints there are in migrating between distros. But, I would think they should work in recent 32-bit puppies. The frisbee package is constrained only by accompanying them with the 3 architecture fix packages that are in the 5.5 alphas. (Actually, you need only the woof_update and wag_profiles packages.) If a puppy was created with a recent woof tool, the architecture packages should work with it, too.


Actually Archpup is not Woof based and has only a couple of puppy scripts outside the initrd!
However, Frisbee works fine (the strange messages I reported were with 20130207 but 20130212 is clean)
So I gues I'm asking what else frisbee would need to work say in Fedora Surprised
So far I have gtkdialog gtkdialog-splash, ipinfo and optionally network_tary and dhcpdh.
I just wonder if I miss something else.

One minor problem I got is with ipinfo actually where format of the interfaces tab is messed up.
I guess is something with gtkdialog. The other tabs look OK

All I get in terminal is the warning
Code:
Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 5 char 50: 'UP,BROADCAST,RUNNING,MULTICAST' is not a valid name: ','

_________________
Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too Very Happy
Back to top
View user's profile Send_private_message 
peebee


Joined: 21 Sep 2008
Posts: 1434
Location: Malvern, Worcs, UK

PostPosted: Wed 13 Feb 2013, 03:26    Post_subject:  

mavrothal wrote:
One minor problem I got is with ipinfo actually where format of the interfaces tab is messed up.
I guess is something with gtkdialog. The other tabs look OK


Hi Mav

I think that is because the output from ifconfig or iwconfig (I forget which) is formatted differently on Archpup and ipinfo can't parse it correctly.

Cheers
peebee

_________________
LxPup-14.03 = Puppy + LXDE

Edited_time_total
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 11 of 26 Posts_count   Goto page: Previous 1, 2, 3, ..., 9, 10, 11, 12, 13, ..., 24, 25, 26 Next
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Network
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1429s ][ Queries: 12 (0.0129s) ][ GZIP on ]