Re: [openobex-users] More than one hci usb device and Ruby wrapper

[Christian Zuckschwerdt <Christian@Zuckschwerdt.org>]

Hi Sylvestre,

you may be using an old version. The current release has an optional  
third argument to connect() when used from bindings. See
http://dev.zuckschwerdt.org/obexftp/browser/trunk/swig/client.i line  
113ff. It was introduced in r196 a year ago
http://dev.zuckschwerdt.org/obexftp/changeset/196

The src arg can either be a number (which will be passed as a string)  
or the name like hci0.

Btw. Changes to a public interface (API) are best done in a compatible  
way. That's why it has many functions with just slightly different  
signatures now.

Am 08.08.2008 um 23:07 schrieb Sylvestre Mergulhão:

> I'm testing sending files with obexftp and push with the Ruby wrapper.
> I saw thats there is no support for sending a file with an especific
> hci device. I'm thinking on how to do this. I thought thats the easier
> is to redefine obexftp_connect_push in obexftp/client.h to use direct
> obexftp_connect_src (and not obexftp_connect_uuid) receiving the hci
> as parameter.

regards,
Christian

[openobex-users] More than one hci usb device and Ruby wrapper

[Sylvestre Mergulhão <mergulhao83@gm...>]

Hi Everyone :)

I'm testing sending files with obexftp and push with the Ruby wrapper.
I saw thats there is no support for sending a file with an especific
hci device. I'm thinking on how to do this. I thought thats the easier
is to redefine obexftp_connect_push in obexftp/client.h to use direct
obexftp_connect_src (and not obexftp_connect_uuid) receiving the hci
as parameter. Is this ok?

If it works, how to modify the ruby wrapper to understand it?

Thanks.

-- 
Sylvestre Mergulhão - Free Software Development
-----------------------------------------------------------------------
http://mergulhao.info
http://just-remind.us

Re: [openobex-users] More than one hci usb device and Ruby wrapper

[Christian Zuckschwerdt <Christian@Zuckschwerdt.org>]

Hi Sylvestre,

you may be using an old version. The current release has an optional  
third argument to connect() when used from bindings. See
http://dev.zuckschwerdt.org/obexftp/browser/trunk/swig/client.i line  
113ff. It was introduced in r196 a year ago
http://dev.zuckschwerdt.org/obexftp/changeset/196

The src arg can either be a number (which will be passed as a string)  
or the name like hci0.

Btw. Changes to a public interface (API) are best done in a compatible  
way. That's why it has many functions with just slightly different  
signatures now.

Am 08.08.2008 um 23:07 schrieb Sylvestre Mergulhão:

> I'm testing sending files with obexftp and push with the Ruby wrapper.
> I saw thats there is no support for sending a file with an especific
> hci device. I'm thinking on how to do this. I thought thats the easier
> is to redefine obexftp_connect_push in obexftp/client.h to use direct
> obexftp_connect_src (and not obexftp_connect_uuid) receiving the hci
> as parameter.

regards,
Christian

Re: [openobex-users] More than one hci usb device and Ruby wrapper

[Sylvestre Mergulhão <contato@me...>]

Oh! I think I was crazy when I do not saw the optional parameter.
Sorry for the inconvenience. I'll test it later.

Many thanks.

-- 
Sylvestre Mergulhão - Free Software Development
-----------------------------------------------------------------------
http://mergulhao.info
http://just-remind.us

On Fri, Aug 8, 2008 at 6:26 PM, Christian Zuckschwerdt
<Christian@...> wrote:
> Hi Sylvestre,
>
> you may be using an old version. The current release has an optional
> third argument to connect() when used from bindings. See
> http://dev.zuckschwerdt.org/obexftp/browser/trunk/swig/client.i line
> 113ff. It was introduced in r196 a year ago
> http://dev.zuckschwerdt.org/obexftp/changeset/196
>
> The src arg can either be a number (which will be passed as a string)
> or the name like hci0.
>
> Btw. Changes to a public interface (API) are best done in a compatible
> way. That's why it has many functions with just slightly different
> signatures now.
>
> Am 08.08.2008 um 23:07 schrieb Sylvestre Mergulhão:
>
>> I'm testing sending files with obexftp and push with the Ruby wrapper.
>> I saw thats there is no support for sending a file with an especific
>> hci device. I'm thinking on how to do this. I thought thats the easier
>> is to redefine obexftp_connect_push in obexftp/client.h to use direct
>> obexftp_connect_src (and not obexftp_connect_uuid) receiving the hci
>> as parameter.
>
> regards,
> Christian
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Openobex-users mailing list
> Openobex-users@...
> http://lists.sourceforge.net/lists/listinfo/openobex-users
>

Re: [openobex-users] More than one hci usb device and Ruby wrapper

[Christian Zuckschwerdt <Christian@Zuckschwerdt.org>]

Sylvestre,

Am 08.08.2008 um 23:32 schrieb Sylvestre Mergulhão:

> Oh! I think I was crazy when I do not saw the optional parameter.
> Sorry for the inconvenience. I'll test it later.

Entirely not your fault, the documentation on the bindings is sparse.  
Please keep reporting your troubles (and perhaps things that do work)  
-- I'll roll that into the documentation some day ;)


regards,
Christian

Re: [openobex-users] More than one hci usb device and Ruby wrapper

[Sylvestre Mergulhão <mergulhao83@gm...>]

Hi Christian!

I have some feedback about the ruby binding. The optional parameter to
connect() works, but not exactaly as you said. I'll explain with
code... is easier.

This works and uses hci0:

----------------------
#!/usr/bin/env ruby
require 'obexftp'

filename = '/home/mergulhao/tmp/avatar/avatar10.jpg'

obex = Obexftp::Client.new(Obexftp::BLUETOOTH)
puts obex.connectpush('00:02:EE:AC:E0:51', 9)
puts obex.put_file(filename)
puts obex.disconnect
----------------------

This works and uses hci0:

----------------------
#!/usr/bin/env ruby
require 'obexftp'

filename = '/home/mergulhao/tmp/avatar/avatar10.jpg'

obex = Obexftp::Client.new(Obexftp::BLUETOOTH)
puts obex.connectpush('00:02:EE:AC:E0:51', 9, '0')
puts obex.put_file(filename)
puts obex.disconnect
----------------------

This works and uses hci0:

----------------------
#!/usr/bin/env ruby
require 'obexftp'

filename = '/home/mergulhao/tmp/avatar/avatar10.jpg'

obex = Obexftp::Client.new(Obexftp::BLUETOOTH)
puts obex.connectpush('00:02:EE:AC:E0:51', 9, 'hci0')
puts obex.put_file(filename)
puts obex.disconnect
----------------------

This works and uses hci1:

----------------------
#!/usr/bin/env ruby
require 'obexftp'

filename = '/home/mergulhao/tmp/avatar/avatar10.jpg'

obex = Obexftp::Client.new(Obexftp::BLUETOOTH)
puts obex.connectpush('00:02:EE:AC:E0:51', 9, 'hci1')
puts obex.put_file(filename)
puts obex.disconnect
----------------------

This does not work, returning -1 in all prints:

----------------------
#!/usr/bin/env ruby
require 'obexftp'

filename = '/home/mergulhao/tmp/avatar/avatar10.jpg'

obex = Obexftp::Client.new(Obexftp::BLUETOOTH)
puts obex.connectpush('00:02:EE:AC:E0:51', 9, '1')
puts obex.put_file(filename)
puts obex.disconnect
----------------------

Is there a way to know what occurs to it return -1? I remember when I
learned the ussp-push source code there is some error codes that says
if it was an connection error, transfer error, negation from the cell
phone and so on.

-- 
Sylvestre Mergulhão - Free Software Development
-----------------------------------------------------------------------
http://mergulhao.info
http://just-remind.us

On Fri, Aug 8, 2008 at 6:42 PM, Christian Zuckschwerdt
<Christian@...> wrote:
> Sylvestre,
>
> Am 08.08.2008 um 23:32 schrieb Sylvestre Mergulhão:
>
>> Oh! I think I was crazy when I do not saw the optional parameter.
>> Sorry for the inconvenience. I'll test it later.
>
> Entirely not your fault, the documentation on the bindings is sparse.
> Please keep reporting your troubles (and perhaps things that do work)
> -- I'll roll that into the documentation some day ;)

Re: [openobex-users] More than one hci usb device and Ruby wrapper

[Christian Zuckschwerdt <Christian@Zuckschwerdt.org>]

Hi Sylvestre,

thanks for the feedback!

Am 14.08.2008 um 05:36 schrieb Sylvestre Mergulhão:

> some feedback about the ruby binding. The optional parameter to
> connect() works, but [giving just a number doesn't]

My bad. It's either a name like "hci7" or the HCI's MAC address. I'll  
add the option for just a number next chance.


regards,
Christian

Re: [openobex-users] More than one hci usb device and Ruby wrapper

[Sylvestre Mergulhão <mergulhao83@gm...>]

Thanks Christian!

About this question:
Is there a way to know what occurs to it return -1? I remember when I
learned the ussp-push source code there is some error codes that says
if it was an connection error, transfer error, negation from the cell
phone and so on.

If it is not implement yet, maybe I can help with it.

-- 
Sylvestre Mergulhão - Free Software Development
-----------------------------------------------------------------------
http://mergulhao.info
http://just-remind.us

On Thu, Aug 14, 2008 at 6:00 PM, Christian Zuckschwerdt
<Christian@...> wrote:
> Hi Sylvestre,
>
> thanks for the feedback!
>
> Am 14.08.2008 um 05:36 schrieb Sylvestre Mergulhão:
>
>> some feedback about the ruby binding. The optional parameter to
>> connect() works, but [giving just a number doesn't]
>
> My bad. It's either a name like "hci7" or the HCI's MAC address. I'll
> add the option for just a number next chance.
>
>
> regards,
> Christian
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Openobex-users mailing list
> Openobex-users@...
> http://lists.sourceforge.net/lists/listinfo/openobex-users
>