Yes, I thought about that, however there are several subtle differences. BTW, I'm not thinking about a single use case, but how this extrapolates to multiple use cases over time.
1. Hierarchy. ----------------------- Tags are intended to show a hierarchy, playlists are flat. Yes, you could have a flat hierarchy with "Best of Year XXX" specifically for this purpose. However, this would pollute the other use of tags. Consider I use my tags as this tree - places - cuba - Jamaica - People - family - Canada - Europe - friends - Sports - Soccer - Volleyball So now, I'm expected to have my organized hierarchy mixed with arbitrary list of tags (examples below).... Nope. Too messy. - Best of 2000 - Best of 2001 - My photo album - My vacation slideshow - Things to print at Costco - ... 2. Static vs Dynamic. ----------------------- Tags are dynamic. Once you assign the tag, the equivalent of a search occurs every time you access a particular hiearchy tag. You could have a saved search that equated to each level of the tag hierarchy... could you not? 3. Metadata ----------------------- Tags are (or can be) written to metadata. A list of photos is not... plain and simple. When I get rid of a static playlist, all I do is delete it. When I get rid of your proposed top level tag, each photo must be augmented to remove said tag.... more work. 4. Temporary vs. Permanent ------------------------------------------- Tags are intended to be continually added to photos, rarely do they get deleted. Static Playlists can be more temporary. When done with the purpose of the static playlist, you simply delete it. Think of the "things to print at costco". 5. Ordering ----------------------- Any dynamic search is basically restricted to ordering by one of the available fields and 99% of the time is invariably by date. Static playlists should have the ability to order by manual ordering. Think of the slideshow... I want the ability to have the picture of grandma followed by grandpa, followed by x. 6. Association of other items ------------------------------------------ Say I want the slideshow to play specific music. Say I want that to be configurable per playlist and more than that, I want that to be a saved configuration. When I get to the hall to do my presentation, I just want to hit play instead of mucking around with settings there. Not sure how that would work with tags, but it seems like the static playlist is a natural fit here. Anyway... some food for thought. Thank You Lu Timdale [email protected] ----- Original Message ----- From: Bruno Girin <[email protected]> To: [email protected] Cc: Sent: Saturday, May 28, 2011 5:29:50 AM Subject: Re: [Shotwell] Saved Searches Rock Lu, Isn't your "static playlist" a tag? So if you create a "Best of 2011" tag and assign it to all the photos you want, you have your static list. Cheers, Bruno On Fri, 2011-05-27 at 18:38 -0700, Lu Timdale wrote: > Saved Searches: Wow what a great feature... brilliant. I love it. > > I have a couple of comments: > > 1. I think it would be easier to find and usable if you had the "Saved > Searches" top level folder visible by default with a + or add button beside > it. At the very least, the right click on saved searches should show "new > search" dropdown. That is the only place it seems that it doesn't do it > currently. > > > > 2. I can't help but think that they are akin to smart playlists in music > collection apps such as banshee. > On that train of thought... > Yes, we now have dynamic/smart playlist equivalents via "Saved Searches". > Yes, we have static playlist equivalents via > > - "events"... but this is only the primary organization structure. > - "flagged" list... but this is only one list and gets overwritten, so it's > temporary. > How about static playlist equivalents that are arbitrary in nature... > Collections/Slideshows/Stacks? > I have a use case in mind already. Every year, I put together a best of the > year or yearbook type collection manually. I hand pick these photos, so this > is not easily doable with a dynamic search. I think these static > collections are a bit different than tags btw, as tags typically (and will > hopefully soon) represent a hierarchy and are part of the metadata. These > collections would never be written out to the file in metadata. > > > > Keep up the very solid work gents. I am truly amazed at how far this app has > come in such a short time. > > No worries if you have thought of these points already and are secretly > planning to implement later. ;-) > > > Cheers. > > > > Lu Timdale > _______________________________________________ > Shotwell mailing list > [email protected] > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
