Howard's ideas sound good to me. Perhaps we should: -- Dev talk...
Make a "QSCollectionObject" type object Set the primary types and actions correctly so that Search Contents is the default Add a simple initWith… method to make creating these objects easier On 2 July 2012 15:41, Howard Melman <[email protected]> wrote: > > On Jul 2, 2012, at 10:13 AM, Rob McBroom wrote: > > > On Jul 2, 2012, at 9:59 AM, Howard Melman wrote: > > > >> I see the distinction, I'm not sure it needs to be exposed to the user. > > > > Agree. I can’t think of a reason anyone needs to know they’re dealing > with one of these. > > > > Internally though, it might be nice to define a consistent “type” for > these so we can prevent actions from appearing that make no sense (or so > users could make “Search Contents” the default). > > Well, letting users make Search Contents the default action would exposing > it to the users. If that's the case then it should be done in the most > obvious way possible. Maybe that's just an object type in the actions prefs > or maybe there's a catalog collection somewhere. > > Howard > > -- You received this message because you are subscribed to the Google > Groups Quicksilver group. To post to this group, send email to > [email protected]. To unsubscribe from this group, > send email to [email protected]. For > more options, visit this group at > https://groups.google.com/d/forum/blacktree-quicksilver?hl=en > -- You received this message because you are subscribed to the Google Groups Quicksilver group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at https://groups.google.com/d/forum/blacktree-quicksilver?hl=en
