obexapp-1.4

[Maksim Yevmenkin]

updated version

http://www.geocities.com/m_evmenkin/obexapp-1.4.1.tar.gz

added 'getdefault' command. changed 'get', 'getdefault' and 'put' 
behavior to match their non-interactive versions.

max


Maksim Yevmenkin wrote:
> Pav Lucistnik wrote:
> 
>> Maksim Yevmenkin píše v čt 09. 12. 2004 v 14:51 -0800:
>>
>>> Hello,
>>>
>>> please help me with testing of obexapp v1.4. it can be downloaded from
>>>
>>> http://www.geocities.com/m_evmenkin/obexapp-1.4.tar.gz
>>>
>>> the main feature is readline(3) support. it is now possible to repeat 
>>> and edit commands in interactive mode. the command parser also has 
>>> been changed. it is now possible to enter command parameters together 
>>> with commands (for example "cd /" or "get foo bar").
>>
>>
>>
>> obex> get Soul.mp3 Soul.mp3
>> Success, response: OK, Success (0x20)
>>
>> obex> get Wazzup.mp3
>> Failure, response: Unautorized (0x41)
>>
>> When I write get with single argument, could obexapp assume it as both
>> remote and local filename?
> 
> 
> well, it could. right now i opted for non-intuitive version :) that is 
> 'get foo' means get default vcard object and save it locally as foo :) 
> funky, huh? :)
> 
> i do not like it myself, and i'm not sure how often one wants to pull 
> default vcard object. i like your idea better, i.e. 'get foo' should 
> mean 'get foo foo'. perhaps adding another command to get default object 
> would be better?
> 
>  > There's some odity with line breaks, it seems, on my terminal:
> 
>>
>> +-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 
>>
>> | obex> get Soul.mp3 
>> Soul.mp3                                                                                                                                                                       
>> Success, response: OK, Success (0x20) |
>> | obex> get Wazzup.mp3
>> | Failure, response: Unautorized (0x41)
>> +-------------------------------------
>>
>> Should there be so many spaces and shouldn't there be line break before
>> "Success" ?
> 
> 
> i'm not really sure what do you mean. could you please provide a sample 
> of what you would like output to be?
> 
>> What about autocompletion, like in shell?
> 
> 
> autocompletion for the remote filenames would be tricky to do. directory 
> listing is required for that. not all devices support 'ls' command.
> 
>> What about unicode characters? My cell phones have czech localisation
>> and name of directories visible over OBEX are with czech characters,
>> coded in Unicode. Accessible for me with obexapp but in latin2 charset:
>>
>> obex> ls
>> Access    Owner    Group    Size       Modified         Name
>>           n/a      n/a      n/a        n/a              Obrázky/
>>           n/a      n/a      n/a        n/a              Zvuky/
>>           n/a      n/a      n/a        n/a              Schémata/
>>           n/a      n/a      n/a        n/a              Videosoubory/
>>           n/a      n/a      n/a        n/a              Jiné/
>> Success, response: OK, Success (0x20)
>> obex> cd Jiné
>> Failure, response: Not found (0x44)
>> obex> cd Jiné
>> Success, response: OK, Success (0x20)
> 
> 
> well, directory listing is a xml document. i just get it and parse/print 
> it with bsdxml(3). does your phone sets xml charset? (hint: use hcidump 
> to actually see xml :)
> 
> unicode input is a completely different beast. you actually have to 
> switch your console to unicode.
> 
>> It wanted to pair my cell phone on connect, obexapp-1.3 does not wanted
>> to pair.
> 
> 
> obexapp does not care about piring. if you want to authenticate incoming 
> connection on freebsd you have to use hccontrol(8). right now there is 
> no way to turn authentication on individual connections. its all or none.
> 
>> Otherwise it works very nice, big step forward in usability.
> 
> 
> thanks for feedback.
> 
> max
> 
> 
> _______________________________________________
> freebsd-bluetooth at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
> To unsubscribe, send any mail to 
> "freebsd-bluetooth-unsubscribe at freebsd.org"