On Thu, Oct 7, 2010 at 08:27,  <g.duale@otasc.org> wrote:
quoted text
>> 2010/10/7 Martin PelikC!n <martin.pelikan@gmail.com>:
>>> 2010/10/7, Hugo Osvaldo Barrera <hugo@osvaldobarrera.com.ar>:
>>>> I don't intend to make a huge daemon like the linux's NetworkManager,
>>>> but, instead, just a simple application you open, connect, and close.
>>>> Done. B No bloat, and definitely ***NO*** requirement for stuff like
>>>> HAL.
>>>
>>> Amen.
>>>
>>>> I wanted to get a few pointers before I started:
>>>> 1) First of all, I want to be sure no one's already working on
>>>> something like this.
>>>
>>> I occasionaly develop one for ncurses. But don't feel any special need
>>> for it, pfctl mostly works just fine. Oh, and it focuses more on pf(4)
>>> manupulation rather than wireless (but it's modular).
>>>
>>>> 2) I initially considered just parsing the output of "ifconfig ****".
>>>> This does seem rather hackish, but would get the job done fast and can
>>>> still be very maintainable code. B However, what's the proper
>>>> alternative (just a few pointer to know what to start reading will do)
>>>> to do this sort of this.
>>>
>>> man getifaddrs
>>> man style
>>> Please, do NOT parse ifconfig output and invest the work into proper C
>>> code. You'll hopefully learn some stuff at least and you have higher
>>> chance you won't write crap. Many people have been there. Just don't.
>>>
>>> --
>>> Martin Pelikan
>>>
>>
>> Thanks, using man getifaddrs, I've managed to find some pretty
>> valuable information (and will probably find most of what I need with
>> enough time).
>> Gotta love OpenBSD's man documentation.
>>
>> Again, thanks :-)
>>
>>
>> @Edho:
>> I don't think wicd would work. B It uses wpa_supplicant, and some other
>> linux-only stuff as backend.
>> I haven't been able to find much on PCBSD's doc, it seems their
>> standards for documentation are quite low, for example, see:
>> http://wiki.pcbsd.org/index.php/PC-BSD_FAQS#Networking
>> or
>> http://wiki.pcbsd.org/index.php/Wireless_Settings
>>
>> From what I've seen on just screenshots, It's probably QT based. B But
>> I'll download it tonight and take a look, there might be some useful
>> parts, at least for studying.
>>
>> @Guillaume:
>> I was considering Python, but since I need to call system functions,
>> it's either going to be C or Python calling a C module, the latter
>> being more likely, since I could learn more, and still use python for
>> the front-end.
>> Tell me if you're interested on doing something, we might be able to
>> help each other :)
>
> Hi Hugo,
> If I understand you think to combine C et Python ?
> Do you think is good to code the tool in C in shell only interface,
> and add the graphical front-end in Python.
> In this case Python will call on each clik the C binary with parameter,
> like :
> B ./assistant --list-wireless-network
>
> It's a good idea

It sounds like going back to parsing a string in order to obtain the
info.  Only that instead of parsing ifconfig, it's some other
application that wraps system calls.  Calling C code from python seems
rather easy, it's the C part that might take some time (reading).

If you'd like for us to collaborate on this, e-mail me.  The same goes
for anyone else who might be interested :-)

@david:
Oh, ok, a shame really.
A few KDE apps would be SO good if they just weren't KDE apps.

quoted text
>>
>>
>> --
>> Hugo Osvaldo Barrera
>>
>>
>
>
>



--
Hugo Osvaldo Barrera