From: Mike B. <mi...@ze...> - 2010-12-25 08:21:49
|
Over the next week I'll finally get around to finishing the implementation of eeze mount support (from the 1.1 branch) in e17 that I've been working on irregularly for some time. Given that eeze mounting is quite a bit more flexible than the mount functionality of other desktops, this gives us some potentially interesting options that I'd like to guage interest in: *network fs mounting (FUSE/NFS/etc) *other partition mounting (ie. anything not currently mounted) *disk image mounting Eeze 1.1 already supports all of the above through currently existing api calls, and so if these are features that we are interested in then I am willing to write all of the necessary backend eeze code to make it work. What I would need, however, is someone who knows the E widget api and whatnot to create the gui (can be done however you like, I can even write the eeze code to your specifications) since I have no knowledge of it and no desire to learn it at this moment. Some other possibly interesting features to consider/comment on based on eeze 1.1 functionality that people may not be aware of: *static disk properties - eeze is able to "track" all disks so that we can save properties for them *realtime *tab monitoring/parsing - eeze can be set to automatically track fstab and mtab, allowing the user to mount/unmount things based on any matching property (/sys/$path, /dev/$path, uuid, hardware info/type, filesystem, etc) which could be useful in apps such as enjoy to use for synchronizing external mp3 players *simple api for gathering disk infos which would be useful for an app that might, for instance, need to gather the specs of an attached digital camera. I'll probably bump this thread in a couple weeks for people who are on vacation since e17's release is some time off and these are some useful features that would make e shine (sshfs mounting remote disks on an embedded device anyone? :)) -- Mike Blumenkrantz Zentific: We run the three-legged race individually. |
From: Carsten H. (T. R. <ra...@ra...> - 2011-01-05 08:17:45
|
On Sat, 25 Dec 2010 03:21:39 -0500 Mike Blumenkrantz <mi...@ze...> said: as per irc - as long as its all at runtime (detecting hal vs udev) i'm happy :) as for network fs's - i wasnt thinking of being that ambitious for e17 - e18 maybe? (same as image mounting). > Over the next week I'll finally get around to finishing the implementation > of eeze mount support (from the 1.1 branch) in e17 that I've been working on > irregularly for some time. Given that eeze mounting is quite a bit more > flexible than the mount functionality of other desktops, this gives us some > potentially interesting options that I'd like to guage interest in: > > *network fs mounting (FUSE/NFS/etc) > *other partition mounting (ie. anything not currently mounted) > *disk image mounting > > Eeze 1.1 already supports all of the above through currently existing api > calls, and so if these are features that we are interested in then I am > willing to write all of the necessary backend eeze code to make it work. > What I would need, however, is someone who knows the E widget api and whatnot > to create the gui (can be done however you like, I can even write the eeze > code to your specifications) since I have no knowledge of it and no desire to > learn it at this moment. > > Some other possibly interesting features to consider/comment on based on eeze > 1.1 functionality that people may not be aware of: > > *static disk properties - eeze is able to "track" all disks so that > we can save properties for them > *realtime *tab monitoring/parsing - eeze can be set to automatically track > fstab and mtab, allowing the user to mount/unmount things based on any > matching property (/sys/$path, /dev/$path, uuid, hardware info/type, > filesystem, etc) which could be useful in apps such as enjoy to use for > synchronizing external mp3 players > *simple api for gathering disk infos which would be useful for an app that > might, for instance, need to gather the specs of an attached digital camera. > > > I'll probably bump this thread in a couple weeks for people who are on > vacation since e17's release is some time off and these are some useful > features that would make e shine (sshfs mounting remote disks on an embedded > device anyone? :)) > -- > Mike Blumenkrantz > Zentific: We run the three-legged race individually. > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |
From: Cedric B. <ced...@fr...> - 2011-01-06 01:26:54
|
On Sat, Dec 25, 2010 at 8:21 PM, Mike Blumenkrantz <mi...@ze...> wrote: > Over the next week I'll finally get around to finishing the implementation > of eeze mount support (from the 1.1 branch) in e17 that I've been working on > irregularly for some time. Given that eeze mounting is quite a bit more > flexible than the mount functionality of other desktops, this gives us some > potentially interesting options that I'd like to guage interest in: > > *network fs mounting (FUSE/NFS/etc) > *other partition mounting (ie. anything not currently mounted) > *disk image mounting > > Eeze 1.1 already supports all of the above through currently existing api calls, > and so if these are features that we are interested in then I am willing to > write all of the necessary backend eeze code to make it work. What I would > need, however, is someone who knows the E widget api and whatnot to create the > gui (can be done however you like, I can even write the eeze code to your > specifications) since I have no knowledge of it and no desire to learn it at > this moment. > > Some other possibly interesting features to consider/comment on based on eeze > 1.1 functionality that people may not be aware of: > > *static disk properties - eeze is able to "track" all disks so that > we can save properties for them > *realtime *tab monitoring/parsing - eeze can be set to automatically track > fstab and mtab, allowing the user to mount/unmount things based on any matching > property (/sys/$path, /dev/$path, uuid, hardware info/type, filesystem, etc) > which could be useful in apps such as enjoy to use for synchronizing external > mp3 players > *simple api for gathering disk infos which would be useful for an app that > might, for instance, need to gather the specs of an attached digital camera. > > > I'll probably bump this thread in a couple weeks for people who are on vacation > since e17's release is some time off and these are some useful features that > would make e shine (sshfs mounting remote disks on an embedded device > anyone? :)) I am still on vacation, but as i like this idea, I need to say something. What would be nice from eeze, is to just provide a call that transform an uri like ftp://somewhere.com/ to a local mounting point using fuse (of course everything with a callback to avoid lock). And yes your idea of simple watching api for apps, like enjoy or enki would be great for eeze 1.1. Write a TODO list somewhere :-) -- Cedric BAIL |
From: Mike B. <mi...@ze...> - 2011-01-06 01:46:59
|
On Thu, 6 Jan 2011 13:26:47 +1200 Cedric BAIL <ced...@fr...> wrote: > On Sat, Dec 25, 2010 at 8:21 PM, Mike Blumenkrantz <mi...@ze...> wrote: > > Over the next week I'll finally get around to finishing the implementation > > of eeze mount support (from the 1.1 branch) in e17 that I've been working on > > irregularly for some time. Given that eeze mounting is quite a bit more > > flexible than the mount functionality of other desktops, this gives us some > > potentially interesting options that I'd like to guage interest in: > > > > *network fs mounting (FUSE/NFS/etc) > > *other partition mounting (ie. anything not currently mounted) > > *disk image mounting > > > > Eeze 1.1 already supports all of the above through currently existing api > > calls, and so if these are features that we are interested in then I am > > willing to write all of the necessary backend eeze code to make it work. > > What I would need, however, is someone who knows the E widget api and > > whatnot to create the gui (can be done however you like, I can even write > > the eeze code to your specifications) since I have no knowledge of it and > > no desire to learn it at this moment. > > > > Some other possibly interesting features to consider/comment on based on > > eeze 1.1 functionality that people may not be aware of: > > > > *static disk properties - eeze is able to "track" all disks so that > > we can save properties for them > > *realtime *tab monitoring/parsing - eeze can be set to automatically track > > fstab and mtab, allowing the user to mount/unmount things based on any > > matching property (/sys/$path, /dev/$path, uuid, hardware info/type, > > filesystem, etc) which could be useful in apps such as enjoy to use for > > synchronizing external mp3 players > > *simple api for gathering disk infos which would be useful for an app that > > might, for instance, need to gather the specs of an attached digital camera. > > > > > > I'll probably bump this thread in a couple weeks for people who are on > > vacation since e17's release is some time off and these are some useful > > features that would make e shine (sshfs mounting remote disks on an > > embedded device anyone? :)) > > I am still on vacation, but as i like this idea, I need to say > something. What would be nice from eeze, is to just provide a call > that transform an uri like ftp://somewhere.com/ to a local mounting > point using fuse (of course everything with a callback to avoid lock). > And yes your idea of simple watching api for apps, like enjoy or enki > would be great for eeze 1.1. > Write a TODO list somewhere :-) Actually, as eeze 1.1 is about 90% feature/performance complete, nearly all of this is already implemented. The only thing that eeze 1.1 lacks are more mount options. Performing uri translation for fuse mounting as you mentioned is literally just a trivial matter of a strcmp and a couple lines. You can read more about eeze 1.1 here along with a fully functional demo mount app: http://trac.enlightenment.org/e/wiki/Eeze -- Mike Blumenkrantz Zentific: We run the three-legged race individually. |
From: Dave A. <da...@gu...> - 2011-01-10 16:51:59
|
I'm really interested in the network mount, to use in a mediacenter I'm writing. I will wait the release of eeze 1.1 to try it 'couse I have no time at the moment, and because my app is written in python and so I will also need to write eeze python bindings... Please keep up this great work :) I will also use eeze in the Places module as soon as you relese the 1.1 DaveMDS Il giorno sabato 25 dicembre 2010, Mike Blumenkrantz <mi...@ze...> ha scritto: > Over the next week I'll finally get around to finishing the implementation > of eeze mount support (from the 1.1 branch) in e17 that I've been working on > irregularly for some time. Given that eeze mounting is quite a bit more > flexible than the mount functionality of other desktops, this gives us some > potentially interesting options that I'd like to guage interest in: > > *network fs mounting (FUSE/NFS/etc) > *other partition mounting (ie. anything not currently mounted) > *disk image mounting > > Eeze 1.1 already supports all of the above through currently existing api calls, > and so if these are features that we are interested in then I am willing to > write all of the necessary backend eeze code to make it work. What I would > need, however, is someone who knows the E widget api and whatnot to create the > gui (can be done however you like, I can even write the eeze code to your > specifications) since I have no knowledge of it and no desire to learn it at > this moment. > > Some other possibly interesting features to consider/comment on based on eeze > 1.1 functionality that people may not be aware of: > > *static disk properties - eeze is able to "track" all disks so that > we can save properties for them > *realtime *tab monitoring/parsing - eeze can be set to automatically track > fstab and mtab, allowing the user to mount/unmount things based on any matching > property (/sys/$path, /dev/$path, uuid, hardware info/type, filesystem, etc) > which could be useful in apps such as enjoy to use for synchronizing external > mp3 players > *simple api for gathering disk infos which would be useful for an app that > might, for instance, need to gather the specs of an attached digital camera. > > > I'll probably bump this thread in a couple weeks for people who are on vacation > since e17's release is some time off and these are some useful features that > would make e shine (sshfs mounting remote disks on an embedded device > anyone? :)) > -- > Mike Blumenkrantz > Zentific: We run the three-legged race individually. > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > |
From: Mike B. <mi...@ze...> - 2011-01-10 19:20:55
|
On Mon, 10 Jan 2011 17:51:53 +0100 Dave Andreoli <da...@gu...> wrote: > I'm really interested in the network mount, to use in a mediacenter I'm > writing. I will wait the release of eeze 1.1 to try it 'couse > I have no time at the moment, and because my app is written in python > and so I will also need to write eeze python bindings... > Please keep up this great work :) > > I will also use eeze in the Places module as soon as you relese the 1.1 > > DaveMDS > > > Il giorno sabato 25 dicembre 2010, Mike Blumenkrantz > <mi...@ze...> ha scritto: > > Over the next week I'll finally get around to finishing the implementation > > of eeze mount support (from the 1.1 branch) in e17 that I've been working on > > irregularly for some time. Given that eeze mounting is quite a bit more > > flexible than the mount functionality of other desktops, this gives us some > > potentially interesting options that I'd like to guage interest in: > > > > *network fs mounting (FUSE/NFS/etc) > > *other partition mounting (ie. anything not currently mounted) > > *disk image mounting > > > > Eeze 1.1 already supports all of the above through currently existing api > > calls, and so if these are features that we are interested in then I am > > willing to write all of the necessary backend eeze code to make it work. > > What I would need, however, is someone who knows the E widget api and > > whatnot to create the gui (can be done however you like, I can even write > > the eeze code to your specifications) since I have no knowledge of it and > > no desire to learn it at this moment. > > > > Some other possibly interesting features to consider/comment on based on > > eeze 1.1 functionality that people may not be aware of: > > > > *static disk properties - eeze is able to "track" all disks so that > > we can save properties for them > > *realtime *tab monitoring/parsing - eeze can be set to automatically track > > fstab and mtab, allowing the user to mount/unmount things based on any > > matching property (/sys/$path, /dev/$path, uuid, hardware info/type, > > filesystem, etc) which could be useful in apps such as enjoy to use for > > synchronizing external mp3 players > > *simple api for gathering disk infos which would be useful for an app that > > might, for instance, need to gather the specs of an attached digital camera. > > > > > > I'll probably bump this thread in a couple weeks for people who are on > > vacation since e17's release is some time off and these are some useful > > features that would make e shine (sshfs mounting remote disks on an > > embedded device anyone? :)) > > -- > > Mike Blumenkrantz > > Zentific: We run the three-legged race individually. > > Check out my recent work in efm with udisks, you should probably integrate that into places module as well. -- Mike Blumenkrantz Zentific: NULL pointer dereferences now 50% off! |