This is a screenshot. It is not the type of Microsoft Aero designs but
it functions and it gives the necessary information while respecting
the intelligence of users.
http://s17.postimg.org/6frwnwmhb/2015_08_22_070752_1600x900_scrot.png
On 22/08/2015, Edward Bartolo <edbarx@???> wrote:
> GUI frontend is ready.
>
> Now, it is time for users to discover deep bugs that only show their
> heads when the user number increases.
>
> A popup window has been provided to display detailed information about
> any available wifi hotspots. This simplified the design and
> implementation of the GUI.
>
> Hopefully, users find it useful.
>
> On 21/08/2015, Edward Bartolo <edbarx@???> wrote:
>> I think, I can also upload the Lazarus code of the frontend. I am
>> using the application, and for those who love the principle of "Keep
>> it simple stuptid", it is a nice simple application which is run on
>> request. It is also controlled by the user, instead of automatically
>> making decisions behind the scenes.
>>
>> Automation will definitely take more time to do, but for the KISS
>> lovers, the application can be provided as is, with a version number
>> of 0.1 or something similar.
>>
>> When the C backend is hardened enough, it will be time for upload to
>> git.devuan.org.
>>
>> Cheers, and may DEVUAN be enjoyed by anyone wanting software freedom.
>>
>> Edward
>>
>> On 21/08/2015, Edward Bartolo <edbarx@???> wrote:
>>> At long last, the backend runs without the frontend having for it to
>>> finish as I wished. This got rid of frontend hangs.
>>>
>>>
>>>
>>> On 21/08/2015, Steve Litt <slitt@???> wrote:
>>>> On Fri, 21 Aug 2015 06:47:13 +0100
>>>> Edward Bartolo <edbarx@???> wrote:
>>>>
>>>>> Parsing headaches:
>>>>>
>>>>> I have this chunk of data retrieved from the backend which I need to
>>>>> parse *reliably*. The goal is to read the SSID and the corresponsing
>>>>> signal strength.
>>>>>
>>>>> How should I proceed. This part of code will be done from within
>>>>> Lazarus. Please, be informed that Lazarus generated GUI uses GTK* as a
>>>>> base. The executable can is also statically built which means an
>>>>> increased portability. Executables are about 3 MB. In the past I have
>>>>> written such applications that dwarf what I am doing and still the
>>>>> size is small.
>>>>>
>>>>> Here is what I want to parse:
>>>>>
>>>>> root@edbarx-pc:/home/edbarx# iwlist wlan0 scan | grep -B 4 ESSID
>>>>>
>>>>> <<<<<<<<<
>>>>> Channel:1
>>>>> Frequency:2.412 GHz (Channel 1)
>>>>> Quality=70/70 Signal level=-34 dBm
>>>>> Encryption key:on
>>>>> ESSID:"EB-TP-LNK67"
>>>>> --
>>>>> Channel:6
>>>>> Frequency:2.437 GHz (Channel 6)
>>>>> Quality=24/70 Signal level=-86 dBm
>>>>> Encryption key:on
>>>>> ESSID:"TNCAPA0332D"
>>>>> --
>>>>> Channel:11
>>>>> Frequency:2.462 GHz (Channel 11)
>>>>> Quality=30/70 Signal level=-80 dBm
>>>>> Encryption key:on
>>>>> ESSID:"Home WiFi"
>>>>> >>>>>>>>>>>>>>>
>>>>
>>>> :-)
>>>>
>>>> Hi Edward,
>>>>
>>>> At this point you're a lot more knowledgeable on this situation than I,
>>>> but I'll give you an opinion. If this problem were any more complex,
>>>> I'd suggest spawning awk, but it looks to me like as long as you can
>>>> get these lines into Lazarus, I think you're golden.
>>>>
>>>> Please refer to http://dpaste.com/0FZE769 ...
>>>>
>>>> First thing: By using grep -B, you're throwing away some information
>>>> you need: Specifically, encryption type. I'd recommend you pull *all*
>>>> the output from iwscan $device scanning into a Turbo Pascal (you know
>>>> what I mean) file linked into your Lazarus program,
>>>> except "^\s+IE: Unknown".
>>>>
>>>> It's pretty easy to parse:
>>>>
>>>> * Throw away anything beginning with "^\s*IE: Unknown"
>>>> * Throw away ^$device\s+Scan completed
>>>> * Every ^\s*Cell \d starts a new record, record the cell number
>>>>
>>>> Every line is one of the following:
>>>>
>>>> 1. ^$device\s+Scan Completed
>>>> 2. ^\s+Cell
>>>> 3. ^\s+IE: Unknown
>>>> 4. ^\s+\S.*:
>>>> 5. ^\s+\S.*=
>>>> 6. Everything else
>>>>
>>>> #3 can be avoided by having your original command be the following:
>>>>
>>>> root@edbarx-pc:/home/edbarx# iwlist wlan0 scan | grep -v "^\s+IE:
>>>> Unknown:"
>>>>
>>>> #4 are the key/value pairs comprising most of what you need
>>>>
>>>> #6 are all additional information appended to the #4 item preceding
>>>> them. So you need a somewhat stateful algorithm. You may or may not
>>>> need a Group Cipher, Pairwise Ciphers, and/or Authentication Suites. If
>>>> you don't need those three things, I think you can throw away all #6.
>>>>
>>>> #2 separates records
>>>> #5 is the signal quality/level line. Give it its own subroutine.
>>>> #1 gets thrown out
>>>>
>>>> Anyway, you definitely need to capture the encryption type, and by
>>>> using your grep -B4 ESSID you're throwing that away. NetworkManager and
>>>> Wicd both show encryption type on the ESSID list, and when I use
>>>> either of this, I want to know which ones are WPA as opposed to
>>>> (eeeuuu) WEP and which are (be very careful) unencrypted.
>>>>
>>>> HTH,
>>>>
>>>> Steve
>>>>
>>>> Steve Litt
>>>> August 2015 featured book: Troubleshooting: Just the Facts
>>>> http://www.troubleshooters.com/tjust
>>>> _______________________________________________
>>>> Dng mailing list
>>>> Dng@???
>>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>>>>
>>>
>>
>
::
Re: [DNG] Systemd Shims
%0A>%20>>>>%0A>%20>>>>%20Hi%20Edward,%0A>%20>>>>%0A>%20>>>>%20At%20this%20point%20you're%20a%20lot%20more%20knowledgeable%20on%20this%20situation%20than%20I,%0A>%20>>>>%20but%20I'll%20give%20you%20an%20opinion.%20If%20this%20problem%20were%20any%20more%20complex,%0A>%20>>>>%20I'd%20suggest%20spawning%20awk,%20but%20it%20looks%20to%20me%20like%20as%20long%20as%20you%20can%0A>%20>>>>%20get%20these%20lines%20into%20Lazarus,%20I%20think%20you're%20golden.%0A>%20>>>>%0A>%20>>>>%20Please%20refer%20to%20http://dpaste.com/0FZE769%20...%0A>%20>>>>%0A>%20>>>>%20First%20thing:%20By%20using%20grep%20-B,%20you're%20throwing%20away%20some%20information%0A>%20>>>>%20you%20need:%20Specifically,%20encryption%20type.%20I'd%20recommend%20you%20pull%20*all*%0A>%20>>>>%20the%20output%20from%20iwscan%20%24device%20scanning%20into%20a%20Turbo%20Pascal%20(you%20know%0A>%20>>>>%20what%20I%20mean)%20file%20linked%20into%20your%20Lazarus%20program,%0A>%20>>>>%20except%20%22%5E%5Cs+IE:%20Unknown%22.%0A>%20>>>>%0A>%20>>>>%20It's%20pretty%20easy%20to%20parse:%0A>%20>>>>%0A>%20>>>>%20*%20Throw%20away%20anything%20beginning%20with%20%22%5E%5Cs*IE:%20Unknown%22%0A>%20>>>>%20*%20Throw%20away%20%5E%24device%5Cs+Scan%20completed%0A>%20>>>>%20*%20Every%20%5E%5Cs*Cell%20%5Cd%20starts%20a%20new%20record,%20record%20the%20cell%20number%0A>%20>>>>%0A>%20>>>>%20Every%20line%20is%20one%20of%20the%20following:%0A>%20>>>>%0A>%20>>>>%201.%20%5E%24device%5Cs+Scan%20Completed%0A>%20>>>>%202.%20%5E%5Cs+Cell%0A>%20>>>>%203.%20%5E%5Cs+IE:%20Unknown%0A>%20>>>>%204.%20%5E%5Cs+%5CS.*:%0A>%20>>>>%205.%20%5E%5Cs+%5CS.*=%0A>%20>>>>%206.%20Everything%20else%0A>%20>>>>%0A>%20>>>>%20#3%20can%20be%20avoided%20by%20having%20your%20original%20command%20be%20the%20following:%0A>%20>>>>%0A>%20>>>>%20root@edbarx-pc:/home/edbarx#%20iwlist%20wlan0%20scan%20%7C%20grep%20-v%20%22%5E%5Cs+IE:%0A>%20>>>>%20Unknown:%22%0A>%20>>>>%0A>%20>>>>%20#4%20are%20the%20key/value%20pairs%20comprising%20most%20of%20what%20you%20need%0A>%20>>>>%0A>%20>>>>%20#6%20are%20all%20additional%20information%20appended%20to%20the%20#4%20item%20preceding%0A>%20>>>>%20them.%20So%20you%20need%20a%20somewhat%20stateful%20algorithm.%20You%20may%20or%20may%20not%0A>%20>>>>%20need%20a%20Group%20Cipher,%20Pairwise%20Ciphers,%20and/or%20Authentication%20Suites.%20If%0A>%20>>>>%20you%20don't%20need%20those%20three%20things,%20I%20think%20you%20can%20throw%20away%20all%20#6.%0A>%20>>>>%0A>%20>>>>%20#2%20separates%20records%0A>%20>>>>%20#5%20is%20the%20signal%20quality/level%20line.%20Give%20it%20its%20own%20subroutine.%0A>%20>>>>%20#1%20gets%20thrown%20out%0A>%20>>>>%0A>%20>>>>%20Anyway,%20you%20definitely%20need%20to%20capture%20the%20encryption%20type,%20and%20by%0A>%20>>>>%20using%20your%20grep%20-B4%20ESSID%20you're%20throwing%20that%20away.%20NetworkManager%20and%0A>%20>>>>%20Wicd%20both%20show%20encryption%20type%20on%20the%20ESSID%20list,%20and%20when%20I%20use%0A>%20>>>>%20either%20of%20this,%20I%20want%20to%20know%20which%20ones%20are%20WPA%20as%20opposed%20to%0A>%20>>>>%20(eeeuuu)%20WEP%20and%20which%20are%20(be%20very%20careful)%20unencrypted.%0A>%20>>>>%0A>%20>>>>%20HTH,%0A>%20>>>>%0A>%20>>>>%20Steve%0A>%20>>>>%0A>%20>>>>%20Steve%20Litt%0A>%20>>>>%20August%202015%20featured%20book:%20Troubleshooting:%20Just%20the%20Facts%0A>%20>>>>%20http://www.troubleshooters.com/tjust%0A>%20>>>>%20_______________________________________________%0A>%20>>>>%20Dng%20mailing%20list%0A>%20>>>>%20Dng@???%0A>%20>>>>%20https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng%0A>%20>>>>%0A>%20>>>%0A>%20>>%0A>%20>%0A>%20 "Responder a este mensaje")
