On Wed, Dec 22, 2010 at 23:40, Jason DeRose
<jderose@xxxxxxxxxxx> wrote:
On Wed, Dec 22, 2010 at 2:03 PM,
frederik.nnaji@xxxxxxxxx <frederik.nnaji@xxxxxxxxx> wrote:
Hi Jean, thanks for your thoughts on this!
On Wed, Dec 22, 2010 at 14:41, Jean Levasseur
<levasseur.jean@xxxxxxxxx> wrote:
2010/12/21 Frederik Nnaji
<frederik.nnaji@xxxxxxxxx>
On Sun, 2010-12-12 at 17:56 +0000, Chris Wilson wrote:
> Personally, if I were to click on a button labeled 'Photos and
> Videos', I would expect to find those files there rather than editors,
> etc.
[...] 2 things: first, there are good content management software for both music (rhythmbox, banshee) and photos (f-spot, shotwell) but none for videos. For videos, there are just players as far as I know.
Jason, would you like to say something at this point?
yeah! That's more like what i would expect to see after clicking on "Videos" in the Unity Dash.
When i select an object, its details appear in a sidepane, editable.
An object's representation is nothing but a proxy to the object itself. So a field labelled "Title" should be a proxy to the title itself, interacting with that field should be interacting with the title.
I miss this a lot in Shotwell..
Originally i was hoping such a context sidepane could be called and dismissed via F9 (for keyboard), as in Nautilus.
Perhaps that would still make sense?
And having search on the top-left would be consistent with Unity, i would so love seeing that.
But more generally, I'm hoping dmedia can help get this important user data (and metadata) out of application-specific silos. This fits well with the overall Ayatana focus on the "space between applications". For example, I'd like to see cool social features integrated with dmedia, which would allow this social use in any context, not just in the context of a single application (Banshee, Shotwell, etc).
social is all about sharing. sharing is all about people. if you get sharing and people integrated, you're social.
I think the use case Frederick brought up is ripe with possibility. The problem I see with *only* relying on domain specific manager apps is when the "stuff" you're looking for spans multiple domains. For example, I think Zeitgeist has clearly demonstrated the value of an aggregate chronological view. And I think that view needs to be more than just a list of recently accessed media files... we need the metadata too. With rich metadata (like what dmedia stores), we can be much smarted about how and what we present in a chronological view.
to me, everything that isn't the content itself or a scaled representation of it, is a backend.
In this way of thinking, dmedia would be the backend that affords the content in a useful manner to the user..
The Zeitgeist "backend" can help with chronology, frequency and recency and some IPC stuff, while dmedia focuses on delivering the appropriate format of information for the other clients to present.
Am i off track?
I think the content rather than application focus is a very exciting idea, Frederick. If you have ideas about specific metadata that would be needed for the use case you have in mind, I'd happily add it to dmedia.
* Places
..in this video
The words Geotagging or Geolocation are ugly, but it would be nice to have a way of adding a city, state, country, district, planet ;)
The most important thing about this is to autocomplete the user's entry, suggesting some known "Places". I mean real places, not GNOME Places.
* Autor
..of this video
In the case of videos this would have to be called "directed by" or so.. what do you suggest?
The ordinary desktop user will most certainly have more hollywood movies than selfmade recordings, i suppose.. but "directed by" is not generic enough, is it?
Perhaps movies should simply have "directed by", and selfmade recordings will have "recorded by" :D
* People
..in this video
This would be appropriate for both hollywood movies, selfmade recordings and downloaded clips from e.g. facebook, youtube or what have you.
Plus, dmedia is a *distributed* media library. We can provide an aggregate view into the user's content and activity across *all* their devices, which is pretty cool, IMHO. This bug is probably the best explanation of the core distributed features, the metadata we will store to enable it -
https://bugs.launchpad.net/dmedia/+bug/680467
I know banshee has a video library, and banshee being now the default music library software in Ubuntu it might as well serve as the default video player/manager in Ubuntu as well. Next, photo management software often offers several ways to modify their content, on the contrary of the other content management softwares that are just that: library management and player. That might be a reason people get confused when they access shotwell or f-spot: they think those are primarly photo editors rather than photo managers.
yes, i think you're right. people want to read their email, so they click on "Email", or any other icon that makes them believe they will find email by touching it.
Clicking is the next best thing to touching.
If you click "Music", and you're confronted with a couple of different apps, then something is wrong.
AIUI distributed will mean that dmedia is more about fetching info and presenting it in a "live" manner than managing metainformation via db I/O horror..
This is the current spirit of things, as it also is in libfolks. Great thinking, i'm happy to be having this conversation ;)