Subject: Re: [Bluez-devel] bluetooth filesystem integration
From: Charles Bueche <charles@bueche.ch>
To: bluez-devel@lists.sourceforge.net
In-Reply-To: <1127899931.5321.16.camel@localhost.localdomain>
References: <1127865130.15926.18.camel@panic>
	 <1127899309.14281.7.camel@bluez.bueche.ch>
	 <1127899931.5321.16.camel@localhost.localdomain>
Content-Type: text/plain
Message-Id: <1127906387.14254.27.camel@bluez.bueche.ch>
Mime-Version: 1.0
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Reply-To: bluez-devel@lists.sourceforge.net
Date: Wed, 28 Sep 2005 13:19:47 +0200

On mer, 2005-09-28 at 11:32 +0200, Marcel Holtmann wrote:
> Hi Charles,
> 
> > > So this post is basically to anounce btfs and to gether some ideas on
> > > what you guys think is need and useful.
> > 
> > That will be great, eg to automatically rsync new pictures taken from my
> > phone to a local dir. I know there is a kbluetoothd plugin, but
> > rsync/btfs seems much more "UNIX-like" to me.
> > 
> > What would be great is to see phone contacts as virtual VCard files (one
> > file per contact). Not sure if it is possible, but you asked for
> > ideas :-)
> > 
> > Seeing my Palm T5 agenda as iCal file would be the top... OK, I stop
> > dreaming :-/
> 
> do you have any thoughts how the directory structure of this filesystem
> should look like. Let's discuss how we design it.

not sure if my ideas make sense, as I don't know the internal of
bluez/btfs/devices. My view is from a user's point.

- first level : device name

- second level : the device's applications. Examples :
   - contacts
   - agenda
   - pictures
   - sd_card_1
   - etc

- third level : the files
   - read & write records from/to contact list
   - read & write events from/to calendar
   - read & write events from/to to-do
   - read pictures out of a camera/phone
   - read & write files to the "storage area" (eg mp3 to a SD card in a
Palm)

I don't know if it's deep enough, it's just a first thought.

some more ideas :

- attributes of files should make sense. Examples :
   - for events, they could reflect the event date instead of the event
creation date
   - for a mp3 file, they could be derived from the tag
   - for a contact, should be name_givenname.vcf (or configurable as
givenname_name.vcf for those reversed people :-)

Charles
-- 
Charles Bueche <charles@bueche.ch>
sand, snow, wave, wind and net -surfer


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel