Hi Luis,
>> > > Another question is where I can put the Python C source files to be
>> built? Is there a preferred path for these C files? I was going to create a
>> PM/btc directory.
>>
>> I have thought about this issue and decided to take a holistic view on
>> it and came out with the proposed structure as stated below. I believe that
>> it should be under umit.bt_sniffer since the Python C source are of the
>> core\backend. This structure is analogous to the relationship UMPA and PM
>> has. The child structure(.core and .firmware) would have more depth as the
>> project progresses and this structure would permit the extensiveness of the
>> project.
>> **
>> * umit.bt_sniffer -> Bluetooth
>> Sniffer<http://trac.umitproject.org/wiki/BluetoothSniffing>
>> *
>>
>> - *umit.bt_sniffer.core*
>> - *umit.bt_sniffer.firmware*
>>
>> *umit.pm -> The **Packet Manipulation
>> Interface*<http://trac.umitproject.org/wiki/PacketManipulator>
>> *. *
>>
>> - *umit.pm.backend *
>> - *umit.pm.core *
>> - *umit.pm.bt_sniffer_gui -> **Bluetooth
>> Sniffer*<http://trac.umitproject.org/wiki/BluetoothSniffing>
>>
>> What should be interface of Bluetooth Sniffer?
> If it is necessary probably should be written in *umit.pm.bt_sniffer.gui*or
> something like that
>
Sure, that can work. I have suggested bt_sniffer_gui as it does not involve
another unnecessary iteration as there is *umit.pm.gui. Would
umit.pm.gui.bt_sniffer
work then as the bt_sniffer interface leverages PM's interface?
Cheers,
Devtar
*
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Umit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/umit-devel
